ReadonlyPi

2024-07-14T20:15:50Z

Erwin:

Overview

https://learn.adafruit.com/read-only-raspberry-pi/overview

RaspberryPi aanpassingen

Voor het omzetten van de dans met wireguard opnieuw starten:

systemctl restart wg-quick@wg0

Unlike most microcontroller projects that can simply be switched off when done, computers like the Raspberry Pi require an orderly shutdown procedure…otherwise the storage card may become corrupted and the system will no longer boot.

There are situations where just pulling the plug would certainly be handy, like slideshow or video kiosks, or systems left in the hands of non-technical users. Fortunately recent Raspberry Pi OS releases have a configuration option to make systems more resistant to unplanned power cuts.
The Concern

Linux—or any substantial computer operating system, Windows and Mac are the same way—behind the scenes they’re frequently writing temporary data to disk (or the SD card with Raspberry Pi). This is why we normally use the shutdown command: every file is put away in a known valid state. But if power is unexpectedly cut, these lingering half-files can render a card unbootable…one can try patching it up, but often there’s no recourse but to wipe the card and reinstall everything.
The Solution

Recent Rapsberry Pi OS releases have an option to put the /boot partition (where the kernel image and other critical files reside) in a read-only mode. If software installed on this system only performs reading and playback operations (e.g. a slideshow kiosk, a Fadecandy server, a Halloween display), then you can just unplug the system when done. It’s not ideal for read/write tasks like databases, web servers or data logging, but it has a place.
Before You Begin

This works with Raspberry Pi OS and close derivatives (e.g. RetroPie), but might not work with other distributions.
Setting up read-only mode should be the very last step before deploying a project. Get all your code and data on the system, get software auto-starting as needed, test it normally with the usual boot and shutdown methodology. It’s easier up-front. Once you’re 100% confident in its operation, then configure the system for read-only boot.
Back up the contents of your SD card first. We’ve tested on a couple versions of Raspbian, but maybe something’s changed, or has been overlooked, and could leave the Pi in a weird intermediate state.

Enabling Read-Only /boot

We assume that you have a Pi booted and on a network…like mentioned above, everything already configured and fully functional (and backed up) before taking this step. We have other guides covering the very basics of getting a Raspberry Pi started.
Using the Desktop/GUI “Full” OS

You’ll find this setting in the Raspberry Pi Configuration tool. From the Raspberry menu at the top-left…

Pi→Preferences→Raspberry Pi Configuration

learn_raspberry_pi_gui-1.png
learn_raspberry_pi_gui-1.png
learn_raspberry_pi_gui-2.png
learn_raspberry_pi_gui-3.png
learn_raspberry_pi_gui-4.png

Go to the “Performance” tab and you’ll see an option “Overlay File System.” Click the “Configure…” button.

Select “Overlay: Enabled” and “Boot Partition: Read-only.”

Click “OK” and wait while the system works. It may take a minute or more to complete. This is normal.

Reboot when prompted.
Using the “Lite” Command-Line OS

These options can be found in the raspi-config tool, which must be run as root:
Download File
Copy Code

sudo raspi-config

learn_raspberry_pi_cmdline-1.png
learn_raspberry_pi_cmdline-1.png
learn_raspberry_pi_cmdline-2.png
learn_raspberry_pi_cmdline-3.png
learn_raspberry_pi_cmdline-4.png

Navigate down to “Performance Options” and then “Overlay File System.” Select “Yes” to both the enable and write-protect questions.

It may take a minute or more while the system works, this is normal. Tab to the “Finish” button and reboot when prompted.
For Both

You’re done! Now the /boot partition is safely locked. If you need to access something there though, like the config.txt file, or a major system update, instructions to temporarily enable write access are given below.

With each new OS release, it’s normal that some configuration options may move to different menus or positions. If you can’t find it where shown, check under the other top-level menu options…even if moved, the name will likely remain similar.
Restoring Read/Write Access

If you need to temporarily enable read/write access, as when editing tricky configuration settings in /boot/config.txt, or major system updates affecting the kernel or device tree files, this can be done from the command line (if using “full” Raspbian with a GUI, open a terminal window):
Download File
Copy Code

sudo mount -o remount,rw /boot

Perform your edits or upgrades, then reboot the system (via Pi→Shutdown with the GUI, or sudo reboot from the command line). It will be back in its read-only state.

If you need to permanently restore read/write access, you must first use the temporary step above, then can navigate to the same GUI or raspi-config settings, selecting “Read-write” for the GUI option, or “No” for the raspi-config write-protect question. Then reboot and the system’s back to normal, with permanent read/write access.
If you have enabled read/write access to /boot, whether temporarily or permanently, always wrap up your session with an orderly shutdown or reboot.
You’re Not Finished Yet

Test the modified system extensively to make sure that the system boots and your application runs as intended. If it doesn’t…does the software you’re using rely on temporary files in the /boot partition? Maybe it can be adjusted.

Now make an image of the SD card (using dd or Apple Pi Baker or whatever your backup tool of preference) and, if it’s a critical application, burn at least one spare. There are other ways cards can go bad…static, brown-outs, falling out and getting lost…this read-only setup won’t always save you. SD cards are cheap now! Spares help if you’ve left a system in someone else’s care (let’s say a museum kiosk) and it fails for some reason, you can ask them to just swap out the card until you can get there to troubleshoot. I know at least one Burning Man project rendered useless in the first few minutes of the event because their one and only card fell out and was lost on the playa.

ReadonlyPi

2024-07-14T19:57:45Z

Erwin:

Overview

https://learn.adafruit.com/read-only-raspberry-pi/overview

Unlike most microcontroller projects that can simply be switched off when done, computers like the Raspberry Pi require an orderly shutdown procedure…otherwise the storage card may become corrupted and the system will no longer boot.

There are situations where just pulling the plug would certainly be handy, like slideshow or video kiosks, or systems left in the hands of non-technical users. Fortunately recent Raspberry Pi OS releases have a configuration option to make systems more resistant to unplanned power cuts.
The Concern

Linux—or any substantial computer operating system, Windows and Mac are the same way—behind the scenes they’re frequently writing temporary data to disk (or the SD card with Raspberry Pi). This is why we normally use the shutdown command: every file is put away in a known valid state. But if power is unexpectedly cut, these lingering half-files can render a card unbootable…one can try patching it up, but often there’s no recourse but to wipe the card and reinstall everything.
The Solution

Recent Rapsberry Pi OS releases have an option to put the /boot partition (where the kernel image and other critical files reside) in a read-only mode. If software installed on this system only performs reading and playback operations (e.g. a slideshow kiosk, a Fadecandy server, a Halloween display), then you can just unplug the system when done. It’s not ideal for read/write tasks like databases, web servers or data logging, but it has a place.
Before You Begin

This works with Raspberry Pi OS and close derivatives (e.g. RetroPie), but might not work with other distributions.
Setting up read-only mode should be the very last step before deploying a project. Get all your code and data on the system, get software auto-starting as needed, test it normally with the usual boot and shutdown methodology. It’s easier up-front. Once you’re 100% confident in its operation, then configure the system for read-only boot.
Back up the contents of your SD card first. We’ve tested on a couple versions of Raspbian, but maybe something’s changed, or has been overlooked, and could leave the Pi in a weird intermediate state.

Enabling Read-Only /boot

We assume that you have a Pi booted and on a network…like mentioned above, everything already configured and fully functional (and backed up) before taking this step. We have other guides covering the very basics of getting a Raspberry Pi started.
Using the Desktop/GUI “Full” OS

You’ll find this setting in the Raspberry Pi Configuration tool. From the Raspberry menu at the top-left…

Pi→Preferences→Raspberry Pi Configuration

learn_raspberry_pi_gui-1.png
learn_raspberry_pi_gui-1.png
learn_raspberry_pi_gui-2.png
learn_raspberry_pi_gui-3.png
learn_raspberry_pi_gui-4.png

Go to the “Performance” tab and you’ll see an option “Overlay File System.” Click the “Configure…” button.

Select “Overlay: Enabled” and “Boot Partition: Read-only.”

Click “OK” and wait while the system works. It may take a minute or more to complete. This is normal.

Reboot when prompted.
Using the “Lite” Command-Line OS

These options can be found in the raspi-config tool, which must be run as root:
Download File
Copy Code

sudo raspi-config

learn_raspberry_pi_cmdline-1.png
learn_raspberry_pi_cmdline-1.png
learn_raspberry_pi_cmdline-2.png
learn_raspberry_pi_cmdline-3.png
learn_raspberry_pi_cmdline-4.png

Navigate down to “Performance Options” and then “Overlay File System.” Select “Yes” to both the enable and write-protect questions.

It may take a minute or more while the system works, this is normal. Tab to the “Finish” button and reboot when prompted.
For Both

You’re done! Now the /boot partition is safely locked. If you need to access something there though, like the config.txt file, or a major system update, instructions to temporarily enable write access are given below.

With each new OS release, it’s normal that some configuration options may move to different menus or positions. If you can’t find it where shown, check under the other top-level menu options…even if moved, the name will likely remain similar.
Restoring Read/Write Access

If you need to temporarily enable read/write access, as when editing tricky configuration settings in /boot/config.txt, or major system updates affecting the kernel or device tree files, this can be done from the command line (if using “full” Raspbian with a GUI, open a terminal window):
Download File
Copy Code

sudo mount -o remount,rw /boot

Perform your edits or upgrades, then reboot the system (via Pi→Shutdown with the GUI, or sudo reboot from the command line). It will be back in its read-only state.

If you need to permanently restore read/write access, you must first use the temporary step above, then can navigate to the same GUI or raspi-config settings, selecting “Read-write” for the GUI option, or “No” for the raspi-config write-protect question. Then reboot and the system’s back to normal, with permanent read/write access.
If you have enabled read/write access to /boot, whether temporarily or permanently, always wrap up your session with an orderly shutdown or reboot.
You’re Not Finished Yet

Test the modified system extensively to make sure that the system boots and your application runs as intended. If it doesn’t…does the software you’re using rely on temporary files in the /boot partition? Maybe it can be adjusted.

Now make an image of the SD card (using dd or Apple Pi Baker or whatever your backup tool of preference) and, if it’s a critical application, burn at least one spare. There are other ways cards can go bad…static, brown-outs, falling out and getting lost…this read-only setup won’t always save you. SD cards are cheap now! Spares help if you’ve left a system in someone else’s care (let’s say a museum kiosk) and it fails for some reason, you can ask them to just swap out the card until you can get there to troubleshoot. I know at least one Burning Man project rendered useless in the first few minutes of the event because their one and only card fell out and was lost on the playa.

ReadonlyPi

2024-06-30T16:01:10Z

Erwin: Nieuwe pagina aangemaakt met ' Overview Unlike most microcontroller projects that can simply be switched off when done, computers like the Raspberry Pi require an orderly shutdown procedure…otherwise the storage card may become corrupted and the system will no longer boot. There are situations where just pulling the plug would certainly be handy, like slideshow or video kiosks, or systems left in the hands of non-technical users. Fortunately recent Raspberry Pi OS releases have a confi...'

Overview

Unlike most microcontroller projects that can simply be switched off when done, computers like the Raspberry Pi require an orderly shutdown procedure…otherwise the storage card may become corrupted and the system will no longer boot.

There are situations where just pulling the plug would certainly be handy, like slideshow or video kiosks, or systems left in the hands of non-technical users. Fortunately recent Raspberry Pi OS releases have a configuration option to make systems more resistant to unplanned power cuts.
The Concern

