Quote from: grb on February 22, 2026, 08:40:13 PMRight, thanks for screenshot, that will help a lot.You are welcome!
QuoteI was trying to replicate those 3 rules, in Destination NAT. Having in mind that, they exists for a reason.IMHO there is no reason to create those since I am using the above for something like 6 to 8 months now without any issue !!
I understand that I could block myself If I will forward 443 or 80 then I could block myself.
This is what I'm struggling with to recreate.
Quote from: Patrick M. Hausen on Today at 12:46:15 PMThe funny thing is that at least in the EU your ISP is way more trustworthy than any so called "VPN provider". With a commercial "VPN" you hand all your communication metadata to a single entity, frequently a company located not in the EU. While your ISP is bound by GDPR and strong consumer protection laws and all hell will break loose should they ever get caught sniffing.Actually there is no right choice there :
Quote from: Monviech (Cedrik) on Today at 10:52:13 AMIt's always better to bind to the ANY interface since the service will always reliably start.Actually I have done some research about that lately and it seems for example that both the webGUI and SSH also bind to the Localhost and Link-Local IP Adresses when you (in my case) just select the LAN Interface as the interface to bind to ?!
Quote from: ftani on February 22, 2026, 10:33:10 PMSorry for being a little bit off topic here, but in the original post it was said "Internal AmneziaWG service hosted in the LAN.", can you share some details about how did you implemented it? I'm very interested in having AmneziaWG running on my network.So, I've got my OPNsense running as a VM on Proxmox (PVE). Alongside it, I spun up an Alpine LXC container right on PVE and compiled `amneziawg-go` and `amneziawg-tools` inside it. Boom—instant AmneziaWG server/client setup!