Where do packets sent to 255.255.255.255 go?

Where do packets sent to 255.255.255.255 go?

[Daniel Brockman]

Hi list,

If I understand correctly, packets sent to the all-ones
broadcast address only go out through a single interface.

My question is threefold:

 1. Why doesn't Linux send 255.255.255.255 packages through
    all network interfaces?  (I realize that this is
    probably not a Linux-specific question.)

 2. How does it choose which interface to send through?
    My first guess was that it just took the first Ethernet
    interface and used that for broadcasting.  But playing
    around with nameif, this seems not to be the case.

 3. Can I set the default broadcast interface explicitly?
    For example, say I wanted broadcasts to go out over eth1
    by default, instead of over eth0.  What if I wanted them
    to get sent through tap0?

Yes, I know that what I *should* be doing is just send the
packages to the broadcast address specific to the network
where I want them to go.  (That is, I should be sending them
to 10.255.255.255 instead of 255.255.255.255 if I want them
to be broadcast to the 10.0.0.0 network.)

Unfortunately, this is not a viable option in my case, as
I'm dealing with a closed-source application that
unconditionally sends broadcasts to 255.255.255.255.
Ideally, the application would let me choose which interface
to broadcast to, but alas it does not.

I've tried searching for a solution to this problem on the
web and on IRC with no luck, so now I'm turning to you guys.


Thanks in advance,

-- 
Daniel Brockman <daniel@brockman.se>

Re: Where do packets sent to 255.255.255.255 go?

[Eric Piel]

25.08.2005 03:02, Daniel Brockman wrote/a écrit:
> Hi list,
> 
> If I understand correctly, packets sent to the all-ones
> broadcast address only go out through a single interface.
Hello,

I have some blur memories about this kind of issue, so my answer my be 
wrong on some points...

> 
> My question is threefold:
> 
>  1. Why doesn't Linux send 255.255.255.255 packages through
>     all network interfaces?  (I realize that this is
>     probably not a Linux-specific question.)
IIRC, Linux 255.255.255.255 as a normal IP address. Therefore it will 
follow the route for such an address and select the interface it is 
associated (probably eth0 if you are on a LAN).

> 
>  2. How does it choose which interface to send through?
>     My first guess was that it just took the first Ethernet
>     interface and used that for broadcasting.  But playing
>     around with nameif, this seems not to be the case.
cf 1

> 
>  3. Can I set the default broadcast interface explicitly?
>     For example, say I wanted broadcasts to go out over eth1
>     by default, instead of over eth0.  What if I wanted them
>     to get sent through tap0?
Again, I'm not sure, but I think that you can force the interface by 
adding a special route for IP 255.255.255.255 and with mask 
255.255.255.255 to the interface you want.


[sniped]

Hope this help, even if my memory is a bit confused,
Eric

Re: Where do packets sent to 255.255.255.255 go?

[Daniel Brockman]

Hi Eric,

>> If I understand correctly, packets sent to the all-ones
>> broadcast address only go out through a single interface.
>
> I have some blur memories about this kind of issue, so my
> answer my be wrong on some points...

It turns out you are exactly right on all points. :-)

>> My question is threefold:
>>
>>  1. Why doesn't Linux send 255.255.255.255 packages
>>     through all network interfaces?  (I realize that
>>     this is probably not a Linux-specific question.)
>
> IIRC, Linux treats 255.255.255.255 as a normal IP address.
> Therefore it will follow the route for such an address and
> select the interface it is associated (probably eth0 if
> you are on a LAN).

That makes a lot of sense, and it appears to be the case.

>>  2. How does it choose which interface to send through?
>>     My first guess was that it just took the first
>>     Ethernet interface and used that for broadcasting.
>>     But playing around with nameif, this seems not to
>>     be the case.
>
> cf 1
>
>>  3. Can I set the default broadcast interface explicitly?
>>     For example, say I wanted broadcasts to go out over
>>     eth1 by default, instead of over eth0.  What if I
>>     wanted them to get sent through tap0?
>
> Again, I'm not sure, but I think that you can force the
> interface by adding a special route for IP 255.255.255.255
> and with mask 255.255.255.255 to the interface you want.

