Re: [foxboro] IP MASKS

I am not sure that will work.  Net 172.27.0.0 with a netmask only includes 
the address ranges 172.16.0.1 - 172.16.1.254 and therefore does not match 
his le1 address.  He would only be part of the class B network if his 
netmask were also class B, i.e., 255.255.0.0.  But maybe such an entry 
includes all such networks -- 172.16.2.1 to 172.16.3.254, 172.16.4.1 to 
172.16.5.254, etc.  I don't have a Sun box I can break to test it.


It is hard to believe that Solaris 2.5.1 fell off of Sun's radar before 
CIDR became popular.


Corey Clingo
BASF Corporation






"Dumitru, Alex" <alex.dumitru@xxxxxxxxxxxxxxxx> 
Sent by: foxboro-bounce@xxxxxxxxxxxxx
10/17/2006 04:15 PM
Please respond to
foxboro@xxxxxxxxxxxxx


To
foxboro@xxxxxxxxxxxxx
cc

Subject
Re: [foxboro] IP MASKS






Your IP address 172.27.8.74 on the second Ethernet port indicates that 
your
AW is part of the Class B network (128-191) 172.27.0.0.
So the entry you need to add to the /etc/netmasks file shoud be:
172.27.0.0      255.255.254.0

This should not impact your Nodebus settings since these are on a 
different
Class B network (151.128.0.0).

Regards,

Alex Dumitru, Eng.
SI & IT
Invensys Systems Canada Inc.
Phone: (514) 421 8073
Fax:   (514) 421 8054

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
Sent: Tuesday, October 17, 2006 4:05 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] IP MASKS

Hi Alex,

This netmasks file affect the I/A addressing?
In my case I need use 255.255.254.0 as our mask, with the 172.27.8.74 IP =
address, what I need to configure?

Best regards and thanks for your help.

Cordial saludo,
__________________________________________
=20
Pedro I. Caraballo A.                                   =20
Smurfit Kappa Cart=F3n de Colombia S.A.
Mantenimiento E&I
-----Mensaje original-----
De: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] = 
En
nombre de Dumitru, Alex Enviado el: Martes, 17 de Octubre de 2006 02:58 
p.m.
Para: foxboro@xxxxxxxxxxxxx
Asunto: Re: [foxboro] IP MASKS

The particularity of Solaris 2.5.1 is that netmasks can only be defined =
for a network number that is a class A, B or C network number.
For example, you cannot define a netmask for the 10.19.123.0 network =
(class
A) but you can define a netmask for the 10.0.0.0 network.
So some limited masking can be exercised but with care...
AW5101# more /etc/netmasks
#
# The netmasks file associates Internet Protocol (IP) address # masks with
IP network numbers.
#
#       network-number  netmask
#
# The term network-number refers to a number obtained from the Internet
Network # Information Center.  Currently this number is restricted to 
being
a = class # A, B, or C network number.  In the future we should be able to
support # arbitrary network numbers per the Classless Internet Domain
Routing # guidelines.
#
# Both the network-number and the netmasks are specified in # "decimal 
dot"
notation, e.g:
#
#               128.32.0.0 255.255.255.0
#
# AD 2006/05/05
10.0.0.0 255.255.255.0
AW5101# ifconfig -a
lo0: flags=3D849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000
le0: flags=3D863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet 151.128.8.65 netmask ffff0000 broadcast 151.128.255.255
ether 8:0:20:76:77:3b
le1: flags=3D863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet 10.19.123.199 netmask ffffff00 broadcast 10.19.123.255 =
<------
This mask is the result of the entry in /etc/netmasks !
ether 8:0:20:76:77:3b





Alex Dumitru, Eng.
SI & IT
Invensys Systems Canada Inc.
Phone: (514) 421 8073
Fax:   (514) 421 8054


=20
=20
_______________________________________________________________________


 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: