linux-kernel - Re: nic enumeration

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <AANLkTilc6DkjD3Jzqv51t1ohzzxgLqvBZnP4ij3GKekB@mail.gmail.com>
Date:	Mon, 12 Jul 2010 11:27:33 -0700
From:	Steve Fink <sphink@...il.com>
To:	"Loke, Chetan" <Chetan.Loke@...scout.com>
Cc:	Florian Weimer <fweimer@....de>, linux-net@...r.kernel.org,
	Matt Domsch <Matt_Domsch@...l.com>,
	Michael Di Domenico <mdidomenico4@...il.com>,
	linux-kernel@...r.kernel.org, kay.sievers@...y.org
Subject: Re: nic enumeration

>> I only partially understand your problem, but I am still wondering if
>> my bridge idea would work for you. (Preferably combined with udev
>> rules or whatever so the bridges are unnecessary after the next
>> reboot.)
>
> Why a bridge? Just to get around naming issues?

Yes. I wasn't claiming it was a *good* way to fix it. Just wondering
if it would work.

I have no idea whether it makes sense or not, not really knowing much
about this stuff myself. I tried it on my workstation. It's a good way
to kick yourself off the network. But it does work in the simplest
possible case, if you fix up routing afterwards. I don't know whether
bridges can be usefully used by VMs.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/