Siduction Forum

Siduction Forum => Software - Support => Topic started by: ajavibp on 2013/11/04, 20:18:38

Title: Problem with a WPA2/TTLS/PAP network
Post by: ajavibp on 2013/11/04, 20:18:38

Hello. I've installed siduction with xfce in a laptop and I can't connect to a WPA2/TTLS/PAP network.

Do you know any problem with this? I'm crazy searching the problem, but all seems fine.

Thank you!
Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: absolut on 2013/11/04, 22:07:39
please give us more details!

what wifi card do you have?
are you able to "see" nearby wifi networks?
does your connection attempt fail with some kind of error?
Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: dibl on 2013/11/04, 22:14:27
Right -- as absolut said.  For example:


- did you use (as root) ceni to configure the wlan?  Did it see the wireless interface?


- if you scan (with ceni, network manager, wicd, or whatever) are you able to see networks?


Tell us what is working, and where it fails.
Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: ajavibp on 2013/11/04, 22:41:58
The wifi card work well. I connect perfectly to my home wifi with Personal WPA2, but I can't connect to Enterprise WPA2. I've entered the data correctly access, of course.

So far I've only tried with network-manager.
Thank you very much.
Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: dibl on 2013/11/04, 23:38:21
This might or might not have helpful information:


http://forums.debian.net/viewtopic.php?f=10&t=106656 (http://forums.debian.net/viewtopic.php?f=10&t=106656)



Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: ajavibp on 2013/11/05, 09:19:57
Thanks dibl.


I will try it when I'm at work.
Greetings!
Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: piper on 2013/11/05, 14:26:17
This is a quote from my help files inside my buffalo router running dd-wrt, don't know if it helps or not.

Quote
WPA EnterpriseWPA Enterprise uses an external RADIUS server to perform user authentication. To use WPA RADIUS, enter the IP address of the RADIUS
server, the RADIUS Port (default is 1812) and the shared secret from the
RADIUS server.

Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: ajavibp on 2013/11/06, 10:21:45
Quote from: dibl on 2013/11/04, 22:14:27
Right -- as absolut said.  For example:

- did you use (as root) ceni to configure the wlan?  Did it see the wireless interface?

- if you scan (with ceni, network manager, wicd, or whatever) are you able to see networks?

Tell us what is working, and where it fails.


I tried with ceni, it doesn't support Enterprise WPA (or I don't see it), and wicd, but I coludn't connect.
I really think it might be a bug, since I have other computers with no problems with Ubuntu and Android.
Thanks for your help
Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: absolut on 2013/11/06, 14:03:19
well, it very much depends on the WPA2-enterprise setup...

for example, eduroam connection settings are stored on my computer in /etc/NetworkManager/system-connections/eduroam ... you might want to check and compare yours to the other working computers

if you are able to share details (online instructions how to configure your wifi) and error logs (dmesg for a start), then please do.


Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: ajavibp on 2013/11/06, 18:33:05
I will try to send the data on Monday when I return to work. Thank you very much.
Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: ajavibp on 2013/11/11, 19:54:53

Hello again, here is my dmes. My laptop is an Asus 1005P with Atheros wifi (ath9K driver)



