Le 06/01/2019 à 19:59, Rainer Dorsch a écrit :
Am Sonntag, 6. Januar 2019, 19:32:46 CET schrieb Ulf Volmer:I'm confused that you have uplink and downlink addresses configured on the client. Anyway, can you also post 'ip -6 r' from the client?I have not explicitly configured the addresses, but I have a dnsmasq running on the server which might be responsible for that, though I do not see how, I have in dnsmasq.conf
(...)
rd@mohot:~$ ip -6 r 2a02:8070:898f:e400::/64 dev eth0 proto kernel metric 256 pref medium 2a02:8070:898f:e4f8::/64 dev eth0 proto kernel metric 256 pref medium 2a02:8070:898f:e4f8::/62 dev eth0 proto kernel metric 256 pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium default via fe80::d263:b4ff:fe00:325c dev eth0 proto ra metric 1024 hoplimit 64 pref medium default via fe80::e228:6dff:fe43:5776 dev eth0 proto ra metric 1024 hoplimit 255 pref medium rd@mohot:~$ I do not understand why there is fe80::e228:6dff:fe43:5776. This is the link local address of the ISP router, which does not make sense (?).
Either dnsmasq is doing something nasty, or something else is leaking RA's from upstream to downstream. Could it be your VLAN setup ?
but even if I delete entry, I do not get it working:
You need at least to delete the bogus upstream address too.You should start with a fully static setup on the host, fix routing, and when done you can try to setup SLAAC/DHCPv6.