RTRMON v2.1.4

v2.1.4 - (November 28, 2024)

      - PATCH: Modified code to ignore ALL character key presses during the initial "Boot Sequence" loop.
      - PATCH: Modified code to ignore all INVALID character key presses within the main loop.
      - PATCH: Added code to avoid updating the timer prematurely within the initial & main loops due to
        repeatedly fast key presses.
      - PATCH: Modified code to avoid redisplaying the top "Options Menu" unnecessarily too often and
        resetting the timer 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 non-integer values to be displayed for percentages of the elapsed time.
      - PATCH: Modified the top "Operations Menu" section with the title for the "Setup Configuration Menu"
        to highlight "M" as the key press to launch the Setup Menu instead of the "S" key press which was
        in conflict with the "S" required to show the "Operations Menu" section.
      - PATCH: Fixed menu option to set "Timer Interval (seconds)" values because it was accepting any user
        input (e.g. "0", "X") with very little validation and there was no lower-bound & upper-bound value
        checking. For example, inputs like "0" && "X" were accepted leading to runtime errors being
        generated.
      - PATCH: Added a toggle switch to pause/resume the timer cycle within the main loop. Pressing the
        character 'X' key (upper-case X only) will toggle the timer to pause/resume. While in the paused
        state, all character key presses are ignored except for the toggle 'X' key to resume the timer.
      - PATCH: Various other coding improvements & fine-tuning.
      - HUGE thanks to @Martinski for helping improve RTRMON with all the above fixes!! :)

RTRMON v2.1.3

v2.1.3 - (October 19, 2024)

      - PATCH: Minor spacing issues fixed for screen #6 (wired/wireless clients page)
      - PATCH: Fixed some logic due to the $VPNSite2Site variable not being considered, though it is set
        in the config. Thanks to @Visortgw for his sleuthing and seeing what worked for him, and implemented
        these changes across the script as it pertains to site-to-site VPN configurations.
      - 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.

RTRMON v2.1.0

v2.1.0 - (October 12, 2024)

      - MINOR: Based on some samples that @RMerlin provided @JGrana when looking at connected WiFi client
        connected time, it seemed like a great idea to provide a view of which connected clients are
        currently attached to your router, and on what interface. This new view (page #7) shows the client
        name, IP, MAC, Uptime, TX/RX Totals (in GB), TX/RX Speeds (in Mbps) for each wireless interface, and
        also shows the name, IP and MAC for everything else connected to the LAN (br0). Still a bit
        experimental as I'm refining this, and would definitely appreciate your feedback!
      - PATCH: Some further debugging to eliminate dupes caused by shoddy coding, and will now just display 
        an "UNKNOWN" entry if a device shows up that is not defined using a custom name.
      - PATCH: Introduced the option to sort your connected client lists by Name, IP or MAC address! Columns
        will sort by alpha or numerical order... in the case of MAC, it seems to go alpha then numeric. Huge
        thanks to @visortgw for suggesting this feature!
      - PATCH: Some additional work was done on the connected clients to account for guest wi-fi clients per
        feedback by both @visortgw and @CaptainSTX. Thanks also to @ColinTaylor and @DJones for narrowing
        down what interface guest wi-fi clients reside on, and providing script samples of pulling legit
        guest wi-fi interface names. RTRMON will now display enabled guest wi-fi ranges along with their
        associated connections.
      - PATCH: Based on a suggestion from @DJones, the client signal strength value has been added to the
        column layout!
      - PATCH: After much back and forth with @visortgw, sleuthing through NVRAM, I have not been able to
        get past the VLAN brick wall, in order to show which devices are on which VLAN. So for the moment,
        until 3006 arrives for my router, I will need to put a pin in it, and will just combine LAN and VLAN
        devices under the same section.
      - PATCH: Added a blank IP for clients that come up as UNKNOWN to help with spacing.
      - PATCH: With many huge thanks to @ExtremeFiretop, he had some very productive time to help debug and
        develop some workarounds while testing it against his live GT-BE98U! He singlehandedly was able to 
        figure out the methodology needed to report which clients fell into which VLANs, along with other
        great code optimization, including falling back to pulling device names from dnsmasq when the
        custom client name entry is non-existent in NVRAM! THANK YOU!:)
      - PATCH: @ExtremeFiretop and @visortgw have been busy working together in the background and putting
        the final finishing touches on the network client listing screen! Thanks so much for your help and
        expertise and putting a nice bow on top! :)

