topic Default route in Operating System - HP-UX

Default route

Brian Monkey — Wed, 15 Jun 2005 04:52:55 GMT

Hello
Can anyone explain why the following is happening?

I am trying to send traffic bound for the address dibftp via the gateway 193.132.36.100

For some reason it always uses lan2 for this path, even though its not on the same subnet.

Can anyone shed any light on this?

root@ns02:/ # traceroute 193.132.36.100
traceroute: Warning: Multiple interfaces found; using 192.168.25.2 @ lan2
traceroute to 193.132.36.100 (193.132.36.100), 30 hops max, 40 byte packets
1 *root@ns02:/ #

root@ns02:/ # netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan3* 1500 none none 0 0 0 0 0
lan2 1500 192.168.25.0 192.168.25.2 0 0 0 0 31
lan1* 1500 193.132.36.0 193.132.36.99 49 0 40 0 0
lo0 4136 127.0.0.0 127.0.0.1 820527 0 820527 0 0
lan7 1500 16.3.197.0 16.3.197.102 932065 0 397979 0 0
lan6* 1500 none none 0 0 0 0 0
root@ns02:/ #

#Links added by Brian Monkey
#Dibnar
ROUTE_DESTINATION[0]="dibftp"
ROUTE_GATEWAY[0]="16.3.197.250"

ROUTE_DESTINATION[1]="dibnet"
ROUTE_GATEWAY[1]="16.3.197.250"

#larry
ROUTE_DESTINATION[2]="larftp"
ROUTE_GATEWAY[2]="16.3.197.250"

#guass
ROUTE_DESTINATION[3]="gauftp"
ROUTE_GATEWAY[3]="193.132.36.100"

Re: Default route

Keith Bryson — Wed, 15 Jun 2005 05:09:51 GMT

Hi Brian

Traceroute can be run with the -i switch to specify which interface to use for the traceroute. This is annoying feature of traceroute (in my opinion).

HTH - Keith

Re: Default route

Alex Lavrov. — Wed, 15 Jun 2005 05:20:05 GMT

Can you please post here the output of:

netstat -rn

Re: Default route

Brian Monkey — Wed, 15 Jun 2005 05:25:32 GMT

netstat -rn

root@ns02:/ # netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
16.3.197.102 16.3.197.102 UH 0 lan7 4136
192.168.25.2 192.168.25.2 UH 0 lan2 4136
193.132.36.99 193.132.36.99 UH 0 lan1 4136
172.16.3.1 193.132.36.99 UH 0 lan1 0
172.16.3.1 193.132.36.98 UGH 0 lan1 0
172.16.3.1 193.132.36.100 UGH 0 lan7 0
158.230.4.197 16.3.197.250 UGH 0 lan7 0
158.230.4.206 16.3.197.250 UGH 0 lan7 0
194.62.239.231 16.3.197.250 UGH 0 lan7 0
193.132.36.100 16.3.197.250 UGH 0 lan7 0
194.62.239.23 16.3.197.250 UGH 0 lan7 0
158.23.4.197 16.3.197.250 UGH 0 lan7 0
16.3.197.0 16.3.197.102 U 2 lan7 1500
192.168.25.0 192.168.25.2 U 2 lan2 1500
127.0.0.0 127.0.0.1 U 0 lo0 0
default 16.3.197.254 UG 0 lan7 0

Re: Default route

Keith Bryson — Wed, 15 Jun 2005 06:08:45 GMT

Hi Brian

Can you also include output from:

ifconfig lan1

Cheers! - Keith

Re: Default route

Alex Lavrov. — Wed, 15 Jun 2005 06:16:24 GMT

It doesn't use lan2.

In routing table you have double entries for lan2 and every time it access routing table it warns you about it. It does not mean that it uses lan2.

Fix the double entries:
192.168.25.2 192.168.25.2 UH 0 lan2 4136
192.168.25.0 192.168.25.2 U 2 lan2 1500

and you'll see that you will stop getting this warning.

Alex.

Re: Default route

Brian Monkey — Wed, 15 Jun 2005 06:49:54 GMT

Im not certain i understand.

The destination i am trying to go to is not on the same subnet as lan2

So for example:
i am trying to go to 193.132.x.x yet its uses the lan card with a 192.168.x.x address.
Even though there is a card with a 193.132.x.x addresses on it.

output from lan1
ifconfig lan1
lan1: flags=1842
inet 193.132.36.99 netmask ffffff00 broadcast 193.132.36.255

Re: Default route

Alex Lavrov. — Wed, 15 Jun 2005 06:53:09 GMT

It does use lan1.

It just tells you, that you have a mistake in routing table in lan2 definitions, that's all. It doesn't meant that it uses lan2 for that subnet.

Try to use traceroute for any other subnet and it still will warn you about misconfiguration of lan2 routing.

That's all.

Re: Default route

Keith Bryson — Wed, 15 Jun 2005 06:56:41 GMT

Brian

According to your ifconfig output, lan1 is NOT UP. Is this LAN port connected or set to the correct speed/duplex setting?

Keith

Re: Default route

Keith Bryson — Wed, 15 Jun 2005 07:27:59 GMT

Brian

In addition to my last post, I would expect your flags to be 1843 (not 1842) if the interface was operational. I suspect that this interface is down and HP-UX has attempted to route via another interface and this has caused the 'dodgy' route to stick in the routing table. I'd suggest:

lanadmin -x 1
(to check the interface speed/duplex)
Resolve the LAN issue and then use a 'route delete ....' command to delete the sticky route.

Let us know how things go - Keith

Re: Default route

Keith Bryson — Fri, 17 Jun 2005 03:12:36 GMT

Hello Brian

Did you resolve this? If so, can you allocate points for each reply. If not, drop another reply and we will help you further.

All the best - Keith