Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#31057 - [netcfg] wifi-menu does not ask for authentication password
Attached to Project:
Arch Linux
Opened by Dan Andresan (forumache) - Wednesday, 08 August 2012, 08:24 GMT
Last edited by Jouke Witteveen (jouke) - Thursday, 09 August 2012, 15:31 GMT
Opened by Dan Andresan (forumache) - Wednesday, 08 August 2012, 08:24 GMT
Last edited by Jouke Witteveen (jouke) - Thursday, 09 August 2012, 15:31 GMT
|
DetailsDescription:
Impossible to use wifi-menu to connect to password protected AP, because the dialog box to enter the password is not presented to the user. dialog package is installed, the problem is in wifi-menu script, see below. Additional info: * package version(s: core/netcfg 2.8.8-1 * config and/or log files etc.: availablenets, intermediary file. Steps to reproduce: 1. Execute wifi-menu in a network with Access Points which use authentication 2. Select one of the AP which use authentication 3. After a delay, you get Connection Failed and the created profile contains security=none 4. You get no chance to enter the password, since wifi-menu believes that there is not need for it This happens because the intermediary $NETWORKS file is parsed incorrectly, so it fails to extract the flags. I added to the log the intermediary file and I run some tests on it to see what do I need to do to parse it correctly and to understand where the problem lies. The line 105 in /usr/bin/wifi-menu says: flags=$(grep -F -m 1 $'\t'"$1\$" "$NETWORKS" | cut -f 2 ) This is incorrect, because \t is not understood by grep -F (fgrep behavior) as a special character (tab). By removing the -F, the flags where parsed correctly and the dialog box asking for the password was presented to me. After entering the password, I was connected. You can test with the attached file (availablenets) as obtained by wifi-menu:213 a) grep -F -m 1 $'\t'"inwatmv\$" "availablenets" | cut -f 2 will return nothing for AP inwatmv b) grep -m 1 $'\t'"inwatmv\$" "availablenets" | cut -f 2 will return the flags for AP inwatmv I think the -F was entered by https://bugs.archlinux.org/task/30598 to correct a previous change which replaced grep with fgrep: http://projects.archlinux.org/netcfg.git/commit/?id=7e2ff917a67573ed957d57d2fd077b4c219c0d86 Fix: There should be no fgrep (or grep -F) because the '\t' is not understood by it. Plain grep will give the expected results. |
This task depends upon
Closed by Jouke Witteveen (jouke)
Thursday, 09 August 2012, 15:31 GMT
Reason for closing: Fixed
Additional comments about closing: 7b8de
Thursday, 09 August 2012, 15:31 GMT
Reason for closing: Fixed
Additional comments about closing: 7b8de
Comment by Jouke Witteveen (jouke) -
Thursday, 09 August 2012, 15:31 GMT
This was a sloppy error. A fix was already planned. Thanks for your time.
availablenets