| To: | Roger Luethi <rl@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: [0/3] mc_filter on big-endian arch |
| From: | David Stevens <dlstevens@xxxxxxxxxx> |
| Date: | Wed, 9 Jun 2004 23:09:53 -0600 |
| Cc: | Andrew Morton <akpm@xxxxxxxx>, David Dillow <dave@xxxxxxxxxxxxxx>, Jeff Garzik <jgarzik@xxxxxxxxx>, Netdev <netdev@xxxxxxxxxxx>, netdev-bounce@xxxxxxxxxxx |
| In-reply-to: | <20040607115921.GB32569@xxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
netdev-bounce@xxxxxxxxxxx wrote on 06/07/2004 04:59:21 AM:
> One thing maybe worth mentioning: If you want to play with different
> addresses, remember that IP addresses are in decimal notation, ethernet
> in hex. So if you set
> target# ip maddr add 01:00:5e:00:00:25 dev eth0
> the test would be
> tester# ping -r -I eth0 -t 1 -c 2 224.0.0.37
This will add "01:00:5e:00:00:25" to the device multicast address filter,
which will mean the host will receive the packet. But because it doesn't
join the group at the IP level, it'll be dropped and the ping won't be
answered (it isn't for a local address).
If you want the machine to answer, you need to join the group, which
will conveniently add the hardware multicast address automatically. :-)
+-DLS
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [RFC] ethtool semantics, Roger Luethi |
|---|---|
| Next by Date: | Re: [0/3] mc_filter on big-endian arch, David Stevens |
| Previous by Thread: | Re: [0/3] mc_filter on big-endian arch, Roger Luethi |
| Next by Thread: | Re: [0/3] mc_filter on big-endian arch, David Stevens |
| Indexes: | [Date] [Thread] [Top] [All Lists] |