Difference between revisions of "Networking"

<translate>

<translate>

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.

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.

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.

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.

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.

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.

To have the resolvconf script handle the resolv.conf file for NetworkManager.  

To have the resolvconf script handle the resolv.conf file for NetworkManager.  

Create a configuration file in NetworkManager's config drop folder

Create a configuration file in NetworkManager's config drop folder

Save the file with this content

Save the file with this content

  rc-manager=resolvconf

  rc-manager=resolvconf

To effectively make DNS handling a manual task create a file named

To effectively make DNS handling a manual task create a file named

Save the file with this content

Save the file with this content

  dns=none

  dns=none

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]].

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]].

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.

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

  # OpenDNS servers

After making any changes simply update and apply your settings with the following command

After making any changes simply update and apply your settings with the following command

  sudo resolvconf -u

  sudo resolvconf -u

{{note|Most Manjaro installs will not be using dhcpd by default}}

{{note|Most Manjaro installs will not be using dhcpd by default}}

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.

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.

Following our previous example, if we want to use the OpenDNS servers with this method, we could place the following in the file:

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

  # OpenDNS servers

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.

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.

If you don't want to use NetworkManager the next easiest thing is to configure a static IP in systemd.

If you don't want to use NetworkManager the next easiest thing is to configure a static IP in systemd.

First, make sure you aren't running NetworkManager

First, make sure you aren't running NetworkManager

  sudo systemctl disable --now NetworkManager.service

  sudo systemctl disable --now NetworkManager.service

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:

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

<pre>ip a

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.

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.

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:

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]

<pre>[Match]

Name=enp0s3

Name=enp0s3

[Network]

[Network]

Address=192.168.1.101/24

Address=192.168.1.101/24

All that remains is to start and enable the service using:

All that remains is to start and enable the service using:

  sudo systemctl enable --now systemd-networkd.service

  sudo systemctl enable --now systemd-networkd.service

NetworkManager is the default solution for networking on most Manjaro editions.  If you would prefer to use dhcpcd, that is also supported.

NetworkManager is the default solution for networking on most Manjaro editions.  If you would prefer to use dhcpcd, that is also supported.

First, ensure NetworkManager is disabled and not running

First, ensure NetworkManager is disabled and not running

  sudo systemctl disable --now NetworkManager.service

  sudo systemctl disable --now NetworkManager.service

Next, start and enable the dhcpcd service

Next, start and enable the dhcpcd service

  sudo systemctl start --now dhcpcd.service

  sudo systemctl start --now dhcpcd.service

* [https://blogs.gnome.org/dcbw/2015/02/16/networkmanager-for-administrators-part-1/ NetworkManager for Administrators]

* [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]

* [https://wiki.archlinux.org/index.php/NetworkManager#Configure_NetworkManager_resolv.conf_management_mode_to_use_resolvconf Using resolvconf with NetworkManager]