Linux—or any substantial computer operating system, Windows and Mac are the same way—behind the scenes they’re frequently writing temporary data to disk (or the SD card with Raspberry Pi). This is why we normally use the shutdown command: every file is put away in a known valid state. But if power is unexpectedly cut, these lingering half-files can render a card unbootable…one can try patching it up, but often there’s no recourse but to wipe the card and reinstall everything.
The Solution

Recent Rapsberry Pi OS releases have an option to put the /boot partition (where the kernel image and other critical files reside) in a read-only mode. If software installed on this system only performs reading and playback operations (e.g. a slideshow kiosk, a Fadecandy server, a Halloween display), then you can just unplug the system when done. It’s not ideal for read/write tasks like databases, web servers or data logging, but it has a place.
Before You Begin

This works with Raspberry Pi OS and close derivatives (e.g. RetroPie), but might not work with other distributions.
Setting up read-only mode should be the very last step before deploying a project. Get all your code and data on the system, get software auto-starting as needed, test it normally with the usual boot and shutdown methodology. It’s easier up-front. Once you’re 100% confident in its operation, then configure the system for read-only boot.
Back up the contents of your SD card first. We’ve tested on a couple versions of Raspbian, but maybe something’s changed, or has been overlooked, and could leave the Pi in a weird intermediate state.

Enabling Read-Only /boot

We assume that you have a Pi booted and on a network…like mentioned above, everything already configured and fully functional (and backed up) before taking this step. We have other guides covering the very basics of getting a Raspberry Pi started.
Using the Desktop/GUI “Full” OS

You’ll find this setting in the Raspberry Pi Configuration tool. From the Raspberry menu at the top-left…

Pi→Preferences→Raspberry Pi Configuration

learn_raspberry_pi_gui-1.png
learn_raspberry_pi_gui-1.png
learn_raspberry_pi_gui-2.png
learn_raspberry_pi_gui-3.png
learn_raspberry_pi_gui-4.png

Go to the “Performance” tab and you’ll see an option “Overlay File System.” Click the “Configure…” button.

Select “Overlay: Enabled” and “Boot Partition: Read-only.”

Click “OK” and wait while the system works. It may take a minute or more to complete. This is normal.

Reboot when prompted.
Using the “Lite” Command-Line OS

These options can be found in the raspi-config tool, which must be run as root:
Download File
Copy Code

sudo raspi-config

learn_raspberry_pi_cmdline-1.png
learn_raspberry_pi_cmdline-1.png
learn_raspberry_pi_cmdline-2.png
learn_raspberry_pi_cmdline-3.png
learn_raspberry_pi_cmdline-4.png

Navigate down to “Performance Options” and then “Overlay File System.” Select “Yes” to both the enable and write-protect questions.

It may take a minute or more while the system works, this is normal. Tab to the “Finish” button and reboot when prompted.
For Both

You’re done! Now the /boot partition is safely locked. If you need to access something there though, like the config.txt file, or a major system update, instructions to temporarily enable write access are given below.

With each new OS release, it’s normal that some configuration options may move to different menus or positions. If you can’t find it where shown, check under the other top-level menu options…even if moved, the name will likely remain similar.
Restoring Read/Write Access

If you need to temporarily enable read/write access, as when editing tricky configuration settings in /boot/config.txt, or major system updates affecting the kernel or device tree files, this can be done from the command line (if using “full” Raspbian with a GUI, open a terminal window):
Download File
Copy Code

sudo mount -o remount,rw /boot

Perform your edits or upgrades, then reboot the system (via Pi→Shutdown with the GUI, or sudo reboot from the command line). It will be back in its read-only state.