Yes, this works!  It's so simple --- I can't believe I
didn't try it before.  I did mess around with iptables,
trying to add some weird PREROUTEing DNAT that would
redirect the packets, but I didn't know what I was doing.

> Hope this help, even if my memory is a bit confused,

Yes, it did help.  Thanks a bunch, Eric!  Your memory seems
to be in great shape. :-)


Regards,

-- 
Daniel Brockman <daniel@brockman.se>

Re: PATCH: Fix race in cpu_down (hotplug cpu)

[Nigel Cunningham]

On Mon, 2005-09-19 at 15:28, Srivatsa Vaddagiri wrote:
> On Mon, Sep 19, 2005 at 03:23:01PM +1000, Nigel Cunningham wrote:
> > Maybe I'm just an ignoramus, but I was thinking (without being a
> > scheduler expert at all) that if the idle thread was already running,
> > trying to set it up to run next might possibly have zero effect. I've
> 
> sched_idle_next actually adds the idle task to its runqueue (normally
> it is not present in a runqueue while running) and as well changes its 
> priority/policy. So it does have *some* effect!

Ok.

> > added a bit of debugging code to try and see in better detail what's
> > happening.
> 
> Could you elaborate (with some stack traces maybe) on the deadlock you are 
> seeing during resume? Maybe that can throw some light.

I'll try. I'm having trouble reproducing it now (yes, having reversed my
patch!).

Regards,

Nigel
-- 

Re: Where do packets sent to 255.255.255.255 go?

[Wei-Che, Hsu]

Dear sir,

I have the same question recently & found a solution on the following url.
http://www.uwsg.iu.edu/hypermail/linux/kernel/0508.3/0397.html
& trace to this mailing list.

I had added a 255.255.255.255 route to a specific interface(eth0).
But seems no luck.
The broadcast package still go out via default gateway(eth1).
(detail "route -n" will be attached on the tail of this mail.)

Does anyone have any idea about it?
Should I enable something on my kernel?

ThanX in advance.

=== Original Post ===
>>> 3. Can I set the default broadcast interface explicitly?
>>> For example, say I wanted broadcasts to go out over
>>> eth1 by default, instead of over eth0. What if I
>>> wanted them to get sent through tap0?
>>
>> Again, I'm not sure, but I think that you can force the
>> interface by adding a special route for IP 255.255.255.255
>> and with mask 255.255.255.255 to the interface you want.

> Yes, this works! It's so simple --- I can't believe I
> didn't try it before. I did mess around with iptables,
> trying to add some weird PREROUTEing DNAT that would
> redirect the packets, but I didn't know what I was doing.
=== Original Post ===

=== Detail route output ===
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
255.255.255.255 0.0.0.0         255.255.255.255 UH    0      0        0 eth0
192.168.7.0     192.168.6.254   255.255.255.0   UG    0      0        0 eth0
192.168.6.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.5.0     192.168.6.254   255.255.255.0   UG    0      0        0 eth0
192.168.4.0     192.168.6.254   255.255.255.0   UG    0      0        0 eth0
172.30.1.0      0.0.0.0         255.255.255.0   U     0      0        0 eth1
192.168.3.0     192.168.6.254   255.255.255.0   UG    0      0        0 eth0
192.168.2.0     192.168.6.254   255.255.255.0   UG    0      0        0 eth0
192.168.12.0    192.168.6.254   255.255.255.0   UG    0      0        0 eth0
192.168.11.0    192.168.6.254   255.255.255.0   UG    0      0        0 eth0
192.168.10.0    192.168.6.254   255.255.255.0   UG    0      0        0 eth0
192.168.9.0     192.168.6.254   255.255.255.0   UG    0      0        0 eth0
192.168.254.0   0.0.0.0         255.255.255.0   U     0      0        0 eth2
192.168.8.0     192.168.6.254   255.255.255.0   UG    0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         172.30.1.254    0.0.0.0         UG    0      0        0 eth1
=== Detail route output ===

Good day.
 
Sincerely yours,
      responder