On Sat, Sep 09, 2006 at 10:59:05AM +1000, Kel Modderman wrote:
> Take some info from 'wpa_cli -i eth1 status' or 'iwconfig eth1' during and
> after attempted association.
I do not have "auto eth1" in my /e/n/i. Thus, the default replies are:
$ sudo wpa_cli -i eth1 status
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
$ sudo iwconfig eth1
eth1 unassociated ESSID:off/any
Mode:Managed Channel=0 Access Point: Not-Associated
Bit Rate=0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:21 Missed beacon:0
When the train came in range of the station, my interface associated
with the Hotspot without wpa_supplicant interfering:
$ sudo iwconfig eth1
eth1 IEEE 802.11g ESSID:"T-Mobile_T-Com"
Mode:Managed Frequency:2.412 GHz Access Point: 00:14:F2:7E:25:00
Bit Rate=54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=58/100 Signal level=-67 dBm Noise level=-84 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:83 Missed beacon:9
$
I then started up the interface, and the interface immediately lost
association:
$ sudo ifup eth1
$ sudo iwconfig eth1
eth1 unassociated ESSID:off/any
Mode:Managed Channel=0 Access Point: Not-Associated
Bit Rate=0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:84 Missed beacon:0
$ sudo wpa_cli -i eth1 status
wpa_state=DISCONNECTED
A minute later, wpa_supplicant tried to associate to my home network:
$ sudo wpa_cli -i eth1 status
wpa_state=ASSOCIATING
$ sudo iwconfig eth1
eth1 unassociated ESSID:"my-home-network"
Mode:Managed Channel=0 Access Point: Not-Associated
Bit Rate=0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:84 Missed beacon:0
This, of course, timed out. Next network on list is
girlfriends-home-network:
$ sudo wpa_cli -i eth1 status
wpa_state=ASSOCIATING
$ sudo iwconfig eth1
eth1 unassociated ESSID:"girlfriends-home-network"
Mode:Managed Channel=0 Access Point: Not-Associated
Bit Rate=0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:D119-901E-8776-3016-3324-7E0E-49 Security mode:open
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:84 Missed beacon:0
This timed out, as well, and wpa_state changed to SCANNING:
$ sudo wpa_cli -i eth1 status
wpa_state=SCANNING
$ sudo iwconfig eth1
eth1 unassociated ESSID:"girlfriends-home-network"
Mode:Managed Channel=0 Access Point: Not-Associated
Bit Rate=0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:84 Missed beacon:0
I then decided to shut down the interface:
$ sudo wpa_action eth1 stop
Stopped wpa_cli (pid 4249).
ifdown eth1
$ sudo wpa_cli -i eth1 status
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
$ sudo wpaiwconfig eth1
eth1 unassociated ESSID:"girlfriends-home-network"
Mode:Managed Channel=0 Access Point: Not-Associated
Bit Rate=0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:84 Missed beacon:0
I would have expected wpa_supplicant to deconfigure the interface
before shutting down. So I decided to deconfigure it manually, and it
immediately associated to the Hotspot again:
$ sudo iwconfig eth1 essid any
$ sudo iwconfig eth1
eth1 IEEE 802.11g ESSID:"T-Mobile_T-Com"
Mode:Managed Frequency:2.412 GHz Access Point: 00:14:69:04:DB:20
Bit Rate=54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=75/100 Signal level=-52 dBm Noise level=-85 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:89 Missed beacon:7
That came kind of as a surprise, since this didn't work the last times
I tried.
Why didn't the interface associate to the hotspot with wpa_supplicant
running?
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
