Remove IPv6 routes for bond slaves and bridge ports
Hello,
Right now, with NetworkManager 1.18.0, when a device is enslaved to a bridge or becomes a bond's slave, any existing IPv6 routes using it are not removed. That leads to situations where the device is not accessible for networks for those routes (probably because the kernel tries to send the response using the bridge port or the bond slave, which does not work). Removing those routes solves this issue. (Real world issue I just had and solved as described). It is possible that for some reason, these routes are installed after the device already became a port or a slave to a bond. If that is the case, then there's obviously a new or different problem here as well.
Maybe the link-local addresses for those ports and slaves should be removed, too, but I have yet to see any negative impact from having them.
Kind regards
Thermi