Hi

On 2016-02-13, Stefan Lippers-Hollmann wrote:
[...]
> $ ip -6 r
> 2001:470:1234:10::/64 dev br0  proto ra  metric 1024  pref medium
> 2001:470:1234:10::/64 dev enp2s0  proto ra  metric 1024  pref medium
> 2001:470:1234:10::/64 dev br1  proto ra  metric 1024  pref medium
> 2001:470:1234:10::/64 dev enp4s0  proto ra  metric 1024  pref medium
> fd01:470:1234:10::/64 dev br0  proto ra  metric 1024  pref medium
> fd01:470:1234:10::/64 dev enp2s0  proto ra  metric 1024  pref medium
> fd01:470:1234:10::/64 dev br1  proto ra  metric 1024  pref medium
> fd01:470:1234:10::/64 dev enp4s0  proto ra  metric 1024  pref medium
> fe80::/64 dev enp2s0  proto kernel  metric 256  pref medium
> fe80::/64 dev br0  proto kernel  metric 256  pref medium
> fe80::/64 dev enp4s0  proto kernel  metric 256  pref medium
> fe80::/64 dev br1  proto kernel  metric 256  pref medium
> default via fe80::92f6:52ff:fef6:c88 dev br0  proto ra  metric 1024  pref 
> medium
> default via fe80::92f6:52ff:fef6:c88 dev enp2s0  proto ra  metric 1024  pref 
> medium
> default via fe80::92f6:52ff:fef6:c88 dev br1  proto ra  metric 1024  pref 
> medium
> default via fe80::92f6:52ff:fef6:c88 dev enp4s0  proto ra  metric 1024  pref 
> medium

Apparently I can work around this problem by explicitly disabling
IPv6AcceptRouterAdvertisements for enp2s0 and enp4s0:

$ cat /etc/systemd/network/51-enp2s0.network 
[Match]
Name=enp2s0

[Network]
Bridge=br0
IPv6AcceptRouterAdvertisements=no

$ cat /etc/systemd/network/51-enp4s0.network 
[Match]
Name=enp4s0

[Network]
Bridge=br1
IPv6AcceptRouterAdvertisements=no

$ ip -6 r
2001:470:1234:10::/64 dev br0  proto ra  metric 1024  pref medium
fd01:470:1234:10::/64 dev br0  proto ra  metric 1024  pref medium
fe80::/64 dev br0  proto kernel  metric 256  pref medium
fe80::/64 dev br1  proto kernel  metric 256  pref medium
fe80::/64 dev enp2s0  proto kernel  metric 256  pref medium
fe80::/64 dev enp4s0  proto kernel  metric 256  pref medium
default via fe80::92f6:52ff:fef6:c88 dev br0  proto ra  metric 1024  pref medium

But it does feel weird having to do this explicitly for a lower bridge
member (and yes, I'm also slightly surprised about the (fe80::/64
routes for enp2s0 and enp4s0, but this isn't new).

Regards
        Stefan Lippers-Hollmann

Attachment: pgp3AvEFOvkFh.pgp
Description: Digitale Signatur von OpenPGP

Reply via email to