Talk:Wireless network configuration

From ArchWiki
Revision as of 16:49, 12 September 2013 by Xtian (Talk | contribs) (Wireless status: new section)

Jump to: navigation, search

Management methods

I'd say Wireless_Setup#Management_methods is quite useless in current state. The basic info has been moved into the introduction in Wireless_Setup#Wireless_management. The first table says absolutely nothing, there's nothing to compare. The second table could be (expanded and) moved to Wireless_Setup#Automatic_setup, but I think it's better to describe the software in sentences. -- Lahwaacz (talk) 13:00, 7 August 2013 (UTC)

The first table denotes the first mention of the packages (wpa_supplicant et al) now. They were linked in the summary but that para was rm'ed. I still think they should be pointed at on that page, early too. The second sould be moved down and could need an overhaul, yes. The column like "autoconnect on boot" is pretty useless for starters.--Indigo (talk) 21:20, 7 August 2013 (UTC)
Is your point that there's no Install userspace tools section at the beginning? I think the userspace tools are only needed in Wireless Setup#Manual setup (and Wireless Setup#Troubleshooting of course, but Wireless Setup#Device driver mentions it). People who read Wireless Setup#Device driver and then skip to Wireless Setup#Automatic setup do not have to install them explicitly, they are installed as dependencies to network managers (note that netctl does not require iw nor wireless_tools). I'm not against adding such section, but I don't see any content which would fit there. If you have an idea, feel free to discuss/edit the page. -- Lahwaacz (talk) 22:44, 7 August 2013 (UTC)
I agree with the managers dependency bit and don't want to create a new subsection on userspace either. But I was giving you a reason why the first table is not useless, since the tools are used right in the next section (which is manual setup). I can edit it a bit later. --Indigo (talk) 18:01, 8 August 2013 (UTC)
Done some editing. I would leave the first table in, but it is true that Wireless Setup#Manual setup mentions packages now too. Contextually it works better like this then rm'ing the table imo though. I added manual connection to the second table to see how it works out. If the second table gets moved down to the tools, that line should go again of course. Thoughts? --Indigo (talk) 10:28, 11 August 2013 (UTC)
I don't like the first table listing multiple tools in one cell with no apparent reason (ip even twice), so I suggest reorganizing the table like this:
Management method
(/=alternatives)
Interface activation Wireless connection management Assigning IP address
Manually managed,
with no or WEP encryption
ip iw / iwconfig ip / dhcpcd / dhclient
Manually managed,
with WPA or WPA2 PSK encryption
ip iw / iwconfig + wpa_supplicant ip / dhcpcd / dhclient
Automatically managed,
with network profiles support
netctl, Wicd, NetworkManager, etc.
The second table should compare tools for the automatic method, I wouldn't list manual there. I'm not even sure if wvdial should be listed there, you could add pppd for the same reason.
As for moving the tables, I'd merge the first table into the introduction of Wireless Setup#Wireless management (effectively just removing the section heading) and move the second table into Wireless Setup#Automatic setup.
-- Lahwaacz (talk) 11:21, 11 August 2013 (UTC)
As I look at the table now, it seems highly inaccurate - netctl, wicd and NetworkManager use wpa_supplicant and dhcpcd internally (wicd even uses net-tools and wireless_tools), you just don't have to manage them directly. Perhaps that should be mentioned. -- Lahwaacz (talk) 11:38, 11 August 2013 (UTC)
Yes, I added that, thanks. Networkmanager uses dhclient btw. And your version is much better, yes. Just changing it slightly
Management method Interface activation Wireless connection management
(/=alternatives)
Assigning IP address
(/=alternatives)
Manually managed,
with no or WEP encryption
ip iw / iwconfig ip / dhcpcd / dhclient
Manually managed,
with WPA or WPA2 PSK encryption
ip iw / iwconfig + wpa_supplicant ip / dhcpcd / dhclient
Automatically managed,
with network profiles support
netctl, Wicd, NetworkManager, etc.

These tools pull in the required dependencies from the list of packages in the manual method.

Replace it, if you are ok with it. I'm fine with your other suggestions too. The reason I added wvdial was to make clear networkmanager is not the only alternative for 3G. --Indigo (talk) 12:34, 11 August 2013 (UTC)
Looks good, I've updated it with slight change to the links. Next I'll try to update the second table. -- Lahwaacz (talk) 14:20, 11 August 2013 (UTC)
I consider this issue solved, closing. -- Lahwaacz (talk) 10:56, 21 August 2013 (UTC)
Yes, also the second table works well now after your move/edit. I learned on the way that netctl also supports ppp/3G modems; great tool they built. --Indigo (talk) 22:37, 22 August 2013 (UTC)

Wireless status

My2c regarding the Check the driver status sub-section:

[quote]

Check kernel messages for firmware being loaded

$ dmesg |grep firmware

[ 7.148259] iwlwifi 0000:02:00.0: loaded firmware version 39.30.4.1 build 35138 op_mode iwldvm

[/quote]

The search keyword 'firmware' was not included in the kernel message for my wireless driver. Being new to manual setup I didn't think about the command dmesg, and assumed the output meant my kernel was not loaded. However the previous command lspci -k had indicated it was loaded creating unnecessary confusion.

I suggest the keyword 'firmware' be changed to reflect the output of the earlier test, lspci -k, in order to maintain continuity. This could change to an adopted convention as with a note further down the page [quote] Note: Examples in this section assume that your wireless device is wlan0 to connect to your_essid wifi accesspoint. Replace both accordingly. [/quote] Or use man page conventions, dmesg | grep [kernel driver] But since I'm a novice, I can't be certain the dmesg output will _always_ include the driver named by lspci on the relevant dmesg line.

See also this this poster's attempt at describing his wireless setup. Its thorough, but it also shows the same discontinuity. "iwlwifi" is the kernel driver, but the output from his posted lspci command seems to be truncated and does not include the driver name (in a sea of some unfamiliar commands, parameters, and device/software proper names).