eddie nftables has been removed from Eddie's Network Lock, and DNS is leaking.

[72MqavduqVa286gd 0]

Until a few days ago, I was able to use nftables with Eddie’s Network-Lock, and I wasn’t experiencing any DNS leaks.

However, when I checked Eddie yesterday, I found that these options had been removed from the Network-Lock settings, leaving me with only iptables-legacy as an option.

I had no choice but to try using iptables-legacy, but now I’m experiencing DNS leaks, which is causing me some trouble.

OS: Arch Linux (6.19.11-arch1-1)
Eddie Version: v2.25.1

Edited ... by 72MqavduqVa286gd

[Staff 10515]

@72MqavduqVa286gd

Hello!

Nothing changed in Eddie's choice order about which firewall utility to run for the Network Lock rules. If both iptables-legacy and nft utilities are available Eddie picks iptables to avoid mixing up nft and iptables rules in various distributions running daemons at startup that, in turn, still run iptables (mixing up nft and iptables causes problems). You may force Eddie to use nft in "Preferences" > "Network Lock" windows, provided that the nft utility is in the command path. However this is probably irrelevant because, for Network Lock purposes, iptables and nft rules are identical.

DNS leaks are not strictly related to network lock: we mean that in general there must be no DNS leak with or without Network Lock. Feel free to publish a system report generated by Eddie for further investigation.

Kind regards
 

[72MqavduqVa286gd 0]

https://eddie.website/report/0416538d/
Here is my system report. Please take a look.

So, the fact that nft isn't showing up in Network Lock wasn't Eddie's problem—it was mine. I apologize.