Bug 431033 - Networkmanager have problems with PEAP/TKIP
Summary: Networkmanager have problems with PEAP/TKIP
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager   
(Show other bugs)
Version: 8
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-01-31 09:59 UTC by Micko
Modified: 2008-10-20 15:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-20 15:10:03 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/sbin/iwlist wlan0 scan of TKIP network (15.20 KB, text/plain)
2008-02-01 09:31 UTC, Micko
no flags Details
Log from NetworkManager (64.93 KB, text/plain)
2008-04-23 08:34 UTC, Micko
no flags Details
At the end of this log NM is trying to connect several times and at last i succed (14.81 KB, text/plain)
2008-04-23 11:18 UTC, Micko
no flags Details
messages from NM F8 and NM F9 (165.59 KB, text/plain)
2008-05-15 12:59 UTC, Micko
no flags Details

Description Micko 2008-01-31 09:59:05 UTC
Description of problem:
Networkmanager disconnects after some time using TKIP. Sometimes its possible to
reconnect after a restart of NM. There is no option in the menu to choose TKIP.
(I compare with for example Ubuntu 7.04-10 where TKIP is an option)

Version-Release number of selected component (if applicable):

[root@wallence ~]# lsmod |grep iw
iwl3945               161461  0
mac80211              125265  1 iwl3945

How reproducible:
I don't know, maybe try a WPA-Enterprice WLAN with PEAP and TKIP? It is hard to
say since uptime seems to vary from time to time. 

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
[root@wallence ~]# iwconfig

wlan0     IEEE 802.11g  ESSID:"PORT-ADM"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:1A:30:33:41:80
          Bit Rate=54 Mb/s   Tx-Power=16 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B
          Link Quality=86/100  Signal level=-47 dBm  Noise level=-85 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

[root@wallence ~]# iwlist wlan0 encryption
wlan0     2 key sizes : 40, 104bits
          4 keys available :
                [1]: off
(256 bits)
                [3]: off
                [4]: off
          Current Transmit Key: [2]

Comment 1 Dan Williams 2008-01-31 15:48:36 UTC
Is your access point hiding it's SSID?

Can you provide "/sbin/iwlist wlan0 scan" output for your access point?  I need
to see it's WPA/RSN information elements.  If the AP is properly advertising
it's capabilities, then wpa_supplicant should be able to automatically choose
the correct cipher suite for the AP and you should not need to set that manually.


Comment 2 Micko 2008-02-01 09:31:15 UTC
Created attachment 293700 [details]
/sbin/iwlist wlan0 scan of TKIP network 

Requested info of network

Comment 3 Micko 2008-04-23 08:34:13 UTC
Created attachment 303454 [details]
Log from NetworkManager 


Comment 4 Micko 2008-04-23 08:36:29 UTC
Comment on attachment 303454 [details]
Log from NetworkManager 

Report: I can now connect to my network but I get disconnected after awhile. I
can reconnect a few times but after awhile I need to reboot NM to get going
again. I send some logs that I hope can help.

Comment 5 Micko 2008-04-23 11:18:45 UTC
Created attachment 303479 [details]
At the end of this log NM is trying to connect several times and at last i succed

Additional information: This log shows how NM tries to connect, fails several
times and then succeds.

Comment 6 Micko 2008-04-30 09:11:12 UTC

Hello, just after I reported problems I got an update and it now works much
better. Some of the problems still occur, sudden disconnect and I have to try
twice sometimes to reconnect. Please tell me if I can be of some help to improve
NM further.  

Maybe it would be better if it said TKIP instead of peapv0? I wasn't familiar
with  that anyway that they were the same. 

Best regards, Micko

Comment 7 Micko 2008-05-15 12:59:50 UTC
Created attachment 305484 [details]
messages from NM F8 and NM F9

At the end of the file there is output from NM in F9. Sorry if its to big. At
the start of the file there is output from NM in F8 working okey.

Comment 8 Micko 2008-05-15 13:00:47 UTC
Comment on attachment 305484 [details]
messages from NM F8 and NM F9

Short report of NM F8 -> F9 I upgraded yesterday. The latest NM in F8 was
working perfect on my WLAN. The new in F9 (that look really promising, nice
work!) is not as stable. It disconnects more often and I have to restart it to
make it reconnect. I include a logfile and hope it can help. Thanks! (I dont
really know what is affecting this, maybe off cource, its something else)

Comment 9 Dan Williams 2008-10-20 15:10:03 UTC
Is this still an issue with latest NM, kernel, and wpa_supplicant?  WPA/WPA2 + PEAP/MSCHAPv2 tested fine with NM svn4022.4,, supplicant 0.5.10-6.fc8.  Please re-open if it's still an issue.

Note You need to log in before you can comment on or make changes to this bug.