In theory you can ping in parallel to all the points[like mtr does][to dns], and choose the one which significantly increases the response time under heavy load.pbix wrote:Gargoyle really has no good way to do pick it other it than just pick the upstream router.
You could perform such a test from time to time, in case of changes in network topology or ping target fail.
----------------------------
The ACCtest is a significant so it gives as an attachment, failed to make the ACC to working.
mtr logs in attachment was done when there was no load.
I think QoS choosing too high ping as ping limit.
Also checked gargoyle github mirror, seems that this change would useful to me:
https://github.com/ericpaulbishop/gargo ... dc1385931b
----------------------------
My ISP always had poor connection quality, mainly by working there morons[strange topology can also be the result].
Customers usually have rj-45 100Mbits/s[physical connection], sometimes fiber-optic cable.
Inside the network there are several wifi switch 5Ghz[work as extension cord].