From: Rob Landley <telomerase@yahoo.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 255.255.255.255 won't broadcast to multiple NICs
Date: Thu, 2 Nov 2000 17:22:47 -0800 (PST) [thread overview]
Message-ID: <20001103012247.8956.qmail@web5205.mail.yahoo.com> (raw)
--- Jeff Garzik <jgarzik@mandrakesoft.com> wrote:
> Rob Landley wrote:
> > 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.
>
> Are the network cards on the same network?
Two subnets. (both martians: 10.blah and
192.168.blah). Gateway's off of 10.blah (beyond which
lives the internet), the 192 thing is the small
cluster I'm putting together in my office to test the
software.
I take it this makes a difference? If there's some
kind of "don't do that" here, I might be happy just
documenting it. (In theory, I could iterate through
the NICs and send out a broadcast packet to each
interface's broadcast address (although for reasons
that are a bit complicated to go into right now unless
you really want to know, that's not easy to do in this
case).) But that's just a workaround to cover up the
fact that the IP stack isn't doing the obvious with
global broadcasts.
So the question is, is the stack's behavior right? If
not, what's involved in fixing it, and if so, is it
documented anywhere?
(I checked google rather a lot before coming here, and
linux/Documentation, and even glanced at the route.c
source code. ip_route_output_slow has several
explicit checks for "FFFFFFFF" which are easily
searched for, but the upshot is that the packet gets
mapped to a single interface anyway. Around line 1641
of my sources there's an #ifdef CONFIG_IP_MROUTE that
looked very interesting, but it turns out only to be
for multicast addresses and I don't know if
IN_DEV_FORWARD is forking the packet or not...)
At which point I came here. :)
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/
next reply other threads:[~2000-11-03 1:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 1:22 Rob Landley [this message]
2000-11-03 2:14 ` 255.255.255.255 won't broadcast to multiple NICs Philippe Troin
-- strict thread matches above, loose matches on Subject: below --
2000-11-04 3:15 Rob Landley
2000-11-03 19:46 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 4:17 Rob Landley
2000-11-02 23:55 Rob Landley
2000-11-03 0:29 ` Jeff Garzik
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=20001103012247.8956.qmail@web5205.mail.yahoo.com \
--to=telomerase@yahoo.com \
--cc=jgarzik@mandrakesoft.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