linux-kernel - Re: How does dummy network driver get its mac addresses?

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: <466D5A2E.3090307@intello.com>
Date:	Mon, 11 Jun 2007 10:20:30 -0400
From:	Mike Schmidt <mike@...ello.com>
To:	unlisted-recipients:; (no To-header on input)
Cc:	linux-kernel@...r.kernel.org
Subject: Re: How does dummy network driver get its mac addresses?

Thanks a lot for the responses I've received. I really appreciate the help.

Sorry about posting in the wrong mailing list. I'll pay more attention 
next time.

Mike

Stephen Hemminger wrote:
> On Fri, 08 Jun 2007 15:03:42 -0400
> Mike Schmidt <mike@...ello.com> wrote:
>
>   
>> please cc me directly with any responses - I am not (yet) a member of this mailing list.
>>
>> I just created 99 dummy network devices, and they all had different, random-looking addresses. I recently searched though all the IANA/IEEE documentation looking for a mechanism or policy to select local, virtual mac addresses that could not interfere with real ones. But there seems to be no clear concensus. Even the use of the 'local' bit seems to be inconsistent, I saw registered OUIs in the AA:... (from memory) range, for example. 
>>
>> I noticed that all the mac addresses assigned by the dummy driver have the 'local' bit set. For those who are wondering, that's the second least significant bit  in the first digit of the mac address: so all addresses that start with x2, x3, x6, x7, xA, xB, and xE, xF are 'local'. The last bit is the multicast bit.
>>
>> In the 2.4 kernels, these devices all received a 00:00:00... mac address, although this is declared incorrect in the RFCs I read. So, I was making my own, somewhat arbitrarily. In 2.6, this seems to be solved. Can anyone tell me what the algorithm/criteria are that allow the 2.6 kernels to set up random mac addresses without conflicting with real devices?
>>     
>
>
>   
>> I have searched the mailing list, but it's pretty hard to select for this kind of information. 
>>
>> Thanks very much. This is a great mailing list. It's been very responsive to me so far. I thank you all. 
>>     
>
>
> 1. Learn to read the kernel source.  dummy gets its addresses from
>    random_ether_addr()
>
> 2. Read the maintainers file, questions like this goto netdev@...r.kernel.org
>
>
>   

View attachment "mike.vcf" of type "text/x-vcard" (355 bytes)