On Sat, Jun 10, 2023 at 6:04 AM Martin-Éric Racine
wrote:
>
> On Fri, 7 Oct 2022 22:34:17 +0200 Santiago Garcia Mantinan
> wrote:
> > > The kernel using the MAC of a real device, if none is specified, is
> > > precisely what we wanna avoid. Systemd is not involed.
> >
> > Like I said, if we
On Fri, 7 Oct 2022 22:34:17 +0200 Santiago Garcia Mantinan
wrote:
> > The kernel using the MAC of a real device, if none is specified, is
> > precisely what we wanna avoid. Systemd is not involed.
>
> Like I said, if we don't specify the mac address systemd will set up a fake
> one for us, so...
> The kernel using the MAC of a real device, if none is specified, is
> precisely what we wanna avoid. Systemd is not involed.
Like I said, if we don't specify the mac address systemd will set up a fake
one for us, so... systemd is involved and the kernel is not allowed to use a
real one, that's
On Fri, Oct 7, 2022 at 1:01 AM Santiago Garcia Mantinan
wrote:
> > It would be desirable for bridge_hw to be able to generate a random MAC
> > address as per ifupdown's generic hwaddress syntax.
>
> I don't know if I get this right or not... if you don't want to specify a
> MAC or get it from an
Hi!
> It would be desirable for bridge_hw to be able to generate a random MAC
> address as per ifupdown's generic hwaddress syntax.
I don't know if I get this right or not... if you don't want to specify a
MAC or get it from an interface... then you better not assign any MAC and so
systemd will
Package: bridge-utils
Version: 1.7-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
It would be desirable for bridge_hw to be able to generate a random MAC address
as per ifupdown's generic hwaddress syntax.
Possible values for bridge_hw would thereafter be:
MAC
interface
6 matches
Mail list logo
