My AIR VPN (Eddie AUR Client) won’t connect to a VPN and there is a message poping up related to Network Lock:
There is no available or enabled Network Lock mode, sorry.
Old info mix from Stable Update Topic:
Does this update includes fixes for the local privilege escalation?
Is it okay to remove some of the module blockages after this update?
If your system works perfectly fine with the mitigations active, keep them. At the current state some kernels are fixed, but upstream is still adding newer fixes to 6.18+ and 7.x+ series. Older series may be more vulnerable …
Some of the module blocks, no longer allowes my VPN to create a Network Lock.
Idk which module is the culprit, but i think its related to your first mitigation recommendation.
Which includes ~4 module blocks, if i remember correctly.
Im on LTS 6.18 btw. but anyways, its not this important to use a VPN right now, so im fine… at least for another week.
7.x series has the latest fixes for these. Try it out. You can check modules one by one and read about them, if they are still affected. And regardless if your disk is not encrypted you can hack it with any Linux Live-Media anyway …
Thanks for the info and thank you for all your hard work you doing for us, im so glad that we can still rely on you 
Fun fact, Veracrypt is normaly working even with this module blocks.
Maybe you wanna check the new shiny wiki
I made a little script to pop up what is blocked in realtime.
Okay im pretty lost now, i removed the mitigations and deleted this files:
/etc/modprobe.d/dirtyfrag.conf
/etc/sysctl.d/10-ptrace.conf
And i restarted my Laptop but AIR VPN still refused to work and complained that he can’t create a Network Lock.
Do you use modulejail? Because it uses another blocklist file?
Nah i don’t use it, my plan was first to find out if my VPN is working as before… but as it looks it is no longer working.
Im wondering if this module blocks are still active in background or what is going on here… maybe it isn’t so easy to revert this changes from mitigation and there is more to do as deleting this files and restarting my device?
The modprobe stuff is immediately active. The file is read on module start attempt. So it isn’t that.
What does say
journalctl -f
Jun 12 20:10:11 koboldx-tuxedopulse15 eddie-ui[2650]: . 2026.06.12 20:10:11 - Collect information about AirVPN completed
It sounds like he can’t activate the kill switch. Have you made any changes to your firewall (iptables/nftables), and have you checked the lock mode in your app/config?
1 month ago in early May it was running fine, i didn’t change much around my system but there was 2 Manjaro Distro Updates since then and this mitigation stuff which i executed.
I also removed maybe 6 orphan pakages few days ago.
What you mean with checked? I clicked there again to connect to a VPN but that message popped up again:
There is no available or enabled Network Lock mode, sorry.
I also just try to run my VPN also on my PC (where this mitigations are still active) but there is also this Network Lock mode info showing up.
Hi @Kobold I’ve split these posts into a dedicated thread. Hopefully this will give better focus to the issue at hand. 
Thanks for cleaning, yeah its probably better to make a own topic, since its not so easy to solve as i thought first 
I also just disabled automatic Network Lock in the Eddie (AIR VPN) Application and also unchecked To Ensure Network has activated.
And with deactivated Network Lock, i could ATLEAST connect to my VPN again.
So the main issues is now the Network Lock, since the connection to the VPN is working again.
The Kill Switch (Network Lock Mode) is a set of firewall rules. There may be an outdated rule getting in the way, or there might be a general issue with your firewall—perhaps a permission problem.
Hmmm was there maybe some changes in the last 2 Distro Updates in May?
Im not even touched Firewalld for year’s.
I have no idea where to look, i never even touched IP Tables or something like that.
Have you tried eddie-ui-git (aka current beta) instead of eddie-ui?
Not yet, i use the stable client.
Update:
I just restored my settings which i used before and activated Network Lock.
But under Network Lock>Modes i switched from None to Linux IPTables-legacy and with that i could established a connection.
Even with Mitigation i have no problem to connect to VPN and do Network Lock now!
Problem looks solved, thanks everyone.
Since @pwx came closest to the solution because he pointed at ip tables, i marked his response.
Aha. We now know what is it. Please correct me if i got it wrong.
To sum up, iptables gets phased out. It now (since 1-2 updates) runs pretty much as a compatibility module for the newer nft firewall. In theory the apps still relying on iptables should work but i guess there will be glitches here and there. I only tested QEMU cause it had problems in this regard before and it worked but i guess your vpn program didn’t.