VPNMON-R3 v1.3.7

v1.3.7 - (October 20, 2024)

     - PATCH: Modified code to handle scenarios where getting the "city exit" value returns an empty/NULL string.
     - PATCH: Modified code to ignore invalid key presses within the main loop.
     - PATCH: Added code to prevent updating the timer prematurely within the main loop due to repeatedly fast
       key presses.
     - PATCH: Modified code to get elapsed time percentage values with 1 decimal place (e.g. 0.5%). This allows
       displaying non-integer values for percentages of the elapsed time.
     - More minor coding improvements & fine-tuning.
     - PATCH: Fixed the Y/N prompts so they now require you to hit <enter> after typing either y or n. This
       changes its behavior from automatically moving on and possibly causing issues from people also using the
       enter key accidentally.

VPNMON-R3 v1.3.6

v1.3.6 - (October 12, 2024)

     - PATCH: After selecting menu option 1 ("Number of VPN Client Slots available"), if the user simply pressed
       the <Enter> key without entering any new value, the currently selected value was reset to "1 2 3 4 5"
       regardless of the current setting.
     - PATCH: After selecting menu option 2 ("Custom PING host to determine VPN health"), if the user simply
       pressed the <Enter> key without entering any new value, the currently selected value was set to empty/NULL
       regardless of the current setting.
     - PATCH: When selecting menu option 2 ("Custom PING host to determine VPN health"), any user input was
       accepted for the IP address because there was no IPv4 address format validation.
     - PATCH: After selecting menu option 3 ("Custom Event Log size (rows)"), if the user simply pressed the
       <Enter> key without entering any new value, the currently selected value was reset to "2000" regardless of
       the current setting. In addition, the error message "[: 0: unknown operand" was generated.
     - PATCH: After selecting menu option 5 ("Refresh Custom Server Lists on -RESET Switch"), if the user simply
       pressed the <Enter> key without entering any new value, the currently selected value was reset to
       "Enabled" regardless of the current setting. In addition, the error message "[: 0: unknown operand" was
       generated.
     - PATCH: After selecting menu option 6 ("Provide additional WAN/Dual WAN monitoring"), if the user simply
       pressed the <Enter> key without entering any new value, the currently selected value was reset to
       "Enabled" regardless of the current setting. In addition, the error message "[: 0: unknown operand" was
       generated.
     - PATCH: After selecting menu option 7 ("Whitelist VPN Server IP Lists in Skynet"), if the user simply
       pressed the <Enter> key without entering any new value, the currently selected value was reset to
       "Disabled" regardless of the current setting. In addition, the error message "[: 0: unknown operand" was
       generated.
     - PATCH: Added user input validation for Cron Job hours & minutes
     - PATCH: Adjusted display format of the number of servers to avoid left-padding with zeros while still
       maintaining table alignment.
     - PATCH: Adjusted display format of ping values to avoid left-padding with zeros while still maintaining
       table alignment.
     - PATCH: Adjusted display format of IPv4 addresses to avoid left-padding with zeros while still maintaining
       table alignment.
     - PATCH: Various other coding improvements & fine-tuning.

VPNMON-R3 v1.3.5

v1.3.5 - (May 11, 2024)

     - PATCH: Small bugfix after looking into issues with the vr3timers.txt file. Seems that there was a variable
       and a function both named the same thing, which could cause an issue down the road, and made sure these
       were formally separated into their own entities from this point forward.
     - PATCH: When the script has detected an issue with the WAN, and falls back into its waiting loop, I seem to
       have mistakenly put in an email notification during this time. I thought it was helpful. Guess not, 
       because it doesn't work when the internet is down, and just throws errors, so I've removed this particular
       email notification. ;)

VPNMON-R3 v1.3.1

v1.3.1 - (March 16, 2024)

     - MINOR: AMTM Email Notification capabilities have been added thanks to @Martinski's shared email functions
       library that he has made available. Once AMTM email (AMTM->em) has been configured, you can activate this
       feature in VPNMON-R3. You have the ability to distinguish between receiving either success, failures or 
       both types of emails as it pertains to your WAN/VPN connectivity. An operations menu item has also been
       added to quickly enable/disable this feature when needed.
     - PATCH: Minor logic correction to a function that determined max server ping would every so often run
       into issues with the info it got back from the ping command, and would display invalid operand errors.

VPNMON-R3 v1.2.3

v1.2.3 - (March 8, 2024)

     - PATCH: Change to the logic for switching back and forth between the number of available slots. Will now
       recreate the vr3timers.txt and vr3clients.txt, as they were not being refreshed when different selections
       were being made. General fixes and optimizations made as being found and identified.
     - PATCH: Added verbiage in the Unbound integration configuration menu item to give a visual warning that
       as of Mar 1 2024, the NordVPN service no longer works with the Unbound integration due to some apparent
       blocking on their end. Hopefully at some point in the future, we can remove this and carry on with Nord.

VPNMON-R3 v1.2.1

What's new?

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.

VPNMON-R3 v1.1.5

What's new?

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 figured it was probably time for me as well. All my scripts moving forward will go this route. Change log wording is now changed to conform to the major/minor/patch standards. So previously, FIXED now conforms to PATCH, ADDED conforms to MINOR, and MAJOR stays the same!
• PATCH: Found a situation where if someone was still using older VPN Slot allocations (like "1 2 3") and didn't update to the newer "1 2" or "1 2 3 4 5" slot allocations, then it would prevent the operations menu from showing, since it is geared towards either one of these two options. VPNMON now has some logic added that will force a "1 2 3" configuration to "1 2", and will require you to select which slots need to be monitored. Thanks to @TITAN for finding this one and working with me on the diagnosis! :)
• PATCH: Minor spacing and verbiage changes to make the experience more consistent.