(post-update): Wireless adapters on systemd-nspawn containers

Mention systemd/systemd#30956 which will fix this problem and we will not need workarounds.
nspawn · Jan 25, 2024 · 5c912b4 · 5c912b4
1 parent 56011c2
commit 5c912b4
Showing 1 changed file with 4 additions and 0 deletions.
diff --git a/_posts/2024-01-15-wireless-adapters-on-systemd-nspawn-containers.md b/_posts/2024-01-15-wireless-adapters-on-systemd-nspawn-containers.md
@@ -9,6 +9,10 @@ image:
   path: /wifi_adapter.png
   alt: Wireless adapter
 ---
+Passing a wireless adapter to a systemd-nspawn container is not as easy as it seems, but it's possible.
+
+Update: it's going to change with [this pull request](https://github.com/systemd/systemd/pull/30956) and should just work out of the box using the `Interface=` option on the `.nspawn` configuration file. I will update this post or create a new one when the feature is released.
+
 ## The problem
 The last night I was trying to setup a systemd-nspawn container that will use a wireless adapter to perform some WiFi pentesting. I said to myself, this is going to be easy, I just need to bind the wireless adapter to the container and that's it. But I was wrong, when I tried to start the container with `Interface=wlan0` on my `.nspawn` configuration file, I got the following error: