https://wiki.ttsh.dk/api.php?action=feedcontributions&feedformat=atom&user=MikeMike's wiki - User contributions [en]2026-06-01T13:39:25ZUser contributionsMediaWiki 1.39.1https://wiki.ttsh.dk/index.php?title=Tips_and_tricks&diff=82Tips and tricks2025-08-01T08:57:23Z<p>Mike: Created page with "There are may tips for debugging yocto. To build any recipy use $bitbake <target name> $bitbake To fetch elements for a recipy $ bitbake <your-image-or-recipe> --runall=fetch To clean a recipy $ bitbake <your-image-or-recipe> --runall=cleanall To analyse the environment $ bitbake -e | grep ^TARGET_ARCH To fetch everything including cross compiler use $ bitbake -c fetch world"</p>
<hr />
<div>There are may tips for debugging yocto.<br />
<br />
<br />
To build any recipy use<br />
<br />
$bitbake <target name><br />
<br />
$bitbake <br />
<br />
<br />
To fetch elements for a recipy<br />
<br />
$ bitbake <your-image-or-recipe> --runall=fetch<br />
<br />
<br />
To clean a recipy<br />
<br />
$ bitbake <your-image-or-recipe> --runall=cleanall<br />
<br />
<br />
To analyse the environment<br />
<br />
$ bitbake -e | grep ^TARGET_ARCH<br />
<br />
<br />
To fetch everything including cross compiler use<br />
<br />
$ bitbake -c fetch world</div>Mikehttps://wiki.ttsh.dk/index.php?title=Yocto&diff=81Yocto2025-08-01T08:52:52Z<p>Mike: </p>
<hr />
<div>[[ create patches ]]<br />
<br />
[[tips and tricks]] <br />
<br />
=== Notes on Yocto. ===<br />
[[Settings for yocto]]</div>Mikehttps://wiki.ttsh.dk/index.php?title=Main_Page&diff=80Main Page2025-08-01T08:52:29Z<p>Mike: </p>
<hr />
<div>Why yet another collection of commands.<br />
<br />
Basically I'm getting tired of trying to find things via google, 90% of the matches are irrelevant to the searches, and thus I am collecting notes on how to do common tasks, that does NOT involve the usage of a GUI, as I find that annoying to use when running remote support -having to go through 3-4 UI bridges, to get to a service, just isn't efficient.<br />
<br />
<br />
This information is put out public, and contains nothing restricted, but is intended as information for people.<br />
<br />
<br />
[[Tooling information]]<br />
<br />
[[git tricks]]<br />
<br />
[[Docker ]]<br />
<br />
[[Linux]]<br />
<br />
[[systemd]]<br />
<br />
[[email]]<br />
<br />
[[yocto]]<br />
<br />
[[wiki tricks]]<br />
<br />
__FORCETOC__</div>Mikehttps://wiki.ttsh.dk/index.php?title=Docker&diff=79Docker2024-10-09T10:01:25Z<p>Mike: </p>
<hr />
<div>Docker information.. <br />
<br />
Docker has a lot of good features, however, there are also caveats that needs to be considered<br />
<br />
[[docker security]]<br />
<br />
[[ docker compose ]]<br />
<br />
[[ Dockerfile]]<br />
<br />
[[Docker rootless]]</div>Mikehttps://wiki.ttsh.dk/index.php?title=Block_id&diff=78Block id2024-02-09T17:04:20Z<p>Mike: Created page with "get the block id<pre> # blkid /dev/sda1 </pre>change fstab to mount by uuid instead. e.g.<pre> UUID="b8f0a58b-6dce-4d8a-89f0-d82bb2edcd01" /nfs ext4 defaults 0 2 UUID="6af41e26-7634-4bb1-9ea0-902401b45375" none swap defaults 0 0 </pre>"</p>
<hr />
<div>get the block id<pre><br />
# blkid /dev/sda1<br />
</pre>change fstab to mount by uuid instead.<br />
<br />
e.g.<pre><br />
UUID="b8f0a58b-6dce-4d8a-89f0-d82bb2edcd01" /nfs ext4 defaults 0 2<br />
UUID="6af41e26-7634-4bb1-9ea0-902401b45375" none swap defaults 0 0 <br />
<br />
</pre></div>Mikehttps://wiki.ttsh.dk/index.php?title=Linux&diff=77Linux2024-02-09T16:55:23Z<p>Mike: </p>
<hr />
<div>[[ Working with disk images]]<br />
<br />
[[working with network interfaces]]<br />
<br />
[[ Working with dhcpd]]<br />
<br />
[[ yocto ]]<br />
<br />
[[iptables-firewalls]]<br />
<br />
[[orangepi]]<br />
<br />
[[block id]]</div>Mikehttps://wiki.ttsh.dk/index.php?title=Boot_from_m.2&diff=76Boot from m.22024-02-09T16:55:00Z<p>Mike: </p>
<hr />
<div>disk imagesTo boot from M.2. requires some changes. transfer boot image to m.2. which can be done by restoring the boot image directly<pre><br />
# dd if=bootimg of=/dev/nvme0 bs=10M status=progress<br />
</pre>However, this does not allow you to easily change the partition tables, and thus..<br />
<br />
use fdisk to create the partition table, and mount it up as you want eg.<pre><br />
Create the following partitions <br />
<br />
/ 100G<br />
/boot 1G<br />
/var 100G<br />
/home 100G<br />
swap 16G<br />
<br />
using fdisk.<br />
<br />
format each partition using mkfs.ext4 for non-swap partitions <br />
format each swap partition using mkswap<br />
<br />
mount up the structure in the way you want.<br />
<br />
# mkdir -p /mnt/sysimage/ /mnt/sysimage/boot /mnt/sysimage/var /mnt/sysimage/home <br />
<br />
mount partitions under /mnt/sysimage<br />
<br />
mount disk image<br />
<br />
- using losetup<br />
<br />
# mkdir -p /mnt/sys1/ /mnt/sys1/boot <br />
<br />
mount partitions under /mnt/sys1<br />
<br />
Transfer files.<br />
<br />
# (cd /mnt/sys1; tar cvf - * ) | (cd /mnt/sysimage ; tar xf -)<br />
</pre>having transferred all of the data to the new drive we need to reset the partitions to mount them, this involved setting the uuid on the devices, and mount them using uuid.</div>Mikehttps://wiki.ttsh.dk/index.php?title=Linux&diff=75Linux2024-02-09T16:53:44Z<p>Mike: </p>
<hr />
<div>[[ Working with disk images]]<br />
<br />
[[working with network interfaces]]<br />
<br />
[[ Working with dhcpd]]<br />
<br />
[[ yocto ]]<br />
<br />
[[iptables-firewalls]]<br />
<br />
[[orangepi]]</div>Mikehttps://wiki.ttsh.dk/index.php?title=Boot_from_m.2&diff=74Boot from m.22024-02-09T16:49:38Z<p>Mike: </p>
<hr />
<div>To boot from M.2. requires some changes. transfer boot image to m.2. which can be done by restoring the boot image directly<pre><br />
# dd if=bootimg of=/dev/nvme0 bs=10M status=progress<br />
</pre>However, this does not allow you to easily change the partition tables, and thus..<br />
<br />
use fdisk to create the partition table, and mount it up as you want eg.<pre><br />
Create the following partitions <br />
<br />
/ 100G<br />
/boot 1G<br />
/var 100G<br />
/home 100G<br />
swap 16G<br />
<br />
using fdisk.<br />
<br />
format each partition using mkfs.ext4 for non-swap partitions <br />
format each swap partition using mkswap<br />
<br />
mount up the structure in the way you want.<br />
<br />
# mkdir -p /mnt/sysimage/ /mnt/sysimage/boot /mnt/sysimage/var /mnt/sysimage/home <br />
<br />
mount partitions under /mnt/sysimage<br />
<br />
mount disk image<br />
<br />
- using losetup<br />
<br />
# mkdir -p /mnt/sys1/ /mnt/sys1/boot <br />
<br />
mount partitions under /mnt/sys1<br />
<br />
Transfer files.<br />
<br />
# (cd /mnt/sys1; tar cvf - * ) | (cd /mnt/sysimage ; tar xf -)<br />
</pre></div>Mikehttps://wiki.ttsh.dk/index.php?title=Boot_from_m.2&diff=73Boot from m.22024-02-09T16:45:02Z<p>Mike: Created page with "To boot from M.2. requires some changes. transfer boot image to m.2. which can be done by restoring the boot image directly<pre> # dd if=bootimg of=/dev/nvme0 bs=10M status=progress </pre>However, this does not allow you to easily change the partition tables, and thus.. use fdisk to create the partition table, and mount it up as you want eg.<pre> Create the following partitions / 100G /boot 1G /var 100G /home 100G swap 16G using fdisk. format each partition using m..."</p>
<hr />
<div>To boot from M.2. requires some changes. transfer boot image to m.2. which can be done by restoring the boot image directly<pre><br />
# dd if=bootimg of=/dev/nvme0 bs=10M status=progress<br />
</pre>However, this does not allow you to easily change the partition tables, and thus..<br />
<br />
use fdisk to create the partition table, and mount it up as you want eg.<pre><br />
Create the following partitions <br />
<br />
/ 100G<br />
/boot 1G<br />
/var 100G<br />
/home 100G<br />
swap 16G<br />
<br />
using fdisk.<br />
<br />
format each partition using mkfs.ext4 for non-swap partitions <br />
format each swap partition using mkswap<br />
<br />
mount up the structure in the way you want.<br />
<br />
# mkdir -p / /boot /var /home <br />
<br />
mount partitions under /mnt/sysimage<br />
<br />
mount disk image<br />
<br />
- using losetup<br />
<br />
mount partitions under /mnt/sys1<br />
<br />
Transfer files.<br />
<br />
# (cd /mnt/sys1; tar cvf - * ) | (cd /mnt/sysimage ; tar xf -)<br />
</pre></div>Mikehttps://wiki.ttsh.dk/index.php?title=Orangepi&diff=72Orangepi2024-02-09T16:30:33Z<p>Mike: Created page with "boot from m.2"</p>
<hr />
<div>[[boot from m.2]]</div>Mikehttps://wiki.ttsh.dk/index.php?title=Linux&diff=71Linux2024-02-09T16:30:15Z<p>Mike: </p>
<hr />
<div>[[ Working with disk images]]<br />
<br />
[[working with network interfaces]]<br />
<br />
[[ Working with dhcpd]]<br />
<br />
[[ yocto ]]<br />
<br />
[[iptables-firewalls]]<br />
<br />
[[disk images]]<br />
<br />
[[orangepi]]</div>Mikehttps://wiki.ttsh.dk/index.php?title=Linux&diff=70Linux2024-02-09T16:29:45Z<p>Mike: </p>
<hr />
<div>[[ Working with disk images]]<br />
<br />
[[working with network interfaces]]<br />
<br />
[[ Working with dhcpd]]<br />
<br />
[[ yocto ]]<br />
<br />
[[iptables-firewalls]]<br />
<br />
[[disk images]]</div>Mikehttps://wiki.ttsh.dk/index.php?title=Disk_images&diff=69Disk images2024-02-09T16:28:59Z<p>Mike: Created page with "Mounting a disk image on linux<pre> # losetup -P /dev/loop0 ./Orangepi5_1.1.8_debian_bullseye_server_linux5.10.160.img # mkdir -p /mnt/sys1/boot # mount /dev/loop0p1 /mnt/sys1/ # mount /dev/loop0p2 /mnt/sys1/boot </pre>To undo the above<pre> # umount /mnt/sys1/boot /mnt/sys1 # losetup -d /dev/looop </pre>"</p>
<hr />
<div>Mounting a disk image on linux<pre><br />
# losetup -P /dev/loop0 ./Orangepi5_1.1.8_debian_bullseye_server_linux5.10.160.img<br />
# mkdir -p /mnt/sys1/boot<br />
# mount /dev/loop0p1 /mnt/sys1/<br />
# mount /dev/loop0p2 /mnt/sys1/boot<br />
</pre>To undo the above<pre><br />
# umount /mnt/sys1/boot /mnt/sys1<br />
# losetup -d /dev/looop<br />
</pre></div>Mikehttps://wiki.ttsh.dk/index.php?title=Linux&diff=68Linux2024-02-09T16:25:26Z<p>Mike: </p>
<hr />
<div>[[ Working with disk images]]<br />
<br />
[[working with network interfaces]]<br />
<br />
[[ Working with dhcpd]]<br />
<br />
[[ yocto ]]<br />
<br />
[[iptables-firewalls]]<br />
<br />
<br />
[[disk images]]</div>Mikehttps://wiki.ttsh.dk/index.php?title=Email&diff=67Email2024-01-29T09:06:34Z<p>Mike: Created page with "# install postfix # install dovecot # enable sasl for dovecot/postfix integration. # install postfwd ## https://postfwd.org/quick.html"</p>
<hr />
<div># install postfix<br />
# install dovecot<br />
# enable sasl for dovecot/postfix integration.<br />
# install postfwd<br />
## https://postfwd.org/quick.html</div>Mikehttps://wiki.ttsh.dk/index.php?title=Main_Page&diff=66Main Page2024-01-29T09:05:13Z<p>Mike: added start of email config</p>
<hr />
<div>Why yet another collection of commands.<br />
<br />
Basically I'm getting tired of trying to find things via google, 90% of the matches are irrelevant to the searches, and thus I am collecting notes on how to do common tasks, that does NOT involve the usage of a GUI, as I find that annoying to use when running remote support -having to go through 3-4 UI bridges, to get to a service, just isn't efficient.<br />
<br />
<br />
This information is put out public, and contains nothing restricted, but is intended as information for people.<br />
<br />
<br />
[[Tooling information]]<br />
<br />
[[git tricks]]<br />
<br />
[[Docker ]]<br />
<br />
[[Linux]]<br />
<br />
[[systemd]]<br />
<br />
[[email]]<br />
<br />
<br />
<br />
[[wiki tricks]]<br />
<br />
__FORCETOC__</div>Mikehttps://wiki.ttsh.dk/index.php?title=Iptables-firewalls&diff=65Iptables-firewalls2023-03-23T10:04:02Z<p>Mike: </p>
<hr />
<div>## allow all traffic on local interface<br />
iptables -A INPUT -i lo -j ACCEPT<br />
iptables -A OUTPUT -o lo -j ACCEPT<br />
<br />
## allow related traffic in and out<br />
iptables -A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT<br />
iptables -A OUTPUT -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
## drop invalid packages<br />
iptables -A INPUT -m conntrack --ctstate INVALID -j DROP<br />
<br />
## allow ssh access<br />
iptables -A INPUT -p tcp --dport 22 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT<br />
iptables -A OUTPUT -p tcp --sport 22 -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
## allow https and http traffic<br />
iptables -A INPUT -p tcp -m multiport --dports 80,443 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT<br />
iptables -A OUTPUT -p tcp -m multiport --dports 80,443 -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
## allow smtp access<br />
iptables -A INPUT -p tcp --dport 25 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT<br />
iptables -A OUTPUT -p tcp --sport 25 -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
## allow IMAP access<br />
iptables -A INPUT -p tcp --dport 143 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT<br />
iptables -A OUTPUT -p tcp --sport 143 -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
## allow IMAPS access<br />
iptables -A INPUT -p tcp --dport 993 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT<br />
iptables -A OUTPUT -p tcp --sport 993 -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
<br />
## NFS<br />
<pre><br />
iptables -A INPUT -s 172.18.0.1 -p udp -m multiport --dports 10053,111,2049,32769,875,892 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p udp -m multiport --dports 10053,111,2049,32769,875,892 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p tcp -m multiport --dports 10053,111,2049,32769,875,892 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p tcp -m multiport --dports 10053,111,2049,32769,875,892 -j REJECT<br />
iptables -A INPUT -s 172.18.0.0/24 -d 172.18.0.0/24 -p udp -m multiport --dports 10053,111,2049,32769,875,892 -m state --state NEW,ESTABLISHED -j ACCEPT <br />
iptables -A INPUT -s 172.18.0.0/24 -d 172.18.0.0/24 -p tcp -m multiport --dports 10053,111,2049,32803,875,892 -m state --state NEW,ESTABLISHED -j ACCEPT <br />
iptables -A OUTPUT -s 172.18.0.0/24 -d 172.18.0.0/24 -p udp -m multiport --sports 10053,111,2049,32769,875,892 -m state --state ESTABLISHED -j ACCEPT <br />
iptables -A OUTPUT -s 172.18.0.0/24 -d 172.18.0.0/24 -p tcp -m multiport --sports 10053,111,2049,32803,875,892 -m state --state ESTABLISHED -j ACCEPT <br />
</pre><br />
## cifs<br />
# The router doesn't need SMB access.<br />
<pre><br />
iptables -A INPUT -s 172.18.0.1 -p udp --dport 137 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p udp --dport 138 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p tcp --dport 139 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p tcp --dport 445 -j REJECT<br />
</pre><br />
# Actual Samba ports<br />
<pre><br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p tcp --dport 137 -j ACCEPT<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p tcp --dport 138 -j ACCEPT<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p udp --dport 137 -j ACCEPT<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p udp --dport 138 -j ACCEPT<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p tcp --dport 139 -j ACCEPT<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p tcp --dport 445 -j ACCEPT<br />
</pre><br />
<br />
<br />
#Note to remove junkt from your iptables like after uninstalling ufw.<br />
<pre><br />
for ufw in `iptables -n -L | grep -E ^Chain.*ufw | awk '{ print $2 }'`; do iptables -F $ufw; done<br />
iptables-save | grep -v ufw > /tmp/iptables<br />
## verify that the /tmp/iptables are as you want it to be<br />
iptables-restore < /tmp/iptables<br />
for ufw in `iptables -n -L | grep -E ^Chain.*ufw | awk '{ print $2 }'`; do iptables -X $ufw; done<br />
<br />
<b> now validate that the rules are as you want them to be </b><br />
</pre></div>Mikehttps://wiki.ttsh.dk/index.php?title=Iptables-firewalls&diff=64Iptables-firewalls2023-03-23T10:00:59Z<p>Mike: </p>
<hr />
<div>## allow all traffic on local interface<br />
iptables -A INPUT -i lo -j ACCEPT<br />
iptables -A OUTPUT -o lo -j ACCEPT<br />
<br />
## allow related traffic in and out<br />
iptables -A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT<br />
iptables -A OUTPUT -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
## drop invalid packages<br />
iptables -A INPUT -m conntrack --ctstate INVALID -j DROP<br />
<br />
## allow ssh access<br />
iptables -A INPUT -p tcp --dport 22 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT<br />
iptables -A OUTPUT -p tcp --sport 22 -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
## allow https and http traffic<br />
iptables -A INPUT -p tcp -m multiport --dports 80,443 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT<br />
iptables -A OUTPUT -p tcp -m multiport --dports 80,443 -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
## allow smtp access<br />
iptables -A INPUT -p tcp --dport 25 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT<br />
iptables -A OUTPUT -p tcp --sport 25 -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
## allow IMAP access<br />
iptables -A INPUT -p tcp --dport 143 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT<br />
iptables -A OUTPUT -p tcp --sport 143 -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
## allow IMAPS access<br />
iptables -A INPUT -p tcp --dport 993 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT<br />
iptables -A OUTPUT -p tcp --sport 993 -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
<br />
## NFS<br />
<pre><br />
iptables -A INPUT -s 172.18.0.1 -p udp -m multiport --dports 10053,111,2049,32769,875,892 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p udp -m multiport --dports 10053,111,2049,32769,875,892 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p tcp -m multiport --dports 10053,111,2049,32769,875,892 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p tcp -m multiport --dports 10053,111,2049,32769,875,892 -j REJECT<br />
iptables -A INPUT -s 172.18.0.0/24 -d 172.18.0.0/24 -p udp -m multiport --dports 10053,111,2049,32769,875,892 -m state --state NEW,ESTABLISHED -j ACCEPT <br />
iptables -A INPUT -s 172.18.0.0/24 -d 172.18.0.0/24 -p tcp -m multiport --dports 10053,111,2049,32803,875,892 -m state --state NEW,ESTABLISHED -j ACCEPT <br />
iptables -A OUTPUT -s 172.18.0.0/24 -d 172.18.0.0/24 -p udp -m multiport --sports 10053,111,2049,32769,875,892 -m state --state ESTABLISHED -j ACCEPT <br />
iptables -A OUTPUT -s 172.18.0.0/24 -d 172.18.0.0/24 -p tcp -m multiport --sports 10053,111,2049,32803,875,892 -m state --state ESTABLISHED -j ACCEPT <br />
</pre><br />
## cifs<br />
# The router doesn't need SMB access.<br />
<pre><br />
iptables -A INPUT -s 172.18.0.1 -p udp --dport 137 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p udp --dport 138 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p tcp --dport 139 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p tcp --dport 445 -j REJECT<br />
</pre><br />
# Actual Samba ports<br />
<pre><br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p tcp --dport 137 -j ACCEPT<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p tcp --dport 138 -j ACCEPT<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p udp --dport 137 -j ACCEPT<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p udp --dport 138 -j ACCEPT<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p tcp --dport 139 -j ACCEPT<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p tcp --dport 445 -j ACCEPT<br />
</pre></div>Mikehttps://wiki.ttsh.dk/index.php?title=Iptables-firewalls&diff=63Iptables-firewalls2023-03-23T10:00:04Z<p>Mike: Created page with "## allow all traffic on local interface iptables -A INPUT -i lo -j ACCEPT iptables -A OUTPUT -o lo -j ACCEPT ## allow related traffic in and out iptables -A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT iptables -A OUTPUT -m conntrack --ctstate ESTABLISHED -j ACCEPT ## drop invalid packages iptables -A INPUT -m conntrack --ctstate INVALID -j DROP ## allow ssh access iptables -A INPUT -p tcp --dport 22 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT iptab..."</p>
<hr />
<div>## allow all traffic on local interface<br />
iptables -A INPUT -i lo -j ACCEPT<br />
iptables -A OUTPUT -o lo -j ACCEPT<br />
<br />
## allow related traffic in and out<br />
iptables -A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT<br />
iptables -A OUTPUT -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
## drop invalid packages<br />
iptables -A INPUT -m conntrack --ctstate INVALID -j DROP<br />
<br />
## allow ssh access<br />
iptables -A INPUT -p tcp --dport 22 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT<br />
iptables -A OUTPUT -p tcp --sport 22 -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
## allow https and http traffic<br />
iptables -A INPUT -p tcp -m multiport --dports 80,443 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT<br />
iptables -A OUTPUT -p tcp -m multiport --dports 80,443 -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
## allow smtp access<br />
iptables -A INPUT -p tcp --dport 25 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT<br />
iptables -A OUTPUT -p tcp --sport 25 -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
## allow IMAP access<br />
iptables -A INPUT -p tcp --dport 143 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT<br />
iptables -A OUTPUT -p tcp --sport 143 -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
## allow IMAPS access<br />
iptables -A INPUT -p tcp --dport 993 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT<br />
iptables -A OUTPUT -p tcp --sport 993 -m conntrack --ctstate ESTABLISHED -j ACCEPT<br />
<br />
<br />
## NFS<br />
iptables -A INPUT -s 172.18.0.1 -p udp -m multiport --dports 10053,111,2049,32769,875,892 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p udp -m multiport --dports 10053,111,2049,32769,875,892 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p tcp -m multiport --dports 10053,111,2049,32769,875,892 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p tcp -m multiport --dports 10053,111,2049,32769,875,892 -j REJECT<br />
iptables -A INPUT -s 172.18.0.0/24 -d 172.18.0.0/24 -p udp -m multiport --dports 10053,111,2049,32769,875,892 -m state --state NEW,ESTABLISHED -j ACCEPT <br />
iptables -A INPUT -s 172.18.0.0/24 -d 172.18.0.0/24 -p tcp -m multiport --dports 10053,111,2049,32803,875,892 -m state --state NEW,ESTABLISHED -j ACCEPT <br />
iptables -A OUTPUT -s 172.18.0.0/24 -d 172.18.0.0/24 -p udp -m multiport --sports 10053,111,2049,32769,875,892 -m state --state ESTABLISHED -j ACCEPT <br />
iptables -A OUTPUT -s 172.18.0.0/24 -d 172.18.0.0/24 -p tcp -m multiport --sports 10053,111,2049,32803,875,892 -m state --state ESTABLISHED -j ACCEPT <br />
<br />
## cifs<br />
# The router doesn't need SMB access.<br />
iptables -A INPUT -s 172.18.0.1 -p udp --dport 137 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p udp --dport 138 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p tcp --dport 139 -j REJECT<br />
iptables -A INPUT -s 172.18.0.1 -p tcp --dport 445 -j REJECT<br />
<br />
# Actual Samba ports<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p tcp --dport 137 -j ACCEPT<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p tcp --dport 138 -j ACCEPT<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p udp --dport 137 -j ACCEPT<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p udp --dport 138 -j ACCEPT<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p tcp --dport 139 -j ACCEPT<br />
iptables -A INPUT -s 172.18.0.0/24 -m state --state NEW -p tcp --dport 445 -j ACCEPT</div>Mikehttps://wiki.ttsh.dk/index.php?title=Linux&diff=62Linux2023-03-23T08:57:56Z<p>Mike: </p>
<hr />
<div>[[ Working with disk images]]<br />
<br />
[[working with network interfaces]]<br />
<br />
[[ Working with dhcpd]]<br />
<br />
[[ yocto ]]<br />
<br />
[[iptables-firewalls]]</div>Mikehttps://wiki.ttsh.dk/index.php?title=Docker_security&diff=61Docker security2023-03-21T14:07:58Z<p>Mike: </p>
<hr />
<div>Docker is actually a major security risk on a system where you allow users to start and stop docker containers. A docker container per default uses root as the running user, and thus starting a docker container using some trickeries as a normal user, will compromise system security..<br />
<br />
For instance if I wish to compromise system passwords, I can simply do<br />
<br />
<pre><br />
mike@Server:~/docker$ docker run --rm -v /etc:/mnt/etc/ httpd:2.4 cat /mnt/etc/shadow<br />
root:(obfuscated by author)::0:99999:7:::<br />
bin:*:18358:0:99999:7:::<br />
daemon:*:18358:0:99999:7:::<br />
</pre><br />
<br />
This should NEVER be possible for a user to access private files, a simpilar proces could be used to create a new root user, with a known password, thus elevating a user to root user. <br />
<br />
Thus you must remember that any memer of the "docker" group, is per defintiion now root on your system.<br />
<br />
<br />
<br />
Always remember that Docker is NOT virtualization, and it runs in scope of your system.. <br />
<br />
A solutino to this is to create the file /etc/docker/daemon.json containing<br />
<br />
<pre><br />
{<br />
"userns-remap": "dockeruser",<br />
"log-driver": "journald",<br />
"log-opts": {<br />
"tag": "{{.Name}}"<br />
},<br />
"bip": "172.19.0.1/16",<br />
"dns" : [ "8.8.6.6" , "8.8.8.8" ] <br />
}<br />
</pre>Where you force a namsspace onto docker, where it runs as the user named - dockeruser, and as no more priviliges than a normal user.<br />
<br />
However you also need to create the user by<pre><br />
useradd dockeruser<br />
</pre>And then validate that the correct entries are created in /etc/subuid, and /etc/subgid<pre><br />
# grep dockeruser /etc/subuid<br />
dockeruser:1476256:65536<br />
# grep dockeruser /etc/subgid<br />
dockeruser:1476256:65536<br />
</pre>However all volumes will need to be owned by the above UID, or they will not be able to access the files..<br />
<br />
Thus you will need to apply the following on each volume<pre><br />
chown -R 1476256:1476256 .<br />
</pre>In my case with the above /etc/subuid, and /etc/subgid.<br />
<br />
Now the same test as above fails.<pre><br />
# docker run --rm -v /etc:/mnt/etc/ httpd:2.4 cat /mnt/etc/shadow<br />
cat: /mnt/etc/shadow: Permission denied<br />
</pre>As it should..<br />
<br />
However Namespaces are relatively new implementations, and they're not complete, and therefore it may be circumventable.<br />
<br />
This is however a much better situation than before.<br />
<br />
Do not let people get access to docker unless you trust them, or the machine is nothing important, and can easily be recreated.</div>Mikehttps://wiki.ttsh.dk/index.php?title=Wiki_tricks&diff=60Wiki tricks2023-02-02T16:27:15Z<p>Mike: </p>
<hr />
<div>{{#mermaid:sequenceDiagram<br />
participant Alice<br />
participant Bob<br />
Alice->John: Hello John, how are you?<br />
loop Healthcheck<br />
John->John: Fight against hypochondria<br />
end<br />
Note right of John: Rational thoughts <br/>prevail...<br />
John-->Alice: Great!<br />
John->Bob: How about you?<br />
Bob-->John: Jolly good!<br />
}}</div>Mikehttps://wiki.ttsh.dk/index.php?title=Wiki_tricks&diff=59Wiki tricks2023-02-02T16:21:03Z<p>Mike: Created page with "{{#mermaid:gantt dateFormat YYYY-MM-DD title Adding GANTT diagram functionality to mermaid section A section Completed task :done, des1, 2014-01-06,2014-01-08 Active task :active, des2, 2014-01-09, 3d Future task : des3, after des2, 5d Future task2 : des4, after des3, 5d section Critical tasks Completed task in the critical line :crit, done, 2014-01-06,24h Implement parser and jison..."</p>
<hr />
<div>{{#mermaid:gantt<br />
dateFormat YYYY-MM-DD<br />
title Adding GANTT diagram functionality to mermaid<br />
section A section<br />
Completed task :done, des1, 2014-01-06,2014-01-08<br />
Active task :active, des2, 2014-01-09, 3d<br />
Future task : des3, after des2, 5d<br />
Future task2 : des4, after des3, 5d<br />
section Critical tasks<br />
Completed task in the critical line :crit, done, 2014-01-06,24h<br />
Implement parser and jison :crit, done, after des1, 2d<br />
Create tests for parser :crit, active, 3d<br />
Future task in critical line :crit, 5d<br />
Create tests for renderer :2d<br />
Add to mermaid :1d<br />
}}</div>Mikehttps://wiki.ttsh.dk/index.php?title=Main_Page&diff=58Main Page2023-02-02T16:19:27Z<p>Mike: </p>
<hr />
<div>Why yet another collection of commands.<br />
<br />
Basically I'm getting tired of trying to find things via google, 90% of the matches are irrelevant to the searches, and thus I am collecting notes on how to do common tasks, that does NOT involve the usage of a GUI, as I find that annoying to use when running remote support -having to go through 3-4 UI bridges, to get to a service, just isn't efficient.<br />
<br />
<br />
This information is put out public, and contains nothing restricted, but is intended as information for people.<br />
<br />
<br />
[[Tooling information]]<br />
<br />
[[git tricks]]<br />
<br />
[[Docker ]]<br />
<br />
[[Linux]]<br />
<br />
[[systemd]]<br />
<br />
<br />
[[wiki tricks]]<br />
<br />
__FORCETOC__</div>Mikehttps://wiki.ttsh.dk/index.php?title=Settings_for_yocto&diff=57Settings for yocto2023-01-26T14:42:46Z<p>Mike: </p>
<hr />
<div>=== Disable Systemd for a app ===<br />
SYSTEMD_AUTO_ENABLE_${PN} = "disable"<br />
<br />
<br />
OPTS="--root=$D"<br />
<br />
systemctl $OPTS mask modutils.service<br />
<br />
Note Disable does not work in yocto<br />
<br />
=== Enable app in systemd ===<br />
OPTS="--root=$D"<br />
<br />
systemctl $OPTS enable modutils.service<br />
<br />
=== Manually disable ===<br />
remove the link created in /etc/systemd/system.<pre><br />
do_install_append() {<br />
rm -rf ${D}${sysconfdir}/systemd/system/sysinit.target.wants/systemd-timesyncd.service<br />
}<br />
</pre></div>Mikehttps://wiki.ttsh.dk/index.php?title=Systemd&diff=56Systemd2023-01-26T14:41:08Z<p>Mike: Created page with "https://docs.fedoraproject.org/en-US/fedora-coreos/tutorial-services/"</p>
<hr />
<div>https://docs.fedoraproject.org/en-US/fedora-coreos/tutorial-services/</div>Mikehttps://wiki.ttsh.dk/index.php?title=Main_Page&diff=55Main Page2023-01-26T14:40:58Z<p>Mike: </p>
<hr />
<div>Why yet another collection of commands.<br />
<br />
Basically I'm getting tired of trying to find things via google, 90% of the matches are irrelevant to the searches, and thus I am collecting notes on how to do common tasks, that does NOT involve the usage of a GUI, as I find that annoying to use when running remote support -having to go through 3-4 UI bridges, to get to a service, just isn't efficient.<br />
<br />
<br />
This information is put out public, and contains nothing restricted, but is intended as information for people.<br />
<br />
<br />
[[Tooling information]]<br />
<br />
[[git tricks]]<br />
<br />
[[Docker ]]<br />
<br />
[[Linux]]<br />
<br />
[[systemd]]<br />
<br />
__FORCETOC__</div>Mikehttps://wiki.ttsh.dk/index.php?title=Settings_for_yocto&diff=54Settings for yocto2023-01-26T14:40:37Z<p>Mike: </p>
<hr />
<div>=== Disable Systemd for a app ===<br />
SYSTEMD_AUTO_ENABLE_${PN} = "disable"<br />
<br />
<br />
OPTS="--root=$D"<br />
<br />
systemctl $OPTS mask modutils.service<br />
<br />
Note Disable does not work in yocto<br />
<br />
=== Enable app in systemd ===<br />
OPTS="--root=$D"<br />
<br />
systemctl $OPTS enable modutils.service<br />
<br />
=== Manually disable ===<br />
remove the link created in /etc/systemd/system.</div>Mikehttps://wiki.ttsh.dk/index.php?title=Settings_for_yocto&diff=53Settings for yocto2023-01-24T13:24:51Z<p>Mike: Created page with "=== Disable Systemd for a app === SYSTEMD_AUTO_ENABLE_${PN} = "disable" OPTS="--root=$D" systemctl $OPTS mask modutils.service Note Disable does not work in yocto === Enable app in systemd === OPTS="--root=$D" systemctl $OPTS enable modutils.service"</p>
<hr />
<div>=== Disable Systemd for a app ===<br />
SYSTEMD_AUTO_ENABLE_${PN} = "disable"<br />
<br />
<br />
OPTS="--root=$D"<br />
<br />
systemctl $OPTS mask modutils.service<br />
<br />
Note Disable does not work in yocto<br />
<br />
=== Enable app in systemd ===<br />
OPTS="--root=$D"<br />
<br />
systemctl $OPTS enable modutils.service</div>Mikehttps://wiki.ttsh.dk/index.php?title=Yocto&diff=52Yocto2023-01-24T13:22:19Z<p>Mike: </p>
<hr />
<div>[[ create patches ]] <br />
<br />
=== Notes on Yocto. ===<br />
[[Settings for yocto]]</div>Mikehttps://wiki.ttsh.dk/index.php?title=Create_patches&diff=51Create patches2023-01-18T15:43:32Z<p>Mike: </p>
<hr />
<div>https://wiki.yoctoproject.org/wiki/TipsAndTricks/Patching_the_source_for_a_recipe<br />
<br />
Patching the source for a recipe<br />
One of the useful things about OpenEmbedded building everything from source is that it's fairly easy to make changes to anything that gets built, but doing so for the first time can be a bit daunting.<br />
<br />
As part of building a recipe, OE creates a tmp/work/<architecture>/<recipe>/<version> directory, known as the "work directory". This is where all of the work done to build a recipe takes place. One of the things you'll find in this directory is the source, usually under a subdirectory named <recipename>-<version> or "git" (depending on how the fetched source is provided). The temptation (and what people used to do in the past) is to simply make changes here and then recompile, but there are several reasons why that's not a good idea:<br />
<br />
It's awkward - you have to use bitbake -c compile -f or bitbake -C compile to force recompilation, since the build system doesn't know that you've made any changes<br />
You can easily lose your changes if you're not careful e.g. running bitbake -c clean will wipe the directory out<br />
Luckily if you're using the fido (1.8) or later release, there's a much better method using the devtool command:<br />
<br />
# Run devtool modify <recipename>. This will fetch the sources for the recipe and unpack them to a workspace/sources/<recipename> directory and initialise it as a git repository if it isn't already one. If you prefer you can specify your own path, or if you already have your own existing source tree you can specify the path along with the -n option to use that instead of unpacking a new one<br />
# Make the changes you want to make to the source<br />
# Run a build to test your changes - you can just bitbake <recipename> or even build an entire image incorporating the changes assuming a package produced by the recipe is part of an image. There's no need to force anything - the build system will detect changes to the source and recompile as necessary.<br />
#* If you wish, test your changes on the target. There's a "devtool deploy-target" command which will copy the files installed at do_install over to the target machine assuming it has network access, and any dependencies are already present in the image<br />
# Repeat from step 2 as needed until you're happy with the results.<br />
#* At this point you will almost certainly want to place your changes in the form of a patch to be applied from the metadata - devtool provides help with this as well. Commit your changes using "git commit" (as many or as few commits as you'd like) and then run either:<br />
# devtool update-recipe <recipename> to update the original recipe - usually appropriate if it's your own recipe or you're submitting the changes back to the upstream layer devtool update-recipe -a <layerpath> <recipename> to put your changes in the form of a bbappend to be applied by a different layer. This is usually the desired method if your changes are customisations rather than bugfixes.<br />
#* If you're finished working on the recipe, run devtool reset <recipename>.<br />
This is just one of the things that devtool can do - it provides some powerful tools to help you maintain recipes and make changes to source code.<br />
<br />
<br />
https://wiki.koansoftware.com/index.php/Using_devtool_to_modify_recipes_in_Yocto<br />
<br />
== Example ==<br />
devtool modify linux-yocto-custom --no-extract tmp-glibc/work-shared/sm800a/kernel-source/<br />
<br />
== Create patches from first principles ==<br />
Do the changes and commit the files to the git repository and then generate a patch. eg.<pre><br />
git format-patch -1 head<br />
</pre>Generates a patch file, that can be added to the .bbappend file by<pre><br />
SRC_URI += "<br />
file://mypatch.patch<br />
"<br />
</pre>build again form a clean system, and the patch will be applied.</div>Mikehttps://wiki.ttsh.dk/index.php?title=Create_patches&diff=50Create patches2023-01-17T11:22:44Z<p>Mike: Created page with "https://wiki.yoctoproject.org/wiki/TipsAndTricks/Patching_the_source_for_a_recipe Patching the source for a recipe One of the useful things about OpenEmbedded building everything from source is that it's fairly easy to make changes to anything that gets built, but doing so for the first time can be a bit daunting. As part of building a recipe, OE creates a tmp/work/<architecture>/<recipe>/<version> directory, known as the "work directory". This is where all of the work..."</p>
<hr />
<div>https://wiki.yoctoproject.org/wiki/TipsAndTricks/Patching_the_source_for_a_recipe<br />
Patching the source for a recipe<br />
One of the useful things about OpenEmbedded building everything from source is that it's fairly easy to make changes to anything that gets built, but doing so for the first time can be a bit daunting.<br />
<br />
As part of building a recipe, OE creates a tmp/work/<architecture>/<recipe>/<version> directory, known as the "work directory". This is where all of the work done to build a recipe takes place. One of the things you'll find in this directory is the source, usually under a subdirectory named <recipename>-<version> or "git" (depending on how the fetched source is provided). The temptation (and what people used to do in the past) is to simply make changes here and then recompile, but there are several reasons why that's not a good idea:<br />
<br />
It's awkward - you have to use bitbake -c compile -f or bitbake -C compile to force recompilation, since the build system doesn't know that you've made any changes<br />
You can easily lose your changes if you're not careful e.g. running bitbake -c clean will wipe the directory out<br />
Luckily if you're using the fido (1.8) or later release, there's a much better method using the devtool command:<br />
<br />
# Run devtool modify <recipename>. This will fetch the sources for the recipe and unpack them to a workspace/sources/<recipename> directory and initialise it as a git repository if it isn't already one. If you prefer you can specify your own path, or if you already have your own existing source tree you can specify the path along with the -n option to use that instead of unpacking a new one.<br />
Make the changes you want to make to the source<br />
Run a build to test your changes - you can just bitbake <recipename> or even build an entire image incorporating the changes assuming a package produced by the recipe is part of an image. There's no need to force anything - the build system will detect changes to the source and recompile as necessary.<br />
If you wish, test your changes on the target. There's a "devtool deploy-target" command which will copy the files installed at do_install over to the target machine assuming it has network access, and any dependencies are already present in the image.<br />
Repeat from step 2 as needed until you're happy with the results.<br />
At this point you will almost certainly want to place your changes in the form of a patch to be applied from the metadata - devtool provides help with this as well. Commit your changes using "git commit" (as many or as few commits as you'd like) and then run either:<br />
devtool update-recipe <recipename> to update the original recipe - usually appropriate if it's your own recipe or you're submitting the changes back to the upstream layer<br />
devtool update-recipe -a <layerpath> <recipename> to put your changes in the form of a bbappend to be applied by a different layer. This is usually the desired method if your changes are customisations rather than bugfixes.<br />
If you're finished working on the recipe, run devtool reset <recipename>.<br />
This is just one of the things that devtool can do - it provides some powerful tools to help you maintain recipes and make changes to source code.</div>Mikehttps://wiki.ttsh.dk/index.php?title=Yocto&diff=49Yocto2023-01-17T11:22:09Z<p>Mike: Created page with " create patches "</p>
<hr />
<div>[[ create patches ]]</div>Mikehttps://wiki.ttsh.dk/index.php?title=Linux&diff=48Linux2023-01-17T11:21:58Z<p>Mike: </p>
<hr />
<div>[[ Working with disk images]]<br />
<br />
[[working with network interfaces]]<br />
<br />
[[ Working with dhcpd]]<br />
<br />
[[ yocto ]]</div>Mikehttps://wiki.ttsh.dk/index.php?title=Network-networkd&diff=47Network-networkd2023-01-17T11:21:31Z<p>Mike: Replaced content with "==Setup for Networkd== ===Switching to Networkd === <pre>$ systemctl stop NetworkManager $ systemctl disable NetworkManager $ systemctl enable systemd-networkd $ systemctl enable systemd-resolved $ systemctl start systemd-resolved $ rm /etc/resolv.conf $ ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf $ mkdir -p /etc/systemd/network</pre> ===Configuring Networkd=== ====What interfaces do we have==== <pre> # networkctl IDX LINK TYPE OPERATI..."</p>
<hr />
<div>==Setup for Networkd==<br />
<br />
===Switching to Networkd ===<br />
<pre>$ systemctl stop NetworkManager <br />
$ systemctl disable NetworkManager <br />
$ systemctl enable systemd-networkd<br />
$ systemctl enable systemd-resolved<br />
$ systemctl start systemd-resolved<br />
$ rm /etc/resolv.conf<br />
$ ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf<br />
$ mkdir -p /etc/systemd/network</pre><br />
<br />
===Configuring Networkd===<br />
<br />
====What interfaces do we have====<br />
<pre><br />
# networkctl<br />
IDX LINK TYPE OPERATIONAL SETUP <br />
1 lo loopback carrier unmanaged<br />
2 eno1 ether routable unmanaged<br />
3 br0 bridge routable unmanaged<br />
4 virbr0 bridge no-carrier unmanaged<br />
5 docker0 bridge no-carrier unmanaged<br />
6 br-b737ea16f9fc bridge no-carrier unmanaged<br />
7 vnet0 ether degraded unmanaged<br />
<br />
7 links listed.<br />
<br />
</pre><br />
<br />
====Configuring en01 - static====<br />
<pre><br />
$ cat >> /etc/systemd/network/00-eno1.network << EOF<br />
[Match]<br />
Name=enp3s0<br />
<br />
[Network]<br />
Address=192.168.1.50/24<br />
Gateway=192.168.1.1<br />
DNS=192.168.1.1<br />
EOF<br />
</pre><br />
<br />
====Configuring en01 - dhcp====<br />
<pre><br />
$ cat >> /etc/systemd/network/00-eno1.network << EOF<br />
[Match]<br />
Name=enp3s0<br />
<br />
[Network]<br />
DHCP=yes<br />
EOF<br />
</pre><br />
<br />
=== Controlling interfaces ===<br />
==== Full Restart ====<br />
<pre><br />
$ systemctl restart systemd-network<br />
</pre><br />
<br />
==== Interface only ====<br />
<br />
<pre><br />
$ networkctl up eno1<br />
</pre><br />
<br />
<pre><br />
$ networkctl down eno1<br />
</pre><br />
<br />
==IP Alias for Networkd==<br />
<pre><br />
$ cat >> /etc/systemd/network/00-eno1.network << EOF<br />
[Match]<br />
Name=enp3s0<br />
<br />
[Network]<br />
Address=192.168.1.50/24<br />
Address=172.14.0.50/24<br />
Gateway=192.168.1.1<br />
<br />
DNS=192.168.1.1<br />
<br />
Address=2a0a:3840:1337:126::b9c1:7ecb:1337/64<br />
Gateway=2a0a:3840:1337:126::1<br />
<br />
EOF<br />
</pre></div>Mikehttps://wiki.ttsh.dk/index.php?title=Working_with_dhcpd&diff=46Working with dhcpd2023-01-15T14:55:05Z<p>Mike: Created page with "== DHCPD is a powerful tool for managing a network == === Setting up dhcpd centos 8 === $ dnf install dhcp-server === Configure dhcpd ==="</p>
<hr />
<div>== DHCPD is a powerful tool for managing a network ==<br />
<br />
=== Setting up dhcpd centos 8 ===<br />
$ dnf install dhcp-server<br />
<br />
=== Configure dhcpd ===</div>Mikehttps://wiki.ttsh.dk/index.php?title=Linux&diff=45Linux2023-01-15T13:37:07Z<p>Mike: </p>
<hr />
<div>[[ Working with disk images]]<br />
<br />
[[working with network interfaces]]<br />
[[ Working with dhcpd]]</div>Mikehttps://wiki.ttsh.dk/index.php?title=First_principles&diff=44First principles2023-01-15T13:36:35Z<p>Mike: </p>
<hr />
<div>== Using ifconfig ==<br />
<br />
=== Show interface configuration ===<br />
<pre><br />
$ ifconfig eno1<br />
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500<br />
inet 192.168.1.79 netmask 255.255.255.0 broadcast 192.168.1.255<br />
inet6 fe80::a6a5:87ad:cb7a:6cad prefixlen 64 scopeid 0x20<link><br />
ether 50:eb:f6:3f:27:61 txqueuelen 1000 (Ethernet)<br />
RX packets 137223 bytes 104941638 (104.9 MB)<br />
RX errors 0 dropped 0 overruns 0 frame 0<br />
TX packets 91146 bytes 22484489 (22.4 MB)<br />
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br />
device interrupt 16 memory 0xa1400000-a1420000 <br />
</pre><br />
<br />
Show All interfaces<br />
<pre><br />
$ ifconfig<br />
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500<br />
inet 192.168.2.1 netmask 255.255.255.0 broadcast 192.168.2.255<br />
ether 92:51:fc:1b:36:38 txqueuelen 1000 (Ethernet)<br />
RX packets 277 bytes 28650 (28.6 KB)<br />
RX errors 0 dropped 0 overruns 0 frame 0<br />
TX packets 899 bytes 129148 (129.1 KB)<br />
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br />
<br />
br-b737ea16f9fc: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500<br />
inet 172.25.0.1 netmask 255.255.0.0 broadcast 172.25.255.255<br />
ether 02:42:79:64:bc:e2 txqueuelen 0 (Ethernet)<br />
RX packets 0 bytes 0 (0.0 B)<br />
RX errors 0 dropped 0 overruns 0 frame 0<br />
TX packets 0 bytes 0 (0.0 B)<br />
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br />
<br />
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500<br />
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255<br />
ether 02:42:db:62:09:42 txqueuelen 0 (Ethernet)<br />
.....<br />
</pre><br />
<br />
=== Add ip alias ===<br />
$ ifconfig eth0:1 10.10.20.218 netmask 255.255.255.0 broadcast 10.10.20.255<br />
<br />
== Using ip ==<br />
<br />
=== ip Usage ===<br />
<br />
==== ip help ====<br />
<br />
==== ip link show ====<br />
<pre><br />
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000<br />
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br />
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000<br />
link/ether 50:eb:f6:3f:27:61 brd ff:ff:ff:ff:ff:ff<br />
altname enp0s31f6<br />
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000<br />
link/ether 52:54:00:1f:16:1e brd ff:ff:ff:ff:ff:ff<br />
4: br-b737ea16f9fc: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default <br />
link/ether 02:42:72:e2:a7:bb brd ff:ff:ff:ff:ff:ff<br />
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default <br />
link/ether 02:42:25:da:f1:ee brd ff:ff:ff:ff:ff:ff<br />
<br />
</pre><br />
<br />
==== ip address show\ ====<br />
<pre><br />
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000<br />
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br />
inet 127.0.0.1/8 scope host lo<br />
valid_lft forever preferred_lft forever<br />
inet6 ::1/128 scope host <br />
valid_lft forever preferred_lft forever<br />
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000<br />
link/ether 50:eb:f6:3f:27:61 brd ff:ff:ff:ff:ff:ff<br />
altname enp0s31f6<br />
inet 192.168.1.80/24 brd 192.168.1.255 scope global eno1<br />
valid_lft forever preferred_lft forever<br />
inet 172.14.0.2/24 brd 172.14.0.255 scope global eno1<br />
valid_lft forever preferred_lft forever<br />
inet6 fe80::52eb:f6ff:fe3f:2761/64 scope link <br />
valid_lft forever preferred_lft forever<br />
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000<br />
link/ether 52:54:00:1f:16:1e brd ff:ff:ff:ff:ff:ff<br />
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0<br />
valid_lft forever preferred_lft forever<br />
4: br-b737ea16f9fc: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default <br />
link/ether 02:42:72:e2:a7:bb brd ff:ff:ff:ff:ff:ff<br />
inet 172.25.0.1/16 brd 172.25.255.255 scope global br-b737ea16f9fc<br />
valid_lft forever preferred_lft forever<br />
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default <br />
link/ether 02:42:25:da:f1:ee brd ff:ff:ff:ff:ff:ff<br />
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0<br />
<br />
</pre><br />
<br />
=== add ip alias ===<br />
$ ip a add 192.168.178.2/24 dev eth0</div>Mikehttps://wiki.ttsh.dk/index.php?title=Main_Page&diff=43Main Page2023-01-15T13:02:14Z<p>Mike: </p>
<hr />
<div>Why yet another collection of commands.<br />
<br />
Basically I'm getting tired of trying to find things via google, 90% of the matches are irrelevant to the searches, and thus I am collecting notes on how to do common tasks, that does NOT involve the usage of a GUI, as I find that annoying to use when running remote support -having to go through 3-4 UI bridges, to get to a service, just isn't efficient.<br />
<br />
<br />
This information is put out public, and contains nothing restricted, but is intended as information for people.<br />
<br />
<br />
[[Tooling information]]<br />
<br />
[[git tricks]]<br />
<br />
[[Docker ]]<br />
<br />
[[Linux]]<br />
<br />
__FORCETOC__</div>Mikehttps://wiki.ttsh.dk/index.php?title=Network-networkd&diff=42Network-networkd2023-01-15T13:00:08Z<p>Mike: </p>
<hr />
<div>==Setup for Networkd==<br />
<br />
===Switching to Networkd ===<br />
<pre>$ systemctl stop NetworkManager <br />
$ systemctl disable NetworkManager <br />
$ systemctl enable systemd-networkd<br />
$ systemctl enable systemd-resolved<br />
$ systemctl start systemd-resolved<br />
$ rm /etc/resolv.conf<br />
$ ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf<br />
$ mkdir -p /etc/systemd/network</pre><br />
<br />
===Configuring Networkd===<br />
<br />
====What interfaces do we have====<br />
<pre><br />
# networkctl<br />
IDX LINK TYPE OPERATIONAL SETUP <br />
1 lo loopback carrier unmanaged<br />
2 eno1 ether routable unmanaged<br />
3 br0 bridge routable unmanaged<br />
4 virbr0 bridge no-carrier unmanaged<br />
5 docker0 bridge no-carrier unmanaged<br />
6 br-b737ea16f9fc bridge no-carrier unmanaged<br />
7 vnet0 ether degraded unmanaged<br />
<br />
7 links listed.<br />
<br />
</pre><br />
<br />
====Configuring en01 - static====<br />
<pre><br />
$ cat >> /etc/systemd/network/00-eno1.network << EOF<br />
[Match]<br />
Name=enp3s0<br />
<br />
[Network]<br />
Address=192.168.1.50/24<br />
Gateway=192.168.1.1<br />
DNS=192.168.1.1<br />
EOF<br />
</pre><br />
<br />
====Configuring en01 - dhcp====<br />
<pre><br />
$ cat >> /etc/systemd/network/00-eno1.network << EOF<br />
[Match]<br />
Name=enp3s0<br />
<br />
[Network]<br />
DHCP=yes<br />
EOF<br />
</pre><br />
<br />
== Controlling interfaces ==<br />
<br />
=== Full Restart ===<br />
<pre><br />
$ systemctl restart systemd-network<br />
</pre><br />
<br />
=== Interface only ===<br />
<br />
===== Link up and down (does not reconfigure) =====<br />
<pre><br />
$ networkctl up eno1<br />
</pre><br />
<br />
<pre><br />
$ networkctl down eno1<br />
</pre><br />
<br />
===== Reconfigure interface based on configuration file =====<br />
<pre><br />
$ networkctl reconfigure eno1<br />
</pre><br />
<br />
== networkd useful commands ==<br />
<pre><br />
$ networkctl list<br />
IDX LINK TYPE OPERATIONAL SETUP <br />
1 lo loopback carrier unmanaged<br />
2 eno1 ether off unmanaged<br />
3 virbr0 bridge no-carrier unmanaged<br />
4 br-b737ea16f9fc bridge no-carrier unmanaged<br />
5 docker0 bridge no-carrier unmanaged<br />
<br />
5 links listed.<br />
root@workstation2:/etc/systemd/network# !ping<br />
<br />
</pre><br />
<br />
==IP Alias for Networkd==<br />
Adding an alias to an interface in networkd is closely related to the ip command, where the device simply receives more addresses on the interfaces. It does not show up as a an aliased device, which IMO makes it harder to understand, but YMMV.<pre><br />
$ cat >> /etc/systemd/network/00-eno1.network << EOF<br />
[Match]<br />
Name=enp3s0<br />
[Network]<br />
Address=192.168.1.50/24<br />
Address=172.14.0.50/24<br />
Gateway=192.168.1.1<br />
DNS=192.168.1.1<br />
EOF<br />
</pre><br />
<br />
== Networkd Configuration Paramters (from ubuntu's man pages) ==<br />
<br />
=== [Match] Section ===<br />
<pre><br />
MACAddress=<br />
The hardware address of the interface (use full colon-delimited hexadecimal, e.g.,<br />
01:23:45:67:89:ab).<br />
<br />
Path=<br />
A whitespace-separated list of shell-style globs matching the persistent path, as<br />
exposed by the udev property "ID_PATH". If the list is prefixed with a "!", the test<br />
is inverted; i.e. it is true when "ID_PATH" does not match any item in the list.<br />
<br />
Driver=<br />
A whitespace-separated list of shell-style globs matching the driver currently bound<br />
to the device, as exposed by the udev property "DRIVER" of its parent device, or if<br />
that is not set the driver as exposed by "ethtool -i" of the device itself. If the<br />
list is prefixed with a "!", the test is inverted.<br />
<br />
Type=<br />
A whitespace-separated list of shell-style globs matching the device type, as exposed<br />
by the udev property "DEVTYPE". If the list is prefixed with a "!", the test is<br />
inverted.<br />
<br />
Name=<br />
A whitespace-separated list of shell-style globs matching the device name, as exposed<br />
by the udev property "INTERFACE". If the list is prefixed with a "!", the test is<br />
inverted.<br />
<br />
Host=<br />
Matches against the hostname or machine ID of the host. See "ConditionHost=" in<br />
systemd.unit(5) for details.<br />
<br />
Virtualization=<br />
Checks whether the system is executed in a virtualized environment and optionally test<br />
whether it is a specific implementation. See "ConditionVirtualization=" in<br />
systemd.unit(5) for details.<br />
<br />
KernelCommandLine=<br />
Checks whether a specific kernel command line option is set (or if prefixed with the<br />
exclamation mark unset). See "ConditionKernelCommandLine=" in systemd.unit(5) for<br />
details.<br />
<br />
KernelVersion=<br />
Checks whether the kernel version (as reported by uname -r) matches a certain<br />
expression (or if prefixed with the exclamation mark does not match it). See<br />
"ConditionKernelVersion=" in systemd.unit(5) for details.<br />
<br />
Architecture=<br />
Checks whether the system is running on a specific architecture. See<br />
"ConditionArchitecture=" in systemd.unit(5) for details.<br />
<br />
</pre><br />
<br />
=== [Link] Section ===<br />
<pre><br />
MACAddress=<br />
The hardware address to set for the device.<br />
<br />
MTUBytes=<br />
The maximum transmission unit in bytes to set for the device. The usual suffixes K, M,<br />
G, are supported and are understood to the base of 1024.<br />
<br />
Note that if IPv6 is enabled on the interface, and the MTU is chosen below 1280 (the<br />
minimum MTU for IPv6) it will automatically be increased to this value.<br />
<br />
ARP=<br />
A boolean. Enables or disables the ARP (low-level Address Resolution Protocol) for<br />
this interface. Defaults to unset, which means that the kernel default will be used.<br />
<br />
For example, disabling ARP is useful when creating multiple MACVLAN or VLAN virtual<br />
interfaces atop a single lower-level physical interface, which will then only serve as<br />
a link/"bridge" device aggregating traffic to the same physical link and not<br />
participate in the network otherwise.<br />
<br />
Unmanaged=<br />
A boolean. When "yes", no attempts are made to bring up or configure matching links,<br />
equivalent to when there are no matching network files. Defaults to "no".<br />
<br />
This is useful for preventing later matching network files from interfering with<br />
certain interfaces that are fully controlled by other applications.<br />
<br />
RequiredForOnline=<br />
A boolean. When "yes", the network is deemed required when determining whether the<br />
system is online when running "systemd-networkd-wait-online". When "no", the network<br />
is ignored when checking for online state. Defaults to "yes".<br />
<br />
The network will be brought up normally in all cases, but in the event that there is<br />
no address being assigned by DHCP or the cable is not plugged in, the link will simply<br />
remain offline and be skipped automatically by "systemd-networkd-wait-online" if<br />
"RequiredForOnline=true".<br />
<br />
</pre><br />
<br />
=== [Netork] Section ===<br />
<pre><br />
The "[Network]" section accepts the following keys:<br />
<br />
Description=<br />
A description of the device. This is only used for presentation purposes.<br />
<br />
DHCP=<br />
Enables DHCPv4 and/or DHCPv6 client support. Accepts "yes", "no", "ipv4", or "ipv6".<br />
Defaults to "no".<br />
<br />
Note that DHCPv6 will by default be triggered by Router Advertisement, if that is<br />
enabled, regardless of this parameter. By enabling DHCPv6 support explicitly, the<br />
DHCPv6 client will be started regardless of the presence of routers on the link, or<br />
what flags the routers pass. See "IPv6AcceptRA=".<br />
<br />
Furthermore, note that by default the domain name specified through DHCP, on Ubuntu,<br />
are used for name resolution. See option UseDomains= below.<br />
<br />
See the "[DHCP]" section below for further configuration options for the DHCP client<br />
support.<br />
<br />
DHCPServer=<br />
A boolean. Enables DHCPv4 server support. Defaults to "no". Further settings for the<br />
DHCP server may be set in the "[DHCPServer]" section described below.<br />
<br />
LinkLocalAddressing=<br />
Enables link-local address autoconfiguration. Accepts "yes", "no", "ipv4", or "ipv6".<br />
Defaults to "ipv6".<br />
<br />
IPv4LLRoute=<br />
A boolean. When true, sets up the route needed for non-IPv4LL hosts to communicate<br />
with IPv4LL-only hosts. Defaults to false.<br />
<br />
IPv6Token=<br />
An IPv6 address with the top 64 bits unset. When set, indicates the 64-bit interface<br />
part of SLAAC IPv6 addresses for this link. Note that the token is only ever used for<br />
SLAAC, and not for DHCPv6 addresses, even in the case DHCP is requested by router<br />
advertisement. By default, the token is autogenerated.<br />
<br />
LLMNR=<br />
A boolean or "resolve". When true, enables Link-Local Multicast Name Resolution[1] on<br />
the link. When set to "resolve", only resolution is enabled, but not host registration<br />
and announcement. Defaults to true. This setting is read by systemd-<br />
resolved.service(8).<br />
<br />
MulticastDNS=<br />
A boolean or "resolve". When true, enables Multicast DNS[2] support on the link. When<br />
set to "resolve", only resolution is enabled, but not host or service registration and<br />
announcement. Defaults to false. This setting is read by systemd-resolved.service(8).<br />
<br />
DNSSEC=<br />
A boolean or "allow-downgrade". When true, enables DNSSEC[3] DNS validation support on<br />
the link. When set to "allow-downgrade", compatibility with non-DNSSEC capable<br />
networks is increased, by automatically turning off DNSSEC in this case. This option<br />
defines a per-interface setting for resolved.conf(5)'s global DNSSEC= option. Defaults<br />
to false. This setting is read by systemd-resolved.service(8).<br />
<br />
DNSSECNegativeTrustAnchors=<br />
A space-separated list of DNSSEC negative trust anchor domains. If specified and<br />
DNSSEC is enabled, look-ups done via the interface's DNS server will be subject to the<br />
list of negative trust anchors, and not require authentication for the specified<br />
domains, or anything below it. Use this to disable DNSSEC authentication for specific<br />
private domains, that cannot be proven valid using the Internet DNS hierarchy.<br />
Defaults to the empty list. This setting is read by systemd-resolved.service(8).<br />
<br />
LLDP=<br />
Controls support for Ethernet LLDP packet reception. LLDP is a link-layer protocol<br />
commonly implemented on professional routers and bridges which announces which<br />
physical port a system is connected to, as well as other related data. Accepts a<br />
boolean or the special value "routers-only". When true, incoming LLDP packets are<br />
accepted and a database of all LLDP neighbors maintained. If "routers-only" is set<br />
only LLDP data of various types of routers is collected and LLDP data about other<br />
types of devices ignored (such as stations, telephones and others). If false, LLDP<br />
reception is disabled. Defaults to "routers-only". Use networkctl(1) to query the<br />
collected neighbor data. LLDP is only available on Ethernet links. See EmitLLDP= below<br />
for enabling LLDP packet emission from the local system.<br />
<br />
EmitLLDP=<br />
Controls support for Ethernet LLDP packet emission. Accepts a boolean parameter or the<br />
special values "nearest-bridge", "non-tpmr-bridge" and "customer-bridge". Defaults to<br />
false, which turns off LLDP packet emission. If not false, a short LLDP packet with<br />
information about the local system is sent out in regular intervals on the link. The<br />
LLDP packet will contain information about the local host name, the local machine ID<br />
(as stored in machine-id(5)) and the local interface name, as well as the pretty<br />
hostname of the system (as set in machine-info(5)). LLDP emission is only available on<br />
Ethernet links. Note that this setting passes data suitable for identification of host<br />
to the network and should thus not be enabled on untrusted networks, where such<br />
identification data should not be made available. Use this option to permit other<br />
systems to identify on which interfaces they are connected to this system. The three<br />
special values control propagation of the LLDP packets. The "nearest-bridge" setting<br />
permits propagation only to the nearest connected bridge, "non-tpmr-bridge" permits<br />
propagation across Two-Port MAC Relays, but not any other bridges, and<br />
"customer-bridge" permits propagation until a customer bridge is reached. For details<br />
about these concepts, see IEEE 802.1AB-2009[4]. Note that configuring this setting to<br />
true is equivalent to "nearest-bridge", the recommended and most restricted level of<br />
propagation. See LLDP= above for an option to enable LLDP reception.<br />
<br />
BindCarrier=<br />
A link name or a list of link names. When set, controls the behavior of the current<br />
link. When all links in the list are in an operational down state, the current link is<br />
brought down. When at least one link has carrier, the current interface is brought up.<br />
<br />
Address=<br />
A static IPv4 or IPv6 address and its prefix length, separated by a "/" character.<br />
Specify this key more than once to configure several addresses. The format of the<br />
address must be as described in inet_pton(3). This is a short-hand for an [Address]<br />
section only containing an Address key (see below). This option may be specified more<br />
than once.<br />
<br />
If the specified address is 0.0.0.0 (for IPv4) or [::] (for IPv6), a new address range<br />
of the requested size is automatically allocated from a system-wide pool of unused<br />
ranges. The allocated range is checked against all current network interfaces and all<br />
known network configuration files to avoid address range conflicts. The default<br />
system-wide pool consists of 192.168.0.0/16, 172.16.0.0/12 and 10.0.0.0/8 for IPv4,<br />
and fc00::/7 for IPv6. This functionality is useful to manage a large number of<br />
dynamically created network interfaces with the same network configuration and<br />
automatic address range assignment.<br />
<br />
Gateway=<br />
The gateway address, which must be in the format described in inet_pton(3). This is a<br />
short-hand for a [Route] section only containing a Gateway key. This option may be<br />
specified more than once.<br />
<br />
DNS=<br />
A DNS server address, which must be in the format described in inet_pton(3). This<br />
option may be specified more than once. This setting is read by systemd-<br />
resolved.service(8).<br />
<br />
Domains=<br />
A list of domains which should be resolved using the DNS servers on this link. Each<br />
item in the list should be a domain name, optionally prefixed with a tilde ("~"). The<br />
domains with the prefix are called "routing-only domains". The domains without the<br />
prefix are called "search domains" and are first used as search suffixes for extending<br />
single-label host names (host names containing no dots) to become fully qualified<br />
domain names (FQDNs). If a single-label host name is resolved on this interface, each<br />
of the specified search domains are appended to it in turn, converting it into a fully<br />
qualified domain name, until one of them may be successfully resolved.<br />
<br />
Both "search" and "routing-only" domains are used for routing of DNS queries: look-ups<br />
for host names ending in those domains (hence also single label names, if any "search<br />
domains" are listed), are routed to the DNS servers configured for this interface. The<br />
domain routing logic is particularly useful on multi-homed hosts with DNS servers<br />
serving particular private DNS zones on each interface.<br />
<br />
The "routing-only" domain "~." (the tilde indicating definition of a routing domain,<br />
the dot referring to the DNS root domain which is the implied suffix of all valid DNS<br />
names) has special effect. It causes all DNS traffic which does not match another<br />
configured domain routing entry to be routed to DNS servers specified for this<br />
interface. This setting is useful to prefer a certain set of DNS servers if a link on<br />
which they are connected is available.<br />
<br />
This setting is read by systemd-resolved.service(8). "Search domains" correspond to<br />
the domain and search entries in resolv.conf(5). Domain name routing has no equivalent<br />
in the traditional glibc API, which has no concept of domain name servers limited to a<br />
specific link.<br />
<br />
NTP=<br />
An NTP server address. This option may be specified more than once. This setting is<br />
read by systemd-timesyncd.service(8).<br />
<br />
IPForward=<br />
Configures IP packet forwarding for the system. If enabled, incoming packets on any<br />
network interface will be forwarded to any other interfaces according to the routing<br />
table. Takes either a boolean argument, or the values "ipv4" or "ipv6", which only<br />
enable IP packet forwarding for the specified address family. This controls the<br />
net.ipv4.ip_forward and net.ipv6.conf.all.forwarding sysctl options of the network<br />
interface (see ip-sysctl.txt[5] for details about sysctl options). Defaults to "no".<br />
<br />
Note: this setting controls a global kernel option, and does so one way only: if a<br />
network that has this setting enabled is set up the global setting is turned on.<br />
However, it is never turned off again, even after all networks with this setting<br />
enabled are shut down again.<br />
<br />
To allow IP packet forwarding only between specific network interfaces use a firewall.<br />
<br />
IPMasquerade=<br />
Configures IP masquerading for the network interface. If enabled, packets forwarded<br />
from the network interface will be appear as coming from the local host. Takes a<br />
boolean argument. Implies IPForward=ipv4. Defaults to "no".<br />
<br />
IPv6PrivacyExtensions=<br />
Configures use of stateless temporary addresses that change over time (see RFC<br />
4941[6], Privacy Extensions for Stateless Address Autoconfiguration in IPv6). Takes a<br />
boolean or the special values "prefer-public" and "kernel". When true, enables the<br />
privacy extensions and prefers temporary addresses over public addresses. When<br />
"prefer-public", enables the privacy extensions, but prefers public addresses over<br />
temporary addresses. When false, the privacy extensions remain disabled. When<br />
"kernel", the kernel's default setting will be left in place. Defaults to "no".<br />
<br />
IPv6AcceptRA=<br />
Enable or disable IPv6 Router Advertisement (RA) reception support for the interface.<br />
Takes a boolean parameter. If true, RAs are accepted; if false, RAs are ignored,<br />
independently of the local forwarding state. When not set, the kernel default is used,<br />
and RAs are accepted only when local forwarding is disabled for that interface. When<br />
RAs are accepted, they may trigger the start of the DHCPv6 client if the relevant<br />
flags are set in the RA data, or if no routers are found on the link.<br />
<br />
Further settings for the IPv6 RA support may be configured in the "[IPv6AcceptRA]"<br />
section, see below.<br />
<br />
Also see ip-sysctl.txt[5] in the kernel documentation regarding "accept_ra", but note<br />
that systemd's setting of 1 (i.e. true) corresponds to kernel's setting of 2.<br />
<br />
IPv6DuplicateAddressDetection=<br />
Configures the amount of IPv6 Duplicate Address Detection (DAD) probes to send.<br />
Defaults to unset.<br />
<br />
IPv6HopLimit=<br />
Configures IPv6 Hop Limit. For each router that forwards the packet, the hop limit is<br />
decremented by 1. When the hop limit field reaches zero, the packet is discarded.<br />
Defaults to unset.<br />
<br />
IPv4ProxyARP=<br />
A boolean. Configures proxy ARP for IPv4. Proxy ARP is the technique in which one<br />
host, usually a router, answers ARP requests intended for another machine. By "faking"<br />
its identity, the router accepts responsibility for routing packets to the "real"<br />
destination. (see RFC 1027[7]. Defaults to unset.<br />
<br />
IPv6ProxyNDP=<br />
A boolean. Configures proxy NDP for IPv6. Proxy NDP (Neighbor Discovery Protocol) is a<br />
technique for IPv6 to allow routing of addresses to a different destination when peers<br />
expect them to be present on a certain physical link. In this case a router answers<br />
Neighbour Advertisement messages intended for another machine by offering its own MAC<br />
address as destination. Unlike proxy ARP for IPv4, it is not enabled globally, but<br />
will only send Neighbour Advertisement messages for addresses in the IPv6 neighbor<br />
proxy table, which can also be shown by ip -6 neighbour show proxy. systemd-networkd<br />
will control the per-interface `proxy_ndp` switch for each configured interface<br />
depending on this option. Defautls to unset.<br />
<br />
IPv6ProxyNDPAddress=<br />
An IPv6 address, for which Neighbour Advertisement messages will be proxied. This<br />
option may be specified more than once. systemd-networkd will add the<br />
IPv6ProxyNDPAddress= entries to the kernel's IPv6 neighbor proxy table. This option<br />
implies IPv6ProxyNDP=true but has no effect if IPv6ProxyNDP has been set to false.<br />
Defaults to unset.<br />
<br />
IPv6PrefixDelegation=<br />
Whether to enable or disable Router Advertisement sending on a link. Allowed values<br />
are "static" which distributes prefixes as defined in the "[IPv6PrefixDelegation]" and<br />
any "[IPv6Prefix]" sections, "dhcpv6" which requests prefixes using a DHCPv6 client<br />
configured for another link and any values configured in the "[IPv6PrefixDelegation]"<br />
section while ignoring all static prefix configuration sections, "yes" which uses both<br />
static configuration and DHCPv6, and "false" which turns off IPv6 prefix delegation<br />
altogether. Defaults to "false". See the "[IPv6PrefixDelegation]" and the<br />
"[IPv6Prefix]" sections for more configuration options.<br />
<br />
Bridge=<br />
The name of the bridge to add the link to. See systemd.netdev(5).<br />
<br />
Bond=<br />
The name of the bond to add the link to. See systemd.netdev(5).<br />
<br />
VRF=<br />
The name of the VRF to add the link to. See systemd.netdev(5).<br />
<br />
VLAN=<br />
The name of a VLAN to create on the link. See systemd.netdev(5). This option may be<br />
specified more than once.<br />
<br />
MACVLAN=<br />
The name of a MACVLAN to create on the link. See systemd.netdev(5). This option may be<br />
specified more than once.<br />
<br />
VXLAN=<br />
The name of a VXLAN to create on the link. See systemd.netdev(5). This option may be<br />
specified more than once.<br />
<br />
Tunnel=<br />
The name of a Tunnel to create on the link. See systemd.netdev(5). This option may be<br />
specified more than once.<br />
<br />
ActiveSlave=<br />
A boolean. Specifies the new active slave. The "ActiveSlave=" option is only valid for<br />
following modes: "active-backup", "balance-alb" and "balance-tlb". Defaults to false.<br />
<br />
PrimarySlave=<br />
A boolean. Specifies which slave is the primary device. The specified device will<br />
always be the active slave while it is available. Only when the primary is off-line<br />
will alternate devices be used. This is useful when one slave is preferred over<br />
another, e.g. when one slave has higher throughput than another. The "PrimarySlave="<br />
option is only valid for following modes: "active-backup", "balance-alb" and<br />
"balance-tlb". Defaults to false.<br />
<br />
ConfigureWithoutCarrier=<br />
A boolean. Allows networkd to configure a specific link even if it has no carrier.<br />
Defaults to false.<br />
<br />
</pre><br />
<br />
=== [Address] Section ===<br />
<pre><br />
An "[Address]" section accepts the following keys. Specify several "[Address]" sections to<br />
configure several addresses.<br />
<br />
Address=<br />
As in the "[Network]" section. This key is mandatory.<br />
<br />
Peer=<br />
The peer address in a point-to-point connection. Accepts the same format as the<br />
"Address" key.<br />
<br />
Broadcast=<br />
The broadcast address, which must be in the format described in inet_pton(3). This key<br />
only applies to IPv4 addresses. If it is not given, it is derived from the "Address"<br />
key.<br />
<br />
Label=<br />
An address label.<br />
<br />
PreferredLifetime=<br />
Allows the default "preferred lifetime" of the address to be overridden. Only three<br />
settings are accepted: "forever" or "infinity" which is the default and means that the<br />
address never expires, and "0" which means that the address is considered immediately<br />
"expired" and will not be used, unless explicitly requested. A setting of<br />
PreferredLifetime=0 is useful for addresses which are added to be used only by a<br />
specific application, which is then configured to use them explicitly.<br />
<br />
Scope=<br />
The scope of the address, which can be "global", "link" or "host" or an unsigned<br />
integer ranges 0 to 255. Defaults to "global".<br />
<br />
HomeAddress=<br />
Takes a boolean argument. Designates this address the "home address" as defined in RFC<br />
6275[8]. Supported only on IPv6. Defaults to false.<br />
<br />
DuplicateAddressDetection=<br />
Takes a boolean argument. Do not perform Duplicate Address Detection RFC 4862[9] when<br />
adding this address. Supported only on IPv6. Defaults to false.<br />
<br />
ManageTemporaryAddress=<br />
Takes a boolean argument. If true the kernel manage temporary addresses created from<br />
this one as template on behalf of Privacy Extensions RFC 3041[10]. For this to become<br />
active, the use_tempaddr sysctl setting has to be set to a value greater than zero.<br />
The given address needs to have a prefix length of 64. This flag allows to use privacy<br />
extensions in a manually configured network, just like if stateless auto-configuration<br />
was active. Defaults to false.<br />
<br />
PrefixRoute=<br />
Takes a boolean argument. When adding or modifying an IPv6 address, the userspace<br />
application needs a way to suppress adding a prefix route. This is for example<br />
relevant together with IFA_F_MANAGERTEMPADDR, where userspace creates autoconf<br />
generated addresses, but depending on on-link, no route for the prefix should be<br />
added. Defaults to false.<br />
<br />
AutoJoin=<br />
Takes a boolean argument. Joining multicast group on ethernet level via ip maddr<br />
command would not work if we have an Ethernet switch that does IGMP snooping since the<br />
switch would not replicate multicast packets on ports that did not have IGMP reports<br />
for the multicast addresses. Linux vxlan interfaces created via ip link add vxlan or<br />
networkd's netdev kind vxlan have the group option that enables then to do the<br />
required join. By extending ip address command with option "autojoin" we can get<br />
similar functionality for openvswitch (OVS) vxlan interfaces as well as other<br />
tunneling mechanisms that need to receive multicast traffic. Defaults to "no".<br />
<br />
[IPV6ADDRESSLABEL] SECTION OPTIONS<br />
An "[IPv6AddressLabel]" section accepts the following keys. Specify several<br />
"[IPv6AddressLabel]" sections to configure several address labels. IPv6 address labels are<br />
used for address selection. See RFC 3484[11]. Precedence is managed by userspace, and only<br />
the label itself is stored in the kernel<br />
<br />
Label=<br />
The label for the prefix (an unsigned integer) ranges 0 to 4294967294. 0xffffffff is<br />
reserved. This key is mandatory.<br />
<br />
Prefix=<br />
IPv6 prefix is an address with a prefix length, separated by a slash "/" character.<br />
This key is mandatory.<br />
</pre><br />
<br />
=== [RoutingPolicyRule] Section ===<br />
<pre><br />
An "[RoutingPolicyRule]" section accepts the following keys. Specify several<br />
"[RoutingPolicyRule]" sections to configure several rules.<br />
<br />
TypeOfService=<br />
Specifies the type of service to match a number between 0 to 255.<br />
<br />
From=<br />
Specifies the source address prefix to match. Possibly followed by a slash and the<br />
prefix length.<br />
<br />
To=<br />
Specifies the destination address prefix to match. Possibly followed by a slash and<br />
the prefix length.<br />
<br />
FirewallMark=<br />
Specifies the iptables firewall mark value to match (a number between 1 and<br />
4294967295).<br />
<br />
Table=<br />
Specifies the routing table identifier to lookup if the rule selector matches. The<br />
table identifier for a route (a number between 1 and 4294967295).<br />
<br />
Priority=<br />
Specifies the priority of this rule. Priority= is an unsigned integer. Higher number<br />
means lower priority, and rules get processed in order of increasing number.<br />
<br />
IncomingInterface=<br />
Specifies incoming device to match. If the interface is loopback, the rule only<br />
matches packets originating from this host.<br />
<br />
OutgoingInterface=<br />
Specifies the outgoing device to match. The outgoing interface is only available for<br />
packets originating from local sockets that are bound to a device.<br />
<br />
</pre><br />
<br />
=== [Route] Section ===<br />
<pre><br />
The "[Route]" section accepts the following keys. Specify several "[Route]" sections to<br />
configure several routes.<br />
<br />
Gateway=<br />
As in the "[Network]" section.<br />
<br />
GatewayOnlink=<br />
The "GatewayOnlink" option tells the kernel that it does not have to check if the<br />
gateway is reachable directly by the current machine (i.e., the kernel does not need<br />
to check if the gateway is attached to the local network), so that we can insert the<br />
route in the kernel table without it being complained about. A boolean, defaults to<br />
"no".<br />
<br />
Destination=<br />
The destination prefix of the route. Possibly followed by a slash and the prefix<br />
length. If omitted, a full-length host route is assumed.<br />
<br />
Source=<br />
The source prefix of the route. Possibly followed by a slash and the prefix length. If<br />
omitted, a full-length host route is assumed.<br />
<br />
Metric=<br />
The metric of the route (an unsigned integer).<br />
<br />
IPv6Preference=<br />
Specifies the route preference as defined in RFC4191[12] for Router Discovery<br />
messages. Which can be one of "low" the route has a lowest priority, "medium" the<br />
route has a default priority or "high" the route has a highest priority.<br />
<br />
Scope=<br />
The scope of the route, which can be "global", "link" or "host". Defaults to "global".<br />
<br />
PreferredSource=<br />
The preferred source address of the route. The address must be in the format described<br />
in inet_pton(3).<br />
<br />
Table=num<br />
The table identifier for the route (a number between 1 and 4294967295, or 0 to unset).<br />
The table can be retrieved using ip route show table num.<br />
<br />
Protocol=<br />
The Protocol identifier for the route. Takes a number between 0 and 255 or the special<br />
values "kernel", "boot" and "static". Defaults to "static".<br />
<br />
Type=<br />
The Type identifier for special route types, which can be "unicast" route to a<br />
destination network address which describes the path to the destination, "blackhole"<br />
packets are discarded silently, "unreachable" packets are discarded and the ICMP<br />
message host unreachable is generated, "prohibit" packets are discarded and the ICMP<br />
message communication administratively prohibited is generated. Defaults to "unicast".<br />
<br />
InitialCongestionWindow=<br />
The TCP initial congestion window is used during the start of a TCP connection. During<br />
the start of a TCP session, when a client requests a resource, the server's initial<br />
congestion window determines how many data bytes will be sent during the initial burst<br />
of data. Takes a size in bytes between 1 and 4294967295 (2^32 - 1). The usual suffixes<br />
K, M, G are supported and are understood to the base of 1024. Defaults to unset.<br />
<br />
InitialAdvertisedReceiveWindow=<br />
The TCP initial advertised receive window is the amount of receive data (in bytes)<br />
that can initally be buffered at one time on a connection. The sending host can send<br />
only that amount of data before waiting for an acknowledgment and window update from<br />
the receiving host. Takes a size in bytes between 1 and 4294967295 (2^32 - 1). The<br />
usual suffixes K, M, G are supported and are understood to the base of 1024. Defaults<br />
to unset.<br />
<br />
QuickAck=<br />
Takes a boolean argument. When true enables TCP quick ack mode for the route. Defaults<br />
to unset.<br />
<br />
</pre><br />
<br />
=== [DHCP] section ===<br />
<pre><br />
The "[DHCP]" section configures the DHCPv4 and DHCP6 client, if it is enabled with the<br />
DHCP= setting described above:<br />
<br />
UseDNS=<br />
When true (the default), the DNS servers received from the DHCP server will be used<br />
and take precedence over any statically configured ones.<br />
<br />
This corresponds to the nameserver option in resolv.conf(5).<br />
<br />
UseNTP=<br />
When true (the default), the NTP servers received from the DHCP server will be used by<br />
systemd-timesyncd and take precedence over any statically configured ones.<br />
<br />
UseMTU=<br />
When true, the interface maximum transmission unit from the DHCP server will be used<br />
on the current link. Defaults to false.<br />
<br />
Anonymize=<br />
Takes a boolean argument. When true, the options sent to the DHCP server will follow<br />
the RFC 7844[13] (Anonymity Profiles for DHCP Clients) to minimize disclosure of<br />
identifying information. Defaults to false.<br />
<br />
This option should only be set to true when MACAddressPolicy= is set to "random" (see<br />
systemd.link(5)).<br />
<br />
Note that this configuration will overwrite others. In concrete, the following<br />
variables will be ignored: SendHostname=, ClientIdentifier=, UseRoutes=,<br />
SendHostname=, UseMTU=, VendorClassIdentifier=, UseTimezone=.<br />
<br />
SendHostname=<br />
When true (the default), the machine's hostname will be sent to the DHCP server.<br />
<br />
UseHostname=<br />
When true (the default), the hostname received from the DHCP server will be set as the<br />
transient hostname of the system<br />
<br />
Hostname=<br />
Use this value for the hostname which is sent to the DHCP server, instead of machine's<br />
hostname.<br />
<br />
UseDomains=<br />
Takes a boolean argument, or the special value "route". When true, the domain name<br />
received from the DHCP server will be used as DNS search domain over this link,<br />
similar to the effect of the Domains= setting. If set to "route", the domain name<br />
received from the DHCP server will be used for routing DNS queries only, but not for<br />
searching, similar to the effect of the Domains= setting when the argument is prefixed<br />
with "~". Defaults to true on Ubuntu.<br />
<br />
It is recommended to enable this option only on trusted networks, as setting this<br />
affects resolution of all host names, in particular of single-label names. It is<br />
generally safer to use the supplied domain only as routing domain, rather than as<br />
search domain, in order to not have it affect local resolution of single-label names.<br />
<br />
When set to true, this setting corresponds to the domain option in resolv.conf(5).<br />
<br />
UseRoutes=<br />
When true (the default), the static routes will be requested from the DHCP server and<br />
added to the routing table with a metric of 1024, and a scope of "global", "link" or<br />
"host", depending on the route's destination and gateway. If the destination is on the<br />
local host, e.g., 127.x.x.x, or the same as the link's own address, the scope will be<br />
set to "host". Otherwise if the gateway is null (a direct route), a "link" scope will<br />
be used. For anything else, scope defaults to "global".<br />
<br />
UseTimezone=<br />
When true, the timezone received from the DHCP server will be set as timezone of the<br />
local system. Defaults to "no".<br />
<br />
CriticalConnection=<br />
When true, the connection will never be torn down even if the DHCP lease expires. This<br />
is contrary to the DHCP specification, but may be the best choice if, say, the root<br />
filesystem relies on this connection. Defaults to false.<br />
<br />
ClientIdentifier=<br />
The DHCPv4 client identifier to use. Either "mac" to use the MAC address of the link<br />
or "duid" (the default, see below) to use an RFC4361-compliant Client ID.<br />
<br />
VendorClassIdentifier=<br />
The vendor class identifier used to identify vendor type and configuration.<br />
<br />
DUIDType=<br />
Override the global DUIDType setting for this network. See networkd.conf(5) for a<br />
description of possible values.<br />
<br />
DUIDRawData=<br />
Override the global DUIDRawData setting for this network. See networkd.conf(5) for a<br />
description of possible values.<br />
<br />
IAID=<br />
The DHCP Identity Association Identifier (IAID) for the interface, a 32-bit unsigned<br />
integer.<br />
<br />
RequestBroadcast=<br />
Request the server to use broadcast messages before the IP address has been<br />
configured. This is necessary for devices that cannot receive RAW packets, or that<br />
cannot receive packets at all before an IP address has been configured. On the other<br />
hand, this must not be enabled on networks where broadcasts are filtered out.<br />
<br />
RouteMetric=<br />
Set the routing metric for routes specified by the DHCP server.<br />
<br />
RouteTable=num<br />
The table identifier for DHCP routes (a number between 1 and 4294967295, or 0 to<br />
unset). The table can be retrieved using ip route show table num.<br />
<br />
When used in combination with VRF= the VRF's routing table is used unless this<br />
parameter is specified.<br />
<br />
ListenPort=<br />
Allow setting custom port for the DHCP client to listen on.<br />
<br />
RapidCommit=<br />
A boolean. The DHCPv6 client can obtain configuration parameters from a DHCPv6 server<br />
through a rapid two-message exchange (solicit and reply). When the rapid commit option<br />
is enabled by both the DHCPv6 client and the DHCPv6 server, the two-message exchange<br />
is used, rather than the default four-method exchange (solicit, advertise, request,<br />
and reply). The two-message exchange provides faster client configuration and is<br />
beneficial in environments in which networks are under a heavy load. See RFC 3315[14]<br />
for details. Defaults to true.<br />
<br />
</pre><br />
<br />
=== [IPv6Acceptra] Section ===<br />
<pre><br />
The "[IPv6AcceptRA]" section configures the IPv6 Router Advertisement (RA) client, if it<br />
is enabled with the IPv6AcceptRA= setting described above:<br />
<br />
UseDNS=<br />
When true (the default), the DNS servers received in the Router Advertisement will be<br />
used and take precedence over any statically configured ones.<br />
<br />
This corresponds to the nameserver option in resolv.conf(5).<br />
<br />
UseDomains=<br />
Takes a boolean argument, or the special value "route". When true, the domain name<br />
received via IPv6 Router Advertisement (RA) will be used as DNS search domain over<br />
this link, similar to the effect of the Domains= setting. If set to "route", the<br />
domain name received via IPv6 RA will be used for routing DNS queries only, but not<br />
for searching, similar to the effect of the Domains= setting when the argument is<br />
prefixed with "~". Defaults to true on Ubuntu.<br />
<br />
It is recommended to enable this option only on trusted networks, as setting this<br />
affects resolution of all host names, in particular of single-label names. It is<br />
generally safer to use the supplied domain only as routing domain, rather than as<br />
search domain, in order to not have it affect local resolution of single-label names.<br />
<br />
When set to true, this setting corresponds to the domain option in resolv.conf(5).<br />
<br />
RouteTable=num<br />
The table identifier for the routes received in the Router Advertisement (a number<br />
between 1 and 4294967295, or 0 to unset). The table can be retrieved using ip route<br />
show table num.<br />
<br />
</pre><br />
<br />
=== [DHCPServer] Section ===<br />
<pre><br />
The "[DHCPServer]" section contains settings for the DHCP server, if enabled via the<br />
DHCPServer= option described above:<br />
<br />
PoolOffset=, PoolSize=<br />
Configures the pool of addresses to hand out. The pool is a contiguous sequence of IP<br />
addresses in the subnet configured for the server address, which does not include the<br />
subnet nor the broadcast address. PoolOffset= takes the offset of the pool from the<br />
start of subnet, or zero to use the default value. PoolSize= takes the number of IP<br />
addresses in the pool or zero to use the default value. By default, the pool starts at<br />
the first address after the subnet address and takes up the rest of the subnet,<br />
excluding the broadcast address. If the pool includes the server address (the<br />
default), this is reserved and not handed out to clients.<br />
<br />
DefaultLeaseTimeSec=, MaxLeaseTimeSec=<br />
Control the default and maximum DHCP lease time to pass to clients. These settings<br />
take time values in seconds or another common time unit, depending on the suffix. The<br />
default lease time is used for clients that did not ask for a specific lease time. If<br />
a client asks for a lease time longer than the maximum lease time, it is automatically<br />
shortened to the specified time. The default lease time defaults to 1h, the maximum<br />
lease time to 12h. Shorter lease times are beneficial if the configuration data in<br />
DHCP leases changes frequently and clients shall learn the new settings with shorter<br />
latencies. Longer lease times reduce the generated DHCP network traffic.<br />
<br />
EmitDNS=, DNS=<br />
Configures whether the DHCP leases handed out to clients shall contain DNS server<br />
information. The EmitDNS= setting takes a boolean argument and defaults to "yes". The<br />
DNS servers to pass to clients may be configured with the DNS= option, which takes a<br />
list of IPv4 addresses. If the EmitDNS= option is enabled but no servers configured,<br />
the servers are automatically propagated from an "uplink" interface that has<br />
appropriate servers set. The "uplink" interface is determined by the default route of<br />
the system with the highest priority. Note that this information is acquired at the<br />
time the lease is handed out, and does not take uplink interfaces into account that<br />
acquire DNS or NTP server information at a later point. DNS server propagation does<br />
not take /etc/resolv.conf into account. Also, note that the leases are not refreshed<br />
if the uplink network configuration changes. To ensure clients regularly acquire the<br />
most current uplink DNS server information, it is thus advisable to shorten the DHCP<br />
lease time via MaxLeaseTimeSec= described above.<br />
<br />
EmitNTP=, NTP=<br />
Similar to the EmitDNS= and DNS= settings described above, these settings configure<br />
whether and what NTP server information shall be emitted as part of the DHCP lease.<br />
The same syntax, propagation semantics and defaults apply as for EmitDNS= and DNS=.<br />
<br />
EmitRouter=<br />
Similar to the EmitDNS= setting described above, this setting configures whether the<br />
DHCP lease should contain the router option. The same syntax, propagation semantics<br />
and defaults apply as for EmitDNS=.<br />
<br />
EmitTimezone=, Timezone=<br />
Configures whether the DHCP leases handed out to clients shall contain timezone<br />
information. The EmitTimezone= setting takes a boolean argument and defaults to "yes".<br />
The Timezone= setting takes a timezone string (such as "Europe/Berlin" or "UTC") to<br />
pass to clients. If no explicit timezone is set, the system timezone of the local host<br />
is propagated, as determined by the /etc/localtime symlink.<br />
</pre><br />
<br />
=== [IPv6PrefixDelegation] section ===<br />
<pre><br />
The "[IPv6PrefixDelegation]" section contains settings for sending IPv6 Router<br />
Advertisements and whether to act as a router, if enabled via the IPv6PrefixDelegation=<br />
option described above. IPv6 network prefixes are defined with one or more "[IPv6Prefix]"<br />
sections.<br />
<br />
Managed=, OtherInformation=<br />
Controls whether a DHCPv6 server is used to acquire IPv6 addresses on the network link<br />
when Managed= boolean is set to "true" or if only additional network information can<br />
be obtained via DHCPv6 for the network link when OtherInformation= boolean is set to<br />
"true". Both settings default to "false", which means that a DHCPv6 server is not<br />
being used.<br />
<br />
RouterLifetimeSec=<br />
Configures the IPv6 router lifetime in seconds. If set, this host also announces<br />
itself in Router Advertisements as an IPv6 router for the network link. Defaults to<br />
unset, which means the host is not acting as a router.<br />
<br />
RouterPreference=<br />
Configures IPv6 router preference if RouterLifetimeSec= is non-zero. Valid values are<br />
"high", "medium" and "low", with "normal" and "default" added as synonyms for "medium"<br />
just to make configuration easier. See RFC 4191[12] for details. Defaults to "medium".<br />
<br />
EmitDNS=, DNS=<br />
DNS= specifies a list of recursive DNS server IPv6 addresses that distributed via<br />
Router Advertisement messages when EmitDNS= is true. If DNS= is empty, DNS servers are<br />
read from the "[Network]" section. If the "[Network]" section does not contain any DNS<br />
servers either, DNS servers from the uplink with the highest priority default route<br />
are used. When EmitDNS= is false, no DNS server information is sent in Router<br />
Advertisement messages. EmitDNS= defaults to true.<br />
<br />
EmitDomains=, Domains=<br />
A list of DNS search domains distributed via Router Advertisement messages when<br />
EmitDomains= is true. If Domains= is empty, DNS search domains are read from the<br />
"[Network]" section. If the "[Network]" section does not contain any DNS search<br />
domains either, DNS search domains from the uplink with the highest priority default<br />
route are used. When EmitDomains= is false, no DNS search domain information is sent<br />
in Router Advertisement messages. EmitDomains= defaults to true.<br />
<br />
DNSLifetimeSec=<br />
Lifetime in seconds for the DNS server addresses listed in DNS= and search domains<br />
listed in Domains=.<br />
</pre><br />
<br />
=== [IPv6Prefix] Section ===<br />
<pre><br />
One or more "[IPv6Prefix]" sections contain the IPv6 prefixes that are announced via<br />
Router Advertisements. See RFC 4861[15] for further details.<br />
<br />
AddressAutoconfiguration=, OnLink=<br />
Boolean values to specify whether IPv6 addresses can be autoconfigured with this<br />
prefix and whether the prefix can be used for onlink determination. Both settings<br />
default to "true" in order to ease configuration.<br />
<br />
Prefix=<br />
The IPv6 prefix that is to be distributed to hosts. Similarly to configuring static<br />
IPv6 addresses, the setting is configured as an IPv6 prefix and its prefix length,<br />
separated by a "/" character. Use multiple "[IPv6Prefix]" sections to configure<br />
multiple IPv6 prefixes since prefix lifetimes, address autoconfiguration and onlink<br />
status may differ from one prefix to another.<br />
<br />
PreferredLifetimeSec=, ValidLifetimeSec=<br />
Preferred and valid lifetimes for the prefix measured in seconds.<br />
PreferredLifetimeSec= defaults to 604800 seconds (one week) and ValidLifetimeSec=<br />
defaults to 2592000 seconds (30 days).<br />
</pre><br />
<br />
=== [Bridge] Section ===<br />
<pre><br />
The "[Bridge]" section accepts the following keys.<br />
<br />
UnicastFlood=<br />
A boolean. Controls whether the bridge should flood traffic for which an FDB entry is<br />
missing and the destination is unknown through this port. Defaults to on.<br />
<br />
HairPin=<br />
A boolean. Configures whether traffic may be sent back out of the port on which it was<br />
received. By default, this flag is false, and the bridge will not forward traffic back<br />
out of the receiving port.<br />
<br />
UseBPDU=<br />
A boolean. Configures whether STP Bridge Protocol Data Units will be processed by the<br />
bridge port. Defaults to yes.<br />
<br />
FastLeave=<br />
A boolean. This flag allows the bridge to immediately stop multicast traffic on a port<br />
that receives an IGMP Leave message. It is only used with IGMP snooping if enabled on<br />
the bridge. Defaults to off.<br />
<br />
AllowPortToBeRoot=<br />
A boolean. Configures whether a given port is allowed to become a root port. Only used<br />
when STP is enabled on the bridge. Defaults to on.<br />
<br />
Cost=<br />
Sets the "cost" of sending packets of this interface. Each port in a bridge may have a<br />
different speed and the cost is used to decide which link to use. Faster interfaces<br />
should have lower costs. It is an integer value between 1 and 65535.<br />
<br />
Priority=<br />
Sets the "priority" of sending packets on this interface. Each port in a bridge may<br />
have a different priority which is used to decide which link to use. Lower value means<br />
higher priority. It is an integer value between 0 to 63. Networkd does not set any<br />
default, meaning the kernel default value of 32 is used.<br />
<br />
</pre><br />
<br />
=== [BridgeFDB] section ===<br />
<pre><br />
The "[BridgeFDB]" section manages the forwarding database table of a port and accepts the<br />
following keys. Specify several "[BridgeFDB]" sections to configure several static MAC<br />
table entries.<br />
<br />
MACAddress=<br />
As in the "[Network]" section. This key is mandatory.<br />
<br />
VLANId=<br />
The VLAN ID for the new static MAC table entry. If omitted, no VLAN ID information is<br />
appended to the new static MAC table entry.<br />
</pre><br />
<br />
=== [BridgeVLAN] section ===<br />
<pre><br />
The "[BridgeVLAN]" section manages the VLAN ID configuration of a bridge port and accepts<br />
the following keys. Specify several "[BridgeVLAN]" sections to configure several VLAN<br />
entries. The VLANFiltering= option has to be enabled, see "[Bridge]" section in<br />
systemd.netdev(5).<br />
<br />
VLAN=<br />
The VLAN ID allowed on the port. This can be either a single ID or a range M-N. VLAN<br />
IDs are valid from 1 to 4094.<br />
<br />
EgressUntagged=<br />
The VLAN ID specified here will be used to untag frames on egress. Configuring<br />
EgressUntagged= implicates the use of VLAN= above and will enable the VLAN ID for<br />
ingress as well. This can be either a single ID or a range M-N.<br />
<br />
PVID=<br />
The Port VLAN ID specified here is assigned to all untagged frames at ingress. PVID=<br />
can be used only once. Configuring PVID= implicates the use of VLAN= above and will<br />
enable the VLAN ID for ingress as well.<br />
</pre><br />
<br />
=== Examples ===<br />
<pre><br />
Example 1. Static network configuration<br />
<br />
# /etc/systemd/network/50-static.network<br />
[Match]<br />
Name=enp2s0<br />
<br />
[Network]<br />
Address=192.168.0.15/24<br />
Gateway=192.168.0.1<br />
<br />
This brings interface "enp2s0" up with a static address. The specified gateway will be<br />
used for a default route.<br />
<br />
Example 2. DHCP on ethernet links<br />
<br />
# /etc/systemd/network/80-dhcp.network<br />
[Match]<br />
Name=en*<br />
<br />
[Network]<br />
DHCP=yes<br />
<br />
This will enable DHCPv4 and DHCPv6 on all interfaces with names starting with "en" (i.e.<br />
ethernet interfaces).<br />
<br />
Example 3. A bridge with two enslaved links<br />
<br />
# /etc/systemd/network/25-bridge-static.network<br />
[Match]<br />
Name=bridge0<br />
<br />
[Network]<br />
Address=192.168.0.15/24<br />
Gateway=192.168.0.1<br />
DNS=192.168.0.1<br />
<br />
# /etc/systemd/network/25-bridge-slave-interface-1.network<br />
[Match]<br />
Name=enp2s0<br />
<br />
[Network]<br />
Bridge=bridge0<br />
<br />
# /etc/systemd/network/25-bridge-slave-interface-2.network<br />
[Match]<br />
Name=wlp3s0<br />
<br />
[Network]<br />
Bridge=bridge0<br />
<br />
This creates a bridge and attaches devices "enp2s0" and "wlp3s0" to it. The bridge will<br />
have the specified static address and network assigned, and a default route via the<br />
specified gateway will be added. The specified DNS server will be added to the global list<br />
of DNS resolvers.<br />
<br />
Example 4.<br />
<br />
# /etc/systemd/network/20-bridge-slave-interface-vlan.network<br />
[Match]<br />
Name=enp2s0<br />
<br />
[Network]<br />
Bridge=bridge0<br />
<br />
[BridgeVLAN]<br />
VLAN=1-32<br />
PVID=42<br />
EgressUntagged=42<br />
<br />
[BridgeVLAN]<br />
VLAN=100-200<br />
<br />
[BridgeVLAN]<br />
EgressUntagged=300-400<br />
<br />
This overrides the configuration specified in the previous example for the interface<br />
"enp2s0", and enables VLAN on that bridge port. VLAN IDs 1-32, 42, 100-400 will be<br />
allowed. Packets tagged with VLAN IDs 42, 300-400 will be untagged when they leave on this<br />
interface. Untagged packets which arrive on this interface will be assigned VLAN ID 42.<br />
<br />
Example 5. Various tunnels<br />
<br />
/etc/systemd/network/25-tunnels.network<br />
[Match]<br />
Name=ens1<br />
<br />
[Network]<br />
Tunnel=ipip-tun<br />
Tunnel=sit-tun<br />
Tunnel=gre-tun<br />
Tunnel=vti-tun<br />
<br />
/etc/systemd/network/25-tunnel-ipip.netdev<br />
[NetDev]<br />
Name=ipip-tun<br />
Kind=ipip<br />
<br />
/etc/systemd/network/25-tunnel-sit.netdev<br />
[NetDev]<br />
Name=sit-tun<br />
Kind=sit<br />
<br />
/etc/systemd/network/25-tunnel-gre.netdev<br />
[NetDev]<br />
Name=gre-tun<br />
Kind=gre<br />
<br />
/etc/systemd/network/25-tunnel-vti.netdev<br />
[NetDev]<br />
Name=vti-tun<br />
Kind=vti<br />
<br />
This will bring interface "ens1" up and create an IPIP tunnel, a SIT tunnel, a GRE tunnel,<br />
and a VTI tunnel using it.<br />
<br />
Example 6. A bond device<br />
<br />
# /etc/systemd/network/30-bond1.network<br />
[Match]<br />
Name=bond1<br />
<br />
[Network]<br />
DHCP=ipv6<br />
<br />
# /etc/systemd/network/30-bond1.netdev<br />
[NetDev]<br />
Name=bond1<br />
Kind=bond<br />
<br />
# /etc/systemd/network/30-bond1-dev1.network<br />
[Match]<br />
MACAddress=52:54:00:e9:64:41<br />
<br />
[Network]<br />
Bond=bond1<br />
<br />
# /etc/systemd/network/30-bond1-dev2.network<br />
[Match]<br />
MACAddress=52:54:00:e9:64:42<br />
<br />
[Network]<br />
Bond=bond1<br />
<br />
This will create a bond device "bond1" and enslave the two devices with MAC addresses<br />
52:54:00:e9:64:41 and 52:54:00:e9:64:42 to it. IPv6 DHCP will be used to acquire an<br />
address.<br />
<br />
Example 7. Virtual Routing and Forwarding (VRF)<br />
<br />
Add the "bond1" interface to the VRF master interface "vrf1". This will redirect routes<br />
generated on this interface to be within the routing table defined during VRF creation.<br />
For kernels before 4.8 traffic won't be redirected towards the VRFs routing table unless<br />
specific ip-rules are added.<br />
<br />
# /etc/systemd/network/25-vrf.network<br />
[Match]<br />
Name=bond1<br />
<br />
[Network]<br />
VRF=vrf1<br />
<br />
Example 8. MacVTap<br />
<br />
This brings up a network interface "macvtap-test" and attaches it to "enp0s25".<br />
<br />
# /lib/systemd/network/25-macvtap.network<br />
[Match]<br />
Name=enp0s25<br />
<br />
[Network]<br />
MACVTAP=macvtap-test<br />
</pre></div>Mikehttps://wiki.ttsh.dk/index.php?title=First_principles&diff=41First principles2023-01-15T12:33:07Z<p>Mike: </p>
<hr />
<div>== Using ifconfig ==<br />
<br />
=== Show interface configuration ===<br />
<pre><br />
$ ifconfig eno1<br />
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500<br />
inet 192.168.1.79 netmask 255.255.255.0 broadcast 192.168.1.255<br />
inet6 fe80::a6a5:87ad:cb7a:6cad prefixlen 64 scopeid 0x20<link><br />
ether 50:eb:f6:3f:27:61 txqueuelen 1000 (Ethernet)<br />
RX packets 137223 bytes 104941638 (104.9 MB)<br />
RX errors 0 dropped 0 overruns 0 frame 0<br />
TX packets 91146 bytes 22484489 (22.4 MB)<br />
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br />
device interrupt 16 memory 0xa1400000-a1420000 <br />
</pre><br />
<br />
Show All interfaces<br />
<pre><br />
$ ifconfig<br />
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500<br />
inet 192.168.2.1 netmask 255.255.255.0 broadcast 192.168.2.255<br />
ether 92:51:fc:1b:36:38 txqueuelen 1000 (Ethernet)<br />
RX packets 277 bytes 28650 (28.6 KB)<br />
RX errors 0 dropped 0 overruns 0 frame 0<br />
TX packets 899 bytes 129148 (129.1 KB)<br />
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br />
<br />
br-b737ea16f9fc: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500<br />
inet 172.25.0.1 netmask 255.255.0.0 broadcast 172.25.255.255<br />
ether 02:42:79:64:bc:e2 txqueuelen 0 (Ethernet)<br />
RX packets 0 bytes 0 (0.0 B)<br />
RX errors 0 dropped 0 overruns 0 frame 0<br />
TX packets 0 bytes 0 (0.0 B)<br />
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br />
<br />
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500<br />
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255<br />
ether 02:42:db:62:09:42 txqueuelen 0 (Ethernet)<br />
.....<br />
</pre><br />
<br />
=== Add ip alias ===<br />
$ ifconfig eth0:1 10.10.20.218 netmask 255.255.255.0 broadcast 10.10.20.255<br />
<br />
== Using ip ==<br />
<br />
=== ip Usage ===<br />
<br />
==== ip help ====<br />
<br />
==== ip link show ====<br />
<br />
=== add ip alias ===<br />
$ ip a add 192.168.178.2/24 dev eth0</div>Mikehttps://wiki.ttsh.dk/index.php?title=First_principles&diff=40First principles2023-01-15T12:13:25Z<p>Mike: </p>
<hr />
<div>== Using ifconfig ==<br />
<br />
=== Show interface configuration ===<br />
<pre><br />
$ ifconfig eno1<br />
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500<br />
inet 192.168.1.79 netmask 255.255.255.0 broadcast 192.168.1.255<br />
inet6 fe80::a6a5:87ad:cb7a:6cad prefixlen 64 scopeid 0x20<link><br />
ether 50:eb:f6:3f:27:61 txqueuelen 1000 (Ethernet)<br />
RX packets 137223 bytes 104941638 (104.9 MB)<br />
RX errors 0 dropped 0 overruns 0 frame 0<br />
TX packets 91146 bytes 22484489 (22.4 MB)<br />
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br />
device interrupt 16 memory 0xa1400000-a1420000 <br />
</pre><br />
<br />
Show All interfaces<br />
<pre><br />
$ ifconfig<br />
br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500<br />
inet 192.168.2.1 netmask 255.255.255.0 broadcast 192.168.2.255<br />
ether 92:51:fc:1b:36:38 txqueuelen 1000 (Ethernet)<br />
RX packets 277 bytes 28650 (28.6 KB)<br />
RX errors 0 dropped 0 overruns 0 frame 0<br />
TX packets 899 bytes 129148 (129.1 KB)<br />
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br />
<br />
br-b737ea16f9fc: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500<br />
inet 172.25.0.1 netmask 255.255.0.0 broadcast 172.25.255.255<br />
ether 02:42:79:64:bc:e2 txqueuelen 0 (Ethernet)<br />
RX packets 0 bytes 0 (0.0 B)<br />
RX errors 0 dropped 0 overruns 0 frame 0<br />
TX packets 0 bytes 0 (0.0 B)<br />
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0<br />
<br />
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500<br />
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255<br />
ether 02:42:db:62:09:42 txqueuelen 0 (Ethernet)<br />
.....<br />
</pre><br />
<br />
=== Add ip alias ===<br />
$ ifconfig eth0:1 10.10.20.218 netmask 255.255.255.0 broadcast 10.10.20.255<br />
<br />
== Using ip ==<br />
<br />
=== add ip alias ===<br />
$ ip a add 192.168.178.2/24 dev eth0</div>Mikehttps://wiki.ttsh.dk/index.php?title=Working_with_network_interfaces&diff=39Working with network interfaces2023-01-15T12:10:46Z<p>Mike: </p>
<hr />
<div>[[first principles | first principles and tools ]]<br />
<br />
[[Network-Centos 8|Centos 8]] (System V)<br />
<br />
[[Network-Debian | Generic Debian ]] <br />
<br />
[[Network - Ubuntu 22.04|ubuntu 22.04]] (Network Manager)<br />
<br />
[[Network-networkd | Systemd/Networkd]] (Systemd based)</div>Mikehttps://wiki.ttsh.dk/index.php?title=Network-networkd&diff=38Network-networkd2023-01-15T12:08:28Z<p>Mike: </p>
<hr />
<div>==Setup for Networkd==<br />
<br />
===Switching to Networkd ===<br />
<pre>$ systemctl stop NetworkManager <br />
$ systemctl disable NetworkManager <br />
$ systemctl enable systemd-networkd<br />
$ systemctl enable systemd-resolved<br />
$ systemctl start systemd-resolved<br />
$ rm /etc/resolv.conf<br />
$ ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf<br />
$ mkdir -p /etc/systemd/network</pre><br />
<br />
===Configuring Networkd===<br />
<br />
====What interfaces do we have====<br />
<pre><br />
# networkctl<br />
IDX LINK TYPE OPERATIONAL SETUP <br />
1 lo loopback carrier unmanaged<br />
2 eno1 ether routable unmanaged<br />
3 br0 bridge routable unmanaged<br />
4 virbr0 bridge no-carrier unmanaged<br />
5 docker0 bridge no-carrier unmanaged<br />
6 br-b737ea16f9fc bridge no-carrier unmanaged<br />
7 vnet0 ether degraded unmanaged<br />
<br />
7 links listed.<br />
<br />
</pre><br />
<br />
====Configuring en01 - static====<br />
<pre><br />
$ cat >> /etc/systemd/network/00-eno1.network << EOF<br />
[Match]<br />
Name=enp3s0<br />
<br />
[Network]<br />
Address=192.168.1.50/24<br />
Gateway=192.168.1.1<br />
DNS=192.168.1.1<br />
EOF<br />
</pre><br />
<br />
====Configuring en01 - dhcp====<br />
<pre><br />
$ cat >> /etc/systemd/network/00-eno1.network << EOF<br />
[Match]<br />
Name=enp3s0<br />
<br />
[Network]<br />
DHCP=yes<br />
EOF<br />
</pre><br />
<br />
=== Controlling interfaces ===<br />
==== Full Restart ====<br />
<pre><br />
$ systemctl restart systemd-network<br />
</pre><br />
<br />
==== Interface only ====<br />
<br />
<pre><br />
$ networkctl up eno1<br />
</pre><br />
<br />
<pre><br />
$ networkctl down eno1<br />
</pre><br />
<br />
==IP Alias for Networkd==<br />
<pre><br />
$ cat >> /etc/systemd/network/00-eno1.network << EOF<br />
[Match]<br />
Name=enp3s0<br />
[Network]<br />
Address=192.168.1.50/24<br />
Address=172.14.0.50/24<br />
Gateway=192.168.1.1<br />
DNS=192.168.1.1<br />
EOF<br />
</pre></div>Mikehttps://wiki.ttsh.dk/index.php?title=Network-networkd&diff=37Network-networkd2023-01-15T12:05:34Z<p>Mike: </p>
<hr />
<div>==Setup for Networkd==<br />
<br />
===Switching to Networkd ===<br />
<pre>$ systemctl stop NetworkManager <br />
$ systemctl disable NetworkManager <br />
$ systemctl enable systemd-networkd<br />
$ systemctl enable systemd-resolved<br />
$ systemctl start systemd-resolved<br />
$ rm /etc/resolv.conf<br />
$ ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf<br />
$ mkdir -p /etc/systemd/network</pre><br />
<br />
===Configuring Networkd===<br />
<br />
====What interfaces do we have====<br />
<pre><br />
# networkctl<br />
IDX LINK TYPE OPERATIONAL SETUP <br />
1 lo loopback carrier unmanaged<br />
2 eno1 ether routable unmanaged<br />
3 br0 bridge routable unmanaged<br />
4 virbr0 bridge no-carrier unmanaged<br />
5 docker0 bridge no-carrier unmanaged<br />
6 br-b737ea16f9fc bridge no-carrier unmanaged<br />
7 vnet0 ether degraded unmanaged<br />
<br />
7 links listed.<br />
<br />
</pre><br />
<br />
====Configuring en01 - static====<br />
<pre><br />
$ cat >> /etc/systemd/network/00-eno1.network << EOF<br />
[Match]<br />
Name=enp3s0<br />
<br />
[Network]<br />
Address=192.168.1.50/24<br />
Gateway=192.168.1.1<br />
DNS=192.168.1.1<br />
EOF<br />
</pre><br />
<br />
====Configuring en01 - dhcp====<br />
<pre><br />
$ cat >> /etc/systemd/network/00-eno1.network << EOF<br />
[Match]<br />
Name=enp3s0<br />
<br />
[Network]<br />
DHCP=yes<br />
EOF<br />
</pre><br />
<br />
=== Controlling interfaces ===<br />
==== Full Restart ====<br />
<pre><br />
$ systemctl restart systemd-network<br />
</pre><br />
<br />
==== Interface only ====<br />
<br />
<pre><br />
$ networkctl up eno1<br />
</pre><br />
<br />
<pre><br />
$ networkctl down eno1<br />
</pre><br />
<br />
==IP Alias for Networkd==</div>Mikehttps://wiki.ttsh.dk/index.php?title=Network-networkd&diff=36Network-networkd2023-01-15T11:53:21Z<p>Mike: </p>
<hr />
<div>===Switching to Networkd===<br />
$ sudo systemctl stop NetworkManager <br />
<br />
$ sudo systemctl disable NetworkManager <br />
<br />
$ sudo systemctl enable systemd-networkd</div>Mikehttps://wiki.ttsh.dk/index.php?title=Network-networkd&diff=35Network-networkd2023-01-15T11:51:31Z<p>Mike: Created page with "Switching to Networkd"</p>
<hr />
<div>Switching to Networkd</div>Mikehttps://wiki.ttsh.dk/index.php?title=Network_-_Ubuntu_22.04&diff=34Network - Ubuntu 22.042023-01-15T11:50:40Z<p>Mike: </p>
<hr />
<div>=== Adding an alias ===<br />
# nmcli connection show<br />
<pre><br />
NAME UUID TYPE DEVICE <br />
Ethernet connection 1 bb928bec-bfb0-45d9-9b58-84d6832cb485 ethernet eno1 <br />
br0 8c929bd9-a291-4278-a2e3-28f5b6820066 bridge br0 <br />
.....<br />
</pre>NetworkManager doesn't really support such aliases. It supports connection profiles (that basically correspond to a regular ifcfg file), and it supports multiple IP addresses per profile. But you can't split one profile into multiple parts, like what initscripts' aliases are.</div>Mikehttps://wiki.ttsh.dk/index.php?title=Network-Debian&diff=33Network-Debian2023-01-15T11:48:35Z<p>Mike: </p>
<hr />
<div>===Adding an IP alias===<br />
$ vi /etc/network/interfaces<br />
<br />
<pre>#secondary ip address<br />
auto eth0:0<br />
iface eth0:0 inet static<br />
address 10.10.1.100<br />
netmask 255.255.255.0</pre>$ ifup eth0:0<br />
<br />
or<br />
<br />
$ service networking restart</div>Mike