On 2020-08-06 09:51, Janne Johansson wrote: > I have a setup where the virtualization (KVM) combined with the networking > does present a IPv6 def-gw as both an fe80::<predictable number here> and > the more normal 2001:a:b:c:d::1/64 and where the 2001-v6 ip works far > better on virtual machines due to redundancy mac sync things on the network > side, and since the ndp list showed the fe80::1 had a VRRP/CARP-lookalike > mac, it could be the same. > > In my case both bsd and linux IPv6-using VMs suffer from ndp "drops" where > it can take seconds for the discovery to figure the mac address out again > after a drop. > > So if you can divine what the "real" v6 ip is of the default-gw, try > setting this hard in the conf or /etc/mygate and retry v6. > > > Den tors 6 aug. 2020 kl 14:46 skrev Matthias Schmidt <open...@xosc.org>: > >> Hi, >> >> * kug1977 wrote: >>> >>> Is this something wrong configured on OpenBSD server or is this something >>> the provider has to check on the gateway side? >> >> I also have a VM at the exact same provider (netcup) and face >> the same problem. Since all of my VMs at different providers are >> identical (base install + conf via ansible) and I don't see the issue at >> other providers (IONOS, Hetzner) I suspect it has nothing to do with >> OpenBSD...
The best option I know of is to add a static, permanent NDP entry with ndp(8) entry before bringing up the interface. This works even if the peer does not respond to NDP at all. Sincerely, Demi
signature.asc
Description: OpenPGP digital signature
