I just tried that and it fails. We get
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
May 17 2021
Hmm, I still have it in my running-config. Is there a way to force config regeneration?
The "Time exceeded" likely means that message is sent to a black hole. There are two bfd sessions running through the same tunnel - one for OSPF and the other for OSPFv3. Timeout settings are the same and the first one is established instantly and is running happily. The OSPFv3 one is not so much:
did you try
set protocols static table 1 route 0.0.0.0/0 interface 'eth1'
Iproute2 is too old and needs a newer version. So, we have to upgrade that package.
Even I also faced this error while upgrading the server from 1.2.7 to the latest rolling release.
Time Exceeded (3)
PR for current https://github.com/vyos/vyos-1x/pull/844
PR for Equuleus https://github.com/vyos/vyatta-cfg-quagga/pull/78
Fix should be easy implement in create function with following add in:
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