SUMMARY: 240 Subnet /etc/netmasks problem

Thanks to Matt Harris and Marco Greene for their quick responses.
Matt had the solution:
/etc/netmasks will fix you up for startup if the system's ip is on that
subnet. Otherwise, you need `route add -net 192.168.54.48 <gateway> netmask
255.255.255.240`
It only needed slight modification:
route add -net 192.168.54.48 -netmask 255.255.255.240 10.20.1.3
Thanks to everyone for their help,
-JohnF
-----Original Message-----
From: John Marrett
Sent: March 17, 2003 10:15 AM
To: 'sunmanagers@sunmanagers.org'
Subject: 240 Subnet /etc/netmasks problem
First let me say that I checked the faqs, google, sunsolve, etc... It's
possible I missed something but I did look.
I need to configure a route on a system to reach a subnetted (netmask
255.255.255.240) network. I have tried a number of different settings in the
/etc/netmasks file but when I add the route for the network I invariably end
up creating a route to the class C and not the subnet.
These are a few attempted /etc/netmasks files.
First I tried the following format (based on past experience):
192.168.0.0 255.255.255.0
192.168.54.0 255.255.255.240
192.168.54.16 255.255.255.240
192.168.54.32 255.255.255.240
192.168.54.48 255.255.255.240
Then I tried the following as suggested on sunsolve:
192.168.54 255.255.255.240
This is the command I am using to add the route.
ptimbwm1# route add -net 192.168.54.48 10.20.1.3
add net 192.168.54.48: gateway 10.20.1.3
And this is what the route invariably looks like:
ptimbwm1# netstat -rn
[...]
192.168.54.0 10.20.1.3 UG 1 0
[...]
Does anyone know what setting I should use in the /etc/netmasks file to have
the route for the subnet exclusively? I should add that I have changed the
IPs and they are in fact real Internet IPs, not private network IPs as shown
here.
Thanks in advance for your help,
-JohnF
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers