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#32945 - [netcfg] can connect to wifi manually, but wifi-menu fails
Attached to Project:
Arch Linux
Opened by trusktr (trusktr) - Monday, 03 December 2012, 06:17 GMT
Last edited by Eric Belanger (Snowman) - Tuesday, 30 April 2013, 01:02 GMT
Opened by trusktr (trusktr) - Monday, 03 December 2012, 06:17 GMT
Last edited by Eric Belanger (Snowman) - Tuesday, 30 April 2013, 01:02 GMT
|
DetailsDescription:
Trying to use wifi-menu to choose a network and enter the WEP key leads to a failure to connect ("CONNECTING FAILED"). But if I try doing # iwconfig wlan0 essid "some network" key "s:XXXXXXXXXXXXX" # dhcpcd -k wlan0; dhcpcd wlan0 then the connection gets established. I have a feeling the problem might be due to the fact that the WEP key is a 13-digit ASCII string containing letters, numbers, and symbols. I haven't tested a HEX key, so I couldn't be sure, but I'll try and remember to do so at another location... Additional info: * package version(s): Most recent install media as of this writing. * config and/or log files etc: What would you like to see? Steps to reproduce: Follow the simple steps in the Beginner's Guide then get stuck when wifi-menu doesn't work. |
This task depends upon
Closed by Eric Belanger (Snowman)
Tuesday, 30 April 2013, 01:02 GMT
Reason for closing: Won't fix
Additional comments about closing: netcfg has been moved to AUR
Tuesday, 30 April 2013, 01:02 GMT
Reason for closing: Won't fix
Additional comments about closing: netcfg has been moved to AUR
Comment by Alexander F. Rødseth (xyproto) -
Saturday, 08 December 2012, 18:51 GMT
netcfg is currently an orphan, assigned to last packager. (Who should netcfg bugs really be assigned to, again, and why aren't they maintainers of the package?)
Comment by Florian Pritz (bluewind) -
Saturday, 08 December 2012, 19:18 GMT
Assign them to Jouke, I just do packaging because he isn't a dev. The PKGBUILD is part of netcfg so I don't do anything apart from makepkg + pushing.
Comment by Alexander F. Rødseth (xyproto) -
Saturday, 08 December 2012, 19:46 GMT
I see, thanks.