Fix should be easy implement in create function with following add in:
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
May 17 2021
I can't reproduce it VyOS 1.3-rolling-202105011026
BFDd amybe creating those addresses automatically. In theory, it doesn't matter what they are as long as both ends have a way of learning them. I'm not sure if this is a general issue or an issue only with wireguard but right now bfd doesn't work with OSPFv3 over wireguard.
As WireGuard has bo MAC address a EUI64 link-local address is calculated artificially https://github.com/vyos/vyos-1x/blob/current/python/vyos/ifconfig/wireguard.py#L161
BTW, it appears ths fe80::... addresses used in bfd dialogue do not belong to any of the actual interfaces. It could be by design but this si something I discovered when trying to troubleshoot the session. This could also be the reason for mismatch between session ends if the other side does not know the peer address.
Attaching packet captures from both ends filered with bfd && ipv6.addr == fe80::/64 rule
I ran a packet capture on the session and It appears had been an issue with firewall settings on the provider site. It just happened that we hit a similar issue with two providers and VyOS was the common denominator but It appears to be red herring. Feel free to close.
May 16 2021
Hi @ernstjo got an idea how we should do it?
Thanks for the hint.
May 15 2021
It will be enough to add a quote here?
"\`"
A quick solution that convert JSON to config set
May 14 2021
Can be "cherry picked" to 1.3 and 1.2