

It’s very different from IPtables for sure and feels more like pf.Same here - never got the micah solution working in the last couple of month.


There’s a certain similarity, but it’s not the same. The Syntaxįor some reason the syntax of Nftables rules reminds me of OpenBSD’s pf. I remember reading about Nftables in the Debian IPtables Wiki page earlier but hadn’t paid much notice. But Buster only uses Nftables in the backend and users deal with it via an IPtables layer (thus you use the IPtables syntax) and that’s why I hadn’t noticed it. I hadn’t realized, but since I had some VMs running Debian Buster I was already using Nftables. Also great references are the Arch Wiki, Gentoo Wiki, and to a lesser extent the Debian Wiki. What is Nftables?įor a quick intro on what Nftables is and how it compares to IPtables check out this article from ungleich.ch. However, since I took a look at Nftables, and I am sure I’ll forget it in a few days, I wanted to jot down the commands here for future reference. The fix was simple eventually – add two rules to the rules created by Mullvad, allowing access to & from the tailscale interface.

(Moreover, when pinging the message was ping: sendmsg: operation not permitted again indicating a firewall). When I’d delete the firewall rules added by the Mullvad client TailScale would work fine. Everything else was similar to what I had blogged about earlier – the IProute2 stuff about policy based routing – and the issue here didn’t seem to be policy based routing related, rather it was to do with the firewall. Ubuntu use Nftables rather than IPtables and that was new to me. I was curious and so I installed Ubuntu 20.04 (which is what he was using) in a VM and took a look at things. I don’t use their app though, I use the WireGuard app with the config pointing to Mullvad). (Mullvad is the VPN provider I too use btw. He was curious to know if I had encountered this. A reader (Doug Miller) wrote to say that he was using WireGuard via the Mullvad VPN app and whenever he started VPN TailScale would stop working. A while ago I had written a post on TailScale and WireGuard (and policy based routing).
