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.

Hi @ernstjo got an idea how we should do it?

Thanks for the hint.

It will be enough to add a quote here?

"\`"

https://github.com/vyos/vyatta-cfg/blob/fa2b172512aa024a9853166528c9e6601fde94d8/src/cli_new.c#L1886-L1888

A quick solution that convert JSON to config set

Can be "cherry picked" to 1.3 and 1.2

PR https://github.com/vyos/vyatta-op-vpn/pull/27

Did you read the error description? It doesn't look like.

Well yeah kinda :) The driver VYOS is using is reporting wrong information to ethtool about autoneg support. No idea if it's fixed in a newer driver. Can't really play around much and I only have this type of nic in a single server. Let's hope someone comes along later with a X710 and can try more.

@Dmitry I can't reproduce it anymore VyOS 1.2.7

vyos@r2-lts:~$ touch tttt.txt
vyos@r2-lts:~$ ls
1.txt  foo.txt  ntp.conf  ntp.conf.2021-05-13-1945.pre-migration  ntp.conf.2021-05-13-2107.pre-migration  test.py  test.txt  tttt.txt  [email protected]
vyos@r2-lts:~$ 
vyos@r2-lts:~$ reset vpn remote-access user 
Possible completions:
  <text>        Terminate specified user's current remote access VPN session(s)

Default value https://github.com/vyos/vyatta-conntrack-sync/blob/7a8827e0d72cf771b0551915d738abe4838c0915/templates-cfg/service/conntrack-sync/mcast-group/node.def#L2

PR https://github.com/vyos/vyos-1x/pull/840
Can be "cherry-picked" to "equuleus" and "crux"

vyos@r6-roll# load ntp.conf
Loading configuration from 'ntp.conf'
Load complete. Use 'commit' to make changes effective.
[edit]
vyos@r6-roll#

Well then somehow this feels to me NIC related as I can not see it here.

Yes. Tried before posting the above comment.

I tried reproducing this issue on VyOS 1.3.0-rc4 but I see no link flaps on my IGB card connected to a Cisco Catalyst 1000.

upd. on vyos-1.4-rolling-202105051111 it's still there eve after reboot

PR: https://github.com/vyos/vyos-1x/pull/838

Hi. Tried it (IPv4) on vyos-1.4-rolling-202103251004 in eve-ng
It reacts to set protocols static route 0.0.0.0/0 next-hop 195.7.0.102
After reboot it's still there
Screens added. It shows static route

Please use the following op-mode command to check: