James Carlson wrote: > Venu Chennupati writes: > >> 1. ifconfig wpi0 plumb >> 2. wificonfig -i wpi0 connect <my_essid> >> >> for my wificonfig -i wpi0 scan is identifying a essid with a signal >> level "2" and encryption "none", this I am trying to test if the >> iterface gets IP adrress and to see configuration >> > > I'd suggest using the dladm wifi subcommands rather than wificonfig; > the latter is going away. > > >> 3. ifconfig wpi0 dhcp >> >> fails with : >> ifconfig : wpi0: wait timeout out, operation still pending... >> >> Is the failure due to the week signal? if the operation need to be >> successful what is the >> minimum signal strength needed.. >> > > There's no defined minimum strength, as far as I know. The "wait > timed out" means that we're sending DHCP messages out, but the server > has not yet responded. Possible causes include many things, such as: > > - DHCP server doesn't exist. > > - DHCP server is out of addresses, and can't respond. > > - Driver in use has a bug that causes packets to get dropped. > dladm connect-wifi fails with operation timed out ifconfig wpi0 dhcp is also timeout, I notice IP address assigned.
- Driver warnings are suspicious during this operations: 1. wpi_init() failed to load firmware(text) 2. wpi_init() timeout waiting for firmware init When there are no timeout dladm connect-wifi/ifconfig wpi0 dhcp, I did not see Warning messages from driver. Thanks, Venu. > I wouldn't immediately jump to "weak signal" or assume that there's > some signal requirement here. Instead, I think you'll need to > eliminate problems from the list -- checking status with 'dladm > show-wifi', examining the DHCP server logs, and snooping the interface > to see if other traffic is visible would all be good initial steps. > > _______________________________________________ driver-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/driver-discuss
