> Is it possible to selectively bridge broadcast traffic in the way I have
> described?
Take a look at how your router handles broadcast dhcp requests cisco at
least have a dhcp helper functionality which is essentially just what
you're asking for (selective forwarding of broadcast traffic.
if
On Sat, 3 Mar 2001, Jon Masters wrote:
> 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.
Write an application that creates 2 sockets
Jon Masters wrote:
> 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
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
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
&
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.
A small part of my local LAN looks like this:
REST OF LAN
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.
A small part of my local LAN looks like this:
REST OF LAN
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
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
Jon Masters wrote:
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
On Sat, 3 Mar 2001, Jon Masters wrote:
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.
Write an application that creates 2 sockets
Is it possible to selectively bridge broadcast traffic in the way I have
described?
Take a look at how your router handles broadcast dhcp requests cisco at
least have a dhcp helper functionality which is essentially just what
you're asking for (selective forwarding of broadcast traffic.
if
12 matches
Mail list logo
