From: Jon Masters <jonathan@jonmasters.org>
To: Jeremy Jackson <jerj@coplanar.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Forwarding broadcast traffic
Date: Sat, 03 Mar 2001 18:32:01 +0000 [thread overview]
Message-ID: <3AA138A1.72E99C7C@jonmasters.org> (raw)
In-Reply-To: <200103031054.KAA29868@localhost.localdomain> <3AA12CD8.7F948E0D@coplanar.net>
Jeremy Jackson wrote:
> try bridging instead if ip forwarding. use netfilter too if you want
I mentioned bridging before - I don't want some kind of transparent
bridge, really so what I would need is for the router to be contactable
in the same way as before and for regular traffic to pass normally but
with a special arrangement for certain broadcast traffic.
Is it possible to selectively bridge broadcast traffic in the way I have
described?
Normally of course I'd have the router either being a standard router or
a bridge but in this case some kind of hybrid arrangement would be
preferable.
Thanks for your help,
--jcm
next prev parent reply other threads:[~2001-03-03 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-03 10:54 Forwarding broadcast traffic Jon Masters
2001-03-03 17:41 ` Jeremy Jackson
2001-03-03 18:32 ` Jon Masters [this message]
2001-03-03 18:53 ` Jeremy Jackson
2001-03-03 22:24 ` Joel Jaeggli
2001-03-03 20:21 ` Eric Lammerts
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=3AA138A1.72E99C7C@jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=jerj@coplanar.net \
--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