Hi!
> Here's what I've found so far. > https://askubuntu.com/questions/460405/ipv6-does-not-work-over-bridge Ok, I see the problem the guy has but I don't get a clear setup definition, also that was a long long time ago. > This answer suggests that it's IGMP snooping *not* STP that is the > problem. The problem we used to have was a behaviour of the kernel. Because of this bug and other bugs I have setup IPv6 all over my network at home, so right now I have... Laptop ---- workstation ---- server ----- router Where the laptop has a wifi card bridged to the ethernet that connects to one of the ethernets of the workstation (without stp) The which runs a bridge between its two ethernets with stp on and that bridges the laptop to the server network. Server is a Pi3 which also has a bridge with the wifi and a ethernet card and then another ethernet routing this bridged net to the internet. The server is stablishing a tunnel to HE ipv6 network over the router's net and then maps the /64 net that HE assigns to the local network, i.e. it's wifi+ethernet bridge which then goes to a switch and from there to the workstation and the laptop. All of these machines can communicate perfectly over the link-local network and also to the internet using IPv6. So... as far as my tests go... what this bug needs and also looks like some other bugs are pointing in this direction is... Changing the documentation. If there is a setup that is not working with current tooling we can discuss it, but if not... please stick to the documentation part, which seems to be causing panic and/or trouble. So... we have the NEWS that I have written lately, which seems to alarm people, I don't know if by current policy we can change what is written, but I don't see any problem with that if we can make this text look clearer and less frightening. Then we have the bridge-utils-interfaces wich documents old bugs and also seems to frighten people when they read the bridge_hw option, maybe I should remove all that and just state that everything works ok and that this option is a must if MAC address means something for your network, then maybe pointing to the old bugs for further reading, or even not? An then we have the README.Debian which maybe needs some more stuff added. Maybe we can agree if this is all that is needed and some native English speaker can write up the changes for me to implement? If there is some problem with a setup that is not working... can we open a bug reflecting the setup? I guess that's all on my side, you guys have filed a lot of bugs lately, just before the freeze, and that is not a good timing at all, let's see if we can agree on what is needed and make it into shape and time for Bullseye. Thanks for the reports, regards... -- Manty/BestiaTester -> http://manty.net
