1
1
I have a laptop with Windows 7 and Ubuntu 12.04. I have a Cisco E1200 and when I set it up, it created 2 SSIDs. Let's name them:
- MyConnection (WPA/WPA2 personal), and
- MyConnection-Guest (no authentication, guest password entered via web browser).
I had no problem connecting to MyConnection before, either in Windows 7 and Ubuntu. But now, I can't access MyConnection on Ubuntu. It just says "connecting..." then disconnects after a while. But I'm able to access the internet (on Ubuntu) when I connect to MyConnection-Guest.
MAC filtering is off (even if it's on its MAC address is in the white list). Any idea why I'm unable to connect to MyConnection in Ubuntu? Thanks.
Update: My Ubuntu installation can connect to ANY WiFi connection (WPA/WEP/no auth), except for MyConnection. Update2: This is what "The not so easy way" returned:
Initializing interface 'eth1' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
Priority group 0
id=0 ssid='MyConnection'
id=1 ssid='MyConnection'
id=2 ssid='MyConnection'
id=3 ssid='MyConnection'
WEXT: cfg80211-based driver detected
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
netlink: Operstate: linkmode=1, operstate=5
Own MAC address: xx:xx:xx:xx:xx:xx
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=4 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Invalid argument
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_key: alg=0 key_idx=5 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: Invalid argument
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_countermeasures
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): 16 3b d8 47 9e 24 50 89 96 16 6d 66 35 f3 58 37
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
Added interface eth1
"Ubuntu is very tricky and very "delicate" when working with this kind of connections". I don't agree. In my opinion It's just horribly designed software. Like few other linux distributions - developers assume that their users are IT geniuses and know everything. And if not - they shall "RTFM". It's ancient approach to software engineering. – Kamil – 2014-10-01T22:52:48.463
Hi. Thanks for the reply and sorry for only replying now. However, both ways didn't work. The "not so easy way" returned the code I included in the Update of this question. Thanks. – d4ryl3 – 2013-02-18T13:49:35.830
@d4ryl3 . have you already restored your AP to fabric mode? – AAlvz – 2013-02-19T19:40:13.150
I'm sorry, how do I do that? The only thing I did before the 2nd way was I removed the SSIDs from my wireless networks. – d4ryl3 – 2013-02-20T05:06:00.540
@d4ryl3 Some AP have a button which you press 5 secs or so and it turns to fabric mode... or you can access to your AP writing
192.168.1.254
in your URL. There you access your AP and look for areset to fabric mode
button. It'll probably ask for the wireless pass – AAlvz – 2013-02-20T18:01:34.787Oh, you mean a reset button? No it doesn't. The only button the router has is the one for WiFi Protected Setup. Accessing 192.168.1.254 didn't give me anything either. Thanks for helping on this. – d4ryl3 – 2013-02-25T11:55:36.170
@d4ryl3 No problem.. It seems that you can't access your AP... since the 192.168.1.254 address returns nothing... mmm.. are you sure it is connected all ok?? – AAlvz – 2013-02-25T16:56:14.623
try the same 192.168.1.254 from windows too – AAlvz – 2013-02-25T16:56:47.103
Hi, sorry I rarely have time to troubleshoot this. Anyway, my PC is connected to the router via ethernet, and my Ubuntu via MyConnection-Guest. Both of them couldn't access 192.168.1.254. It's really weird, because I use Ubuntu at the office and it can connect to ANY wifi I choose to, regardless of its authentication. So I'm really stumped here. Thanks for taking time to help. – d4ryl3 – 2013-03-07T12:02:21.140
It seems to me that your AP is broken... I had once the same problem (no access to 192.168.1.254) .. I had to request a change of AP. My ISP gave me another access point and all worked fine after that... – AAlvz – 2013-03-24T19:13:31.417