![]() |
[solved] Enterprise WPA2 Auto-connect fails
I have the exact opposite problem of this fellow: http://talk.maemo.org/showthread.php?t=62736
I have wifi networks configured on my N900 for my house, girlfriend's house, and work. I scan every 5 min and auto-connect to wifi when avail. When I go home or to girlfriend's house the wifi automatically connects. When I go to work it sees the wifi network, and it can connect to the wifi network, but it doesn't. The main difference is that the wifi at work is WPA2/PEAP/MSCHAPv2. Is there some reason that security would prevent auto-connect from working? I am using the power kernel. |
Re: WiFi Auto-connect fails
I've heard from my reading that WPA2 Enterprise (as opposed to PSK) doesn't allow for auto connection. Is this the case with your network?
|
Re: WiFi Auto-connect fails
I don't think so. Both my work-provided laptop (windows) and my personal laptop (ubuntu) will auto-connect to the enterprise network at work.
|
Re: WiFi Auto-connect fails
delete the AP from your n900 the try to add/connect to your wifi network at your work again....
|
Re: WiFi Auto-connect fails
I think this post mentions the bug, which I was describing to prevent auto-association with WPA enterprise.
http://talk.maemo.org/showpost.php?p=206365&postcount=3 |
Re: WiFi Auto-connect fails
ahh, so its a "feature". yeah, i've used that trick before too.
seems like a script could be written and then scheduled to auto-run during hours i might be at work. i'll look into this tomorrow. |
Re: WiFi Auto-connect fails
Ok, here's what I figured out so far....
I used 'alarmed' to run a script. The script is scheduled to run every 5 min between 8am and 6pm on weekdays (when I would typically be at work). The script uses dbus commands to disconnect from the network, wait five seconds (required for disconnect to complete), then attempt to connect to the WPA Enterprise network. This, unfortunately, is only a start. The script doesn't check to see if it is already connected to the Enterprise network, so it will perpetually disconnect and re-connect. The script also doesn't check to see if the Enterprise network is available before attempting to switch to it. |
Re: WiFi Auto-connect fails
OK, I wrote a bash script that should do the following:
1) check if i'm already connected to the enterprise network. if not... 2) look for the SSID of the enterprise network. if found... 3) disconnect from current connection and connect to enterprise network. then I will use alarmed to auto-run the script every 10 min or so during business hours. I haven't fully tested the script yet, but it seems to be working. I'm not really good with bash and never used awk so don't laugh! Code:
#!/bin/bash |
Re: [solved] Enterprise WPA2 Auto-connect fails
Here's my current bash at it:
Code:
#!/bin/sh
Might try to add check for network status so I can remove the extra sleeps but probably won't get round to it! EDIT: Doesn't seem to like being run as User. I'm running "sudo /usr/bin/run-standalone.sh /path/script 'SSID'" in alarmd to get round this |
Re: [solved] Enterprise WPA2 Auto-connect fails
I saw some people complaining about this bug again in bugzilla and came back to revisit the problem. I have two N900s now and only one sim card so I always want the other to be on wifi.
hutchinsfairy - sorry I am not smart enough to get your script to work for me. Here is what happens when I run it: Code:
$ sudo /usr/bin/run-standalone.sh ~/MyDocs/scripts/hutchinsfairy 'nasa' My old script does seem to still be more-or-less working for me, but I did not include enough information for anyone else to be able to use it too. 1) i don't know if there are any dependencies, except bash obviously 2) You have to manually replace my SSID with yours in two places in the script. 2a) In line 7, my ssid is nasa. Replace that with yours: Code:
if [ $LIST = '"nasa"' ]; then 2b) The second-to-last line looks like this: Code:
dbus-send --type=method_call --system --dest=com.nokia.icd /com/nokia/icd com.nokia.icd.connect string:5f027850-3445-4eef-ac3f-76b423515990 uint32:0 Code:
string:5f027850-3445-4eef-ac3f-76b423515990 Code:
gconftool -R /system/osso/connectivity/IAP (I had better luck connecting to the network and then using the gconftool command and near the top there is a line that says "last used network: blahblahblah". I used that string.) 3) you need to have a folder under MyDocs called scripts. put the script there. 4) To run the script, type: Code:
sudo bash nameofscript 6) if you test it, let us know how it went. |
All times are GMT. The time now is 21:44. |
vBulletin® Version 3.8.8