If you need to permanently restore read/write access, you must first use the temporary step above, then can navigate to the same GUI or raspi-config settings, selecting “Read-write” for the GUI option, or “No” for the raspi-config write-protect question. Then reboot and the system’s back to normal, with permanent read/write access.
If you have enabled read/write access to /boot, whether temporarily or permanently, always wrap up your session with an orderly shutdown or reboot.
You’re Not Finished Yet

Test the modified system extensively to make sure that the system boots and your application runs as intended. If it doesn’t…does the software you’re using rely on temporary files in the /boot partition? Maybe it can be adjusted.

Now make an image of the SD card (using dd or Apple Pi Baker or whatever your backup tool of preference) and, if it’s a critical application, burn at least one spare. There are other ways cards can go bad…static, brown-outs, falling out and getting lost…this read-only setup won’t always save you. SD cards are cheap now! Spares help if you’ve left a system in someone else’s care (let’s say a museum kiosk) and it fails for some reason, you can ask them to just swap out the card until you can get there to troubleshoot. I know at least one Burning Man project rendered useless in the first few minutes of the event because their one and only card fell out and was lost on the playa.

2024-02-22T08:10:52Z

Erwin: Nieuwe pagina aangemaakt met 'Logging uitschakelen If you are not interested in the logs you can switch a lot off using a log configuration setting. Edit the file /etc/rsyslog.conf and just after the section starting ############### #### RULES #### ############### add the following line. <code>*.* ~</code> If you want to be more fine-grained you will need to read the file comments. Do not forget to restart rsyslog daemon: <code>sudo service rsyslog restart</code>'

Logging uitschakelen

If you are not interested in the logs you can switch a lot off using a log configuration setting.

Edit the file /etc/rsyslog.conf and just after the section starting

###############
#### RULES ####
###############

add the following line.

<code>*.* ~</code>

If you want to be more fine-grained you will need to read the file comments.

Do not forget to restart rsyslog daemon:

<code>sudo service rsyslog restart</code>

Handleidingen voor diverse applicaties met Rocky 9

2024-02-22T08:09:52Z

Erwin:

2024-02-22T07:28:23Z

Erwin:

2024-02-21T20:49:30Z

Erwin:

Connect to Wi-Fi From Terminal on Debian 11/10 with WPA Supplicant
Last Updated: November 8th, 2022 Xiao Guoan (Admin) 20 Comments
Debian

This tutorial is going to show you how to connect to Wi-Fi network from the command line on Debian 11/10 server and desktop using wpa_supplicant, which is an implementation of the supplicant component for the WPA protocol. A supplicant in wireless LAN is client software installed on end-user’s computer that needs to be authenticated in order to join a network.

Please note that you will need to install the wpa_supplicant software before connecting to Wi-Fi, so you need to connect to Wired Ethernet first, which is done for just one time. If you don’t like this method, please don’t be mad at me. Maybe someday Debian will ship wpa_supplicant out of the box.
Step 1: Find The Name of Your Wireless Interface And Wireless Network

Run iwconfig command to find the name of your wireless interface.

<code>iwconfig</code>

wlan0 is a common name for a wireless network interface on Linux systems. On systemd-based Linux distros, you might have a wireless interface named wlp4s0.

debian server connect to wifi terminal

As you can see, the wireless interface isn’t associated with any access point right now. Then run the following command to bring up the wireless interface.

<code>sudo ip link set dev wlp4s0 up</code>

If you encounter the following error,

RTNETLINK answers: Operation not possible due to RF-kill

you need to unblock Wi-Fi with the following command.

<code>sudo rfkill unblock wifi</code>

Next, find your wireless network name by scanning nearby networks with the command below. Replace wlp4s0 with your own wireless interface name. ESSID is the network name identifier.

*<code>sudo iwlist wlp4s0 scan | grep ESSID</code>

debian connect to wifi command line wpa supplicant
Step 2: Connect to Wi-Fi Network With WPA_Supplicant

Now install wpa_supplicant on Debian 11/10 from the default software repository.

<code>sudo apt install wpasupplicant</code>

