The following is a detailed description of each of profile types that are supported in the Oracle Solaris release.
An NCP defines system-specific network configuration, for example datalinks and IP interfaces and addresses. The various NCUs (network configuration units) that are part of each NCP specify how to configure the various network links and interfaces, for example, which interface or interfaces should be brought up, and under what conditions that interface should be brought up, as well as how the IP address for the interface is obtained.
The Automatic NCP represents all of the network links and interfaces that are currently in the system. The content of the Automatic NCP changes if network devices are added or removed. The Automatic NCP provides access to a profile that utilizes DHCP address autoconfiguration, which makes it possible to obtain IP addresses for the system. This NCP also implements a link selection policy that favors wired links over wireless links. If the specification of an alternate IP configuration policy or an alternate link selection policy is required, you would need to create another NCP on your system. You cannot delete the Automatic NCP. You can copy this NCP and make changes to the copy. See Example 6–7.
NCUs contain the property values that define an NCP. NCUs represent the individual physical links and interfaces that are on a system. The process of configuring a user-defined NCP includes creating NCUs that specify how and under what conditions each link and interface should be configured.
There are two types of NCUs:
Link NCUs – Represent physical devices (Layer 2 entities in the Open Systems Interconnection (OSI) model)
Interface NCUs – Represent IP interfaces (Layer 3 entities)
Link NCUs represent the following datalink layer classes:
Aggregations
Bridges
Etherstubs
Ethernet over IB (EoIB),
Physical links (Ethernet or WiFi)
Tunnels
Virtual eXtensible local areal networks (VXLANs)
Virtual local area networks (VLANs)
Virtual network interface cards (VNICs)
Interface NCUs represent the following IP layer classes:
IP interfaces
IPMP interfaces
VNI interfaces
For information about the properties that you can set for the various object types, see the netcfg(1M) man page.
A Location profile (also referred to simply as a Location) consists of network configuration information such as naming services and firewall settings that are applied together to specify system-wide network configuration when that Location is active. Because a Location does not necessarily correspond to a physical location, you can set up several Location profiles to meet different networking needs. For example, one Location can be used when you are connected to the company intranet. Another Location can be used when you are connected to the public Internet by using a wireless access point that is located in your office.
By default, there are three Locations that are predefined by the system:
DefaultFixed
The DefaultFixed Location is enabled whenever the DefaultFixed NCP is active. The DefaultFixed Location cannot be directly modified by the using the netcfg command. When this Location is enabled (as part of enabling the DefaultFixed NCP), the relevant Service Management Facility (SMF) properties are updated to reflect the settings of the Location. When the system is shut down or another Location is enabled, the relevant SMF properties are saved as part of the DefaultFixed Location's configuration.
Automatic
The Automatic Location is activated if there are networks available but no other Location supersedes it. You can modify the Automatic Location by using the netcfg command.
NoNet
The NoNet Location has very specific activation conditions. This Location is applied by the system to a stand-alone system when no local interfaces have an assigned IP address. You can modify the NoNet Location by using the netcfg command.
User-defined Locations are identical to system-defined Locations, with the exception that a user-defined Location is configured with custom values that you specify, while system-defined Locations have preset values.
ENMs enable you to specify when applications or scripts should perform network configuration that is external to the configuration that is specified in the NCP and Location profiles. ENMs can also be defined as services or applications that directly modify your network configuration when they are enabled or disabled. You can specify the conditions under which an ENM should be enabled or disabled. You can also enable or disable an ENM manually. Unlike an NCP or a Location profile, where only one of each profile type can be active on the system at any given time, multiple ENMs can potentially be active on the system at the same time. The ENMs that are active on a system at any given time are not necessarily dependent on the NCP or Location profile that is also enabled on the system at the same time.
Although there are several external applications and services for which you can create an ENM, the obvious example is the VPN application. After you install and configure VPN on your system, you can create an ENM that automatically activates and deactivates VPN under the conditions that you specified.
Persistent information about any network configuration that is performed by an ENM is not stored or tracked in exactly the same way that information about an NCP or a Location profile is stored. However, the system is capable of noting an externally initiated network configuration, and then based on any configuration changes that are made to the system by an ENM, reevaluating which Location should be active, and subsequently activating that Location. An example would be switching to a Location that is activated conditionally when a certain IP address is in use. If the svc:/network/physical:default service is restarted at any time, the network configuration that is specified by the active NCP is reinstated. ENMs are restarted as well, possibly tearing down and recreating network configuration in the process.
Known WLANs are profiles that are used to manage wireless networks that are known to the system. A global list of these known wireless networks is then maintained by the system. This information is used to determine the order in which attempts to connect to available wireless networks are made. If a wireless network that exists in the Known WLAN list is available, the system automatically connects to that network. If two or more known wireless networks are available, the system attempts to connect to the wireless network with the highest priority (lowest number). Any new wireless network that you connect to is automatically added to the top of the Known WLAN list and becomes the current highest priority wireless network.
The default behavior is to prefer more recently connected WLANs over WLANs that you connected to previously. At no time can any Known WLAN share the same priority. If a new WLAN is added to the list with the same priority value as an existing WLAN, the existing entry is shifted to a lower priority value. Subsequently, the priority value of every other WLAN in the list is dynamically shifted to a lower priority value.
One key name can also be associated with a Known WLAN. A Key name enables you to create your own key by using the dladm create-secobj command. You can then associate this key with WLANs by adding the secure object names to the WLAN keyname property. For more information, see the dladm(1M) man page.
For more information managing WLANs from the command line, see Administering Known WLANs in Reactive Mode.