Talk:Network configuration

Device names

I've updated the section to also introduce users to systemd.link(5). Should we switch the whole section to prefer the systemd mechanism over udev? I'd vote in favor of systemd, since I believe systemd.links will instruct udev and not the other way round. I also find the link files easier to read and understand. We could keep the udev rules as a side note, but I'd rather remove them -1 (talk) 21:38, 8 March 2017 (UTC)

At least a note that udev processes the result of the link files should be kept. I'd also keep udev in Network_configuration#Reverting_to_traditional_device_names because 99-default.link contains more than just the way interface names are set up. Maybe 99-default.link it is not the best idea, it should be possible to override just the NamePolicy. -- Lahwaacz (talk) 21:51, 8 March 2017 (UTC)

Thank you. I'll just quickly read up on how the mechanism works exactly. I shall retain some information on udev as an alternative and remove overlaps. -1 (talk) 22:05, 8 March 2017 (UTC)

I'm sorry to say, but the rabbit hole got too deep and I sadly don't have the time to research this properly. I reverted the changes to the device name section since I don't want to leave the section in this unpolished state. I'd be happy if anyone wants to pick it up again: have a look at this diff. -1 (talk) 13:14, 10 March 2017 (UTC)

dhcpcd static profile expansion

In reference to the flag for expansion mentioning that the dhcpcd static profile is gone - it is now linked with the other network managers in the table. Static IP addresses can be assigned with all of the listed network managers, so I don't think we should list dhcpcd here as a special case. -- Rdeckard (talk) 15:39, 14 April 2017 (UTC)

Indeed, I missed that the table contains something else from the Network manager list. On second thought, maybe dhcpcd should be added there as well. -- Lahwaacz (talk) 20:53, 14 April 2017 (UTC)

Realtek RTL8111/8168B

The chipset version affected are shown as:

Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)

Upon installation, the network would work sporadically and was not the result of misconfigured DNS. The issue is a hardware issue. The 8169 driver will work, but requires setting the kernel parameter iommu=soft on various AMD FX cpus.

David C. Rankin, J.D.,P.E. -- Rankin Law Firm, PLLC (talk) 22:40, 22 January 2018 (UTC)

See Network_configuration#Gigabyte_Motherboard_with_Realtek_8111.2F8168.2F8411. -- Lahwaacz (talk) 22:50, 22 January 2018 (UTC)

Shall we cleanup these 2 sections and merge them into one? Isn't it observed only on AMD systems, I have this exact revision 06 with an intel based MB and I have not noticed issues. -- Kewl (talk) 12:12, 17 March 2018 (UTC)

Wifi Radar

The fact that Wifi Radar is a GUI application does not make it suitable for listing in the general "Network managers" section. Wireless_network_configuration#Utilities is more appropriate. —This unsigned comment is by Lahwaacz (talk) 1 June 2018‎. Please sign your posts with ~~~~!

Wifi Radar is a network manager and therefore belongs in Network configuration#Network managers. Also Wireless network configuration#Utilities implement wireless networking, while Wifi Radar doesn't.--Larivact (talk) 15:50, 10 June 2018 (UTC)

In that case WPA supplicant and iwd are network managers too. They should all be mentioned on the same page, which is Wireless network configuration. -- Lahwaacz (talk) 16:00, 10 June 2018 (UTC)

Good point but my argument that Wireless network configuration#Utilities implement wireless standards (WEXT, nl80211, WEP, WPA/WPA2) and Network configuration#Network managers don't still stands. --Larivact (talk) 04:58, 11 June 2018 (UTC)

Merge DHCP clients, network managers and wireless utilities tables

I propose merging Network configuration#DHCP, Network configuration#Network managers and Wireless network configuration#Utilities in one table. A lot of them depend or use one another and some can not be cleanly categorizes in only one category, e.g. dhcpcd is more than a simple DHCP client and iwd has built-in network configuration. I think that by placing them in one table it would be more easier to evaluate them and express their relationship.

I'll create a draft table in a while.

-- nl6720 (talk) 12:42, 7 October 2019 (UTC)

That table is a lot to take in, more so when half the entries have a large merged cell for wpa_supplicant. -- Alad (talk) 15:13, 7 October 2019 (UTC)

Two out of five also mention iwd :D But, I think, it does illustrate the relationship between the software in a better way than the separate tables.

This table has been on my mind for a while now, but now that I actually created it, it turned out more horrible than I though it would. I have no plans to merge it until the draft is in a usable state.

-- nl6720 (talk) 15:23, 7 October 2019 (UTC)

I'd definitely remove the "Systemd units" column, it is not necessary for users to make a choice - it's just an implementation detail which is described on the relevant wiki page (which users should definitely see before attempting to use it).

Also the "Wired" columns are misleading for wpa_supplicant, because it has a wired driver. Maybe just leave out "Wired" entirely, because green "Ethernet" is just an implication of green "Static" OR "DHCP", and most people don't care about "PPPoE" anyway.

-- Lahwaacz (talk) 16:38, 7 October 2019 (UTC)

Oh, right, it's that IEEE 802.1X thing.

I'm not certain about removing PPPoE, but I'd definitely like to remove WEXT and nl80211.

-- nl6720 (talk) 07:19, 8 October 2019 (UTC)

Yes, I think that WEXT and nl80211 can be removed... -- Lahwaacz (talk) 19:51, 8 October 2019 (UTC)

Looking at the table now, I'm wondering if there is enough content on the wiki to create the Network configuration/PPPoE and/or Network configuration/PPP subpages... -- Lahwaacz (talk) 07:08, 14 October 2019 (UTC)

Draft

Software	Package	Archiso [1]	Wired		PPP (e.g. 3G modem)	Wireless			IP address and route management		Interface
			Ethernet	PPPoE		WEP	WPA/WPA2	WPA3	Static	DHCP	CLI	TUI	GUI
ISC dhclient	dhclient	Yes	Yes	?	?	No			Yes	Yes	No
dhcpcd	dhcpcd	Yes	Yes	?	Yes	launches wpa_supplicant			Yes	Yes	No	No	dhcpcd-uiAUR
ConnMan	connman	No	Yes	No	Yes (uses ofonoAUR)	Yes (uses wpa_supplicant or iwd)			Yes	Yes	connmanctl(1)	Yes	Yes
netctl	netctl	Yes	Yes	Yes (uses ppp)	Yes	Yes (uses wpa_supplicant)		No	Yes	Yes (uses dhcpcd or dhclient)	netctl(1)	wifi-menu	No
NetworkManager	networkmanager	No (FS#54934)	Yes	Yes (uses rp-pppoe)	Yes (uses modemmanager)	Yes (uses wpa_supplicant or iwd)			Yes	Yes (uses internal, dhclient or dhcpcd)	nmcli(1)	nmtui(1)	Yes
systemd-networkd	systemd	Yes	Yes	No	No	No			Yes	Yes	networkctl(1)	No	No
Wicd	wicd-gitAUR	No	Yes	No	No	Yes (uses wpa_supplicant)		?	Yes	Yes (uses dhcpcd or dhclient)	wicd-cli(8)	wicd-curses(8)	wicd-gtk-gitAUR
wireless_tools	wireless_tools	Yes	No		No	Yes	No		No		No
iw	iw	Yes	No		No	Yes	No		No		iw(8)	No	No
wpa_supplicant	wpa_supplicant	Yes	Yes	No	No	Yes	Yes	Yes	No		wpa_cli(8)	No	wpa_supplicant_guiAUR
iwd	iwd	Yes	Yes	No	No	Yes	Yes	?	Yes	Yes	iwctl(1)	No	No