Hi Folks, I'm Jeff and I've been away from this level of stuff for far too long. Feel like a newbie.

Anyway, I'm trying to route all packets from 192.168.1.0 to 192.168.42.0 . Shouldn't be too hard should it? 192.168.1.0 is my test segment, and the rest of the world, including gateways, printers etc is on 192.168.42.0.

On the Linux box that I'm trying to route on (Suse 7.3 and kernel 2.2.18), both NICs are working properly, and I can ping to both segments and the outside world, so DNS and local routing seem fine. I have a default route set up to the internet router at 192.168.42.254.

/proc/sys/net/ipv4/ip_forward has been set to '1'.

Now - on a windows box on 192.168.1.5, I can ping to both NICs on the Linux box, but no further on the 192.168.42.0 segment. The Linux box does not seem to be working as a router yet. I can't get to the bottom of it.

I have ipchains installed, but it's not configured to do anything. I'm hoping this is NOT the problem :-)

Has anyone got the answer, or a clue? Sorry for seeming to have forgotten everything :-(

Jeff

it would sound to me like there would be no return route back from the destination machine. this is a test subnet you're coming from right? so therefore is not on the default route from the network on a live network. so that live destination machine has no idea how to get back to that subnet. try a tcpdump on that router to check if that's the case... you should see the echo request packet leave the .42 subnet nic but no reply come back.

and suse 7.3....?? wtf??

Thanks Chris,

Yes - Suse 7 - I said it had been a while :-)

Thanks for the reply. I was just trying to keep my test world separate while still being able to pick up the office printers, and at best, the internet connection.

What are my options? I'm supposing I'd have to make the Linux box do some NAT work to make it look like the packets are existing on the 198.162.42.0 segment :-(

Thanks for pointing out the obvious though. I'd never have got there without a lot more time.

Jeff