Hello everybody,
Sorry for the long delay, but here is the summary :-)
Original post:
We have a SPARC2 that doesn't recognized its netmask addresses using the file
S72inetsvc during the boot sequence. In the file S72inetsvc their is the
line:
/usr/sbin/ifconfig -au netmask + broadcast +
The file /etc/netmasks contains two lines (we have two ethernet card on that
machine) saying
<interface1 network number> <netmask1>
<interface2 network number> <netmask2>
Ex: 132.176.144.0 255.255.254.0
The file /etc/nsswitch.conf has an entry saying:
networks: files
For me, everything seems OK! But that does not work!
I have to specify new lines in /etc/rc2.d/S72inetsvc specifying directly
the netmasks used for each ethernet card :-(
What is wrong?
====================================================================
====================================================================
The problem was that 132.176.144.0 is a class B address and that inside
the /etc/netmasks file I must have only network number. So instead of having:
132.176.144.0 255.255.254.0,
I should have:
132.176.0.0 255.255.254.0
So I learned that I can't use network number with subnetting in that file and
the reason (see below) is very logical.
Thank to everybody, you just proved me once again how it is valuable to
be a member of this list!
Here the answer of Torsten Metzner that resume very well the solution to
my problem. (Solution shared by almost everybody that replied):
Hello Michel,
if you want to use the netmasks from your local files you have to specify
this. For this reason there must be the:
netmasks: files
entry in your /etc/nsswitch.conf .
The entry in the /etc/netmasks file is wrong.
132.176.144.0 is a class B address, so the network number is 131.176
The correct entry would be.
132.176.0.0 255.255.254.0
Some more remarks to this:
(1) Your network number, without subnetting, is 132.176.0.0
(2) Your network number, with subnetting, is 132.176.144.0
(3) The network number in the /etc/netmasks had to be the network number
without subnetting. Why:
(a) That's the way it works {;-)
(b) Sorry (a) was a little joke. With your netmask you are using
subnetting, but on what net are you using subnetting ?
On your official class B network ! So this network ( 132.176 )
is divided in subnets with the netmask and that's the reason why you
have to use the official class B address.
(4) An example from our net. On a machine in the 131.234.104.0 net ( with
subnetting ) we have the following /etc/netmasks entry and no problems.
131.234.0.0 255.255.254.0
Hope this helps and forgive me my bad english,
Torsten.
-------------------
Thanks alot to:
Torsten Metzner <tom@plato.uni-paderborn.de>
Cameron Humphries <Cameron.Humphries@camtech.com.au>
Leif Hedstrom <leif@infoseek.com>
"Endre Polgar Technical Support Engineer ICON Ltd." <epolgar@petra.icon.hu>
rwh@atmos.albany.edu (Ronald W. Henderson)
clg@zygote.csph.psu.edu (Craig Gruneberg)
twoln@mat.uni.torun.pl (Tomasz Wolniewicz)
kao@artecon.artecon.com (Philip Kao)
garcia@f18sunc.chinalake.navy.mil (Mike Garcia)
miket@Seagate.COM (Michael Tripoli)
sho@oaktech.com (Steven Ho)
"David Evans" <djve@deakin.edu.au>
-- \\~ ~// ( o o ) ---------------------------o00o--0--o00o------------------------- Michel Pilon E-mail: michel.pilon@CCG.RNCan.gc.ca Administrateur de systemes Unix Tel: (819) 564-5600 ext.4819 Centre Canadien de Geomatique Fax: (819) 564-5698 2144 King Ouest, suite 010, Sherbrooke, Quebec, Canada, J1J 2E8
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:35 CDT