public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <telomerase@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: 255.255.255.255 won't broadcast to multiple NICs
Date: Thu, 2 Nov 2000 15:55:38 -0800 (PST)	[thread overview]
Message-ID: <20001102235538.25699.qmail@web5205.mail.yahoo.com> (raw)

Under 2.2.16, broadcast packets addressed to
255.255.255.255 do not go out to all interfaces in a
machine with multiple network cards.  They're getting
routed out the default gateway's interface instead.

If I ifconfig eth1 down (which has the gateway behind
it), I start getting "no route to host", even though
the other subnet's still up and the default gateway's
cleaned out of the routing tables.  Under no
circumstances can I get the broadcast packet to go out
more than one interface (I hate to say "like it does
under windows" but in this case, yes).

The packets aren't actually getting sent to the
gateway, they're just getting sent out the gateway's
interface.  They're still broadcast packets.  I.E. in
a machine with only one NIC, broadcasting
255.255.255.255 works fine.

Is there something I can echo into /proc somewhere to
make this work, or some magic combination of ifconfig
and route that will tell it to actually broadcast out
more than one interface?  Should I mess around with
the ethernet bridging code?  I don't know if any of
these will work.  The problem seems to be conceptual:
when one packet goes into the stack, only one packet
comes out.  Global broadcast means with multiple NICS,
multiple packets should come out (one per NIC), and
apparently there's no support for that.

Ummm...  Help?

(I have config info and test code if you can't
reproduce this.  I, unfortunately, have spent the
entire afternoon trying NOT to reproduce this. 
Sigh...)

Rob

__________________________________________________
Do You Yahoo!?
>From homework help to love advice, Yahoo! Experts has your answer.
http://experts.yahoo.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-11-02 23:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-02 23:55 Rob Landley [this message]
2000-11-03  0:29 ` 255.255.255.255 won't broadcast to multiple NICs Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2000-11-03  1:22 Rob Landley
2000-11-03  2:14 ` Philippe Troin
2000-11-03  4:17 Rob Landley
2000-11-03 17:33 Rob Landley
2000-11-03 18:11 ` Paul Flinders
2000-11-03 20:19 ` Philippe Troin
2000-11-03 19:46 Rob Landley
2000-11-04  3:15 Rob Landley

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=20001102235538.25699.qmail@web5205.mail.yahoo.com \
    --to=telomerase@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    /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