Merge pull request #4 from ViktorJp/develop

Pull v1.2.1

README.md

@@ -1,7 +1,7 @@
-## VPNMON-R3 v1.1.5
+## VPNMON-R3 v1.2.1
 Asus-Merlin VPN Monitor R3
-![image](https://github.com/ViktorJp/VPNMON-R3/assets/97465574/4764e2bd-0f1c-4e00-8c2a-54ed70f254b7)
+![image](https://github.com/ViktorJp/VPNMON-R3/assets/97465574/b7323648-5acc-4a8c-b96f-d9c7a9163d9e)
 
-**EXECUTIVE SUMMARY:** VPNMON-R3 (VPNMON-R3.SH) is an all-in-one script that is optimized to maintain multiple VPN connections and is able to provide for the capabilities to randomly reconnect using a specified server list containing the servers of your choice. Special care has been taken to ensure that only the VPN connections you want to have monitored are tended to. This script will check the health of up to 5 VPN connections on a regular interval to see if monitored VPN connections are connected, and sends a ping to a host of your choice through each active connection. If it finds that a connection has been lost, it will execute a series of commands that will kill that single VPN client, and randomly picks one of your specified servers to reconnect to for each VPN client. It also monitors your WAN/Dual-WAN connection and drops back until your WAN connection comes back up to reconnect your VPN tunnels.
+**EXECUTIVE SUMMARY:** VPNMON-R3 (vpnmon-r3.sh) is an all-in-one script that is optimized to maintain multiple VPN connections and is able to provide for the capabilities to randomly reconnect using a specified server list containing the servers of your choice. Special care has been taken to ensure that only the VPN connections you want to have monitored are tended to. This script will check the health of up to 5 VPN connections on a regular interval to see if monitored VPN connections are connected, and sends a ping to a host of your choice through each active connection. If it finds that a connection has been lost, it will execute a series of commands that will kill that single VPN client, and randomly picks one of your specified servers to reconnect to for each VPN client. It also monitors your WAN/Dual-WAN connection and drops back until your WAN connection comes back up to reconnect your VPN tunnels.
 
 **FINAL RELEASE NOTES:** Throughout the development of VPNMON-R2, I had many requests from those who were running multiple VPN connections. R2 was designed to support a single VPN connection, and would have been tough to integrate the ability to manage multiple VPN connections within it. I decided it was just better to start from the ground up with R3. Also, I wanted R3 to be a more open platform, that gives you the freedom and ability to use whatever VPN provider you want, without being tied to certain BIG-NAME VPN providers out there. Ultimately, R3 just needs a single column list of VPN Server IPs that it can randomly choose from should a connection need to be reset. And if you don't have a list? That's fine too... and it will just try to reconnect with whatever server you currently have configured in your VPN Slot. Having created a completely different thread that covers examples how you can pull the necessary VPN Server IP data from various sources, this should give you enough to go on to support your own efforts! I brought a couple of features over from R2, the biggest one being the integration with Unbound. In this day and age of privacy, I believe this is a must-have feature which allows your DNS queries to remain private from your ISP or other monitoring agencies. All in all, R3 is a slimmed down, more efficient and more open version of R2. I hope it serves your purposes well! :)

changelog.txt

@@ -1,3 +1,14 @@
+v1.2.1   - (February 23, 2024)
+         - MINOR: Added a new configuration menu item that allows you to enable/disable the ability to import your
+           VPN Server IP lists directly into the Skynet Firewall for whitelisting purposes. This is another feature
+           coming over from VPNMON-R2, as there have been instances in the past where the Skynet blacklist would
+           prevent a connection to a perfectly legitimate VPN Server that belongs to your VPN provider. This
+           function will fire off each time you execute a VPN Server List automation under option (U), and will
+           also run each time a "vpnmon-r3 -reset" command is executed. Please note: Skynet must already have been
+           installed (using AMTM) and working/functional.
+         - PATCH: The update logic now pulls the vpnmon-r3.sh directly from github starting from versions after
+           1.2.1, instead of the vpnmon-r3-X.Y.Z.sh file based on the version number from the version.txt file.
+
 v1.1.5   - (February 7, 2024)
          - PATCH: Changed the versioning logic to align with the general accepted way of versioning, using the
            notation: major.minor.patch ... finally, right? After seeing @thelonelycoder changing his ways, I

version.txt

@@ -1 +1 @@
-1.1.5
+1.2.1