Uwe Dippel writes:
> I have been having this problem with rum1 for several versions of Nevada
> (actually, since it kind of works):
Which builds exactly?
> rum1: flags=201004803<UP,BROADCAST,MULTICAST,DHCP,IPv4,CoS> mtu 1500 index 2
> inet 0.0.0.0 netmask ff000000 broadcast 255.255.255.255
> ether 0:21:27:c0:a8:9b
If this is something prior to build 106, then CR 6730161 could be at
fault here.
There are other possibilities, so please do look for errors in
/var/adm/messages.
It's possible to run dhcpagent (the DHCP client) in a debug mode that
will print a _large_ amount of data to the system log file. To do
this, set up syslogd to log daemon.debug to a file, and then add lines
like this to your /etc/default/dhcpagent file:
.DEBUG_LEVEL=3
.VERBOSE=yes
(If dhcpagent is running, just pkill it to get rid of it. That
configuration file is just read at start-up.)
> # dladm connect-wifi -e wlan -k psk rum1
> # dladm show-wifi
> LINK STATUS ESSID SEC STRENGTH MODE
> SPEED
> rum1 connected wlan wpa excellent g 36Mb
> # ifconfig rum1 dhcp
> ^C
> (times out, never connects)
Does a snoop show any traffic on the rum1 interface? It should show
the DHCP messages going out, but if it shows no response, then that
points to a driver failure of some sort (perhaps something wrong with
the way WPA is used).
--
James Carlson, Solaris Networking <[email protected]>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
networking-discuss mailing list
[email protected]
