All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Jackson <jerj@coplanar.net>
To: Jon Masters <jonathan@jonmasters.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Forwarding broadcast traffic
Date: Sat, 03 Mar 2001 12:41:44 -0500	[thread overview]
Message-ID: <3AA12CD8.7F948E0D@coplanar.net> (raw)
In-Reply-To: <200103031054.KAA29868@localhost.localdomain>

Jon Masters wrote:

> Hello,
>         I have a brain-dead application here which relies on broadcast
> traffic for client/server discovery and I have a question with regard
> to forwarding broadcast traffic.

try bridging instead if ip forwarding.  use netfilter too if you want

>
>
> A small part of my local LAN looks like this:
>
>                  REST OF LAN
>                       |
>                       | (router eth1)
>                       |
>                  masquerading
>                 router (kernel 2.2.14)
>                       |
>                       | (router eth0)
>                       |
>                    desktop (private IP)
>                     boxen  (kernel 2.4.2)
>
> * upgrading the router is not a problem[0].
>
> I wish to have the router forward certain broadcast traffic coming
> from either side out to the other (as well as itself).
>
> e.g. on desktop a broadcast udp packet (with a specified port) needs to
> go not only to itself and the router but also the "REST OF LAN" part
> too - and vice versa. Removing the router is not an option.
>
> I know this isn't a *nice* idea and ordinarily I wouldn't be jumping up
> and down suggesting one throws broadcast traffic around however I need
> to do this for various reasons and the solution appears to be
> non-obvious at least to me[1].
>
> I have considered the idea of creating a transparent bridge however I
> would really rather not do that here for various reasons.
>
> I have posted this message to groups elsewhere however I have not yet
> had any useful responses beyond basic instruction of IP forwarding,
> etc. which is not what I need here :P
>
> Any ideas? I think this one has come up before but I could not find a
> helpful answer in my archives.
>
> Appreciate your time,
>                         --jcm
>
> P.S. My lkml feed at home is great but here it is not so could you
>      please CC me on replies thanks.
>
> [0] Yeah, yeah, I know 2.2.14 is old but it's an old router and when I
>     move that box over to Debian I'll upgrade the kernel at the same
>     time :P
> [1] either due to general stupidity or tiredness, or both.
> -


  reply	other threads:[~2001-03-03 17:46 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 [this message]
2001-03-03 18:32   ` Jon Masters
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=3AA12CD8.7F948E0D@coplanar.net \
    --to=jerj@coplanar.net \
    --cc=jonathan@jonmasters.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.