route add with netmask 255.255.0.0, dest dont respond !

[Xavier BLANC]

hello
current config : ( HPUX 11.23
local ip 192.168.158.10
mask 255.255.0.0
default route is 192.168.0.254 )

I need to add a new gateway :
dest = 192.168.110.0
mask = 255.255.255.0
gw = 192.168.0.254

- here what I've done
route add net 192.168.110.0 netmask 255.255.255.0 192.168.0.254
ping it's not ok neither traceroute ( stars and stars ...)
- 192.168.0.254 routing tableis ok ( other windows server are ok : on subnet 192.168.158)
- i can ping 192.168.0.254

here's is netstat -rnv
127.0.0.1/255.255.255.255 127.0.0.1 UH 0 lo0 4136
192.168.158.10/255.255.255.255 192.168.158.10 UH 0 lan0 4136
192.168.0.0/255.255.0.0 192.168.158.10 U 2 lan0 1500
192.168.110.0/255.255.255.0 192.168.0.254 UG 0 lan0 0
127.0.0.0/255.0.0.0 127.0.0.1 U 0 lo0 0
default/0.0.0.0 192.168.0.199 UG 0 lan0 0

I suspect the 192.168.0.0/255.255.0.0 192.168.158.10.
I read somewhere in this forum Gw should be on same subnet, normaly wih my mask

Please may some one help me to find an issue.
best regards

[Steven E. Protter · Accepted solution]

Shalom,

Your suspicions are correct. I believe the problem is the route you are defining is not valid.

You might need to talk to your network administrators to understand what the gateways already set up on your network are and what their addresses are.

SEP

[Asif Sharif]

Hi,

The problem seems to be network side, might be your network team didn't add route in router. GW can be in other subnet but with proper routing.

Regards,
Asif Sharif

[Duncan Edmonstone]

Xavier,

A couple of points:

1) You state your default gateway is 192.168.0.254, but according to the output of your netstat it is in fact 192.168.0.199.

2) If your current local subnet is 192.168.0.0, then I can't see how you can have another subnet of 192.168.110.0 as the routing tables are always going to think anything starting with 192.168 is for the local subnet - ask your network admins if they have this correct.

HTH

Duncan

[Xavier BLANC]

first of all sorry default gw is not 192.168.0.254 but really 192.168.0.199 as you can see on netstat.
Thank's to all for replying so quickly
192.168.100.0 route should help a remote user to connect the server via 192.168.0.254.

This is a customer config, as far as I know lan hosts are 192.168.0 mask 255.255.0.0
Some few servers including the HP are 192.168.158.0 mask 255.255.0.0
the default gw is an AD( win2003) I don't know why.

Then they had a remote site/users connecting these servers(192.168.158.x), so they ask me to add the new route.

To Asif : customer network team says the router is ok, the remote customer connect to other 192.168.158.* server : they say the router routes are properly configured.

To Duncan and Steven that's what I was thinking, most of the desktop PC are in
192.168.0.0 lan, they can connect the HP because lan mask is 255.255.0.0.
Now my question is : is it possible to remove 192.168.0.0/255.255.0.0 192.168.158.10
Will the lan 192.168.0 still able to connect to server . If yes, It should be possible to add the new route.

Hope my thought are clear ...

[Sandman!]

Let's see if I understand correctly what you want:

-- Segmenting the 192.168.0.0 address space into two subnets: 192.168.0.0 and 192.168.110.0.

-- lan0 of the host has IP 192.168.158.10 and falls in the 192.168.0.0 subnet.

The above is not possible no can't do. Based on the above config lan0 should fall in the 192.168.110.0 subnet but the routing table puts it in the 192.168.0.0 subnet. Need to reassign lan0's IP and subnet and then the route add net cmd will work. Here's how the routing table on your machine should look like:

