topic Re: HP-UX B11.31 Routing problem in Operating System - HP-UX

HP-UX B11.31 Routing problem

Enrique Altuna Castillo — Mon, 20 Jul 2009 13:22:34 GMT

I have a server with two network interfaces, one lan0 connected to a 10.*.*.* network with the adress 10.1.49.137 and one lan5 connected to Internet with the adress 200.30.204.45 The Internet gateway is 200.30.204.41.

When i run the netstat -rn get:
netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 32808
192.168.0.2 192.168.0.2 UH 0 lan2 32808
10.1.49.137 10.1.49.137 UH 0 lan0 32808
200.30.204.45 200.30.204.45 UH 0 lan5 32808
200.30.204.40 200.30.204.45 U 2 lan5 1500
192.168.0.0 192.168.0.2 U 2 lan2 1500
10.0.0.0 10.1.49.137 U 2 lan0 1500
127.0.0.0 127.0.0.1 U 0 lo0 32808
default 200.30.204.41 UG 0 lan5 1500

When I run traceroute google.com get:
traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 74.125.45.100
traceroute to google.com (74.125.45.100), 30 hops max, 40 byte packets
1 something
2 something
...
14 yx-in-f100.google.com (74.125.45.100) 74.212 ms 76.080 ms 76.522 ms

When I run traceroute -i lan0 google.com the host can't be reached.

I need any suggestion about this problem.

Re: HP-UX B11.31 Routing problem

Steven E. Protter — Mon, 20 Jul 2009 13:26:38 GMT

Shalom,

My suggestion: stop working on this.

When I run traceroute -i lan0 google.com the host can't be reached.

Most hosts including google block traceroute and port scan. The reason is that these protocols have been used in denial of service attacks.

There is no need to complete this command. The problem is not with HP-UX, it is with google protecting itself.

SEP

Re: HP-UX B11.31 Routing problem

Enrique Altuna Castillo — Mon, 20 Jul 2009 13:37:24 GMT

I think you can't be more wrong, because I do get response when I run the traceroute google.com command.

Re: HP-UX B11.31 Routing problem

bright image — Mon, 20 Jul 2009 13:43:47 GMT

Why is this a problem?

traceroute -i lan0 google.com is using an internal interface (lan0) that is not connected to the internet so it won't be able to get to google.com

traceroute google.com is using the default route that is on lan5 and is connected to the internet so can reach google.com

Re: HP-UX B11.31 Routing problem

Enrique Altuna Castillo — Mon, 20 Jul 2009 13:56:30 GMT

Oh yes my mistake. But the thing is I am trying to use the server as gateway from the local network to Internet and when I ping google.com from the local network I don't get response at all.

Re: HP-UX B11.31 Routing problem

bright image — Mon, 20 Jul 2009 14:04:29 GMT

Is gated enabled?

See man gated for more information

It is set in /etc/rc.config.d/netconf

Set GATED to 1 to start the daemon at boot time...

Re: HP-UX B11.31 Routing problem

Ganesan R — Mon, 20 Jul 2009 14:10:00 GMT

Hi,

When you send any pocket to the network(for example ping or traceroute), first it will broadcosted to internel network and if the packet is not on the same subnet it will be routed to the default gateway where the router will route the packet to outside network.

But if you specify a network interface to obtain the source IPv4 or IPv6 address for outgoing probe packets using -i option, then it will not go to gateway at all. This option can be useful only when you have multi-homed host.

Re: HP-UX B11.31 Routing problem

Steven E. Protter — Mon, 20 Jul 2009 15:16:34 GMT

Shalom,

Here is my traceroute to google.com

root@lappy:~# traceroute google.com
traceroute to google.com (74.125.67.100), 64 hops max, 52 byte packets
1 * * *
2 * bzq-79-178-150-1.red.bezeqint.net (79.178.150.1) 11 ms 22 ms
3 bzq-115-191-241.static.bezeqint.net (192.115.191.241) 12 ms 10 ms 11 ms
4 bzq-179-124-129.static.bezeqint.net (212.179.124.129) [MPLS: Label 302704 Exp 0] 11 ms 12 ms 11 ms
5 bzq-179-124-162.static.bezeqint.net (212.179.124.162) [MPLS: Label 500976 Exp 1] 11 ms 12 ms bzq-179-124-150.static.bezeqint.net (212.179.124.150) [MPLS: Label 452720 Exp 1] 12 ms
6 bzq-219-189-18.cablep.bezeqint.net (62.219.189.18) 851 ms bzq-179-124-18.static.bezeqint.net (212.179.124.18) 834 ms 828 ms
7 72.14.198.85 (72.14.198.85) 106 ms 99 ms 99 ms
8 209.85.255.170 (209.85.255.170) 61 ms (TOS=128!) 82 ms 62 ms
9 72.14.233.104 (72.14.233.104) [MPLS: Label 416477 Exp 4] 72 ms 209.85.248.45 (209.85.248.45) [MPLS: Label 685976 Exp 4] 64 ms 72.14.233.104 (72.14.233.104) [MPLS: Label 453181 Exp 4] 91 ms
10 216.239.43.90 (216.239.43.90) [MPLS: Label 667252 Exp 4] 187 ms 209.85.248.94 (209.85.248.94) [MPLS: Label 445592 Exp 4] 109 ms 72.14.232.105 (72.14.232.105) [MPLS: Label 465933 Exp 4] 72 ms
11 66.249.95.149 (66.249.95.149) 184 ms 72.14.239.94 (72.14.239.94) [MPLS: Label 622405 Exp 4] 200 ms 66.249.95.149 (66.249.95.149) 168 ms
12 216.239.48.69 (216.239.48.69) 185 ms 72.14.239.127 (72.14.239.127) 188 ms 66.249.95.149 (66.249.95.149) 167 ms
13 209.85.255.190 (209.85.255.190) 195 ms 72.14.239.131 (72.14.239.131) 200 ms 64.233.174.46 (64.233.174.46) 172 ms
14 209.85.255.190 (209.85.255.190) 170 ms gw-in-f100.google.com (74.125.67.100) 187 ms (TOS=0!) 209.85.255.190 (209.85.255.190) 171 ms (TOS=128!)

They appear to be filtering the traffic heavily. The last hop is their gateway firewall.

SEP