visortgw
Very Senior Member
... but not until after your CISSP certification.Not yet, but that is definitely on my to-do list...
Hey - thanks so much for your "coffee" donation! I truly appreciate it!![]()
... but not until after your CISSP certification.Not yet, but that is definitely on my to-do list...
Hey - thanks so much for your "coffee" donation! I truly appreciate it!![]()
U know it!... but not until after your CISSP certification.
You're welcome and I am looking forward to it!Not yet, but that is definitely on my to-do list...
Hey - thanks so much for your "coffee" donation! I truly appreciate it!![]()
well, if u think a US or German/EU based VPN provider is a good idea... enjoy. I prefer services outside EU and US dependence.What's a real VPN to you?
If you are this level of paranoid, then perhaps running your own managed VPN server in your own cloud instance is the way to go.well, if u think a US or German/EU based VPN provider is a good idea... enjoy. I prefer services outside EU and US dependence.
Proton might be one of those. But now as CH is turning to EU, this is no longer an option.
did already few years ago while in China, it is not possible any more. The great firewall will detect it after a few days or now even minutes. no chance.If you are this level of paranoid, then perhaps running your own managed VPN server in your own cloud instance is the way to go.
curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R2/master/vpnmon-r2-2.63.sh" -o "/jffs/scripts/vpnmon-r2.sh" && chmod a+rx "/jffs/scripts/vpnmon-r2.sh"
did already few years ago while in China, it is not possible any more. The great firewall will detect it after a few days or now even minutes. no chance.
R3 simply is more powerful and gives you more fine-tuning control, and uses the *same* exact randomization function as in R2.Last working and stable version of VPNMON R2 is version 2.63 - do not use or update to 2.64 or 2.65 as they are simply not working and just force u to use VPNMON R3 which is complicated and doesn’t have the same good random function. (or I didn’t understand it)
Happy to hear its still working OK for you... Just so you know, I will be cleaning up this old repository in the near future, but will keep a copy of the last release in an archive folder under R3. I'll document this when the time comes.might be useful for others, thanks for writing it![]()
the future will go not only to multi hop vpn but a camouflaged multi entrance and exit hop vpns. there are already a few promising technologies. however, not very user friendly yet.How about Starlink?Nevermind... it doesn't work in China. Randomized multi-hop-multi-VPN-provider tunneling I guess is the way to go.
thanks! would be great to have this simple version still available. If it is although in R3, maybe u can think about an Idea of a simple second menu similar to R2, like 2 user interface for 1 engine. (Maybe I m juts to stupid to use it, or to tired when I try at night shift. ...) thanks anywayR3 simply is more powerful and gives you more fine-tuning control, and uses the *same* exact randomization function as in R2.
Happy to hear its still working OK for you... Just so you know, I will be cleaning up this old repository in the near future, but will keep a copy of the last release in an archive folder under R3. I'll document this when the time comes.
What do you mean with "2 user interface for 1 engine" and "a simple second menu similar to R2"? If you can describe a bit more what you're looking for (or screenshots/mockups), perhaps that will spark an idea to help make R3 even simpler to use? I still really don't understand what's holding you back from it's use. R3 is pretty much set-and-forget.thanks! would be great to have this simple version still available. If it is although in R3, maybe u can think about an Idea of a simple second menu similar to R2, like 2 user interface for 1 engine. (Maybe I m juts to stupid to use it, or to tired when I try at night shift. ...) thanks anyway
I agree, it is complicated to a new user. But persevere, it's a lot more powerful than the old R2 - it's worth it. I was hesitant at first, all these new options can be daunting until you've played with it a while. Not something you can pick up in just a few minutes.force u to use VPNMON R3 which is complicated
#Restart WAN connection to get new IP
if [ "$restartwanonreset" -ne 0 ]; then
printf "${CGreen}\r[Restarting WAN]"
service "restart_wan_if 0" >/dev/null 2>&1
sleep 20
printf "\33[2K\r"
fi
service "restart_wan_if 0" >/dev/null 2>&1
That's pretty strange behavior... If it's stuck on connecting, it's either got to be a router problem, or a VPN Provider problem? Not seeing this happen locally, nor have we seen anyone else comment on this as a known issue... which means the issue might be on your end?Hello @Viktor Jaep I'm facing a problem with VPNMON where the vpn connection stays stuck on connecting usually happens once or twice a week.
Resetting the WAN connection is a pretty big deal. Even if you're dealing with DHCP, your router should be renewing that lease without issue and needing to force a disconnect. I can go months between actual reboots, and I'm getting new leases on a regular basis without interruption. So I'm a bit on the fence. If we see an outcry for this particular feature, I'd be happy to add it?Would you like to add it to your script officially?
I'm using ProtonVPN OpenVPN over TCP 443. The issue probably could be from the ISP or Proton detecting and blocking the connection, since getting getting a new wan ip allows the connection to be established again. It could also be that ProtonVPN servers require reauthentication and the issue is acctually caused by the WAN DHCP when renewing a lease. This is actually can be solved by monitoring wan ip changes and resetting the vpn connection when a change happens.That's pretty strange behavior... If it's stuck on connecting, it's either got to be a router problem, or a VPN Provider problem? Not seeing this happen locally, nor have we seen anyone else comment on this as a known issue... which means the issue might be on your end?
Resetting the WAN connection is a pretty big deal. Even if you're dealing with DHCP, your router should be renewing that lease without issue and needing to force a disconnect. I can go months between actual reboots, and I'm getting new leases on a regular basis without interruption. So I'm a bit on the fence. If we see an outcry for this particular feature, I'd be happy to add it?
Thoughts?
I'm new to using ProtonVPN as well for these last few weeks... have not had any issues with a locked "connecting" issue. Yes, please keep an eye on it for other kinds of behavior. Typical cable modem providers will renew their DHCP leases every 2-4hrs. So depending on how many times a day you reset your VPN connection, it could have renewed your IP like 6-12 times.I'm using ProtonVPN OpenVPN over TCP 443. The issue probably could be from the ISP or Proton detecting and blocking the connection, since getting getting a new wan ip allows the connection to be established again. It could also be that ProtonVPN servers require reauthentication and the issue is acctually caused by the WAN DHCP when renewing a lease. This is actually can be solved by monitoring wan ip changes and resetting the vpn connection when a change happens.
What I did with the script to solve the issue I'm facing is force a WAN IP change by disconnecting and reconnecting the WAN connection and thus establishing a new connection to the VPN with the new WAN IP.
I'm not sure exactly why the VPN connection gets stuck on connecting I will keep "Provide WAN/Dual WAN Monitoring Functionality" set to Enabled and do further testing. Resetting the WAN connection might not be necessary.
Assign an IP address to the Firestick via the LAN DCHP screen/page (use whatever IP it was already assigned), then using the VPN director functionality, direct that device to use whichever VPN tunnel you would like. You can even, via the VPN Director, turn on/off the use of the tunnel by the Firestick device on an as needed basis (though you'll have to login to the router to manage....So my question is not directly related to VPNMGR but more general VPN but assumed this is the best crew to ask. I have VPN and VPNMGR all setup with 2 slots to use NordVPN in 2 locations. I plan on using the VPN exclusively to get around GEO restrictions in ESPN+ to watch hockey. How can I make it so the VPN only impacts the IP address/host-name for my Firestick?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!