Networking in Shared-IP Non-Global Zones
On a Solaris system with zones installed, the zones can communicate with each other
over the network. The zones all have separate bindings, or connections, and the
zones can all run their own server daemons. These daemons can listen on
the same port numbers without any conflict. The IP stack resolves conflicts by
considering the IP addresses for incoming connections. The IP addresses identify the zone.
Shared-IP Zone Partitioning
The IP stack in a system supporting zones implements the separation of network
traffic between zones. Applications that receive IP traffic can only receive traffic sent
to the same zone.
Each logical interface on the system belongs to a specific zone, the global
zone by default. Logical network interfaces assigned to zones though the zonecfg utility
are used to communicate over the network. Each stream and connection belongs to
the zone of the process that opened it.
Bindings between upper-layer streams and logical interfaces are restricted. A stream can only
establish bindings to logical interfaces in the same zone. Likewise, packets from a
logical interface can only be passed to upper-layer streams in the same zone
as the logical interface.
Each zone has its own set of binds. Each zone can be
running the same application listening on the same port number without binds failing
because the address is already in use. Each zone can run its own
version of the following services:
Internet services daemon with a full configuration file (see the inetd(1M) man page)
sendmail (see the sendmail(1M) man page)
apache (see the apache(1M) man page)
Zones other than the global zone have restricted access to the network. The
standard TCP and UDP socket interfaces are available, but SOCK_RAW socket interfaces are
restricted to Internet Control Message Protocol (ICMP). ICMP is necessary for detecting and
reporting network error conditions or using the ping command.
Shared-IP Network Interfaces
Each non-global zone that requires network connectivity has one or more dedicated IP
addresses. These addresses are associated with logical network interfaces that can be placed
in a zone by using the ifconfig command. Zone network interfaces configured by
zonecfg will automatically be set up and placed in the zone when it
is booted. The ifconfig command can be used to add or remove logical
interfaces when the zone is running. Only the global administrator can modify the
interface configuration and the network routes.
Within a non-global zone, only that zone's interfaces will be visible to ifconfig.
For more information, see the ifconfig(1M) and if_tcp(7P) man pages.
IP Traffic Between Shared-IP Zones on the Same Machine
Between two zones on the same machine, packet delivery is only allowed if
there is a “matching route” for the destination and the zone in the
The matching information is implemented as follows:
The source address for the packets is selected on the output interface specified by the matching route.
By default, traffic is permitted between two zones that have addresses on the same subnet. The matching route in this case is the interface route for the subnet.
If there is a default route for a given zone, where the gateway is on one of the zone's subnets, traffic from that zone to all other zones is allowed. The matching route in this case is the default route.
If there is a matching route with the RTF_REJECT flag, packets trigger an ICMP unreachable message. If there is a matching route with the RTF_BLACKHOLE flag, packets are discarded. The global administrator can use the route command options described in the following table to create routes with these flags.
Emit an ICMP unreachable message when matched.
Silently discard packets during updates.
For more information, see the route(1M)
Solaris IP Filter in Shared-IP Zones
Solaris IP Filter provides stateful packet filtering and network address translation (NAT). A
stateful packet filter can monitor the state of active connections and use the
information obtained to determine which network packets to allow through the firewall. Solaris
IP Filter also includes stateless packet filtering and the ability to create and
manage address pools. See Chapter 25, Solaris IP Filter (Overview), in System Administration Guide: IP Services for additional information.
Solaris IP Filter can be enabled in non-global zones by turning on
loopback filtering as described in Chapter 26, Solaris IP Filter (Tasks), in System Administration Guide: IP Services.
Solaris IP Filter is derived from open source IP Filter software.
IP Network Multipathing in Shared-IP Zones
IP network multipathing (IPMP) provides physical interface failure detection and transparent network access
failover for a system with multiple interfaces on the same IP link. IPMP
also provides load spreading of packets for systems with multiple interfaces.
All network configuration is done in the global zone. You can configure IPMP
in the global zone, then extend the functionality to non-global zones. The functionality
is extended by placing the zone's address in an IPMP group when you
configure the zone. Then, if one of the interfaces in the global zone
fails, the non-global zone addresses will migrate to another network interface card.
In a given non-global zone, only the interfaces associated with the zone are
visible through the ifconfig command.
See How to Extend IP Network Multipathing Functionality to Shared-IP Non-Global Zones. The zones configuration procedure is covered in How to Configure the Zone. For information on
IPMP features, components, and usage, see Chapter 27, Introducing IPMP (Overview), in System Administration Guide: IP Services.