ke 24. helmik. 2021 klo 21.04 Guus Sliepen (g...@debian.org) kirjoitti:
>
> On Wed, Feb 24, 2021 at 03:04:18PM +0100, Santiago Garcia Mantinan wrote:
>
> > > Looking at the debdiff, I notice that upstream considers this package
> > > as deprecated and recommends using the 'bridge' command from ipro
On Wed, Feb 24, 2021 at 03:04:18PM +0100, Santiago Garcia Mantinan wrote:
> > Looking at the debdiff, I notice that upstream considers this package
> > as deprecated and recommends using the 'bridge' command from iproute2.
> > Is there any plan to migrate bridge-utils-interfaces to use this?
>
>
> Looking at the debdiff, I notice that upstream considers this package
> as deprecated and recommends using the 'bridge' command from iproute2.
> Is there any plan to migrate bridge-utils-interfaces to use this?
Well, kind of, I mean, on some of the bugs, at least on #868220, we've
have talked ab
ke 24. helmik. 2021 klo 12.03 Santiago Garcia Mantinan
(ma...@debian.org) kirjoitti:
>
> > Noted. There's indeed too many patches for me to keep track of. At
> > some point, I lose track of what you need to validate each one.
>
> Well, after some more testing I uploaded the latest versions to unsta
> Noted. There's indeed too many patches for me to keep track of. At
> some point, I lose track of what you need to validate each one.
Well, after some more testing I uploaded the latest versions to unstable, so
you don't need to access salsa as unstable is now in sync with the git
repository.
I'
ti 23. helmik. 2021 klo 15.18 Santiago Garcia Mantinan
(ma...@debian.org) kirjoitti:
>
> > Like I have just said on the other bug report (looks like we have the same
> > setup on both bugs) I need to know how the system looks after the setup to
> > find what is wrong or different to mine here, "ip
> Like I have just said on the other bug report (looks like we have the same
> setup on both bugs) I need to know how the system looks after the setup to
> find what is wrong or different to mine here, "ip a" output would solve some
> of my doubts.
I don't know if you could test all the patches I
> I HAVE set bridge_hw to a static device. That's what I described.
Like I have just said on the other bug report (looks like we have the same
setup on both bugs) I need to know how the system looks after the setup to
find what is wrong or different to mine here, "ip a" output would solve some
of
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
(ma...@debian.org) 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 b
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'
Package: bridge-utils
Version: 1.6-5+b1
Followup-For: Bug #979963
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I wouldn't know whether it's because of the kernel driver or because of
bridge-utils.
What I DO notice is that because the bridge is stupid enough to use the MAC
address of a remov
> Whenever I need to perform maintenance at the console, I have to remove the
> USB dongles, because their casings are wide enough to prevent access to the
> VGA connector. Removing the USB dongles tends to collapse the bridge.
> Restoring the bridge requires issuing the "sudo invoke-rc.d networ
Package: bridge-utils
Version: 1.6-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
My router bridges 2 Ethernet cards and a couple of USB dongles configured as
WiFi hostspots with hostapd.
Whenever I need to perform maintenance at the console, I have to remove the USB
don
13 matches
Mail list logo
