default route issue

[kemo]

As Usual, when you stuck inside an issue, you try to involve other parties with you, Netwrok Team :(
they put access list on the VLAN. when they removed the list. it worked.

i put them as the last resort, and the problem usually comes from their sides.

thanks everybody

[Bob_Vance]

What does the nestat -rvn show now?

I don't see how an ACL could cause bad entries to appear in the routing table.

These entries were not dynamic entries added because of ICMP redirects; they were trash.

Doesn't make sense to me.

bv

[kemo]

still showing rubbish, but at least i have got my problem fixed.

# netstat -rvn
Routing tables
Dest/Netmask Gateway Flags Refs Interface Pmtu
127.0.0.1/255.255.255.255 127.0.0.1 UH 2130706433 lo0 4136
108.97.110.49/108.97.110.49 0.0.25.191 U 2 16384
10.10.51.1/0.0.0.0 0.0.0.5 U 4294967295 2130706432
0.0.25.222/0.0.0.0 * U 4 4294967295
0.0.0.5/0.0.0.0 * U 9864560 16

[Bob_Vance]

That makes me feel better ;>)

I don't want to beat a dead horse, but I think the critter is still breathing, or maybe a zombie or something.

I don't understand why originally it worked for the 5 minutes.

Also, I still would like to see
netstat -ivn

and also both
netstat -ivn
netstat -rvn
IMMEDIATELY after a reboot.

bv

[kemo]

i have already announced to the dev team that the server is back. i am sorry i won't be able to reboot, but below is the current output

# netstat -inv
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan1 1500 10.10.51.0 10.10.51.1 16 0 3 0 0 2147483647 none 255.0.0.0 849 0 0 0 0
#
=============
# netstat -rvn
Routing tables
Dest/Netmask Gateway Flags Refs Interface Pmtu
127.0.0.1/255.255.255.255 127.0.0.1 UH 2130706433 lo0 4136
108.97.110.49/108.97.110.49 0.1.13.179 U 2 16384
0.0.0.1/0.0.0.1 0.0.0.5 U 4294967295 2130706432
default/0.0.9.64 * U 9864560 16
=========

thanks

[Bob_Vance]

There is something very wrong with your system.
That output is totally trash.
Your output should be like the attached file.

I've never seen anything like this, except when something is stomping around on memory, but that usually portends more serious problems, like crashes.

OTOH, the default route seems to be working, so maybe it's just an output problem.

I would look for the latest patches
and also call HP.

bv