Recent content by greenspanner

Just a side note on CG-NAT, I encountered this issue myself and only picked it up when I noticed that my DDNS IP was different from my WAN IP even though it refreshed and registered successfully and I could ping it. I had changed ISPs and din't realise that they enabled it by default. Turned it...

This worked perfectly! Every interface can be curled out, even ppp0. I had to make some wg-up scripts for the setting to survive a reboot as per your IPSET guide. Now my wireguard is fully set up and everything seems super stable compared to my previously patchy OpenVPN setup. Thank you!

Here is what I get when I curl out my WAN interface with all my wg clients in policy mode: curl -v ipecho.net/plain --interface ppp0 * Trying 34.160.111.145:80... * Connected to ipecho.net (34.160.111.145) port 80 (#0) > GET /plain HTTP/1.1 > Host: ipecho.net > User-Agent: curl/7.79.1 >...

That did the job perfectly, thanks so much @ZebMcKayhan Any clues on how to curl out via different interfaces from the router?

Thanks for your suggestion. I tried this rule peer wg13 rule add wan 10.50.1.1/24 comment wg21toTransmission And still 192.168.1.111:9091 isn't accessible from a wg21 connection. Trying something randomly to eliminate wg11 passthru as an issue, I added peer wg11 rule add wan 10.50.1.1/24...

Hi, I've successfully moved all my OpenVPNs over to Wireguard and I am very impressed with the speed and the session manager script. After solving a few things myself, I have a couple of issues that I'm hoping are quite straightforward but beyond my skills. Firstly, with ovpn, on the router...