From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Rob Landley <rob@landley.net>
Subject: Re: [uml-devel] Test for ethernet broadcast address?
Date: Wed, 9 Nov 2005 02:44:52 +0100 [thread overview]
Message-ID: <200511090244.52916.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200511081913.14657.rob@landley.net>
On Wednesday 09 November 2005 02:13, Rob Landley wrote:
> So I'm trying to play with ifenslave under UML, and my naieve attempt to go
>
> ./linux LD_ASSUME_KERNEL=2.4.1 eth0=daemon,11:11:11:11:11:11 \
> eth1=daemon,22:22:22:22:22:22 rootfstype=hostfs rw init=/bin/sh
>
> Led to unexpected results that eth0 had a mac addr of 00:00:00:00:00:00.
> Eventually, I tracked it down to this test in arch/um/drivers/net_kern.c:
> if(addr[0] & 1){
> printk(KERN_ERR
> "Attempt to assign a broadcast ethernet address to a "
> "device disallowed\n");
> return(0);
> }
>
> My question is: where's the spec for what is and isn't a broadcast address?
Don't know what Jeff means, but he and UML consistently says "first byte odd
<-> broadcast". That's even coded above.
Don't ask me what exaclty he means. ^H^H^H^H
Ouch, I have the vice to understand things. So I went to the RFC, I spent
enough time on them, and I understood they're not the Ethernet specification
(the real spec is the DIX one, and later IEEE ones).
They're way too short!
But quoting from your link to ethereal's wiki:
"A destination MAC address of ff:ff:ff:ff:ff:ff indicates a Broadcast, meaning
the packet is sent from one host to any other on that network.
<<<<<<<<<<<<<<<<<<<<<
A destination MAC address where the low-order bit of the first byte is set
<<<<<<<<<<<<<<<<<<<<<
indicats a Multicast, meaning the packet is sent from one host to all hosts
on the network interested in packets sent to that MAC address. A number of
multicast addresses have been assigned; see Ethernet numbers at the IANA,
Michael A. Patton's list of multicast addresses, and Ethereal's list of
Ethernet vendor codes and well-known MAC addresses, from the Ethereal source
distribution, for assigned multicast addresses."
So. UML is not exact technically, but it's enough for our purposes. Don't know
whether it may make sense to assign a multicast address to an iface, but I
guess it's more complicate.
Anyway, complete references and patches (or indications about what to code)
are always welcome.
--
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
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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:[~2005-11-09 1:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 1:13 [uml-devel] Test for ethernet broadcast address? Rob Landley
2005-11-09 1:44 ` Blaisorblade [this message]
2005-11-10 4:03 ` Jeff Dike
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=200511090244.52916.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=rob@landley.net \
--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