Re: dumb question...route from local eth1 to eth2 and vice versa

["Jesse Gordon" <jesseg@nikola.com>]

Thomas Kuiper said:
> Jesse,
>
> I think his problems has nothing to do with iptables but routing in 
> general.
>

Thomas,

Ahh. I guess he did use the word "route" didn't he! I should pay more 
attention.

I just figured that since packets were going to be going in one eth and out 
another, that iptables had to be involved. :-)

Thanks!

Joel,

I also want to learn how to route packets as you describe. When you find 
your solution, perhaps you could email me privately and let me know what it 
turned out to be.

Thanks!

-Jesse

----- Original Message ----- 
From: "Thomas Kuiper" <tkuiper-netfilter@inxsoft.net>
To: "Jesse Gordon" <jesseg@nikola.com>
Cc: "Joel F" <roadapathy@yahoo.com>; <netfilter@lists.netfilter.org>
Sent: Wednesday, November 30, 2005 7:22 PM
Subject: Re: dumb question...route from local eth1 to eth2 and vice versa


> Jesse,
>
> I think his problems has nothing to do with iptables but routing in 
> general.
>
> Joel,
>
> I guess you want to ask your question (which is very basic) to a network 
> related linux beginners groups (there are thousands of those), but you 
> might find the one that is related to your linux distribution.
>
> Or one of the linux network related usenet groups that you can simply 
> browse at http://groups.google.com/
>
> Best Regards,
> Thomas
>
>
>
> Jesse Gordon wrote:
>> ----- Original Message ----- From: "Joel F" <roadapathy@yahoo.com>
>> To: <netfilter@lists.netfilter.org>
>> Sent: Wednesday, November 30, 2005 6:43 PM
>> Subject: dumb question...route from local eth1 to eth2 and vice versa
>>
>>
>>> eth0 - my WAN ip.
>>>
>>> eth1 - 192.168.0.0  My kids network
>>> eth2 - 192.168.1.0  My personal network
>>>
>>> How can I route packets to and from my network of
>>> 192.168.1.x (eth2)
>>> to my kids network 192.168.0.x (eth1) so that we can
>>> all play
>>> network games???
>>
>>
>> You may get away with simply enabling forwarding between eth1 and eth2, 
>> something like this might allow both the *.1.x and the *.0.x networks to 
>> communicate with eachother:
>> iptables -A FORWARD -i eth1 -o eth2 -j ACCEPT  #Data going one way is 
>> allowed
>> iptables -A FORWARD -i eth2 -o eth1 -j ACCEPT #And data going other way 
>> is allowed.
>
> ...
>