Dear Janne, traceroute6 -I ipv6.google.com traceroute6 to ipv6.l.google.com (2a00:1450:4001:81b::200e), 64 hops max, 60 byte packets 1 2a03:4000:24::3 (2a03:4000:24::3) 0.384 ms 0.558 ms 0.563 ms 2 2a00:11c0:47:3::20 (2a00:11c0:47:3::20) 0.887 ms 0.545 ms 0.421 ms 3 2a00:11c0:47:1:47::141 (2a00:11c0:47:1:47::141) 4.227 ms 3.486 ms 3.574 ms 4 2001:4860:1:1::6bc (2001:4860:1:1::6bc) 6.794 ms 5.098 ms 3.559 ms 5 2001:4860:0:11df::1 (2001:4860:0:11df::1) 4.243 ms 3.825 ms 3.843 ms 6 2001:4860:0:1::671 (2001:4860:0:1::671) 4.169 ms 3.866 ms 3.856 ms 7 fra15s16-in-x0e.1e100.net (2a00:1450:4001:81b::200e) 3.776 ms 3.889 ms 3.867 ms
OpenBSD is learning the default route fe80:1%vio0 by NDP, so even without configure it as gateway will be used. And using somethings next hop is gw is not working either route add -inet6 default 2a03:4000:24::3 add net default: gateway 2a03:4000:24::3: Network is unreachable I have opened a ticket with NETcup … hopefully they will check. -Kay-Uwe > On 06 Aug 2020, at 16:10, Janne Johansson <icepic...@gmail.com> wrote: > > No, I think in my case it is Juniper multichassis LAG (link aggregation > groups) getting confused by identical fe80::x for multiple local v6 > networks, or something to that effect. > > How does the traceroute6's look when it "works"? If you get a "real" v6 > there you might (ab)use that as the gw ip? > >> On 06 Aug 2020, at 16:04, kug1977 <kug1...@web.de> wrote: >> >> Unfortuanatly, the Provider netcup doesn’t give out IPv6 gw address >> configuration other than fe80::1, so I cannot check these. But all >> virtualization there is based on KVM, too. So I guess the issue is with KVM? >>
signature.asc
Description: Message signed with OpenPGP using GPGMail