We need to create a file named wpa_supplicant.conf using the wpa_passphrase utility. wpa_supplicant.conf is the configuration file describing all networks that the user wants the computer to connect to. Run the following command to create this file. Replace ESSID (network name) and Wi-Fi passphrase with your own.
wpa_passphrase your-ESSID your-wifi-passphrase | sudo tee -a /etc/wpa_supplicant/wpa_supplicant.conf

<code>wpa_passphrase your-ESSID your-wifi-passphrase | sudo tee -a /etc/wpa_supplicant/wpa_supplicant.conf</code>

debian wpa_passphrase

If your ESSID contains whitespace such as (linuxbabe WiFi), you need to wrap the ESSID with double-quotes ("linuxbabe WiFi") in the above command.

The output of wpa_passphrase command will be piped to tee, and then written to the /etc/wpa_supplicant/wpa_supplicant.conf file. Now use the following command to connect your wireless card to the wireless access point.

<code>sudo wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -i wlp4s0</code>

The following output indicates your wireless card is successfully connected to an access point.

Successfully initialized wpa_supplicant
wlp4s0: SME: Trying to authenticate with c5:4a:21:53:ac:eb (SSID='CMCC-11802' freq=2437 MHz)
wlp4s0: Trying to associate with c5:4a:21:53:ac:eb (SSID='CMCC-11802' freq=2437 MHz)
wlp4s0: Associated with c5:4a:21:53:ac:eb
wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp4s0: WPA: Key negotiation completed with c5:4a:21:53:ac:eb [PTK=CCMP GTK=CCMP]
wlp4s0: CTRL-EVENT-CONNECTED - Connection to c5:4a:21:53:ac:eb completed [id=0 id_str=]

Note that if you are using Debian desktop edition, then you need to stop Network Manager with the following command, otherwise it will cause a connection problem when using wpa_supplicant.

<code>sudo systemctl stop NetworkManager</code>

And disable NetworkManager auto-start at boot time by executing the following command.

<code>sudo systemctl disable NetworkManager-wait-online NetworkManager-dispatcher NetworkManager</code>

By default, wpa_supplicant runs in the foreground. If the connection is completed, then open up another terminal window and run

<code>iwconfig</code>

You can see that the wireless interface is now associated with an access point.

enable wifi on debian using terminal command

You can press CTRL+C to stop the current wpa_supplicant process and run it in the background by adding the -B flag.

*<code>sudo wpa_supplicant -B -c /etc/wpa_supplicant.conf -i wlp4s0</code>

Although we’re authenticated and connected to a wireless network, we don’t have an IP address yet. To obtain a private IP address from DHCP server, use the following command:

<code>sudo dhclient wlp4s0</code>

Now your wireless interface has a private IP address, which can be shown with:

<code>ip addr show wlp4s0</code>

debian dhclient obtain private ip address

Now you can access the Internet. To release the private IP address, run

<code>sudo dhclient wlp4s0 -r</code>

Connecting to Hidden Wireless Network

If your wireless router doesn’t broadcast ESSID, then you need to add the following line in /etc/wpa_supplicant/wpa_supplicant.conf file.

scan_ssid=1

Like below:

<nowiki><code>network={
ssid="LinuxBabe.Com Network"
#psk="12345qwert"
psk=68add4c5fee7dc3d0dac810f89b805d6d147c01e281f07f475a3e0195
scan_ssid=1
}</code></nowiki>

Step 3: Auto-Connect At System Boot Time

To automatically connect to wireless network at boot time, we need to edit the wpa_supplicant.service file. It’s a good idea to copy the file from /lib/systemd/system/ directory to /etc/systemd/system/ directory, then edit the file content, because we don’t want a newer version of wpa_supplicant to override our modifications.

<code>sudo cp /lib/systemd/system/wpa_supplicant.service /etc/systemd/system/wpa_supplicant.service</code>

