Adding a fixed link-local address to the router and using that as gateway works fine.
Thanks for the detailed explanation, - Milan On 9/28/20 12:32 PM, Robert Elz wrote: > Date: Mon, 28 Sep 2020 10:20:31 +0200 > From: =?UTF-8?Q?Milan_P=c3=a4ssler?= <[email protected]> > Message-ID: <[email protected]> > > | -bash-5.0$ cat /etc/route.conf > | inet 195.39.247.8 -static -link -iface vioif0 > | inet default 195.39.247.8 > | inet6 2a0f:4ac0::8 -static -link -iface vioif0 > | inet6 default 2a0f:4ac0::8 > > For IPv6 the router address should be the link local address of the > router (wherever you want your host to send packets for other than > directly attached links, or other known routes) - it needs to be > something that you can send to directly (kind of obviously, as its > job is to forward to other destinations). > > The way you have it configured, your host has no idea how to send to > the 2a0f:4ac0::8 address, the only v6 addr it knows about is > inet6 2a0f:4ac0::17 prefixlen 128 alias and the /128 means that > that one address is the only one expected to exist on that link. > > There's no way to work out how to get to the router's IP v6 addr. > > Whatever reasons you think there are for your v6 config, you'll find > things work mush better if you configure things the way that the network > was always intended to be configured (which means having a separate > prefix for each link). IPv4 ran out of addresses and has had to be > totally mangled to keep workable - don't copy the nightmares that have > been inflicted upon it into v6, where there is no need. > > This doesn't mean that you need to use stateless autoconfig, v6 always > intended to allow that, and DHCP, and static config, as addr assignment > methods - you can use whatever of those works best for you, but the > network configured should be configured like a correct IP network once > all the addresses and routes are assigned, however that is achieved. > > kre >