127.0.0.1/255.255.255.255 127.0.0.1 UH 0 lo0 4136
192.168.158.10/255.255.255.255 192.168.158.10 UH 0 lan0 4136
192.168.110.0/255.255.255.0 192.168.158.10 U 2 lan0 1500
127.0.0.0/255.0.0.0 127.0.0.1 U 0 lo0 0

and you need to pick a new default gateway which is in the same subnet as your server ie 192.168.110.0

[Xavier BLANC]

sandman thank for your concern.
As I'm french I'm not sure of what you mean by "fall in subnet".
I'll try another aproach to explain. It's typically
local -> router1 ( wan) router2 <- remote
192.168.0 is local
192.168.15 is local
192.168.110 is remote
192.168.0.254 is router1
192.168.110.254 is router2
by local I mean same physical network I don't know why my customer have mask 255.255.0.0 and I must admit I've not worked a lot with these kind of mask's. they have some 192.168.0, 192.168.1, ...
Now my problem
I've 2 servers : one HP1(fail) and one win2003(Ok) .
1)----- HP1 lan0 ( ifconfig lan0
lan0: flags=1843
inet 192.168.158.10 netmask ffff0000 broadcast 192.168.255.255
netstat -rnv
Routing tables
Dest/Netmask Gateway Flags Refs Interface Pmtu
127.0.0.1/255.255.255.255 127.0.0.1 UH 0 lo0 4136
192.168.158.10/255.255.255.255 192.168.158.10 UH 0 lan0 4136
192.168.0.0/255.255.0.0 192.168.158.10 U 2 lan0 1500
192.168.110.0/255.255.255.0 192.168.0.254 UG 0 lan0 0
127.0.0.0/255.0.0.0 127.0.0.1 U 0 lo0 0
default/0.0.0.0 192.168.0.199 UG 0 lan0 0
traceroute 192.168.110.254
traceroute to 192.168.110.254 (192.168.110.254), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 * * *
... until the end.

2) win2003
ipconfig
Suffixe DNS propre à la connexion :
Adresse IP. . . . . . . . . . . . : 192.168.158.15
Masque de sous-réseau . . . . . . : 255.255.0.0
Passerelle par défaut . . . . . . : 192.168.0.199
route print
===========================================================================
===========================================================================
Itinéraires actifs :
Destination réseau Masque réseau Adr. passerelle Adr. interface Métrique
0.0.0.0 0.0.0.0 192.168.0.199 192.168.158.15 10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.0.0 192.168.158.15 192.168.158.15 10
192.168.110.0 255.255.255.0 192.168.0.254 192.168.158.15 1
192.168.135.0 255.255.255.0 192.168.0.254 192.168.158.15 1
192.168.158.15 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.158.255 255.255.255.255 192.168.158.15 192.168.158.15 10
192.168.222.0 255.255.255.0 192.168.158.20 192.168.158.15 1
224.0.0.0 240.0.0.0 192.168.158.15 192.168.158.15 10
255.255.255.255 255.255.255.255 192.168.158.15 192.168.158.15 1
Passerelle par défaut : 192.168.0.199
===========================================================================
Itinéraires persistants :
Adresse réseau Masque réseau Adresse passerelle Métrique
192.168.222.0 255.255.255.0 192.168.158.20 1
192.168.135.0 255.255.255.0 192.168.0.254 1
192.168.110.0 255.255.255.0 192.168.0.254 1

C:\>tracert 192.168.110.254
Détermination de l'itinéraire vers 192.168.110.254 avec un maximum de 30 sauts.
1 <1 ms <1 ms <1 ms 192.168.0.254
2 2 ms 2 ms 3 ms 10.250.0.5
3 18 ms 14 ms 15 ms 192.168.110.254

Itinéraire déterminé.

we can perfectly ping 192.168.110.254 from the win2003. From HPUX it fails.

Sorry but when someone says, "it's not possible" may he/she explain why it can work from windows and not from UNIX.
Forget to mention no firewall involve in this configuration.

Again, for me I can't see why adding route 192.168.110.0 with mask 255.255.255.0 cannot work ( I may be stupid :) ! ).

