I HAVE set bridge_hw to a static device. That's what I described. Martin-Éric
la 30. tammik. 2021 klo 14.13 Santiago Garcia Mantinan ([email protected]) kirjoitti: > > Hi again! > > > What I DO notice is that because the bridge is stupid enough to use the > > MAC address of a removable device to build the EUI64 address for fe80 > > local link (despite bridge_hw specifying the MAC address of a fixed > > device), disconnecting that removable device collapses the bridge. > > I've just done an IPv6 setup just to be able to debug the problems that I've > been reported on bridge-utils, so let's see what I have... > > 1: lo: ... > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state > UP group default qlen 1000 > link/ether 00:23:88:7c:cd:11 brd ff:ff:ff:ff:ff:ff > 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 > state UP group default qlen 1000 > link/ether 00:ea:cd:26:fc:e4 brd ff:ff:ff:ff:ff:ff > 4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP > group default qlen 1000 > link/ether 00:ea:cd:26:fc:e4 brd ff:ff:ff:ff:ff:ff > inet 192.168.1.222/24 brd 192.168.1.255 scope global br0 > valid_lft forever preferred_lft forever > inet6 2001:X:X:X:2ea:cdff:fe26:fce4/64 scope global dynamic mngtmpaddr > valid_lft 85748sec preferred_lft 13748sec > inet6 fe80::2ea:cdff:fe26:fce4/64 scope link > valid_lft forever preferred_lft forever > > You can see here that I'm using the MAC address from the wlan0 on the bridge > instead of the address of the ethernet which is lower and which in older > kernels would be automatically assigned to it, on current (5.10) kernel the > MAC address of the bridge would be completelly made up (like it was reported > on #980505), but that's not the case because I'm using the new overloadinf > of bridge_hw we did for #966244 available since bridge-utils 1.6-5, I have > specified "bridge_hw wlan0". > > Getting back to your problem... if you have a device that is not hot > pluggable on the bridge, I'd set up bridge_hw to that device, that way you > won't get any MAC or any IPv6 address from the hotplugged devices, like you > can see on my example, the only place where the mac of the ethernet MAC is > used is on the ethernet MAC address, the rest is taken from wlan0's MAC. > > I'd suggest you try this, but I don't think it will make any difference. I > mean try it, but I believe the problem is not related to the addresses or > anything related to the networking code but to the driver doing weird things > when the card is unplugged and not what it should, and that is causing the > problems. > > I have at work and at home usb network cards and never had any problem like > the one you are experiencing here, I'm not plugging them in and out all the > time, but I do it from time to time and I've had no problems at all, that's > why I think the driver may be the difference here. > > Try the bridge_hw thing set to the static device and let me know how it > went. > > Regards... > > -- > Manty/BestiaTester -> http://manty.net
