Difference between revisions of "Talk:Wireless network configuration"

From ArchWiki
Jump to: navigation, search
(Splitting the page: new section)
m (Setting regulatory domain: unsigned)
 
(98 intermediate revisions by 15 users not shown)
Line 1: Line 1:
== iwlist wlan0 scanning syntax ==
+
== Modules - Generic ==
  
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.) -- [[User:Scr|Scr]] ([[User talk:Scr|talk]]) 12:26, 5 April 2013‎ (UTC)
+
If you found that you wireless permanently disconnects and you're using NetworkManager try to run:
:Similar to [[Core Utilities#ip|ip]], all objects may be written in full or abbreviated form, as long as it's unambiguous. For example, following commands are equivalent: {{ic|iwlist wlan0 scanning}}, {{ic|iwlist wlan0 scan}}, {{ic|iwlist wlan0 s}}. For good readability, I'd definitely not use the shortest {{ic|s}}. As {{ic|iwlist --help}} yields the full form {{ic|scanning}}, I think it's better to keep it that way. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 19:00, 1 August 2013 (UTC)
+
echo "options mac80211 probe_wait_ms=3000" > /etc/modprobe.d/wireless.conf -- 19:40, 23 September 2014‎ NickNill
  
== wpa_supplicant.conf ==
+
:Moved to talk as it doesn't explain what this does, nor how it fits in the article. Possibly belongs in [[Wireless_network_configuration#Random_disconnections]] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:55, 23 September 2014 (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)
+
== <s>Setting rts and fragmentation thresholds</s> ==
: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)
+
I'm not sure if this section is right. Because AFAIK, if rts and fragmentation threshold is at maximum, it's effectively disabled. Could someone with better knowledge enlighten me about this? --[[User:Baongoc124|Baongoc124]] ([[User talk:Baongoc124|talk]]) 08:10, 3 June 2015 (UTC)
  
==Mention modprobe -l==
+
:After reading up on the topic, I believe you are correct. I have edited the section accordingly. [[User:Silverhammermba|Silverhammermba]] ([[User talk:Silverhammermba|talk]]) 20:35, 23 February 2016 (UTC)
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.
+
<br>--[[User:Bhobbit|Bhobbit]] 01:03, 7 June 2009 (EDT)
+
  
== Overall article readability (notes and split) ==
+
== wireless_tools ==
There is no doubt this article is very rich, but I find it a bit messy overall.
+
iwlist uses outdated interfaces, and iw works better with modern wireless drivers. Can we remove the wireless_tools options from [[Wireless_network_configuration#Manual_setup]]? [[User:Pid1|Pid1]] ([[User talk:Pid1|talk]]) 15:11, 3 October 2015 (UTC)
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!
+
:Many sections in [[Wireless_network_configuration#Troubleshooting]] still suggest only iwconfig commands. We need to find equivalent iw options first... -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 15:21, 3 October 2015 (UTC)
  
-- [[User:Ambrevar|Ambrevar]] ([[User talk:Ambrevar|talk]]) 10:27, 6 July 2012 (UTC)
+
== "your key" ==
  
== Auto-connect if dropped or changed location Wicd ==
+
What is ''my key''? [[Wireless_network_configuration#Association]] --[[User:Kete|Kete]] ([[User talk:Kete|talk]]) 00:38, 11 March 2016 (UTC)
  
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 believe it is the security password configured on the router. [[User:Silverhammermba|Silverhammermba]] ([[User talk:Silverhammermba|talk]]) 12:47, 11 March 2016 (UTC)
  
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?
+
== <s>connection timeouts</s> ==
<br>-- [[User:Warddr|Warddr]] ([[User talk:Warddr|talk]]) 15:17, 22 August 2012 (UTC)
+
  
== Splitting the page ==
+
I have replaced the expansion with a remove template for [[Wireless network configuration#Connection always times out]]. Of course there will still be cases where a particular Linux client wifi module <-> access point can benefit from limiting either tx power or rate, yet the methods create more problems now than they used to. For rates and tx power both, all new wireless modes change them dynamically (for power saving) anyway. For tx power it often depends more on the traffic and how routers/clients in the area are setup (if they use auto channel for example).
 +
One could update instructions linking to new related [https://wireless.wiki.kernel.org/en/users/documentation/iw#modifying_transmit_bitrates iw docs], but I see this as detrimental for readers expecting a general troublesection item regarding "connection timeouts". --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 16:11, 4 April 2016 (UTC)
  
Regarding the note on top of the page, what about moving [[Wireless_Setup#Part_I:_Identify_Card.2FInstall_Driver]] to separate page, for example [[Wireless Setup/Hardware Support]]? That page would be focused on troubleshooting connection problems, installing drivers problems, and hardware support in general. Perhaps it would even make sense to merge some short dedicated pages into this one. What do you think? -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 19:13, 1 August 2013 (UTC)
+
No objections raised, removed with [https://wiki.archlinux.org/index.php?title=Wireless_network_configuration&type=revision&diff=432954&oldid=432952]. Closing. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 06:51, 27 April 2016 (UTC)
 +
 
 +
== Setting regulatory domain ==
 +
 
 +
In the section ''Respecting the regulatory domain'' in my opinion the following information should be added:
 +
 
 +
Another reason for an unchanged regulatory domain after adjusting the settings can be the fact, that linux uses information about the regulatory domain provided by the access point.
 +
As far as I unterstand these information are only retrieved, if the PC is associated with the access point.
 +
For details see: [https://wireless.wiki.kernel.org/en/developers/regulatory/processing_rules] (subsection: ''Country IE processing'')
 +
 
 +
{{unsigned|15:21, 7 May 2016‎|Aluser1137}}

Latest revision as of 15:47, 7 May 2016

Modules - Generic

If you found that you wireless permanently disconnects and you're using NetworkManager try to run: echo "options mac80211 probe_wait_ms=3000" > /etc/modprobe.d/wireless.conf -- 19:40, 23 September 2014‎ NickNill

Moved to talk as it doesn't explain what this does, nor how it fits in the article. Possibly belongs in Wireless_network_configuration#Random_disconnections -- Alad (talk) 17:55, 23 September 2014 (UTC)

Setting rts and fragmentation thresholds

I'm not sure if this section is right. Because AFAIK, if rts and fragmentation threshold is at maximum, it's effectively disabled. Could someone with better knowledge enlighten me about this? --Baongoc124 (talk) 08:10, 3 June 2015 (UTC)

After reading up on the topic, I believe you are correct. I have edited the section accordingly. Silverhammermba (talk) 20:35, 23 February 2016 (UTC)

wireless_tools

iwlist uses outdated interfaces, and iw works better with modern wireless drivers. Can we remove the wireless_tools options from Wireless_network_configuration#Manual_setup? Pid1 (talk) 15:11, 3 October 2015 (UTC)

Many sections in Wireless_network_configuration#Troubleshooting still suggest only iwconfig commands. We need to find equivalent iw options first... -- Lahwaacz (talk) 15:21, 3 October 2015 (UTC)

"your key"

What is my key? Wireless_network_configuration#Association --Kete (talk) 00:38, 11 March 2016 (UTC)

I believe it is the security password configured on the router. Silverhammermba (talk) 12:47, 11 March 2016 (UTC)

connection timeouts

I have replaced the expansion with a remove template for Wireless network configuration#Connection always times out. Of course there will still be cases where a particular Linux client wifi module <-> access point can benefit from limiting either tx power or rate, yet the methods create more problems now than they used to. For rates and tx power both, all new wireless modes change them dynamically (for power saving) anyway. For tx power it often depends more on the traffic and how routers/clients in the area are setup (if they use auto channel for example). One could update instructions linking to new related iw docs, but I see this as detrimental for readers expecting a general troublesection item regarding "connection timeouts". --Indigo (talk) 16:11, 4 April 2016 (UTC)

No objections raised, removed with [1]. Closing. --Indigo (talk) 06:51, 27 April 2016 (UTC)

Setting regulatory domain

In the section Respecting the regulatory domain in my opinion the following information should be added:

Another reason for an unchanged regulatory domain after adjusting the settings can be the fact, that linux uses information about the regulatory domain provided by the access point. As far as I unterstand these information are only retrieved, if the PC is associated with the access point. For details see: [2] (subsection: Country IE processing)

—This unsigned comment is by Aluser1137 (talk) 15:21, 7 May 2016‎. Please sign your posts with ~~~~!