Sorry I try to explain the best I can, but I've a lack of english vocabulary.

[Eric SAUBIGNAC]

Bonjour Xavier,

D'abord arrete de jeter la pierre sur ton Anglais : le mien est au moins aussi mauvais, mais j'arrive a me debrouiller ;-)

Once this has been said, and though I am not a network guru, here are some suggestions :

1) -------

<<>>

I guess it would be a very, very bad idea. I think it is not possible, but if it would, you host would be no more reachable.

2) -------

<<<- here what I've done
route add net 192.168.110.0 netmask 255.255.255.0 192.168.0.254 >>>

Not possible, the metric is missing. You said later that routing table is :

<<<192.168.110.0/255.255.255.0 192.168.0.254 UG 0 lan0 0>>>

The "G" in UG means the route has been entered with a metric, that it is a Gateway. So wich metric did you used for this route ?

3) -------

Since we are speaking of metrics, take a look at the W2K's routing table and notice that default route has a metric of 10, and that the routes to the exception networks (192.168.100.0/24, 192.168.135/24 and 192.168.222.0/24) have a metric of 1.

Maybe you could try to modify HP-UX's routing table in the same way ? For example metric of 10 for the default route, 1 for the exceptions.

4) -------

I am a bit surprised by output of traceroute on the HP-UX box. No answer from 192.168.0.254. You said you can ping it. Still true ?

5) -------

What about routing tables on the client side, that is on 192.168.110.254 box ? Maybe there is a route to the only W2K box (192.168.158.15) ?

6) -------

<<>>

I think it can work. But the whole local network mask is 255.255.0.0 wich means that its is possible to have local boxes configured with an IP in the form 192.168.110.X/16. If you add this route to a remote 192.168.110.0 network, local 192.168.110.X boxes will be no more able to speak with the HP-UX.

Hope this will help ... and please be fair with my English ;-)

Regards

Eric

[Xavier BLANC]

Ok Eric I'm not sorry :) no problem

1) I understand why
2) you are true :(1) route add net 192.168.110.0 netmask 255.255.255.0 192.168.0.254 1
3) I've tried this
route add default netmask 0.0.0.0 192.168.0.199 10
route add net 192.168.110.0 netmask 255.255.255.0 192.168.0.254 1
after deleting previous route, with no more chance.
is "route count" same as metrics ????
4) - I can ping 192.168.0.254
and I'm suprised too ...
5) the admin customer says no : he has verified, he has several win 2003 srv samples, I must be confident with him, he really seems ok and have spent time searching. On an other side you can never know !
6) I agree, I have already said that to them.
That was my first argument before they said to me the @#&ù{@ "ok but why windows is working well"

I understand this lan config is not really ok, I'm just unable to explain why, and more I was thinking it should work.

Can someone tell me about : default route ->
route add default netmask 0.0.0.0 192.168.0.199 10
( in particular mask 0.0.0.0 )


and what about count ? does'it works like metrics ?

[Eric SAUBIGNAC]

Xavier,

3)
The good syntax for default route is not :

route add default netmask 0.0.0.0 192.168.0.199 10

It is simply :

route add default 192.168.0.199 10

It seems to work, but on an other side you can never know side effects.

3) again
<<>>

I guess it is. "man route" does'not speak in terms of metrics but I understood it has the same impact.

Well, I have very few ideas now to help you. Do you think it is possible to have routing tables of remote router in 192.168.110.0/24 network, local router 192.168.0.254 and local router 192.168.0.199 ?

Regards

Eric

[Xavier BLANC]

I've tried route add default 192.168.0.199 10
same problem.
I'm waiting for the router's route tables.

un 10 point pour les efforts. ca me fait plaisir.

[Sandman!]

One more thing...post the output of the arp table on both the HP-UX server and the Windoze machine. The command "arp -a" should work on the Windoze box and "arp -an" on the HPUX server.

~thanks