Mike Gerdts writes:
> On Dec 3, 2007 5:43 AM, James Carlson <[EMAIL PROTECTED]> wrote:
> > It doesn't always work very well, which is why I generally recommend
> > against /etc/netmasks. It may have been an ok interface 20 years ago,
> > but with CIDR, it's mostly a defect looking for a place to h
On Dec 3, 2007 8:45 AM, James Carlson <[EMAIL PROTECTED]> wrote:
> Besides the look-up ambiguity, there are also the chicken-and-egg
> problems that occur when users accidentally configure the system to
> use NIS or some other directory service for netmask resolution.
> Trying to configure an inter
On Dec 3, 2007 5:43 AM, James Carlson <[EMAIL PROTECTED]> wrote:
> It doesn't always work very well, which is why I generally recommend
> against /etc/netmasks. It may have been an ok interface 20 years ago,
> but with CIDR, it's mostly a defect looking for a place to happen.
If using only a loca
Jordan Brown (Sun) writes:
> OTOH, I don't immediately understand how the example can work. It says
> that 128.32.*.* (except for the exclusions) gets a 24-bit netmask, but I
> don't see how that can be unambiguously determined. The example *seems*
> to want to explicitly specify a 28-bit netm
[EMAIL PROTECTED] wrote:
> What does the "netmasks" entry in /etc/nsswitch.conf say? A common
> issue is that a user changes their local /etc/netmasks file but their
> the switch says to use something like "nis".
Bingo! Thanks!
>> (I also tried 172.20.0.0 on the theory that maybe it wanted me t
> zoneadm: zone 'int-sagent-1-z1': WARNING: bge0:1: no matching subnet
> found in netmasks(4) for 172.20.46.188; using default of 255.255.0.0.
>
> but my /etc/netmasks (on both the global and local zone) looks good:
What does the "netmasks" entry in /etc/nsswitch.conf say? A common
issue is that
Antonello Cruz wrote:
> I would definitely run
>
> zonecfg -z int-sagent-1-z1 info
>
> to check what the zone thinks is the netmask.
Doesn't display a netmask.
> I suspect if you haven't defined the '/24' it will pick the default for
> the address class. In this case, '/16' IIRC.
> Sometimes d
I would definitely run
zonecfg -z int-sagent-1-z1 info
to check what the zone thinks is the netmask.
I suspect if you haven't defined the '/24' it will pick the default for
the address class. In this case, '/16' IIRC.
Sometimes documentation gets old...
Antonello
Jordan Brown (Sun) wrote:
> An
Antonello Cruz wrote:
>> zoneadm: zone 'int-sagent-1-z1': WARNING: bge0:1: no matching subnet
>> found in netmasks(4) for 172.20.46.188; using default of 255.255.0.0.
> How did you setup the IP address for that zone?
>
> Did you use, in zonecfg:
> zonecfg:int-sagent-1-z1:net> set address=172.20.4
Jordan,
How did you setup the IP address for that zone?
Did you use, in zonecfg:
zonecfg:int-sagent-1-z1:net> set address=172.20.46.188/24
?
Antonello
Jordan Brown (Sun) wrote:
> I get:
>
> zoneadm: zone 'int-sagent-1-z1': WARNING: bge0:1: no matching subnet
> found in netmasks(4) for 172.20.
I get:
zoneadm: zone 'int-sagent-1-z1': WARNING: bge0:1: no matching subnet
found in netmasks(4) for 172.20.46.188; using default of 255.255.0.0.
but my /etc/netmasks (on both the global and local zone) looks good:
172.20.46.0255.255.255.0
(I also tried 172.20.0.0 on the theory that maybe
11 matches
Mail list logo
