Happy to announce the next version of
VPNMON-R3 v1.6.0! Super happy to offer
"Unbound over Wireguard" in many thanks to
@ZebMcKayhan for his awesome guidance and incredible expertise on the subject! I truly appreciate your contributions to this! Also, huge thanks to all of you beta testers! Wouldn't have gotten this far without you - thank you
@CaptainSTX ,
@fourty6and2 ,
@iTyPsIDg ,
@Stephen Harrington, and
@ZebMcKayhan (and anyone else I may have forgotten)!
What's new!
v1.6.0 - (August 21, 2025)
- MINOR: Very happy to announce that
"Unbound-over-Wireguard" has actually become a reality! With huge help and guidance from
@ZebMcKayhan, a methodology was developed that is easier, simpler and much more elegant than it's Unbound-over-VPN twin. In essence, VPNMON-R3 creates a new virtual br0 interface, ties that to the WG client of your choice, and assigns that virtual br0 IP as the designated outgoing interface. Should the Wireguard client happen to go down or stop, Unbound will continue to resolve DNS directly over the WAN.
- PATCH: Based on a recommendation from
@JGrana, the RL
(Email Rate Limiting) indicators will no longer show up on the main UI (or in the config display) when AMTM email functionality is turned off.
- PATCH: Thanks to the keen eye of
@ZebMcKayhan,
important failsafe's for Unbound were not yet being addressed. This version adds those failsafes. If you're coming from Beta 1, please make sure you (1) update your script to Beta 2, (2) Disable Unbound over WG, (3) Re-enable Unbound over WG. This process will then write the appropriate commands to your init-start and nat-start files.
- PATCH: Implemented
Recovery Timeout Opportunities, they're kind of like second chances to allow your connection to recover before issuing a restart. By default, connections will restart after your timer loop finishes (default: 60 sec). The Recovery Timeout would extend the number of loops before it would issue a reset, and hopefully within that time, would recover the connection on its own. For example, your timer loop = 60 seconds. Your Recovery Timeout is set to 3x. This would mean if your connection doesn't recover in 3 minutes, then it will issue a reset. This option might help bring down the amount of times your connection resets throughout the day, but then there's also a greater chance your connection might become unusable for a slightly longer amount of time. This was inspired by
@CaptainSTX! Thank you!
- PATCH: Added the
router uptime value under the WAN monitoring section, some visual enhancements to the main UI, and providing content values in the logs when you get "invalid ping response received" messages, showing exactly what it was coming back with.
- PATCH: Added
compatibility for AirVPN WG, which not only requires a Public Key, a Private Key, but also a Preshared Key. A 6th field is now an optional requirement for AirVPN or vpn providers like them who require this field. Both the Update/Maintain WG server lists and Run Server List Automation screens have updated language, while code in charge of resetting the WG connection will insert this Preshared Key into the appropriate NVRAM value for the WGC slot.
Download link (or update directly through AMTM/VPNMON-R3):
Code:
curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R3/main/vpnmon-r3.sh" -o "/jffs/scripts/vpnmon-r3.sh" && chmod 755 "/jffs/scripts/vpnmon-r3.sh"
Significant Screenshots:
Too many changes to mention... but here's a few newly added:
(1) Email Rate Limiting, (2) Recovery Timeout Opportunities and
(3) Unbound over Wireguard! If you have questions about usage or anything, please don't hesitate to drop a note below and I (or the rest of this great community) will help out the best we can.
