Difference between revisions of "Talk:Network configuration"

From ArchWiki
Jump to: navigation, search
(Udev rule for static interface naming)
(Need to replace this part about IP address aliasing with netctl: new section)
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==Set host name/IP==
== Need to replace this part about IP address aliasing with netctl ==
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==
Configuration presented here isn't working.
The section entitled Troubleshooting should probably include a section to address the problem of ping not working correctly.
- [[User:KitchM|KitchM]] 02:36, 1 June 2009 (EDT)
== Needs cleanup ==
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.
We are left with another question; is it listed in hosts under the loopback address only, or also included in the standard IP address?
Under IP Aliasing we are missing the explanation of what it is and why one would use it.
Regarding the TCP window scaling, what does the following phrase mean:
"Or you can try to remove one of your RAM sticks (yes, sir)."
Let's clean this up, everyone.
Thanks. - [[User:KitchM|KitchM]] 22:38, 27 November 2009 (EST)
== <s>Title </s>==
Shouldn't that be Configuring The Network, or Network Configuration? - [[User:KitchM|KitchM]] 00:50, 25 December 2009 (EST)
In fact, wouldn't "Network Configuration" be better because Network would be the first and most common sense search item? _ [[User:KitchM|KitchM]] 12:36, 8 February 2010 (EST)
:Perhaps "Network" would be the best title, then, since this article deals primarily with using the "network" daemon. -- [[User:Pointone|pointone]] 11:37, 26 February 2010 (EST)
::You think so?  I don't know.  Doesn't it have more to do with network setup in general?  - [[User:KitchM|KitchM]] 00:14, 5 March 2010 (EST)
::: Page renamed. Close. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 09:45, 24 February 2013 (UTC)
== <s> Carrier Detect </s>==
This code can be used in <code>/etc/rc.d/network</code> to skip dhcp on interfaces without carriers:
if [[ "$ifcfg" = "dhcp" ]]; then
    carrier=`cat /sys/class/net/$ifname/carrier`
    if [[ $carrier -eq "1" ]]; then
        # remove the .pid file if it exists
        /bin/rm -f /var/run/dhcpcd-${1}.pid >/dev/null 2>&1
        /bin/rm -f /var/run/dhcpcd-${1}.cache >/dev/null 2>&1
        /sbin/dhcpcd $DHCPCD_ARGS ${1}
        echo "No carrier on $ifname"
    /sbin/ifconfig $ifcfg
: Close. Arch do not use rc.d anymore. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 09:46, 24 February 2013 (UTC)
== <s>Static IP </s>==
The indications given for the static ip configuration do not work for me. Concretely, the gateway config gives me problems. There should be another way of doing it.
:There is no doubt that one has to be extremely careful to follow the directions, keeping in mind that the directions are based on a clean install.  Missing any step, or having some pre-existing setting that conflicts will cause the failure.
:This is a perfect place for feedback so we can get this completely goof-proof.  Can you verify that you followed the exact steps described here?  Can you give us a list of which you did and where you skipped something that didn't apply?  Don't forget the hardware arrangement of your network.  I think your information would help us polish this a little and make it more accurate. - [[User:KitchM|KitchM]] 21:21, 11 November 2010 (EST)
::you might have to get an ip via dhcp, then assign yourself a static ip in the router settings and make your computer use that with no dhcp - it really depends on the type of router [[User:Thestinger|thestinger]] 21:32, 11 November 2010 (EST)
:::There is no doubt that the suggestion you offered might work in one particular situation.  However, we don't have enough information to make that determination yet, nor do we have any information to improve the article, which is the point here. - [[User:KitchM|KitchM]] 22:59, 11 November 2010 (EST)
:::: Old method changed to systemd service. Close this old report. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 09:49, 24 February 2013 (UTC)
== Udev rule for static interface naming ==
Save of reverted dispute:
{{Accuracy|From [http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames upstream document]:''The biggest of all however is that the userspace components trying to assign the interface name raced against the kernel assigning new names from the same "ethX" namespace, a race condition with all kinds of weird effects, among them that assignment of names sometimes failed. As a result support for this has been removed from systemd/udev a while back''. Someone should check this method work or not. Even if it does work, this method is highly '''not recommended'''.}}
:Hi, thanks for reviewing the addition. I revert the dispute though for the following reason: If you follow the upstream link you provide, you will see the udev rule set out as option 2 at the bottom when the systemd wiki explains about how to opt-out from the new naming scheme. Hence, it _is_ supported as long as arbitrary names (eth,wlan) are not used. The note in the section warns about arbitrary names already. I actually added the note about race conditions after either Dave or Thomas pointed it out on the bbs about a year ago. Feel free to dispute again, but I don't have information this does not work as of today (do you? maybe, systemd is updating quick). If you are ok with it, feel free to clean talk right away. Regards--[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 19:04, 26 March 2013 (UTC)

Revision as of 11:33, 17 September 2013

Need to replace this part about IP address aliasing with netctl

Configuration presented here isn't working.