Edit the file with a command-line text editor, such as Nano.

<code>sudo nano /etc/systemd/system/wpa_supplicant.service</code>

Find the following line.

<code>ExecStart=/sbin/wpa_supplicant -u -s -O /run/wpa_supplicant</code>

Change it to the following. Here we added the configuration file and the wireless interface name to the ExecStart command.

<code>ExecStart=/sbin/wpa_supplicant -u -s -c /etc/wpa_supplicant/wpa_supplicant.conf -i wlp4s0</code>

It’s recommended to always try to restart wpa_supplicant when failure is detected. Add the following right below the ExecStart line.

<code>Restart=always</code>

Save and close the file. (To save a file in Nano text editor, press Ctrl+O, then press Enter to confirm. To exit, press Ctrl+X.) Then reload systemd.

<code>sudo systemctl daemon-reload</code>

Enable wpa_supplicant service to start at boot time.

<code>sudo systemctl enable wpa_supplicant.service</code>

We also need to start dhclient at boot time to obtain a private IP address from DHCP server. This can be achieved by creating a systemd service unit for dhclient.

<code>sudo nano /etc/systemd/system/dhclient.service</code>

Put the following text into the file.

<code>
[Unit]
Description= DHCP Client
Before=network.target
After=wpa_supplicant.service

[Service]
Type=forking
ExecStart=/sbin/dhclient wlp4s0 -v
ExecStop=/sbin/dhclient wlp4s0 -r
Restart=always

[Install]
WantedBy=multi-user.target
</code>

Save and close the file. Then enable this service.

<code>sudo systemctl enable dhclient.service</code>

How to Obtain a Static IP Address

If you want to obtain a static IP address, then you need to disable dhclient.service.

<code>sudo systemctl disable dhclient.service</code>

Create a network config file.

<code>sudo nano /etc/systemd/network/static.network</code>

Add the following lines.
<code>
[Match]
Name=wlp4s0

[Network]
Address=192.168.1.8/24
Gateway=192.168.1.1
</code>
Save and close the file. Then create a .link file for the wireless interface.

sudo nano /etc/systemd/network/10-wifi.link

Add the following lines in this file. You need to use your own MAC address and wireless interface name. This is to prevent the system from changing the wireless interface name.
<code>
[Match]
MACAddress=a8:4b:05:2b:e8:54

[Link]
NamePolicy=
Name=wlp4s0
</code>
Save and close the file. Then disable the networking.service and enable systemd-networkd.service, which will take care of networking.

<code>sudo systemctl disable networking

sudo systemctl enable systemd-networkd</code>

You can now restart systemd-networkd to see if your configuration works.

<code>sudo systemctl restart systemd-networkd</code>

Another way to obtain a static IP address is by logging into your router’s management interface and assigning a static IP to the MAC address of your wireless card, if your router supports this feature.

Recommended Reading:

How to Use Systemd on Linux – Manage Services, Run Levels and Logs

Multiple Wi-Fi Networks

The /etc/wpa_supplicant.conf configuration file can include multiple Wi-Fi networks. wpa_supplicant automatically selects the best network based on the order of network blocks in the configuration file, network security level, and signal strength.

To add a second Wi-Fi network, run:

<code>wpa_passphrase your-ESSID your-wifi-passphrase | sudo tee -a /etc/wpa_supplicant/wpa_supplicant.conf</code>

Note that you need to use the -a option with the tee command, which will append, instead of deleting the original content, the new Wifi-network to the file.
Wi-Fi Security

Do not use WPA2 TKIP or WPA2 TKIP+AES as the encryption method in your Wi-Fi router. TKIP is not considered secure anymore. You can use WPA2-AES as the encryption method.
Wrapping Up

I hope this tutorial helped you connect Debian 11/10 to Wi-Fi network from the command line with WPA Supplicant. As always, if you found this post useful, then subscribe to our free newsletter to get more tips and tricks 🙂