Can't ping gateway.

[Roger Elcot]

I'm having problems connecting my machine to the network. I am unable to ping any machine other than localhost.

Here's what I have in /etc/rc.config.d/netconf:
ROUTE_DESTINATION[0]=default
ROUTE_MASK[0]=
ROUTE_GATEWAY[0]=192.168.0.1
ROUTE_COUNT[0]=
ROUTE_ARGS[0]=

No problems in rc.log and am able to run /sbin/rc2.d/S340net [stop|start] without any noticable problems.

the results from netstat -rn on lan0 are:
192.168.0.7 192.168.0.7 UH 0 222 lan0 4136
192.168.0.0 192.168.0.7 U 0 0 lan0 1500
default 192.168.0.1 UG 0 0 lan0 1500

If I try to do a:
route add 192.168.0.0 192.168.0.1
I get:
add net 192.168.0.0: gateway 192.168.0.1: Network is unreachable

Any suggestions?
Cheers,
Roger

PS I'm running HP-UX 11.0 and using an AUI->10baseT tranceiver. When I ping, I see the link lights on my hub turn on.

[Michael Tully]

Hi Roger,

First off there is an error ion your netconf file.
Where the entry reads:
ROUTE_DESTINATION[0]="default"
ROUTE_MASK[0]=""
ROUTE_GATEWAY[0]="10.53.10.10"
ROUTE_COUNT[0]="1"
ROUTE_ARGS[0]=""

Change your ROUTE_COUNT to be "1"

If this doesn't fix it, what are the actual results of the ping??

HTH
-Michael

[Michael Tully]

Hi Roger (again)

I just read your question again.
When you want to add a default route try
this:

# route add default 192.168.0.1 1

You need to tell the routing daemon how many
hops there are to the router. The answer I
posted previously will fix the route for the
next time your system is booted.

HTH
-Michael

[Sanjay_6 · Accepted solution]

Hi Roger,

what is the speed of the port on the HUB / Switch. Is it set to 10 MBPS or autosensing. Can you set it to 10 and see if your network works.

Also why don't you try to configure your card and the gateway using sam. might work.

hope this helps.

thanks

[Darrell Allen]

Hi Roger,

Sanjay has already suggested it could be a speed mismatch between your machine and the switch. If not and you can't ping anything else on the local subnet then perhaps it's a physical network issue. Is the cable ok? Is the port on the switch active? Is the transceiver ok? Does your machine have an RJ-45 port you could use instead of the AUI port? Is the port on your machine ok?

Depending on your NIC, you may have to set a jumper for the AUI port to be active. See http://us-support.external.hp.com/cki/bin/doc.pl/sid=c5de93cd15fcb8b62e/screen=ckiDisplayDocument?docId=200000053279165

There are other docs in the ITRC that may help. Search for AUI will list a number of them.

Elementary issues but I've been bitten by them numerous times.

Darrell

[linuxfan]

Hi Roger,

If speed mismatch was a problem, then you would atleast be able to ping the gateway and reach the network but don't think that is the problem here.

what you could try is do
netstat -nrv
(make sure the netmasks are ok)

also looking at your routing table looks like you have an entry for default, delete it first using route delete and then add it back using "route add default 192.168.0.1 1"

Again check your output of netstat -nrv

-HTH
Ramesh

[John Waller]

I would definetly check your network connection. The netstat -rn idicates that the default route has been configured successfully as 192.168.0.1. As a matter of interest when I tried a similar excersise to yourself with the route add 192.168.0.0 192.168.0.1 command it also failed probably because 192.168.0 is your local network and as such does not need to go through the router.

[Roger Elcot]

Thanks for the suggestions.

I wrote the wrong ROUTE_COUNT in my email. I had set ROUTE_COUNT="1" in netconf.

If I do
# route add default 192.168.0.1 1
it adds the line without any problem, but nothing happens. If I try
# route add default 255.255.255.0 192.168.0.1
it says network is unreachable.

As for checking to see if the problem is hardware related, here are the clues that I've gathered. Any suggestions are appreciated...

The ethernet card is using a AUI->10bT tranceiver, hooked up to a 10/100baseT autosensing (only) hub.

When I try pinging a machine on the local subnet, I see the link light on the hub blink, but ping simply does nothing after printing:
PING 192.168.0.1: 64 byte packets

Could this still signify a hardware problem? Ideas?

Thanks,
Roger

[Roger Elcot]

Ok, I solved the problem.

As suggested, it was indeed a hardware problem. For some reason, my NetGear hub was not happy with the 10bT connection. I tried connecting directly to our 3com switch and things worked fine. So I am now bypassing the hub and connecting directly to the wall's patch panel.

Thanks for the help.

Cheers,
Rog