[ 1096.207102] wlan0: authenticate with 00:0a:b8:1b:6e:92
[ 1096.229192] wlan0: send auth to 00:0a:b8:1b:6e:92 (try 1/3)
[ 1096.230898] wlan0: authenticated
[ 1096.232588] ath9k 0000:02:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 1096.233178] wlan0: associate with 00:0a:b8:1b:6e:92 (try 1/3)
[ 1096.235814] wlan0: RX AssocResp from 00:0a:b8:1b:6e:92 (capab=0x431 status=0 aid=157)
[ 1096.237195] wlan0: associated
[ 1096.237292] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1097.354157] wlan0: deauthenticated from 00:0a:b8:1b:6e:92 (Reason: 23)
[ 1097.361695] cfg80211: Calling CRDA to update world regulatory domain
[ 1097.387549] cfg80211: World regulatory domain updated:
[ 1097.387561] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 1097.387572] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1097.387581] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1097.387589] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 1097.387596] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1097.387603] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1097.604775] wlan0: authenticate with 00:13:c3:44:7f:b2
[ 1097.621163] wlan0: send auth to 00:13:c3:44:7f:b2 (try 1/3)
[ 1097.622847] wlan0: authenticated
[ 1097.623400] ath9k 0000:02:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 1097.624490] wlan0: associate with 00:13:c3:44:7f:b2 (try 1/3)
[ 1097.627930] wlan0: RX AssocResp from 00:13:c3:44:7f:b2 (capab=0x431 status=0 aid=155)
[ 1097.628788] wlan0: associated
[ 1099.194532] wlan0: deauthenticated from 00:13:c3:44:7f:b2 (Reason: 23)
[ 1099.200638] cfg80211: Calling CRDA to update world regulatory domain
[ 1099.224304] cfg80211: World regulatory domain updated:
[ 1099.224314] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 1099.224321] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1099.224327] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1099.224333] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 1099.224339] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1099.224345] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1099.377235] wlan0: authenticate with 00:0a:b8:1b:70:b2
[ 1099.396316] wlan0: direct probe to 00:0a:b8:1b:70:b2 (try 1/3)
[ 1099.597153] wlan0: direct probe to 00:0a:b8:1b:70:b2 (try 2/3)
[ 1099.798150] wlan0: direct probe to 00:0a:b8:1b:70:b2 (try 3/3)
[ 1099.999127] wlan0: authentication with 00:0a:b8:1b:70:b2 timed out
[ 1101.136269] wlan0: authenticate with 00:0a:b8:1b:6e:92
[ 1101.155643] wlan0: send auth to 00:0a:b8:1b:6e:92 (try 1/3)
[ 1101.160098] wlan0: authenticated
[ 1101.160604] ath9k 0000:02:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 1101.161090] wlan0: associate with 00:0a:b8:1b:6e:92 (try 1/3)
[ 1101.165115] wlan0: RX AssocResp from 00:0a:b8:1b:6e:92 (capab=0x431 status=0 aid=158)
[ 1101.165845] wlan0: associated
[ 1120.007930] wlan0: deauthenticating from 00:0a:b8:1b:6e:92 by local choice (reason=3)
[ 1120.011674] cfg80211: Calling CRDA to update world regulatory domain
[ 1120.045530] cfg80211: World regulatory domain updated:
[ 1120.045542] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 1120.045552] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1120.045561] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1120.045570] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 1120.045578] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1120.045586] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: ajavibp on 2013/11/20, 16:58:30

Hello. Today I copied the configuration file of a pc where it works as absolut advised me, but again it don't connect.
Any idea? You know what logfile can help me find the bug?
Thank you for your help!
Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: absolut on 2013/11/20, 23:15:03
is there a wpa-enterprise certificate required for your wifi connection?
what settings (encryption/handshake/etc...) are to be configured?
have you verified your personal and anonymous (if any) credentials?
Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: ajavibp on 2013/11/21, 08:35:46
Quote from: absolut on 2013/11/20, 23:15:03is there a wpa-enterprise certificate required for your wifi connection?

No, is not. I

Quote from: absolut on 2013/11/20, 23:15:03
what settings (encryption/handshake/etc...) are to be configured?


Security: WPA2
Authentication: TTLS (Tunnel TLS)
Internal Authentication: PAP
User and password

Quote from: absolut on 2013/11/20, 23:15:03
have you verified your personal and anonymous (if any) credentials?

Of course, many times before post in this forum the first time.

I have instaled Ubuntu in the desktop computer of my office and wifi network works perfect, but in my laptop with a clean intalation of Siduction, I can't make it run. I have some knowledge because I've been using linux a few years, but I'm no expert.

Thanks!
Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: absolut on 2013/11/21, 16:11:49
i did not have such issues myself, so my input on this might be rather limited....

by looking at your dmesg output, i see multiple things to search for:
1)
ath9k 0000:02:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
why is this? you were trying to connect to WPA2-PSK enterprise

2)
wlan0: deauthenticated from 00:0a:b8:1b:6e:92 (Reason: 23)
what is this reason #23
Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: ajavibp on 2013/11/21, 16:44:43
1) I have no idea. May be this is the real problem.
2) Reason 23 is IEEE 802.1X authentication failed, but I'm completly sure about user and password.
Title: Re: Problem with a WPA2/TTLS/PAP network
Post by: ajavibp on 2013/12/03, 11:16:15
I finally found a solution. Reading this bug (https://bugs.launchpad.net/linuxmint/+bug/1187483) similar to mine, I found how to solve it (https://bugs.launchpad.net/linuxmint/+bug/1187483/comments/3).
The problem seems to be the network-manager who always seeks a certificate even when is not required.
Should I open a bug for Siduction?
Thank a lor for your help!