Please be kind I'm a newbie ...

I am having problems connecting to my router. I'm using Redhat v9, have ip forwarding on. No
firewall rules are in place. From the server I can ping both cards eth0 and eth1.
From my internal machine I can ping eth0 but not eth1.
From the server I can ping the my machine on the internal LAN.
I can connect to the router from the server OK.

Another thing is I'm not sure whether adding routing table entries will fix the problem or if I should use bridging.



Please help!



Routing Table


Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
192.168.44.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo



Network

-----------
- Router -
-----------
192.168.0.1
|
|
192.168.0.254 <-- eth1
-----------
- Server -
-----------
192.168.44.2 <-- eth0
|
|
192.168.44.100
-----------
Internal LAN

I would try adding gateway=192.168.0.1 on ifcfg-eth1 should allow packets to talk to router.

I agree with beyer42 for getting to the router.
Also on the windows machine you need to add a default route.
route -p add 0.0.0.0 mask 0.0.0.0 192.168.44.2
So that machine can get to eth1 and the router.

I am still unable to get to the router :-(

My workstation gateway is 192.168.44.2
From the server I can ping 192.168.0.254 and 192.168.44.2
From my workstation I can ping I can ping 192.168.0.254 and 192.168.44.2

I still cannot ping 192.168.0.1.

The router is an ADSL netgear modem/router and is accessible from my server. I can get to the admin page ok via a browser.

I have tried a browser on my workstation but that doesnt work either :-(

This is my routing table at the moment.


Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
192.168.44.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.0.254 0.0.0.0 UG 0 0 0 eth1


Is this wrong?

Please, any more ideas???

I assume that the routing table is from the machine you call server. If it is that looks correct.
Just to review.
You have two networks
192.168.0.x
192.168.44.x
and the server is the gateway between the two networks. The machine you call workstation is on the 192.168.44.x network and the router is on the 192.168.0.x network. The route is the connection to the internet.
Problem
You are unable to ping the router from the server, but you able to get to the admin web page of the router. If this is true it sounds like a firewall issue.
What is the output of the following.
iptables -L -n;
arp;
sysctl net.ipv4.ip_forward;
if this returns 0 you are not forwarding run
sysctl -w net.ipv4.ip_forward=1;

Check the route and make sure that it is configured to respond to pings (ICMP protocal).

man, i spend 3 days to fix this thing out. So here is complete guide t all
Do exactly as here.

route del default
route add 0.0.0.0 gw 192.168.0.1 ( at your server)
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -t nat - A POSTROUTING -0 eth1 -j MASQUERADE
echo "1" > /proc/sys/net/ipv4/ip_forward


You are done, but remember that this is unsecure and you need to write you rules for iptables

Many thanks to you all! Finally have it working. Here's what I did:

Took g-rods advice (sorry robik, was writing this while you was posting) and checked the firewall rules, and forwarding. I had cleared all the rules from the firewall so I knew that was not causing problems. Again I checked to make sure. Then I checked forwarding and discovered it was disabled. The problem was that at one point I checked to make sure it was enabled and assumed it would stay enabled. How wrong could I be? Very!

OK, so now I had everything in place so I tried to ping the router on 192.168.0.1 and guess what ... nothing! The last piece of the puzzle was in the router. I needed to set a static route to 192.168.0.254 so packets could make their way back. As I'm new to all this I'm not sure that was the right thing to do but it seemed logical and worked for me.

I did notice that I could use either 192.168.0.1 or 192.168.0.254 as the default gateway and it would still work.

For your information the router is a Netgear DG834UK ADSL Firewall Router.

Just like to finish this of with thanks to everyone who helped.

Phil.

Just read my last post and would like to clarify. When I said:

"I did notice that I could use either 192.168.0.1 or 192.168.0.254 as the default gateway and it would still work"

This was on eth1 on the server not on the router and instead of adding the default route for eth1 I just added as the gateway in ifcfg-eth1.

Thanks again!