Hi - I have seen various posts related to this topic but none really give a step by step guide so hopefully someone out there can fill in the blanks
We would like to set up a SLES 10.3 server to be able to route packets between different subnets
For example subnet 192.168.0.0 /24 will be able to route to 10.0.0.0 /8 - This server will not have any connections to the the internet.
eth0 = 192.168.0.1
eth1 = 10.0.0.1
I have enabled ip-forwarding on the SLES box and can ping from a separate device on the 192.168.0.0 network throught to eth1 on 10.0.0.1 but I cannot ping any devices beyond that interface on the 10.0.0.0 network.
From reading the board I suspect this may be firewall related but I am not sure how to resolve the issue.
Thanks for the reply Tom
In the meantime I managed to ping devices on 10.0.0.x from 192.168.0.x by editing the /etc/sysconfigSuSEfirewall2 - In the FW_FORWARD= section I added the two subnets
is this what you meant by add the route or were you refering to
adding a static route? I would be interested to know the answer. Doing a netstat -r shows a route to the 10.0.0.0 network as this is associated with the interface with the IP of 10.0.0.1
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 * 255.255.255.0 U 0 0 0 eth7
is this what you meant by add the route or were you refering to[color=blue]
adding a static route? I would be interested to know the answer. Doing[/color]
No, I meant ‘route add net…’
But there’s no need to because the route exists, as your ping after
adding the fw-rules shows
Everything looks good now- thanks for the replies[/color]
I see you got this resolved. That’s great.
When IP Forwarding is not enabled, devices on either subnet should be
able to access either interface on your server but none of the devices
on the other subnet. Once you enable IP Forwarding, you still have to
specify what traffic is to be forwarded. It’s not a case of all or
nothing.