[H-GEN] lost the plot... most likely

[Marc Dergacz]

[ Humbug *General* list - semi-serious discussions about Humbug and
Unix-related topics. ]

Stephen Brine wrote:

> [ Humbug *General* list - semi-serious discussions about Humbug and
> Unix-related topics. ]
>
> I am toying with setting up routing with my linux box. I have 2 NIC in one
> set to 192.160.0.22 and the other set to 192.168.105.14. now my network
> mostly runs on the 192.160.0. network ok. but I wanted to set it up so i
> can effectively have two segments (don't need but want to try out routing
> with linux). now what I want to know is this should routed be able to
> detect that a ping is coming in from 192.160.0.20(NT) to 192.160.0.22(linux
> eth0) then to 192.168.105.14(linux eth1) and then consequencly to
> 192.168.105.1(win95) OR do i need to start mucking around with IPCHAINS. I
> have tried doing what the linux networkjing HOWTO mentioned about routing
> but no success. BUT it will ping the other card if I set it to say
> 192.160.0.12
>
> 192.160.0.20(NT) --> 192.160.0.22(eth0) --> 192.160.0.12(eth1)
>
> if this doesn't make much sense I will try to figure it out on saturday night

This is fairly trivial.

Set your routes for eth0 and eth1 as per usual

Then all you will need is an entry into your firewall to tell it where to
forward incomming packets.  Your routes will tell the kernel when to deliver the
packet.

(Correct me if im wrong)
ipchains -I forward -s 192.168.0.0/24 -d 192.168.105.0/24

where 192.168.0.0 is on eth0 and 192.168.105.0 being on eth1

hope that is clear enought

Marc Dergacz
marcd at kermit.humbug.org.au


--
This is list (humbug) general handled by majordomo at lists.humbug.org.au .
Postings only from subscribed addresses of lists general or general-post.