From: Jason Lunz <lunz@falooley.org>
To: Jeff Dike <jdike@addtoit.com>
Cc: linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/5] UML - Assign random MACs to interfaces if necessary
Date: Wed, 27 Sep 2006 15:33:43 -0400 [thread overview]
Message-ID: <20060927193135.GA13322@knob.reflex> (raw)
In-Reply-To: <200609271757.k8RHvmgj005727@ccure.user-mode-linux.org>
On Wed, Sep 27, 2006 at 01:57:47PM -0400, Jeff Dike wrote:
> Now, if there is no MAC from the command line, one is generated. We
> use the microseconds from gettimeofday (20 bits), plus the low 12
> bits of the pid to seed the random number generator. random() is
> called twice, with 16 bits of each result used. I didn't want to
> have to try to fill in 32 bits optimally given an arbitrary
> RAND_MAX, so I just assume that it is greater than 65536 and use 16
> bits of each random() return.
Why not use random_ether_addr() like dummy, tun, ifb and others?
Jason
prev parent reply other threads:[~2006-09-27 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 17:57 [PATCH 1/5] UML - Assign random MACs to interfaces if necessary Jeff Dike
2006-09-27 19:32 ` dhollis
2006-09-27 19:33 ` Jason Lunz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060927193135.GA13322@knob.reflex \
--to=lunz@falooley.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox