adding a route

[WilliamSmith11]

Hi I two machine running hpux 11.23 they are in separate site, separate networks

Site A machine have IP address 172.16.180.37
Mask 255.255.0.0 Gateway 172.16.180.1

Site B Machine have IP address 10.1.11.7
Mask 255.255.0.0 Gateway 10.1.255.253

I have try differents command to add route and trying to connect from one site to the other and viceversa.

SITE B
#route add net 10.1.0.0 netmask 255.255.0.0 172.16.180.1 1


for the other site I do as follow

SITE A
#route add net 172.16.0.0 netmask 255.255.0.0 10.1.255.253 1

[Steven Schweda]

> Site A machine have IP address 172.16.180.37
[...]
> SITE A
> #route add net 172.16.0.0 [...]

Doesn't site A already know how to find
172.16.x.x? Why add a route for that?

Saying "add route" does not connect two
separate networks. A network router (and
some wire or equivalent medium) can do that
job. After you add a router, you can start
to worry about adding routes.

If you already have a router, you need to
know its IP addresses on each of your
existing networks.

[Eric SAUBIGNAC]

Hi William,

----
Site A machine have IP address 172.16.180.37
Mask 255.255.0.0 Gateway 172.16.180.1

Site B Machine have IP address 10.1.11.7
Mask 255.255.0.0 Gateway 10.1.255.253
----

Does "Gateway" mean that you have configured a default route on both HP-UX boxes ? So you should not need to configure more routes to enable traffic between 2 HP-UX (of course I suppose that routers themselves are correctly configured)

Could you show us the result of "netstat -rn" ?

Eric

[Matti_Kurkela]

Note that both your network segments are "private" or "non-routable" networks. Those addresses are *not* globally unique: anyone can re-use them in their private networks. When viewed from the outside (=from the internet), these private networks are usually hidden behind some sort of a NAT scheme.

Unless the network admins of those two sites are cooperating and have arranged for a routing between your two sites, you cannot solve your problem with any "route" commands.

For example, the router on the Site A's border (between Site A and the internet) will see packets coming from 172.16.180.37 with a destination of 10.1.255.253. Now it has a problem: the router is likely to see either multiple overlapping 10.1.*.* networks (if the owners of those networks have not properly filtered their outgoing traffic) or none at all. If it sees multiple hosts with the address 10.1.255.253, how is it going to know which one is correct?

If both your sites and the WAN connections between them all belong to the same organization, your routing *might* work if the WAN administrator has specifically made it possible.

If there are different organizations and/or different ISPs involved, routing from one private network segment to another private segment over the public Internet is unlikely to work like that, except by accident. You would need some knowledge about both sites' NAT schemes and/or a VPN tunnel between the sites to solve this problem.

Contact your network admin(s) to solve this problem: it's likely you cannot do it without their help.

MK