I used the information above to fill in the SETUP-TUNNELS page (see attachment).
After, I copy/paste the scripts in the ADMINSTRATION-COMMANDS page (see attachment).
Because, this didn't work, I tried also the IVPN one.
Remarkable between 'your' and 'IVPN' instructions are, that they use the DNS-address. In the configuration file DNS is set to 1.1.1.1, but you instructed not to use it.
I do not get an internet connection to or from TUNSAFE. In fact, I do not know what the cause is
I can follow instructions, but I am not a specialist in solving this issue. Can someone help me?
Joined: 22 Mar 2019 Posts: 27 Location: Gamma Quadrant
Posted: Fri Apr 03, 2020 7:45 Post subject:
As egc suggested, try his Wireguard script provided in his client setup guide. I'm currently working on a better version of the script provided in my guide, however I haven't had a lot of time to test it out because my husband has been working from home due to the *current* state of the world right now.
I'm not personally familiar with TunSafe as a VPN service, however it is not necessary to include the output of the configuration file in the script itself. The config file is meant to give you the info to plug into the boxes within the DD-WRT "Tunnels" tab when Wireguard is selected as the protocol.
Joined: 18 Mar 2014 Posts: 12885 Location: Netherlands
Posted: Fri Apr 03, 2020 8:27 Post subject:
I am currently working on an update for the WireGuard GUI in DDWRT to add buttons to route the allowed IP's and a button to NAT out via the tunnel in this way you do not need any script.
Will be ready next week, but it is up to the main developer if and when it will be implemented.
Joined: 22 Mar 2019 Posts: 27 Location: Gamma Quadrant
Posted: Fri Apr 03, 2020 8:39 Post subject:
Ayyy, this is what I like to hear! I just recently looked up the change logs for newer releases of DD-WRT builds and didn't see anything mentioned for Wireguard's GUI that would fix the need for a corrective script. It's been a year now since I made this guide so I haven't bothered upgrading my build unless it would improve Wireguard's support.
Joined: 10 Jul 2012 Posts: 28 Location: Sint Maarten, D.W.I
Posted: Sat Apr 04, 2020 12:17 Post subject:
egc wrote:
I am currently working on an update for the WireGuard GUI in DDWRT to add buttons to route the allowed IP's and a button to NAT out via the tunnel in this way you do not need any script.
Will be ready next week, but it is up to the main developer if and when it will be implemented.
I have it running on my routers and it works very good
Thank you for working on the addition. If you like somebody to test and to make it dummy-proof, I look forward to help you with that.
I followed your instructions, unfortunately it didn't work for me, yet. _________________ Netgear R6700v3 (from MAR2020) - Firmware: DD-WRT v3.0-r42819 std (03/30/20)
AzireVPN dont have an option to submit the Local Public Key before generate the file xxxx.conf
And in the gui of the ddwrt dont let-me change the Local Public Key to my own.
So there is any way to work with ddwrt changing the Local Public Key in the ddwrt?
But ddwrt have is own public key, so i think this is a problem i already check other manuals like strongvpn they have in the website a field to introduce the ddwrt public key before generate the file.
But ddwrt have is own public key, so i think this is a problem i already check other manuals like strongvpn they have in the website a field to introduce the ddwrt public key before generate the file.
if I understand you correctly they give you a private key to use.
I just recently looked up the change logs for newer releases of DD-WRT builds and didn't see anything mentioned for Wireguard's GUI that would fix the need for a corrective script. It's been a year now since I made this guide so I haven't bothered upgrading my build unless it would improve Wireguard's support.