Export translations

Settings

Group

Language

Format

Export for off-line translation

Export in native format

<languages/>
__TOC__

<div lang="en" dir="ltr" class="mw-content-ltr">
=Overview=
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Networking on Manjaro generally works out of the box without any special user intervention.  This article presents some specialized circumstances which some users may encounter and provides advice on how to overcome them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=Manually Setting DNS Servers=
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Usually, your DNS servers will be provided by your ISP automatically through DHCP.  However, sometimes it nesecary to use different DNS servers than the ones provided by your ISP.  In this situation you may find that your DNS or other non-standard nameserver addresses will get reset on reboot as {{ic|/etc/resolv.conf}} can be overwritten by NetworkManager or during the boot process. Here we will look at some techniques to preserve your settings.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==NetworkManager==
If you are using NetworkManager, this is one solution to the problem.  The NetworkManager's config drop folder is placed in <code>/etc/NetworkManager/conf.d</code>. In this folder you can place snippets which controls how NetworkManager works. The files should be named with a number and a description of its purpose and always end with {{ic|.conf}}. The files are then applied in numerical order from the lowest to the highest. A configuration in a file with a higher number will override what could have been configured in a lower numbered file.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
===Use resolvconf===
To have the resolvconf script handle the resolv.conf file for NetworkManager. 
Create a configuration file in NetworkManager's config drop folder
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
/etc/NetworkManager/conf.d/20-rc-manager.conf
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Save the file with this content
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
[main]
 rc-manager=resolvconf
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
To effectively make DNS handling a manual task create a file named
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
/etc/NetworkManager/conf.d/99-dont-touch-my-dns.conf
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Save the file with this content
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==/etc/resolvconf.conf==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The resolvconf.conf file is a shell script that is sourced by resolvconf, meaning that resolvconf.conf must contain valid shell commands. Take a look at its [https://jlk.fjfi.cvut.cz/arch/manpages/man/resolvconf.conf.5 man page] for more details and commands. The file is located at {{ic|/etc/resolvconf.conf}} and will require root privelege to edit.  For more information on how to edit a configuration file owned by root, please review [[Viewing_and_editing_configuration_files|this article]].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As an example, we will prepend OpenDNS nameservers to the top of our resolvconf file whenever called. We can achieve this by adding the following lines to the bottom of resolvconf.conf.
 # OpenDNS servers
 name_servers="208.67.222.222 208.67.220.220"
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
After making any changes simply update and apply your settings with the following command
{{UserCmd|command=sudo resolvconf -u}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==dhcpcd and resolv.conf.head/tail==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{note|Most Manjaro installs will not be using dhcpd by default}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
An alternative solution if you are using dhcpd is to input our settings to the {{ic|/etc/resolv.conf.head}} file. If this file does not exist then create it. The contents of {{ic|/etc/resolv.conf.head}} get sent to the top of {{ic|/etc/resolv.conf}} during the boot process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Following our previous example, if we want to use the OpenDNS servers with this method, we could place the following in the file:
 # OpenDNS servers
 nameserver 208.67.222.222
 nameserver 208.67.220.220
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=Setting Static IP Address=
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Using a GUI Tool==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Most editions of Manjaro come with some type a GUI tool or applet to manage NetworkManager.  This is the easiest way to set a static IP.  Simply go into the tool, usually in the system tray or menu, and input the required parameters for your network.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
==Using systemd==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you don't want to use NetworkManager the next easiest thing is to configure a static IP in systemd.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
First, make sure you aren't running NetworkManager
{{UserCmd|command=sudo systemctl disable --now NetworkManager.service}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Next you will need to find the name of your network device.  To locate the name, use the command {{ic|ip a}} as seen here:
<pre>ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:0c:29:02:55:c4 brd ff:ff:ff:ff:ff:ff
    inet 172.16.197.200/24 brd 172.16.197.255 scope global dynamic noprefixroute ens33
       valid_lft 1725sec preferred_lft 1725sec
    inet6 fe80::7116:2769:dac:6314/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
</pre>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
lo is the loopback device which can be ignored for the purposes of this article.  The device we need here is identified above as {{ic|ens33}}.  We will need this name in the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Now create or edit a file to hold the network configuration at {{ic|/etc/systemd/network/devicename.network}}.  Using the example above, the file would be called {{ic|/etc/systemd/network/ens33.network}}.  This file will need to be created/edited as root.  For more information on how to do that please review [[Viewing_and_editing_configuration_files|this article]].  An example of the contents of the file would look like this:
<pre>[Match]
Name=enp0s3
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
[Network]
Address=192.168.1.101/24
Gateway=192.168.1.1
DNS=208.67.222.222
DNS=208.67.220.220
</pre>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
All that remains is to start and enable the service using:
{{UserCmd|command=sudo systemctl enable --now systemd-networkd.service}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=Using dhcpcd Instead of NetworkManager=
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
NetworkManager is the default solution for networking on most Manjaro editions.  If you would prefer to use dhcpcd, that is also supported.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
First, ensure NetworkManager is disabled and not running
{{UserCmd|command=sudo systemctl disable --now NetworkManager.service}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Next, start and enable the dhcpcd service
{{UserCmd|command=sudo systemctl start --now dhcpcd.service}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* [https://blogs.gnome.org/dcbw/2015/02/16/networkmanager-for-administrators-part-1/ NetworkManager for Administrators]
* [https://wiki.archlinux.org/index.php/NetworkManager#Configure_NetworkManager_resolv.conf_management_mode_to_use_resolvconf Using resolvconf with NetworkManager]
</div>

[[Category:Contents Page{{#translation:}}]]