Difference between revisions of "How to configure the network interfaces"
(apply network configuration at runtime with systemd) (Tag: Visual edit) |
|||
| (11 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | == How to configure the network interfaces == | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | == | ||
For deploying an Embedded System, one of the most important configuration is the ''Network Interface configuration''. | For deploying an Embedded System, one of the most important configuration is the ''Network Interface configuration''. | ||
| Line 25: | Line 14: | ||
* [https://www.freedesktop.org/software/systemd/man/systemd.network.html systemd network configuration] | * [https://www.freedesktop.org/software/systemd/man/systemd.network.html systemd network configuration] | ||
| − | == Examples== | + | === Examples=== |
The following configuration assumptions are used in the paragraphs shown below: | The following configuration assumptions are used in the paragraphs shown below: | ||
| Line 33: | Line 22: | ||
* IP address of the device '''192.168.1.100''' | * IP address of the device '''192.168.1.100''' | ||
| − | == | + | === systemd === |
| − | The configuration | + | The network configuration for systemd are basically found in the <code>/etc/systemd/network/</code> directory. |
| − | + | The most simply way for configuring the network interface is to create/edit the file '''/etc/systemd/network/20-eth0.network''' as per the following paragraphs. In the event that there are another network interface, then this must be create/edit as '''/etc/systemd/network/20-eth1.network'''. | |
| + | For more example and usage hints on systemd, please refer to our [[XELK-AN-008:_How_to_use_systemd_on_an_Embedded_system#Configuring_the_network_interfaces | wiki]] page. | ||
| − | + | ==== Static IP address ==== | |
| − | + | SBC ORCA has two network interfaces, below is shown how to configure them both through a static IP. In the case of SBCX MINI there is only one ethernet interface, consequently going to configure only eth0 interface. | |
| − | |||
| − | |||
| − | === Static IP address === | ||
| − | |||
| + | Example for ethernet interface 0. | ||
<pre> | <pre> | ||
| − | + | [Match] | |
| − | + | Name=eth0 | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | = | + | # Prevent the interface loading if the kernel boots from nfs |
| + | KernelCommandLine=!nfsroot | ||
| − | + | [Network] | |
| − | + | Address=192.168.1.100 | |
| − | + | Gateway=192.168.1.254 | |
| − | + | DNS=192.168.1.1 | |
| − | |||
</pre> | </pre> | ||
| − | + | Example for ethernet interface 1. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<pre> | <pre> | ||
| − | + | [Match] | |
| − | + | Name=eth1 | |
| − | + | # Prevent the interface loading if the kernel boots from nfs | |
| + | KernelCommandLine=!nfsroot | ||
| − | + | [Network] | |
| − | + | Address=192.168.1.101 | |
| − | = | + | Gateway=192.168.1.254 |
| − | + | DNS=192.168.1.1 | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
</pre> | </pre> | ||
| − | + | Once modified, the <code>networkd</code> service should be resarted: | |
| − | + | systemctl restart systemd-networkd | |
| − | + | ==== Dynamic IP addres (DHCP) ==== | |
| − | + | SBC ORCA has two network interfaces, below is shown how to configure them both through DHCP. In the case of SBCX MINI there is only one ethernet interface, consequently going to configure only eth0 interface. | |
| − | + | The network interface is configured - using a proper DHCP server on the network - by using the '''DHCP''' key in the configuration file as the following: | |
| − | |||
| − | |||
<pre> | <pre> | ||
| Line 106: | Line 78: | ||
[Network] | [Network] | ||
| − | + | DHCP=yes | |
| − | |||
| − | |||
</pre> | </pre> | ||
| − | + | In the event that there are another network interface, the configuration file as the following: | |
| − | |||
| − | |||
<pre> | <pre> | ||
[Match] | [Match] | ||
| − | Name= | + | Name=eth1 |
# Prevent the interface loading if the kernel boots from nfs | # Prevent the interface loading if the kernel boots from nfs | ||
| Line 128: | Line 96: | ||
When systemd network starts, it tries to use a DHCP server present in the network to configure the interface. | When systemd network starts, it tries to use a DHCP server present in the network to configure the interface. | ||
| − | === DNS === | + | ==== DNS ==== |
The DNS key (in the configuration file) is used only if the '''systemd-resolved service''' is enabled and the ''/etc/resolv.conf'' has a symbolic link to ''/run/systemd/resolve/stub-resolv.conf'' | The DNS key (in the configuration file) is used only if the '''systemd-resolved service''' is enabled and the ''/etc/resolv.conf'' has a symbolic link to ''/run/systemd/resolve/stub-resolv.conf'' | ||
| Line 134: | Line 102: | ||
ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf | ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf | ||
| − | === loopback network interface === | + | Once modified, the <code>resolved</code> service should be resarted: |
| + | |||
| + | systemctl restart systemd-resolved | ||
| + | |||
| + | ==== loopback network interface ==== | ||
systemd contains native implementations of various tasks that need to be executed as part of the boot process. | systemd contains native implementations of various tasks that need to be executed as part of the boot process. | ||
For example, it sets the hostname or configures the loopback network device. | For example, it sets the hostname or configures the loopback network device. | ||
| − | === Apply configuration changes === | + | ==== Apply configuration changes ==== |
After editing the above files, changes are applied after reboot or by restarting <code>systemd-networkd.service</code>:<syntaxhighlight lang="bash"> | After editing the above files, changes are applied after reboot or by restarting <code>systemd-networkd.service</code>:<syntaxhighlight lang="bash"> | ||
| − | root@ | + | root@desk-mx8mp:~# systemctl restart systemd-networkd.service |
</syntaxhighlight> | </syntaxhighlight> | ||
Latest revision as of 09:51, 15 February 2023
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Contents
How to configure the network interfaces[edit | edit source]
For deploying an Embedded System, one of the most important configuration is the Network Interface configuration.
Once the Embedded Device is finally configured for stand-alone bootstrap, the network interface should be configured for reaching the device remotely via network connections like ssh, telnet, ftp, http, etc.
This Application Note briefly describes how it is possible to simply configure the network interfaces on SystemV (aka SysV) or systemd
Resources[edit | edit source]
For further details on network configuration, please refer - for example - to:
Examples[edit | edit source]
The following configuration assumptions are used in the paragraphs shown below:
- IP address range of the LAN network 192.168.1.0 - 192.168.1.255
- IP address of the gateway 192.168.1.254
- IP address of the device 192.168.1.100
systemd[edit | edit source]
The network configuration for systemd are basically found in the /etc/systemd/network/ directory.
The most simply way for configuring the network interface is to create/edit the file /etc/systemd/network/20-eth0.network as per the following paragraphs. In the event that there are another network interface, then this must be create/edit as /etc/systemd/network/20-eth1.network. For more example and usage hints on systemd, please refer to our wiki page.
Static IP address[edit | edit source]
SBC ORCA has two network interfaces, below is shown how to configure them both through a static IP. In the case of SBCX MINI there is only one ethernet interface, consequently going to configure only eth0 interface.
Example for ethernet interface 0.
[Match] Name=eth0 # Prevent the interface loading if the kernel boots from nfs KernelCommandLine=!nfsroot [Network] Address=192.168.1.100 Gateway=192.168.1.254 DNS=192.168.1.1
Example for ethernet interface 1.
[Match] Name=eth1 # Prevent the interface loading if the kernel boots from nfs KernelCommandLine=!nfsroot [Network] Address=192.168.1.101 Gateway=192.168.1.254 DNS=192.168.1.1
Once modified, the networkd service should be resarted:
systemctl restart systemd-networkd
Dynamic IP addres (DHCP)[edit | edit source]
SBC ORCA has two network interfaces, below is shown how to configure them both through DHCP. In the case of SBCX MINI there is only one ethernet interface, consequently going to configure only eth0 interface.
The network interface is configured - using a proper DHCP server on the network - by using the DHCP key in the configuration file as the following:
[Match] Name=eth0 # Prevent the interface loading if the kernel boots from nfs KernelCommandLine=!nfsroot [Network] DHCP=yes
In the event that there are another network interface, the configuration file as the following:
[Match] Name=eth1 # Prevent the interface loading if the kernel boots from nfs KernelCommandLine=!nfsroot [Network] DHCP=yes
When systemd network starts, it tries to use a DHCP server present in the network to configure the interface.
DNS[edit | edit source]
The DNS key (in the configuration file) is used only if the systemd-resolved service is enabled and the /etc/resolv.conf has a symbolic link to /run/systemd/resolve/stub-resolv.conf
ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
Once modified, the resolved service should be resarted:
systemctl restart systemd-resolved
loopback network interface[edit | edit source]
systemd contains native implementations of various tasks that need to be executed as part of the boot process.
For example, it sets the hostname or configures the loopback network device.
Apply configuration changes[edit | edit source]
After editing the above files, changes are applied after reboot or by restarting systemd-networkd.service:
root@desk-mx8mp:~# systemctl restart systemd-networkd.service
