I tried to connect to an insecure network and, after double clicking on it, I go to the main window where nothing happens (at least in the foreground).
This is similar with what happens when I try to connect to the eduroam.
I have done some tests and believe that I understand what is going on. However, I would like to know if the same solution works for you before putting in code to deal with it.
I notice that when I disable wireless through Network Manager that the wireless interface shows down when I do an "ifconfig" from the command line. During this time, clicking connect results in XSupplicant not doing anything. If I use the command line to bring the interface up, and then attempt to connect, I am able to connect.
If this also works for you, then I will change the behavior of the supplicant to work better under these circumstances.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I disabled Wireless in the Network Manager, did a 'ifup wlan0' in the terminal and got the error "Ignoring unknown interface wlan0=wlan0." so I did a 'ifup -a'. I don't think this had any effect because I went to the /etc/network and found no reference on the wlan0. A full 'grep -R wlan0 /etc/network' prints nothing. As far as I know the wlan0 info should have been there somewhere.
I still tried to connect to the insecure wireless and got the same problem.
The log file was showing this:
Wed Jul 15 12:31:58 2009 - Couldn't find the profile used by connection 'ECS-WLAN_Connection'!
Wed Jul 15 12:31:58 2009 - Interface 'wlan0' is attempting to associate.
Wed Jul 15 12:31:58 2009 - Checking AUTH_NONE.
Wed Jul 15 12:31:58 2009 - Couldn't continue association attempt due mismatch in profile between AP and client
Wed Jul 15 12:31:58 2009 - The association attempt timed out.
Wed Jul 15 12:31:58 2009 - Error setting key!! (IOCTL failure.)
Wed Jul 15 12:31:58 2009 - Error 2 : No such file or directory
Wed Jul 15 12:31:58 2009 - Interface 'wlan0' is scanning for wireless networks. Please wait.
Wed Jul 15 12:31:58 2009 - Error with SCAN ioctl! (Perhaps your card doesn't support scanning, or isn't up?)
Wed Jul 15 12:31:58 2009 - Error was (100) : Network is down
Wed Jul 15 12:31:58 2009 - There was an error starting a scan.
Wed Jul 15 12:31:58 2009 - Your interface is down.
Wed Jul 15 12:31:58 2009 - Error setting key!! (IOCTL failure.)
Wed Jul 15 12:31:58 2009 - Error 2 : No such file or directory
Wed Jul 15 12:32:01 2009 - Couldn't find the profile used by connection 'ECS-WLAN_Connection'!
Wed Jul 15 12:32:01 2009 - Couldn't find the profile used by connection 'ECS-WLAN_Connection'!
I then created a profile manually but kept having the same problem when trying to connect.
Also, when I try to scan I get this error:
Wed Jul 15 12:35:53 2009 - Error with SCAN ioctl! (Perhaps your card doesn't support scanning, or isn't up?)
Wed Jul 15 12:35:53 2009 - Error was (100) : Network is down
Wed Jul 15 12:35:53 2009 - Unhandled error while attempting to scan.
The above error not only happens in this situation but in many others.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have done some tests and believe that I understand what is going on. However, I would like to know if the same solution works for you before putting in code to deal with it.
I notice that when I disable wireless through Network Manager that the wireless interface shows down when I do an "ifconfig" from the command line. During this time, clicking connect results in XSupplicant not doing anything. If I use the command line to bring the interface up, and then attempt to connect, I am able to connect.
If this also works for you, then I will change the behavior of the supplicant to work better under these circumstances.
I disabled Wireless in the Network Manager, did a 'ifup wlan0' in the terminal and got the error "Ignoring unknown interface wlan0=wlan0." so I did a 'ifup -a'. I don't think this had any effect because I went to the /etc/network and found no reference on the wlan0. A full 'grep -R wlan0 /etc/network' prints nothing. As far as I know the wlan0 info should have been there somewhere.
I still tried to connect to the insecure wireless and got the same problem.
The log file was showing this:
Wed Jul 15 12:31:58 2009 - Couldn't find the profile used by connection 'ECS-WLAN_Connection'!
Wed Jul 15 12:31:58 2009 - Interface 'wlan0' is attempting to associate.
Wed Jul 15 12:31:58 2009 - Checking AUTH_NONE.
Wed Jul 15 12:31:58 2009 - Couldn't continue association attempt due mismatch in profile between AP and client
Wed Jul 15 12:31:58 2009 - The association attempt timed out.
Wed Jul 15 12:31:58 2009 - Error setting key!! (IOCTL failure.)
Wed Jul 15 12:31:58 2009 - Error 2 : No such file or directory
Wed Jul 15 12:31:58 2009 - Interface 'wlan0' is scanning for wireless networks. Please wait.
Wed Jul 15 12:31:58 2009 - Error with SCAN ioctl! (Perhaps your card doesn't support scanning, or isn't up?)
Wed Jul 15 12:31:58 2009 - Error was (100) : Network is down
Wed Jul 15 12:31:58 2009 - There was an error starting a scan.
Wed Jul 15 12:31:58 2009 - Your interface is down.
Wed Jul 15 12:31:58 2009 - Error setting key!! (IOCTL failure.)
Wed Jul 15 12:31:58 2009 - Error 2 : No such file or directory
Wed Jul 15 12:32:01 2009 - Couldn't find the profile used by connection 'ECS-WLAN_Connection'!
Wed Jul 15 12:32:01 2009 - Couldn't find the profile used by connection 'ECS-WLAN_Connection'!
I then created a profile manually but kept having the same problem when trying to connect.
Also, when I try to scan I get this error:
Wed Jul 15 12:35:53 2009 - Error with SCAN ioctl! (Perhaps your card doesn't support scanning, or isn't up?)
Wed Jul 15 12:35:53 2009 - Error was (100) : Network is down
Wed Jul 15 12:35:53 2009 - Unhandled error while attempting to scan.
The above error not only happens in this situation but in many others.
Pushing Linux bugs to SEA-Badger.