Difference between revisions of "Talk:Network configuration"

From ArchWiki
Jump to: navigation, search
(Udev rule for static interface naming: talk point done)
(dhcpcd static profile expansion: re)
 
(97 intermediate revisions by 19 users not shown)
Line 1: Line 1:
==Set host name/IP==
+
== Wired network configuration ==
Shouldn't the hosts file include the local static IP address and computer name along with the loopback version?
 
- [[User:KitchM|KitchM]] 02:54, 1 June 2009 (EDT)
 
:Does anybody have more info on this? - [[User:Aaahaaap|Aaahaaap]] 11:22, 2 November 2009 (EST)
 
::I sure wish someone did. - [[User:KitchM|KitchM]] 18:43, 2 November 2009 (EST)
 
  
==Troubleshooting Ping==
+
The introduction states:
The section entitled Troubleshooting should probably include a section to address the problem of ping not working correctly.
+
:"This page explains how to set up a wired connection to a network. If you need to set up wireless networking see the Wireless network configuration page."
- [[User:KitchM|KitchM]] 02:36, 1 June 2009 (EDT)
+
So, should this page be renamed to '''Wired network configuration'' ? Though in an ideal world, both Wired and Wireless configuration pages would be merged to reduce duplication, and move subtopics such as Troubleshooting to subpages ... -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:39, 29 September 2015 (UTC)
  
== Needs cleanup ==
+
:I don't really mind the current state, i.e. [[Wireless network configuration]] building on top of [[Network configuration]] (with a small overlap in [[Wireless_network_configuration#Check_the_driver_status]]). Otherwise there would have to be a "Network configuration" page and "Wired" and "Wireless" subpages, but what content from the current [[Network configuration]] is specific to wired connections? I think only [[Network_configuration#Device_Driver]] (which is easy to generalize) and [[Network_configuration#Troubleshooting]]. On the other hand most of the content in [[Wireless network configuration]] is unique to wireless devices, so IMO it is more natural to have just 2 pages instead of 3. Maybe the introduction should be modified instead? -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 16:30, 29 September 2015 (UTC)
  
The hostname portion fails to explain whether or not the quotation marks around the name is required.  The next example does not have them.  Either way, it must be explained.
+
::If we keep two pages, perhaps we should move [[Wireless network configuration]] to [[Network configuration/Wireless]], in addition to rewording the introduction? -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 01:36, 29 August 2016 (UTC)
  
We are left with another question; is it listed in hosts under the loopback address only, or also included in the standard IP address?
+
:::It might be argued that pages like [[dhcpcd]], [[Internet sharing]], [[Network bridge]] or [[MAC address spoofing]] could be all subpages of [[Network configuration]], just like [[Wireless network configuration]], and that's why they are all in [[:Category:Networking]] already. That's exactly the problem Wikipedia decided to solve by not using subpages for categorization, which I think makes sense here. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:28, 30 August 2016 (UTC)
  
Under IP Aliasing we are missing the explanation of what it is and why one would use it.
+
== Device names ==
 +
I've updated the section to also introduce users to {{man|5|systemd.link}}. 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 [[User:-1|-1]] ([[User talk:-1|talk]]) 21:38, 8 March 2017 (UTC)
  
Regarding the TCP window scaling, what does the following phrase mean:
+
: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 {{ic|99-default.link}} contains more than just the way interface names are set up. Maybe {{ic|99-default.link}} it is not the best idea, it should be possible to override just the {{ic|NamePolicy}}. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 21:51, 8 March 2017 (UTC)
"Or you can try to remove one of your RAM sticks (yes, sir)."
 
  
Let's clean this up, everyone.
+
::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. [[User:-1|-1]] ([[User talk:-1|talk]]) 22:05, 8 March 2017 (UTC)
  
Thanks. - [[User:KitchM|KitchM]] 22:38, 27 November 2009 (EST)
+
:::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 [https://wiki.archlinux.org/index.php?title=Network_configuration&type=revision&diff=470305&oldid=470152 this diff]. [[User:-1|-1]] ([[User talk:-1|talk]]) 13:14, 10 March 2017 (UTC)
 +
 
 +
== <s>Set device MTU and queue length</s> ==
 +
 
 +
I don't think info about changing MTU should be shared because it is almost certainly not what you want to do.  Anyone that needs to do this will easily figure out how to do this.  I feel making this info available somehow makes people think its a good thing to do, which it almost always is not and requiring it is probably hinting at a different problem.
 +
 
 +
I find it very unlikely anyone will need to increase the qlen.  Very unlikely.
 +
 
 +
{{unsigned|05:37, 30 March 2017‎|Rnabinger}}
 +
 
 +
:I agree. Moved to tips and tricks.  -- [[User:Rdeckard|Rdeckard]] ([[User_talk:Rdeckard|talk]]) 15:42, 14 April 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.  -- [[User:Rdeckard|Rdeckard]] ([[User_talk: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. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 20:53, 14 April 2017 (UTC)

Latest revision as of 20:53, 14 April 2017

Wired network configuration

The introduction states:

"This page explains how to set up a wired connection to a network. If you need to set up wireless networking see the Wireless network configuration page."

So, should this page be renamed to 'Wired network configuration ? Though in an ideal world, both Wired and Wireless configuration pages would be merged to reduce duplication, and move subtopics such as Troubleshooting to subpages ... -- Alad (talk) 14:39, 29 September 2015 (UTC)

I don't really mind the current state, i.e. Wireless network configuration building on top of Network configuration (with a small overlap in Wireless_network_configuration#Check_the_driver_status). Otherwise there would have to be a "Network configuration" page and "Wired" and "Wireless" subpages, but what content from the current Network configuration is specific to wired connections? I think only Network_configuration#Device_Driver (which is easy to generalize) and Network_configuration#Troubleshooting. On the other hand most of the content in Wireless network configuration is unique to wireless devices, so IMO it is more natural to have just 2 pages instead of 3. Maybe the introduction should be modified instead? -- Lahwaacz (talk) 16:30, 29 September 2015 (UTC)
If we keep two pages, perhaps we should move Wireless network configuration to Network configuration/Wireless, in addition to rewording the introduction? -- Alad (talk) 01:36, 29 August 2016 (UTC)
It might be argued that pages like dhcpcd, Internet sharing, Network bridge or MAC address spoofing could be all subpages of Network configuration, just like Wireless network configuration, and that's why they are all in Category:Networking already. That's exactly the problem Wikipedia decided to solve by not using subpages for categorization, which I think makes sense here. -- Lahwaacz (talk) 07:28, 30 August 2016 (UTC)

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)

Set device MTU and queue length

I don't think info about changing MTU should be shared because it is almost certainly not what you want to do. Anyone that needs to do this will easily figure out how to do this. I feel making this info available somehow makes people think its a good thing to do, which it almost always is not and requiring it is probably hinting at a different problem.

I find it very unlikely anyone will need to increase the qlen. Very unlikely.

—This unsigned comment is by Rnabinger (talk) 05:37, 30 March 2017‎. Please sign your posts with ~~~~!

I agree. Moved to tips and tricks. -- Rdeckard (talk) 15:42, 14 April 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)