RTRMON v2.0.17

v2.0.17 - (June 8, 2024)

      - PATCH: Fixed compatibility issues with the GT-AX11000_Pro. Apparently, I was searching for an
        incorrect model name... Thanks to @Kingp1n for noticing that his 2nd 5GHz band was not showing up.

RTRMON v2.0.16

v2.0.16 - (June 3, 2024)
- PATCH: Added some logic to the network connections/bandwidth test to try to exclude VPN connections
that come up with a private IP address in the vpn_clientX_addr NVRAM field. In the process, added
another option under the configuration menu (item #13) that asks whether or not the router is purely
being used in a VPN site-to-site configuration, as that would have a bearing on how the "public-
facing" IP ends up, and is most likely a private IP that will cause delays or no data during testing.

RTRMON v2.0.15

What's new! (Better question, what isn't new!)
v2.0.15 - (June 1, 2024)

• MAJOR: Brought RTRMON up to the new visual standards in use across VPNMON-R3, TAILMON and BACKUPMON. All screens have been resized for the more "wide-screen" look, allowing me to condense information, and make better use of screen space. This also includes an operations menu which you can show/hide in order to capitalize on even more screen space in much of the same way VPNMON-R3 functions. It just feels like a whole new script! ;)
• PATCH: In previous versions, only 2 VPN slots would be presented with relevant info. In today's version, up to 5 different VPN slots are displayed depending on which ones are in use.
• PATCH: In previous versions, you could only run a speedtest against your first VPN connection. In this release, you can indicate whether to run a speedtest against any of your up to 5 VPN slots.
• PATCH: Previously, when WiFi interfaces turn on or shut off, they would not be represented in RTRMON as doing such, and would require a restart of RTRMON to see the current WiFi state. Now, the WiFi interfaces reflect reality in realtime.
• PATCH: Prevously, the iftop network stats would only gather WAN, LAN and the first available VPN slot. Page 6 (network/bandwidth stats) now queries and displays all VPN connection info.
• PATCH: Added some additional information on page 1: Total Available RAM, and Total Swap File Size.
• PATCH: On the Network Diagnostics page, RTRMON is now showing a preview of the test command involved in determining if a function works or not. This gives more insight as to the command, IP or network address that the test is attempting to connect to.
• PATCH: Added a new item (12) under the Configuration menu that allows you to specify whether the router that RTRMON is running on is an iMesh Node, AP, Repeater or Bridge. In these operating modes, the eth0 interface is most likely not being used, and will no longer be reporting on or capturing any WAN0 traffic in the RTRMON UI.
• PATCH: Added a new item (13) under the Configuration menu that allows you to specify how large you want your log file to reach. The default is currently 2000 rows, which would give you many months of log data.
• PATCH: After getting some nvram feedback from @visortgw and @dave14305, I've made more modifications on how to determine if a router is truly a router, not an AP/Repeater/iMesh Node. This version is now compliant in supporting routers in these particular configurations.
• PATCH: Through testing with @visortgw, it was determined that the nslookup diag command does not work on iMesh nodes, and made a small modification to it so that it may hopefully pass this test.
• PATCH: Now proudly includes compatibility for the newly announced supported Asus-Merlin FW routers: the GT-BE98_PRO, RT-BE96U and GT-BE98. The BE98_PRO is the first router that makes use of two distinct 6GHz ranges requiring new capabilities from RTRMON! Huge thanks to @nzwayne for installing the Alpha on his GT-BE98_PRO and making sure RTRMON worked flawlessly on it! Also, many thanks to @GNUton for his help determining Wifi interface ranges on the GT-BE98!
• PATCH: Logging standards have been updated across the script, and open to suggestions for other log events that might be reported on.
• PATCH: Implemented the -now switch functionality, giving you the ability to bypass the 5 second SCREEN utility instructions and timer. This functionality works inconjunction with being able to specify which page (1-6) you want to jump to. Examples: "rtrmon -screen -now", "rtrmon -screen 2 -now". The second example would jump to page 2 using screen with no wait.
• PATCH: With many thanks to @nzwayne for allowing us some time to play with his GT-BE98_Pro, and making sure RTRMON is fully compatible with the new dual 6GHz bands, we have worked through all issues! Wanted to say how much I truly appreciate SNB Forum members like @nzwayne for jumping in, being willing to sacrifice his router and load the latest Merlin FW Alpha version on there to ensure compatibility. You rock!
• PATCH: After some debug/testing with @visorgtw, it was determined that a change to the ping command needed to be reverted due to site-to-site VPNs not returning pings as expected. Huge thanks for his great help testing this on his various pieces of router and iMesh-configured equipment!

