su 21. helmik. 2021 klo 1.34 Santiago Garcia Mantinan
(ma...@debian.org) kirjoitti:
> > iface br0 inet dhcp
> > bridge_hw enp4s0MAC
> > bridge_ports regex (en|wl).*
> > post-up ifup /wl*
> > iface br0 inet6 auto
> > privext 2
> >
> > iface enp3s0 inet manual
> > iface enp4s0 inet ma
> We wouldn't need hwaddress anymore with the new patch, right?
Nope, I have found another problem with the kind of setup that you have, on
this setups brctl addif fails because the interface needs to be configured
by hostapd, and as the code for setting the mac was conditionally tight to
the brct
pe 19. helmik. 2021 klo 16.22 Santiago Garcia Mantinan
(ma...@manty.net) kirjoitti:
>
> > > auto br0
> > > iface br0 inet dhcp
> > > hwaddress enp4s0mac
> > > bridge_hw enp4s0mac
> > > bridge_ports regex (en|wl).*
>
> > That would fail to raise enp4s0, and it also still has
> > auto br0
> > iface br0 inet dhcp
> > hwaddress enp4s0mac
> > bridge_hw enp4s0mac
> > bridge_ports regex (en|wl).*
> That would fail to raise enp4s0, and it also still has hwaddress. I
Wel... isn't enp4s0mac a fixed ethernet port? if it is it should be
available on boot
to 18. helmik. 2021 klo 1.41 Santiago Garcia Mantinan
(ma...@debian.org) kirjoitti:
>
> > > > Btw, the discrepancy in behavior explained in Bug#980752 remains. With
> > > The problem is with neither, I believe.
> > Oh? What would cause this then?
>
> Like I have explained to you in other bugs, I co
> > > Btw, the discrepancy in behavior explained in Bug#980752 remains. With
> > The problem is with neither, I believe.
> Oh? What would cause this then?
Like I have explained to you in other bugs, I could replicate the problem
and found that it was a problem with bridge-utils, I have assigned #9
> Was there any particular reason for not enabling hotplug out of the box?
This was like that to preserve things working like they used to (some years
ago, when we introduced hotplug)
> Btw, the discrepancy in behavior explained in Bug#980752 remains. With
> BRIDGE_HOTPLUG=yes, upon startup, th
la 30. tammik. 2021 klo 19.32 Santiago Garcia Mantinan
(ma...@manty.net) kirjoitti:
>
> > Was there any particular reason for not enabling hotplug out of the box?
>
> This was like that to preserve things working like they used to (some years
> ago, when we introduced hotplug)
Hmm...
> > Btw, the
la 30. tammik. 2021 klo 17.42 Santiago Garcia Mantinan
(ma...@debian.org) kirjoitti:
> BTW: one thing I do on this kind of hotplug setup is allow hotplug on
> bridge-utils, which means setting it to yes on /etc/default/bridge-utils
> This allows me to plug in and out ethernet devices without needin
> > What I need to be able to replicate this is more info on your setup, I mean,
> > I need your network/interfaces (you can change macs and IPs of course) and
> > the "ip a" output with everything plugged and up like you have it setup and
> > then the same but without hwaddress applied (I'm suppos
la 30. tammik. 2021 klo 14.46 Santiago Garcia Mantinan
(ma...@debian.org) kirjoitti:
>
> > On a host with a mixture of USB WiFi dongles and Ethernet cards, I have to
> > specify the MAC address using both bridge_hw and ifup's generic hwaddress
> > to ensure that the host fetches the correct IP addr
> On a host with a mixture of USB WiFi dongles and Ethernet cards, I have to
> specify the MAC address using both bridge_hw and ifup's generic hwaddress
> to ensure that the host fetches the correct IP address via DHCP.
> Nonetheless, the bridge picks up the IPv6 EUI64 local link (fe80) of one
> o
Package: bridge-utils
Version: 1.6-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On a host with a mixture of USB WiFi dongles and Ethernet cards, I have to
specify the MAC address using both bridge_hw and ifup's generic hwaddress to
ensure that the host fetches the corre
13 matches
Mail list logo
