Difference between revisions of "Talk:Wireless network configuration"

From ArchWiki
Jump to: navigation, search
(wpa_supplicant.conf)
Line 2: Line 2:
  
 
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.  [[User:DavidEGrayson|DavidEGrayson]] ([[User talk:DavidEGrayson|talk]]) 23:17, 16 December 2012 (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.  [[User:DavidEGrayson|DavidEGrayson]] ([[User talk: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. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 18:27, 17 December 2012 (UTC)
  
 
==Mention modprobe -l==
 
==Mention modprobe -l==

Revision as of 18:27, 17 December 2012

wpa_supplicant.conf

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!

-- Ambrevar (talk) 10:27, 6 July 2012 (UTC)

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)