RTRMON v1.6.9

v1.6.9 - (May 3, 2024)

      - PATCH: After @bubba123 reported some display issues with his SDA devices, it was determined that the large
        size of his drive was creating some sort of math/integer problem, and was causing the division problem to
        equal zero, eventhough it should have amounted to 5544GB. I changed the way that RTRMON calculates these
        large drive space numbers using the awk tool, and implemented a fix.  Thanks for the heads-up @bubba123!

RTRMON v1.6.8

v1.6.8 - (March 17, 2024)

      - PATCH: After some back and forth on how to best handle the CPU temp range and colors, I'm going to settle on
        agreeing that the upper max range for the graph will be 100C. It's at this temperature that your router starts
        shutting down CPU cores to prevent damage, though it could probably get to 120C before it actually starts
        physically causing damage. I think if you're getting close to 100C, you should be getting concerned. So the
        bar chart will show green up to 80C, yellow from 80C-90C, and red from 90C-100C+. Thanks much to @Tech9,
        @L&LD and @visortgw for their valuable feedback on this!

RTRMON v1.6.7

v1.6.7 - (March 16, 2024)

      - PATCH: Based on some great feedback from @adzie and @ExtremeFiretop, I've added stats for your attached USB
        storage. All /dev/sd* devices will now show up under the "Disk" section on page 1, showing % used and GB used.
      - PATCH: Thanks to the keen eye of @Tech9, the "mem used" counter being displayed on page 1 was displaying the
        color scheme wrong... (ie. low memory was marked green, but in this case, should be red). Fixed and reversed!
      - PATCH: Also thanks to @Tech9 for his feedback on this, the MAX range for all CPU temps has been dropped from
        130C down to 100C, 212F and 373K, as noted that the router will start shutting down CPUs when it hits 100C to
        protect itself.

RTRMON v1.6.2

v1.6.2 - (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: Updated the NC statement that runs the SSL Handshake test under the Diagnostics menu. For some reason,
        something changed on possibly Google's end, yielding a failure each time. Now utilizing the same modified SSL
        Handshake statement carried over from VPNMON-R3 which is coming back successful. Thanks to @Makaveli for the
        heads-up!
      - MINOR: Added new functionality that allows you to start on a specific page. A very old request from @Stephen
        Harrington! Thank you! :) You can make use of this functionality by specifying a page number (1-6) after you
        execute RTRMON using the -monitor or -screen function switch. (Example: rtrmon -monitor 2) This would execute
        RTRMON, and will start on the 2nd page (network bandwidth/usage stats). Enjoy!