WireGuard not routing IPv4 traffic: GNOME 3 / Network Manager
A reminder for me.
If you’ve got WireGuard configured as a VPN client in Debian 11 Bullseye’s Network Manager, and it does not route IPv4, check that your IPv4 address has “/32” after it.
(Note that this the “/32” is not present in the config which is generated by algo.)
You may also like:
- WireGuard VPN plugin for NetworkManager in GNOME 3 on Debian 11 Bullseye
- Removing the default games in GNOME 3 on Debian 10
- wireguard via algo: a simpler, faster(ish) alternative to IPSec
- Early impressions of CryptPad on a Raspberry Pi
- Removing pages from a PDF with pdftk
- SurfaceBook 2 13: keyboard layout for English
- Rotating all the odd pages in a PDF document
- Microsoft Surface, Debian, and two 4k monitor frustrations
- Implementing BusKill: shutting down a Debian 11 Bullseye machine when a specific USB device is removed
- Fixing 'tee: command not found' on Debian 11 Bullseye
- Installing Twitter client cawbird from the official Debian 11 Bullseye repo
- Installing Debian 11 on a Microsoft Surface Go: secure boot, mokutil, Wi-Fi, and libinih1
- Adding music from an ssh-accessible remote server to an Android phone via Debian 11
- PineTab running Mobian and GNOME: an iPad replacement?
- PinePhone: WireGuard, dns-over-https, and other thoughts