After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 391067 - cannot parse 'group' and 'pairwise' options in wpa_supplicant.conf
cannot parse 'group' and 'pairwise' options in wpa_supplicant.conf
Status: RESOLVED INCOMPLETE
Product: NetworkManager
Classification: Platform
Component: general
0.6.6
Other All
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2006-12-30 19:29 UTC by Carl Roth
Modified: 2009-01-19 19:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Carl Roth 2006-12-30 19:29:55 UTC
Please describe the problem:
The 'group' and 'pairwise' network options in wpa_supplicant.conf support a list of alternate methods, separated by whitespace.  For example:

  network={
    ...
    group=CCMP TKIP
    ..
  }

NetworkManager doesn't support this syntax.  If multiple 'group' or 'pairwise' options are listed, NetworkManager is unable to associate to that AP.  If the fields are trimmed down to a single keyword each, then NetworkManager is able to associate.

The same wpa_supplicant.conf file (with multiple keywords listed) works fine if wpa_supplicant is launched by hand.


Steps to reproduce:
1. Create a wpa_supplicant.conf file for an AP
2. List multiple options for 'group' or 'pairwise'
3. Launch NetworkManger (or something like nm-supplicant-test)


Actual results:
NetworkManager eventually fails because association does not complete in a timely fashion.


Expected results:
NetworkManager should be able to pass the network options to wpa_supplicant without mangling them.

Does this happen every time?
Yes.

Other information:
This is easily reproducible.  The workaround is to

1. Don't use a wpa_supplicant.conf file

OR

2. Sanitize the 'group' and 'pairwise' options appropriately.
Comment 1 Dan Williams 2007-12-07 15:51:24 UTC
Are you using a hidden network?  If you're _not_, then this doesn't matter as wpa_supplicant will just pick the right option because it can find out what's supported from your AP's beacon frames.
Comment 2 Christoph Wurm 2009-01-19 19:13:27 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!