vpnmgr vpnmgr - Manage and update VPN Client configurations for NordVPN and PIA

[JR Godwin]

I'll have to double check but block would make sense as a default. Can you let me know why you need to allow inbound connections on your VPN client?

Also, maybe the feature set should be to keep all of the other options that are currently set for the vpn client with the only change that vpnmgr is doing when resetting is finding the next best server. I can totally understand if you're first setting up the vpn client via vpnmgr, but once tweaks are made via the client page.....should keep them?

 

[HappyJuicy]

Windscribe

 

[Rafael Viana]

I would like to know if you can configure protonvpn in this script

 

[octopus]

ovpn.com

 

[Charlesk]

I would like to know if you can configure protonvpn in this script

I would also like to know if this can be configured to work with protonvpn.

 

[Jack Yaz]

I would also like to know if this can be configured to work with protonvpn.

I would like to know if you can configure protonvpn in this script

ProtonVPN isn't supported currently

 

[Charlesk]

ProtonVPN isn't supported currently

Are there any plans to add support for ProtonVPN?

 

[JT Strickland]

There are too many vpn providers to meet the requirements for each one.
Fantastic Jack probably put much juju in the script to have two.
I would have liked to see surfshark, my current vpn provider in there, but it ain't gonna happen.
I may switch to Nord or PIA when my 'script runs out.

 

[Wishmaster1965]

Has anyone else noticed that amtm u does not work when connected ?

 

[Galaxysurfer]

How will this interact with new VPN Director?

 

[Jack Yaz]

How will this interact with new VPN Director?

Beta - VPN Director testing

The setting "Accept DNS Configuration" in VPN Client tab doesn't seem to work anymore. If I choose "Exclusive" there, the DNS requests are not routed to my VPN:s DNS server through the encrypted channel. Furthermore, if I choose "Disabled", then nothing is routed through the VPN! In VPN...

www.snbforums.com

and

Beta - VPN Director testing

The setting "Accept DNS Configuration" in VPN Client tab doesn't seem to work anymore. If I choose "Exclusive" there, the DNS requests are not routed to my VPN:s DNS server through the encrypted channel. Furthermore, if I choose "Disabled", then nothing is routed through the VPN! In VPN...

www.snbforums.com

 

[TonyK132]

I previous ran the install line, and got vpnmgr to show up as a tab in the VPN GUI. But then sometime later, I rebooted the router, and the tab disappeared although I can run vpnmgr from the CLI. Now I just redid the install script but the tab still refuses to display. Is there something I can do to get that tab back?

 

[Jack Yaz]

I previous ran the install line, and got vpnmgr to show up as a tab in the VPN GUI. But then sometime later, I rebooted the router, and the tab disappeared although I can run vpnmgr from the CLI. Now I just redid the install script but the tab still refuses to display. Is there something I can do to get that tab back?

you're not still on 384.19_0 are you? i don't think that will contribute but that version is getting on a bit
try

vpnmgr startup force

 

[TonyK132]

That worked, thanks. Is that something I should do after a reboot? Also, can I tell from a script if the tab will be visible in the GUI?

Yes to 384.19. I know I'll need to transition to 386 at some point, but 384.19 is mostly solid for me, and 386 still looks like it has not settled down yet.

 

[Jack Yaz]

That worked, thanks. Is that something I should do after a reboot? Also, can I tell from a script if the tab will be visible in the GUI?

Yes to 384.19. I know I'll need to transition to 386 at some point, but 384.19 is mostly solid for me, and 386 still looks like it has not settled down yet.

Personally I don't think it's wise running a firmware with a vulnerable dnsmasq

386.1 (30-Jan-2021)
UPDATED: dnsmasq to 2.84, resolving CVE-2020-25681,
             CVE-2020-25682, CVE-2020-25683, CVE-2020-25687,
             CVE-2020-25684, CVE-2020-25685 and
             CVE-2020-25686 aka DNSpooq

 

[chongnt]

That worked, thanks. Is that something I should do after a reboot? Also, can I tell from a script if the tab will be visible in the GUI?

Yes to 384.19. I know I'll need to transition to 386 at some point, but 384.19 is mostly solid for me, and 386 still looks like it has not settled down yet.

I get this from one of the thread to check addons tab name. Not sure if this is helpful but I do agree with @Jack Yaz on upgrade to 386. You may notice some temperature hike but nothing much to worry about. It has been stable for me.

ls -lah /tmp/var/wwwext | grep -TE "user[1-9]+.*";grep -TH . /tmp/var/wwwext/*.title;grep -THE "user[1-9]\." /tmp/menuTree.js

 

[TonyK132]

Thanks, that code is useful.

Personally I don't think it's wise running a firmware with a vulnerable dnsmasq

Right, looks like I better get going and make the transition.

I get this from one of the thread to check addons tab name. Not sure if this is helpful but I do agree with @Jack Yaz on upgrade to 386. You may notice some temperature hike but nothing much to worry about. It has been stable for me.

ls -lah /tmp/var/wwwext | grep -TE "user[1-9]+.*";grep -TH . /tmp/var/wwwext/*.title;grep -THE "user[1-9]\." /tmp/menuTree.js

Thanks, this does look useful.

 

[TonyK132]

Right, looks like I better get going and make the transition.

About this. I'm running unbound in addition to dnsmasq. For this config, are the dnsmasq vulnerabilities an issue? I thought that for a dns query, dnsmasq resolves from its cache, but if not there, it goes to unbound, and that dnsmasq does not go out to the big, internet itself. If that is right, then it's unbound's job to protect against the baddies not dnsmasq. Have I got that right? I'm using the default config files for unbound and dnsmasq.

 

[abracadabra11]

Running into issues with VPN Client 1 (managed by vpnmgr) since updating to 386.3.

Unable to connect to VPN Server and the following error is listed on the VPN Client Tab:

Error - check configuration!

Reviewing the log, I see the following:

Jul 26 09:19:44 ovpn-client1[26824]: Options error: In config.ovpn:52: Maximum option line length (256) exceeded, line starts with mssfix

Any tips on troubleshooting? I tried uninstalling and reinstalling vpnmgr and issue persists.

 

[L&LD]

Reduce your line length in the options with the line that starts with mssfix. (I would remove to test first).