Arch Linux

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!
Tasklist

FS#20135 - [initscripts] net: handle whitespace in essid

Attached to Project: Arch Linux
Opened by Brendan (brendan) - Saturday, 10 July 2010, 07:40 GMT
Last edited by Tom Gundersen (tomegun) - Wednesday, 27 April 2011, 10:21 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Aaron Griffin (phrakture)
Thomas Bächler (brain0)
Tom Gundersen (tomegun)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
In rc.conf when using an ESSID with a whitespace in it, the network daemon fails to start. Before posting possible solutions please read what has allready been tried and failed in the forum link!

Additional info:
See here for forum discussion : http://bbs.archlinux.org/viewtopic.php?pid=789191


Steps to reproduce:

Create a WIFI hotspot with an essid that has a space in it.
Declare it in your rc.conf
wlan_wlan0="wlan0 essid My Wireless key mykey"
on network dameon restart an error will be spat out as the command is splitted out on the whitespace.


This task depends upon

Closed by  Tom Gundersen (tomegun)
Wednesday, 27 April 2011, 10:21 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Use netcfg instead.
Comment by Diego Martin Nieto Cid (diego) - Sunday, 11 July 2010, 06:09 GMT
While I was looking at this I figured that switching to arrays for "parameter-like-things" fixes this problem. For wlans it's something along the lines of the attached patch. And the configuration would look like:

wlan_wlan0=(wlan0 essid 'My Wireless' key mykey)

But the git history shows some attempts to "remove bashisms". If they are aiming for sh, this would be a step back :(
   essid.patch (0.5 KiB)
Comment by Ben Ruijl (revelation60) - Saturday, 14 August 2010, 22:34 GMT
I am afraid your patch isn't working. My line:

wlan_wlan0=(wlan0 essid 'prinses doperwtje' key something)

gives: wlan0[@]} No such device.

Anyway, this seems like a kind of issue that is very important, so I hope an official patch will come soon.
Comment by Randy Heydon (Tempel) - Thursday, 19 August 2010, 04:32 GMT
I'm not sure about "very important". I wish I could recall the source, but I heard that the network daemon is not extensively tested with wireless connections; even if you connect to only one network, netcfg or something similar is recommended. I switched myself after installing kernel 2.6.33, since the network daemon stopped working almost entirely for me.

But if this really is the case, then perhaps wireless support should be removed from the network daemon entirely. At the very least, the wiki should reflect this somewhere.
Comment by Diego Martin Nieto Cid (diego) - Saturday, 16 October 2010, 19:58 GMT
Ben: It wasn't meant to be applied. The patch was there only to show the idea. I don't have wifi so I can't test it anyway. :)
But if you are still interested, I can try fix it. Run 'sh -x /etc/rc.d/network start' and attach the output. That should give me an idea of what is going on.

Comment by Leonid Isaev (lisaev) - Saturday, 04 December 2010, 21:18 GMT
Why can't you use netcfg? See the related discussion:  FS#18562 

Loading...