From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: "Brock, Anthony - NET" <Anthony.Brock@oregonstate.edu>
Subject: Re: [uml-devel] Randomize on MAC address when bringing up ethernet iface
Date: Thu, 1 Jun 2006 10:46:20 +0200 [thread overview]
Message-ID: <200606011046.20338.blaisorblade@yahoo.it> (raw)
In-Reply-To: <7B4268E5ACB878429B58D4BE5B780E83010B6896@NWS-EXCH2.nws.oregonstate.edu>
On Wednesday 31 May 2006 23:22, Brock, Anthony - NET wrote:
> > -----Original Message-----
> >
> > On Tue, May 30, 2006 at 08:12:59PM +0200, Blaisorblade wrote:
> > > I've being thinking to this and I'm wondering why we
> >
> > shouldn't do it. When we
> >
> > > have set no IP or 0.0.0.0, which is not a unique IP, and we
> >
> > bring it up, we
> >
> > > should choose a random MAC to use.
> > > Conditions: the broadcast bit must be 0 and the
> >
> > "locally-assigned address
> >
> > > flag" must be 1 (as likely we already do).
> >
> > Yeah, this sounds like a good idea.
> This sounds good to me, provided we can still override on the
> command-line. I like having the flexibility of knowing what MAC address
> a guest will have before the instance is launched.
For sure.
I've thought to add a check that the address is a
http://en.wikipedia.org/wiki/Locally_Administered_Address
But I think the Linux network stack doesn't enforce that (inside the guest you
can violate the rule with ifconfig) so it wouldn't make sense to enforce it
ourselves.
We should add a warning though, for the user who cares and who didn't want to
break rules.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2006-06-01 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 21:22 [uml-devel] Randomize on MAC address when bringing up ethernet iface Brock, Anthony - NET
2006-06-01 8:46 ` Blaisorblade [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-30 18:12 Blaisorblade
2006-05-31 19:05 ` Jeff Dike
2006-06-01 8:40 ` Blaisorblade
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=200606011046.20338.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=Anthony.Brock@oregonstate.edu \
--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