* broadcast and router ?
@ 2005-05-15 0:36 Sdimitrov
0 siblings, 0 replies; 3+ messages in thread
From: Sdimitrov @ 2005-05-15 0:36 UTC (permalink / raw)
To: netfilter
Hi. Sorry for my bad english.
Our local chat use a UDP 8167 and broadcast. All is OK but people over
router in other network don't receive a packets.
Can I have route this packets to they's network with iptables?
networks are 192.168.0.255 and 192.168.1.255
thanks
________________________________________________
Message sent using
UebiMiau 2.7.2
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: broadcast and router ?
[not found] <42876bf0.7523c613.1324.592eSMTPIN_ADDED@mx.gmail.com>
@ 2005-05-16 8:24 ` Mohamed Eldesoky
2005-05-16 21:22 ` Taylor, Grant
0 siblings, 1 reply; 3+ messages in thread
From: Mohamed Eldesoky @ 2005-05-16 8:24 UTC (permalink / raw)
To: Sdimitrov, netfilter
ebtables ??
On 5/15/05, Sdimitrov <st.dimitrov@gmail.com> wrote:
> Hi. Sorry for my bad english.
>
> Our local chat use a UDP 8167 and broadcast. All is OK but people over
> router in other network don't receive a packets.
>
> Can I have route this packets to they's network with iptables?
>
> networks are 192.168.0.255 and 192.168.1.255
>
> thanks
>
> ________________________________________________
> Message sent using
> UebiMiau 2.7.2
>
>
--
Mohamed Eldesoky
www.eldesoky.net
RHCE
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: broadcast and router ?
2005-05-16 8:24 ` broadcast and router ? Mohamed Eldesoky
@ 2005-05-16 21:22 ` Taylor, Grant
0 siblings, 0 replies; 3+ messages in thread
From: Taylor, Grant @ 2005-05-16 21:22 UTC (permalink / raw)
To: netfilter
> ebtables ??
>
>>Hi. Sorry for my bad english.
>>
>>Our local chat use a UDP 8167 and broadcast. All is OK but people over
>>router in other network don't receive a packets.
>>
>>Can I have route this packets to they's network with iptables?
>>
>>networks are 192.168.0.255 and 192.168.1.255
If I could not get both networks working on a larger subnet (/23?) I would possibly try (D/S)NATing traffic that was destined to one subnetworks broadcast address to another and vice-versa. I would also seriously look to see if there was an application level proxy for your chat program. Below is a sample rule that I would be tempted to try:
iptables -t nat -A PREROUTING -i $LAN_1_if -d 192.168.0.255 -p udp --dport 8167 -j DNAT --to-destination 192.168.1.255
iptables -t nat -A PREROUTING -i $LAN_2_if -d 192.168.1.255 -p udp --dport 8167 -j DNAT --to-destination 192.168.0.255
iptables -t nat -A POSTROUTING -o $LAN_1_if -d 192.168.0.255 -p udp --dport 8167 -j SNAT --to-source $LAN_1_if_IP
iptables -t nat -A POSTROUTING -o $LAN_2_if -d 192.168.1.255 -p udp --dport 8167 -j SNAT --to-source $LAN_2_if_IP
I *think* this is a quick and *DIRTY* hack that should get the traffic to cross the subnets. I say DIRTY b/c this type of practice is avoided for a lot of different reasons. You may or may not want to SNAT the traffic depending on how the client software plays. I would make sure to ONLY DNAT traffic to the broadcast to a specific UDP port to prevent spreading of any other broadcast traffic.
Grant. . . .
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-05-16 21:22 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <42876bf0.7523c613.1324.592eSMTPIN_ADDED@mx.gmail.com>
2005-05-16 8:24 ` broadcast and router ? Mohamed Eldesoky
2005-05-16 21:22 ` Taylor, Grant
2005-05-15 0:36 Sdimitrov
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.