FS#24599 - [netcfg] net-auto-wireless :no dhcp is done for a profile file with square brackets

Attached to Project: Arch Linux
Opened by Emmanuel GAUDE (mAn) - Monday, 06 June 2011, 12:32 GMT
Last edited by Thomas Bächler (brain0) - Monday, 19 March 2012, 19:34 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Thomas Bächler (brain0)
Rémy Oudompheng (remyoudompheng)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After the boot, with net-auto-wireless dameon started and a network profile with square brackets in its filename, the connection to the access point is done but dhcpcd is not running. If the network profile does not have any [] in its name, an IP is get automatically after the boot.
The same network profile (with []) is working with a manual netcfg and net-profiles daemon.

Additional info:
* core/netcfg 2.5.5-1
* core/wpa_actiond 1.1-2
* core/wireless_tools 29-4
* core/wpa_supplicant 0.7.3-3
* core/dhcpcd 5.2.12-1

Config files :
* /etc/rc.conf
* /etc/network.d/Sarrazine[wifi] (with key masked)

Steps to reproduce:
* Get a wireless machine with the wireless driver set.
* Create a wep network profile with square brackets in its name (like Sarrazine[wifi])
* Get core/wireless_tools, core/netcfg and core/wpa_actiond packages
* Designate the wlan interface in the /etc/rc.conf (WIRELESS_INTERFACE="wlan0")
* Put net-auto-wireless in the daemon array of /etc/rc.conf and disable other net daemons.
* Restart the computer
* Try $ ping archlinux.org : network is unreachable
* Try $ iwconfig wlan0 : the ESSID is ok
* Try # dhcpcd wlan0 : Dhcp client was not running and start yet.
   Sarrazine[wifi] (0.2 KiB)
   rc.conf (3.2 KiB)
This task depends upon

Closed by  Thomas Bächler (brain0)
Monday, 19 March 2012, 19:34 GMT
Reason for closing:  Fixed
Comment by Rémy Oudompheng (remyoudompheng) - Saturday, 30 July 2011, 18:07 GMT
There is unproper quoting somewhere in the code. This kind of problem is awful to debug, so I won't have a look at it until I have a lot of time.
Comment by Jouke Witteveen (jouke) - Friday, 24 February 2012, 13:13 GMT
This is a bug in wpa_actiond. Most likely line 191 of wpa_actiond.c is at fault.
Maybe Thomas Bächler knows the rationale behind that line.
Comment by Thomas Bächler (brain0) - Tuesday, 28 February 2012, 07:54 GMT
Right, that parser for the id_str= argument is primitive, to say the least. This is fixable though - if anyone can do it, please do so, I don't know when I have time to look into it myself.
Comment by Thomas Bächler (brain0) - Tuesday, 28 February 2012, 15:39 GMT
I know this bug is old (I wasn't made aware of it until today), but can you test the attached patch against wpa_actiond?
   0001-Fix-action-call-for-prof... (0.9 KiB)

Loading...