1nwamd(1M) System Administration Commands nwamd(1M)
2
6 nwamd - network auto-magic daemon
7
9 /lib/inet/nwamd
10
13 nwamd is a system daemon to manage network interfaces.
14 This daemon is started automatically and should not be invoked
17 directly. It does not constitute a programming interface.
18 Operation
20 Whether this daemon is enabled or not depends on your installation
21 medium. To check from within the GNOME desktop environment, double
22 click on the "Network Manager" icon to open the "Connection Properties"
23 window. If "Configure network automatically" is checked, then auto-
24 magic mode is enabled. To check from the command line, enter the fol‐
25 lowing:
26 % svcs svc:/network/physical
28 Two instances will be listed, one online and the other disabled. If the
33 "nwam" instance is online, then this daemon is running.
34 To switch between manual and auto-magic mode, you can use the Network
37 Monitor applet available within the GNOME desktop environment. You can
38 also switch manually from the command line by entering:
39 % svcadm disable svc:/network/physical:default
41 % svcadm enable svc:/network/physical:nwam
42 To go from auto-magic mode to manual mode:
47 % svcadm disable svc:/network/physical:nwam
49 % svcadm enable svc:/network/physical:default
50 When switching modes like this, keep in mind that all network inter‐
55 faces will be brought down then back up. Therefore, if a different IP
56 address is configured in this process, existing applications and ses‐
57 sions might be disrupted.
58 There is a limitation that only one link is active at a time in auto-
61 magic mode. This mode is not recommended for machines that use more
62 than one link at a time. For machines with wired and wireless links,
63 wired link are preferred by default, although this can be adjusted from
64 the GNOME NWAM Manager menu (right-click on the icon), or from the com‐
65 mand line, by editing the plain text file /etc/nwam/llp. For the lat‐
66 ter (hand-editing) procedure, the first instance of a link in
67 /etc/nwam/llp sets the priority of that link. Subsequent instances of
68 that link set parameters associated with the interface on that link.
69 The /etc/nwam/llp interface is volatile and might change in a future
72 release.
73 Static IP Addresses
75 A static IP address can be configured by changing the line in the
76 /etc/nwam/llp file that contains an interface name and the name of the
77 method for obtaining an IP address. It might look like:
78 nge0 dhcp
80 Change this line to one that looks like:
85 nge0 static I1.I2.I3.I4/P
87 ...where the I's are the digits of the IPv4 address and the P is an
92 optional prefix. If the prefix is not provided, it is derived, using
93 classful assumptions.
94 Configuring IPv6
96 IPv6 is configured by default on a link. It can also be explicitly
97 added in the /etc/nwam/llp file by providing a line that contains an
98 interface name and the string ipv6. It might look like:
99 nge0 ipv6
101 If IPv6 should not be plumbed on a given link, a noipv6 entry should be
106 created in the /etc/nwam/llp file for that link. It might look like:
107 nge0 noipv6
109 An optional static IPv6 address can be provided on the same line, imme‐
114 diately after the ipv6 token. Whether you provide a static address or
115 not, IPv6 will use DHCPv6 or stateless address configuration, as
116 directed by the local network configuration.
117 PROFILES
119 All interfaces listed in this section are volatile and may change in a
120 future release. They are documented here so that those wishing to
121 experiment with this may do so.
122 Profiles are a mechanism for making multiple related changes to the
125 system configuration after IP service is available.
126 There is no direct support for the profiles yet, but a "roll your own"
129 mechanism is provided for now. Once an interface is brought up and an
130 IP address is configured for it, the daemon looks for the file
131 /etc/nwam/ulp/check-conditions. If this file exists and is executable,
132 it is run. This should print a single line of output, which is the name
133 of the profile that the user wishes to activate based on the current
134 conditions. If such a line is read successfully (foo in this example),
135 then /etc/nwam/ulp/foo/bringup is executed. Likewise, when the inter‐
136 face gets torn down for whatever reason, /etc/nwam/ulp/foo/teardown is
137 executed. The "bringup" and "teardown" scripts are invoked via
138 pfexec(1) with default basic privileges. Samples for each of these
139 scripts can be found at:
140 o http://opensolaris.org/os/project/nwam/prototype/check-con‐
142 ditions
143 o http://opensolaris.org/os/project/nwam/prototype/bringup
145 o http://opensolaris.org/os/project/nwam/prototype/teardown
147 Wireless
149 If no wired link is available, a scan for wireless LANs is done, and
150 the resulting list offered via a GUI popup window prompts the console
151 user to select a preference. If a successful connection is made, the
152 WLAN in question is stored in the plain text file
153 /etc/nwam/known_wifi_nets and the daemon may connect to any WLAN in
154 that list without prompting the user again. If a user wishes to add
155 other preferences or revoke existing ones, he can do so by bringing up
156 the NWAM Manager menu with right-click on the icon, and then selecting
157 "Manage Favorite Wireless Networks...". A user can also edit the
158 known_wifi_nets file directly. This interface is volatile and might
159 change in a future release.
160
162 See attributes(5) for descriptions of the following attributes:
163 ┌─────────────────────────────┬─────────────────────────────┐
168 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
169 ├─────────────────────────────┼─────────────────────────────┤
170 │Availability │SUNWcsr │
171 ├─────────────────────────────┼─────────────────────────────┤
172 │Interface Stability │Volatile │
173 └─────────────────────────────┴─────────────────────────────┘
174
176 svcs(1), svcadm(1M), attributes(5), smf(5)
177 See also nwam-manager(1M), available in the JDS/GNOME man page collec‐
180 tion.
181
183 The networking service is managed by the service management facility,
184 smf(5), under the service identifier:
185 svc:/network/physical
187 Administrative actions on this service, such as enabling, disabling, or
192 requesting restart, can be performed using svcadm(1M). The service's
193 status can be queried using the svcs(1) command.
194SunOS 5.11 24 Nov 2008 nwamd(1M)