Thank you for confirming. Your policy based VPN is controlling your client DNS requests, meaning RouterPilot can’t see any client information as it’s getting the details from Adguard DNS control. I’m not sure a VPN would give up the client information, it should, but I’ll dive a little deeper to find out. In theory, the router should have client information prior to any DNS or access control. I’ll check it out and see what I can come up with. I really appreciate your feedback, it’s certainly helped.
1 Like
I’m pleased to announce that RouterPilot v2.2.0 RC1 is available for testing. This release candidate focuses on improved device identification using router, DHCP and mDNS information. I also need VPN + AdGuard Home testers, see GitHub pre release notes for more information. I’m particularly interested in those with AdGuard running alongside a VPN policy, but not using AdGuard for DNS request handling. I’ve also included read-only Tailscale implementation and router temp in overview as requested by @Lastimosa - A number of small cosmetic updates, client controls and bug fixes have been shipped with this RC. Thank you for testing, it is greatly appreciated.
Got a little hasty - RouterPilot v2.2.0 RC2 is now released - Only updated the changelog, release information and release history references. It’s late, I’m tired….that’s my excuse. Thanks for testing.
Ready for testing - RouterPilot v2.2.0
Thankyou
RouterPilot v2.3.0 — Development Preview
Just a quick look at some of the work going into the next RouterPilot release if anyone is interested.
v2.3.0 is turning into a bigger update than I initially planned, with the main focus on giving much better read-only visibility into the router and network without RouterPilot guessing when the data isn’t authoritative.
Obviously, I’ve only got a Flint 2 for this work, looking to get some feedback from anyone using a Flint 3 or the Flint 4 to see if RouterPilot is able to communicate with these models.
Highlights currently in development include:
-
New Router section with Overview, Ports, Wi-Fi, Multi-WAN, DNS and Performance
-
Improved Ethernet/port telemetry including link state, speed, duplex, errors/drops and session changes
-
Much richer Wi-Fi telemetry including radios, channels, widths, DFS and associated clients
-
Better Multi-WAN / failover visibility
-
Expanded VPN and Tailscale information, including peers, exit-node state and routes where available
-
New Protection / AdGuard intelligence with better DNS statistics, observability and client correlation
-
Improved Clients with better identification, presence history and DNS/traffic integration
-
More useful Network diagnostics and connection history
-
Expanded Data Statistics
-
A smarter Overview bringing the important router/network state together
-
More useful Maintenance / diagnostics / support tools
-
Improved router performance and temperature monitoring
-
Other stuff I’ve not figured out yet - lol
I’m also currently working on a LAN Network Map / topology view so you can get a clearer picture of wired, Wi-Fi and unknown-attached devices. The key rule I’m sticking to is that RouterPilot won’t invent connections it can’t actually prove.
There are also a couple of reliability/UI jobs being worked on before release, including better recovery after a long Windows sleep/resume as this has been a bug since I started this project, therefore it needs the attention is deserves.
RouterPilot is developed in my spare time, if you would like to support my work, please see my github page.
Thanks again for everyone’s feedback and support.
1 Like
What a great tool. Installed and appears to be working as designed with the Flint 3. If I come across any issues I’ll report straight back.
1 Like
Thank you for the feedback, that’s reassuring that it works with a model I don’t have access too.
RouterPilot v.2.3.0 is up and ready for testing. Release notes. If you can, please support the project. Thankyou and enjoy.
I’ve just dropped RouterPilot v.2.3.1 with added controls for Tailscale amongst a few bug fixes and improvements. I’m at the limits now of what the Flint 2 router will expose to RouterPilot, so if you are feeling frisky, please consider supporting the project and I’ll try and grab a Flint 4 - Support Router Pilot