From: Poltorak Serguei <poltorak@df.ru>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] routing broadcast messages
Date: Wed, 10 Jul 2002 10:03:37 +0000 [thread overview]
Message-ID: <marc-lartc-102629546720551@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102626138529774@msgid-missing>
Hello
but packets are going To their subnetwork. then m.n.o.w sends packet to
a.b.c.255 gateways other than a.b.c.1 doesn't know that a.b.c.255 is a
broadcast. it's only a.b.c.1 (m.n.o.p) who discards the packet
may be I should redraw my pic.
a.b.c.0/24,brd+ -----[ a.b.c.1, m.n.o.p ]-----m.n.o.w
<-------pings are going in that direction
So, packets are going TO their subnet.
Any idea???
thanks,
PoltoS/
On Wed, 10 Jul 2002, bert hubert wrote:
;On Wed, Jul 10, 2002 at 04:35:16AM +0400, Poltorak Serguei wrote:
;> Hello.
;>
;> I would like to route broadcast messages.
;> For now, if I ping a.b.c.255 from m.n.o.w the packet is passing through
;> each router, except the last, a.b.c.1 (m.n.o.p, other "external" address)
;> and only he replys to that packet, but not from a.b.c.1, he does it from
;> m.n.o.p address (logic, it's the address of the output interface).
;
;Broadcast messages don't leave their subnet. If you want that, you don't
;need a router but a bridge!
;
;Regards,
;
;bert
;
;--
;http://www.PowerDNS.com Versatile DNS Software & Services
;http://www.tk the dot in .tk
;http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
;
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-07-10 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 0:35 [LARTC] routing broadcast messages Poltorak Serguei
2002-07-10 8:30 ` bert hubert
2002-07-10 10:03 ` Poltorak Serguei [this message]
2002-07-10 12:42 ` Eran Man
2002-07-14 0:40 ` Poltorak Serguei
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=marc-lartc-102629546720551@msgid-missing \
--to=poltorak@df.ru \
--cc=lartc@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