schumaku 1 Posted September 28, 2015 Report Share Posted September 28, 2015 (edited) DUT: ReadyNAS RN516, ReadyNASOS 6.2.4, domotz 0.9.2-1Appears the agent is designed and/or coded using wrong assumptions - the second hop in the traceroute does not have the be the ISP ... here it is yet another local router: Edited September 28, 2015 by schumaku Quote Link to post Share on other sites
Silvio 29 Posted September 28, 2015 Report Share Posted September 28, 2015 Thanks Kurt,yes this is something we were aware. We haven't put yet the logic to detect all the internal hops and just made something working in a large percentage of homes. Definitely we must fix this and it's already in our backlog.S. Quote Link to post Share on other sites
System_Error_Message 2 Posted November 7, 2015 Report Share Posted November 7, 2015 relating to route assumptions, would it be possible for domotz to detect dual WAN? In home use there are some users with dual WAN or multi WAN. This would also go well in tandem of detecting multiple networks as some do have multiple networks such as the management network which network admins secure and use to configure devices but that do not have internet access. Quote Link to post Share on other sites
(1)(1)(1)(1)(1)(1).jpg.7dcdeb3fb90919aa2df390a4f448ac4b.thumb.jpg.77bf24b1396f1fd80d63b164713f41ff.jpg)
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.