Talk:Wireless network configuration
iwlist wlan0 scanning syntax
In section "https://wiki.archlinux.org/index.php/Wireless_Setup#Access_point_discovery" is the shell command "iwlist wlan0 scanning" mentioned. "iwlist scan" will do in most cases, and is even without system dependent interface names. (Also, its at least 4 characters shorter, depending on system configuration, and in this respect more according to the arch way than the current version.) -- Scr (talk) 12:26, 5 April 2013 (UTC)
- Similar to ip, all objects may be written in full or abbreviated form, as long as it's unambiguous. For example, following commands are equivalent:
iwlist wlan0 scanning,
iwlist wlan0 scan,
iwlist wlan0 s. For good readability, I'd definitely not use the shortest
iwlist --helpyields the full form
scanning, I think it's better to keep it that way. -- Lahwaacz (talk) 19:00, 1 August 2013 (UTC)
I installed Arch Linux in December 2012 and my wpa_supplicant.conf file is at /etc/wpa_supplicant/wpa_supplicant.conf , so I would suggest updating this page to reflect that. DavidEGrayson (talk) 23:17, 16 December 2012 (UTC)
- That is intentional in order not to change the original .conf which is really good reference documentation in itself. Explanation for it you find in the wpa_supplicant wiki here. The idea is you create a new /etc/wpa_supplicant.conf and work with that. Since all wpa_supplicant calls mentioned in the wiki address the /etc version, its fine in my view. --Indigo (talk) 18:27, 17 December 2012 (UTC)
Mention modprobe -l
Does anybody else besides me think that it would be helpful to mention modprobe -l to get a list of loaded modules/drivers and that ath9k is already included in the kernel at the beginning of First steps or Drivers and Firmware section? In my case (I have a Thinkpad x61) I didn't have to install any additional drivers, so I could proceed immediately to Manual setup and everything worked perfectly.
--Bhobbit 01:03, 7 June 2009 (EDT)
Overall article readability (notes and split)
There is no doubt this article is very rich, but I find it a bit messy overall. At first sight, the newcomer may think managing wireless is a real odyssey, whereas it may be 2 simple steps for most users.
- More than 50% of the article is dedicated to specific drivers installation. Perhaps it would be worth moving the whole section to a dedicated page, leaving only generic install guidelines here.
- I've found 21 Note templates. Too much imho, it makes different sections and code lines harder to distinguish, and thus diminishes article's overall readability. Some of them definitely do not deserve a template, they should be written as is.
Still I won't say there is no doubt these 2 changes would make the article really better. So feel free to discuss!
Auto-connect if dropped or changed location Wicd
I tested this with wicd and this didn't work (with my raspberry pi and an ASUS USB-N10 adaptor). Once the connection was dropped the device didn't even search for other networks (the light at the adaptor didn't blink).
I now tried again with netcfg and that works like a charm, so it has nothing to do with my hardware. Are there others who are experiencing the same problem?
-- Warddr (talk) 15:17, 22 August 2012 (UTC)