also look at your netmasks. if the clients are a router hop away, and your netmasks are off, you won't connect. i have had this happen on some configs when i wasn't careful to add the netmask to the net->address config line, or did not update /etc/netmasks in the zone itself. i'll see errors on the terminal where i start the zone.

Just a clarification that /etc/inet/netmasks is not really used within
the zone itself.  The copy in the *global zone* does get referenced
when a zone boots in order to determine the correct netmask to apply to
any "net" resources specified for the zone that are 1) for the IPv4
family and 2) don't explicitly specify the subnet's prefix length.

zones-discuss mailing list

Reply via email to