Wiki code for NWAM Phase 0.5 Troubleshooting

Hide Line numbers
1: == Troubleshooting Network Problems
2: 
3: 1. Is NWAM enabled?
4:  To determine if NWAM is running, double-click on the Network Monitor applet. If you don’t have that in your panel (it normally shows the two-computer icon if connected to a wired network or the radio wave icon if on wireless), then right-click and add it to the panel. The status screen will indicate if automatic mode is enabled via a checkbox.
5:  To check from the command line, run:
6: 
7: {{{
8: % svcs physical
9: }}}
10: 
11:  If NWAM is running, you should see:
12: 
13: {{{
14: STATE          STIME    FMRI
15: disabled       15:18:18 svc:/network/physical:default
16: online         16:44:23 svc:/network/physical:nwam
17: }}}
18: 
19:  If you see this instead:
20: 
21: {{{
22: STATE        STIME    FMRI
23: online       15:18:18 svc:/network/physical:default
24: disabled     16:44:23 svc:/network/physical:nwam
25: }}}
26: 
27:  then NWAM is not enabled, and doing the following will reenable it:
28: 
29: {{{
30: # svcadm disable network/physical:default
31: # svcadm enable network/physical:nwam
32: }}}
33: 
34:  On the OpenSolaris distribution, preface those two svcadm commands with "pfexec".
35: 1. Driver problems?
36:  To determine if drivers have attached successfully for your network devices, run:
37: 
38: {{{
39: % ifconfig -a
40: }}}
41: 
42:  If you see only
43: 
44: {{{
45: lo0: flags=2001000849 mtu 8232 index 1
46:         inet 127.0.0.1 netmask ff000000 
47: lo0: flags=2002000849 mtu 8252 index 1
48:         inet6 ::1/128 
49: }}}
50: 
51:  Then try this command to list the network hardware known to the system:
52: 
53: {{{
54: # dladm show-link
55: }}}
56: 
57:  If these commands fail to list network interfaces, or if the "ifconfig" output shows only the loopback interfaces, then you likely need drivers or need to update /etc/driver_aliases for the devices you have. [[The laptop community>>Community Group laptop.WebHome]] is a great resource for troubleshooting these sorts of issues.
58: 1. Wireless problems
59:  First, ensure that your wireless device is present:
60: 
61: {{{
62: # dladm show-link
63: }}}
64: 
65:  Now to determine if the wireless device can see any WLANs, run
66: 
67: {{{
68: # dladm scan-wifi
69: }}}
70: 
71:  If the scan is picking up WLANs, we know wireless is working, so there may be an NWAM-specific problem.
72:  Note: for systems running the OpenSolaris distribution, each of those dladm commands should be prefixed with "pfexec".
73: 1. Wireless/WEP/DHCP problems
74:  Because of the way authentication works with WEP, there is no definitive indication of keying problems: if an incorrect key is given, the connection to the AP will succeed, but packets will not move.
75:  If you are connected to a WEP-protected network, the NWAM Manager applet will wait a few seconds after the connection attempt is started, and then prompt for a new key if DHCP has not yet succeeded. This is only a heuristic; there is no way for the system to determine whether a new key is actually needed. Supplying a new key at this point will delete the old key and retry; this may resolve the problem.
76:  From the perspective of the nwam daemon, the connect operation succeeds, and then DHCP is started, but never acquires a lease. Since the DHCP protocol does not have a time limit, the DHCP client will continue to try to connect; in this case, there is no protocol-defined way to distinguish between an authentication failure and a missing/slow DHCP server.
77: 1. Wired/wireless preferences
78:  By default, NWAM prefers, and will first try to configure, plugged in wired interfaces. If this fails, it will fall back to wireless. In cases where drivers do not support notifications of plugging/unplugging, NWAM may erroneously assume the wired devices are plugged in, and may take a minute to notice apparent failure. (This time is tunable using svccfg to adjust "nwamd/dhcp_wait_time.")
79:  If a more-preferred interface becomes available (e.g., if you plug in a wired network connection), NWAM will switch to that interface and shut down the previous one.
80:  If you wish to change the preference order of network devices, right click on the NWAM Manager icon, and select "Network Interface Priority..." to adjust the priority of the interfaces. These changes are saved in a file, and will be retained across reboot.
81:  Alternatively, you can select one of the "Always use ..." entries from the NWAM Manager menu. This is a temporary selection, and is not retained across reboot. It can be used to work around interfaces that transition when not wanted.
82: 1. Static addressing and advanced configuration
83:  The /etc/nwam/llp file contains entries that look like this:
84: 
85: {{{
86: wired_if0 dhcp
87: ..
88: wireless_if0 dhcp
89: }}}
90: 
91:  Changing the order of the entries causes the priority to change; just move the wireless_if0 entry/entries above the wired. If you wish to assign a static address, replace "dhcp" with "static", followed by the static address and an optional prefix length, e.g. "static 192.168.1.4/24". See nwamd(1M) for more information on static configuration of NWAM.
92: 1. None of the above
93:  If NWAM appears to be finding all your interfaces and attempting to bring the up, but you still don’t have the expected network connectivity, it’s often useful to know how far NWAM got in its attempt to bring things up. Some helpful things to check are:
94: 1* The output of ’{{code}}ifconfig -a{{/code}}’: which interface(s) is/are marked RUNNING? Is DHCPRUNNING set on any of the interfaces? Is an IP address assigned to any of the interfaces?
95: 1* For a wireless link, the output of ’{{code}}dladm show-wifi{{/code}}’: is the link connected to a WLAN?
96: 1* The output of ’{{code}}netstat -rn{{/code}}’: do you have a default route?
97: 1* Are name services set up properly? The typical dhcp-based configuration will include a file called /etc/resolv.conf, which configures DNS for network name resolution; does that file exist, with data entered in it? You also need the correct entries in /etc/nsswitch.conf; does that file list "dns" for both the "hosts:" and "ipnodes:" entries? (A typical entry reads "hosts: files dns")
98:  Enabling debugging in NWAM can also help diagnosis. First, /etc/syslog.conf needs to be modified to ensure syslogging captures daemon debug messages. Add a line such as this (note that the syslog.conf fields must be TAB-separated, so if you copy and paste the text from this page, you’ll probably need to manually insert a tab before the filename):
99: 
100: {{{
101: daemon.debug	/var/tmp/nwam.log
102: }}}
103: 
104:  followed by
105: 
106: {{{
107: # touch /var/tmp/nwam.log
108: # pkill -HUP syslogd
109: }}}
110: 
111:  This tells syslog to dump daemon messages in /var/tmp/nwam.log. Now, enable debugging in NWAM:
112: 
113: {{{
114: # svccfg -s nwam setprop nwamd/debug = true
115: # svcadm refresh nwam
116: }}}
117: 
118:  To dump the current internal state of the daemon to the log file established above, send it SIGINT:
119: 
120: {{{
121: # pkill -INT nwamd
122: }}}
123: 
124:  If you need to restart in order to reproduce the problem, it may help to run:
125: 
126: {{{
127: # svcadm restart nwam
128: }}}
129: 
130:  When contacting [[nwam-discuss>>mailto:nwam-discuss@opensolaris.org]] about problems, the debug log will be helpful in diagnosing the issue. You should also include the version of the NWAM Manager applet. You can obtain this with:
131: 
132: {{{
133: % /usr/lib/nwam-manager ~--version
134: }}}
OpenSolaris

Top Menu

Wiki code for NWAM Phase 0.5 Troubleshooting

Search

Collectives

Community Group

Project

User Group

Subsites

Project nwam Pages
