quick client setup walkthrough

created onNovember 18, 2025
This walkthrough is for a quick client machine network setup by hand. The examples are for a fictive client machine with the following client and network values: ...

dhcpd setup

created onNovember 18, 2025
dhcpcd reached its EOL in the end of 2022 and is now superseded by kea. One reason to use dhcpd any longer is when a migration is to kea version 1.9.1 or later is not possible. ...

dhcpcd setup

created onOctober 7, 2025
dhcpcd (Dynamic Host Configuration Protocol Client Demon) is the demon responsible for querying a DHCP server (i.e., ISC kea) and configure the machine for the network it is about to join from the lease it receives from the DHCP server. A DHCP lease contains configuration values, i.e.: ...

wireless setup

created onNovember 18, 2025
preparations check if wlan0 is powered up iwlist wlan0 power list available networks with iwlist iwlist wlan0 scanning generate config block for SSID with wpa_passphrase wpa_passphrase computes a 256-bit PSK and generates a configuration block for the network with the SSID (Service Set Identifier) or ESSID (Extended Service Set Identifier) provided as parameter. For an access point with the SSID base, the command line is: ...

network setup with iproute2 and net-tools commands

created onNovember 12, 2025
In Linux, the network setup of a machine is done with the iproute2 tools. The iproute tools supersede the now obsolete net-tools, which include, among others, the well known ifconfig, route and netstat commands. ...

interface naming schemes

created onAugust 21, 2025
there are several naming schemes in Linux: the “traditional” or “classic” naming scheme of the nineties with iface names eth0, eth1, wlan0, wlan1, etc. Interfaces get their names assigned by the kernel on a first-come, first-serve policy as they are probed by the network interface drivers. With nowadays complex hardware, this way of naming is no longer predictable if more than one interface of a kind (ethernet, wlan, …) exists in the machine. some custom schemes working towards alleviating the problem mentioned above. Programs like nameif and ifrename (which uses udev) used config files like /etc/iftab and assigned interface names based on the MAC address – which comes with another set of problems. These custom schemes seem to be no longer in use. the predictable network interface devices names introduced in udev. Note that udev is developed as a part of systemd but can be used completely without systemd (at least at the time of writing). The authoritative documentation on the persistent naming on freedesktop.org is marked as obsolete and refers to the systemd.net-naming-scheme man page. Unfortunately, I can’t wrap my head around that man page completely. ...