I upgraded my Flint router to 4.5.x when it was out originally and found that the failover function had stopped working correctly and my adjustable settings for number of bad pings and good pings had been removed with a sensitivity setting. This sensitivity setting not being customizable causes my router to not failover properly when my main network goes down. After a couple of months of quickly running to the router when my main internet goes down during teams calls to disconnect the patch cable to get it to failover to the back wifi, I downgraded my router back to 4.4.6. Everything went back to working correctly. When I saw the upgrade to 4.6.x, I decided to go ahead and upgrade hoping this issue was fixed. Again after a few weeks I have had my main internet go down again during a teams call and it was back to not failing over unless I disconnected the patch cable from the router. I just finished downgrading the firmware back to 4.4.6 again on my router. Anyone have any suggestions on what to try in 4.6.x or can we please get a customizable sensitivity setting so I can set it up like I have it in 4.4.6 that works?
Hi,
Here are the sensitivity options in the v4.6.x supported customize, may I know what requirement about the sensitivity (special in v4.4.6?) did you need?
Note that the minimum value of three seconds means a detection time of 3 (or 3.9) seconds. Therefore, when the main (Like Eth1) down occurs and switche to the repeater (Wi-Fi), the switching time is approximately 4 seconds.
If there are many team calls, can try choosing to ‘Load Balance’. As the response time of switch may be faster.
Thanks for the reply! Here are the settings that work the best in 4.4.6 and previous firmware....
My main ISP will go offline and then seem to flap quickly online and then off for a few minutes. This is typically not a huge issue while streaming but doesn't work for teams calls. This is why I have it fail over quickly but not show the line as active until it get 50 successful pings.
I tried load balance also but found that streaming can have an issue because my "backup" internet is 5g and it doesn't show my correct location. Sometimes shows I'm in a different state so location based streaming doesn't work correctly if it happens to use that connection during load balancing.
Got it, thanks for the clarification.
Because some users said that the previous sensitivity setting was very complicated and difficult to use, so we optimized this setting and in fact optimized the internal link detection rules.
GL is also in dilemma and cannot take care of all users.
But I will collect this requirement, and evaluate how to continue to optimize this setting (like add the advanced settings) in later iterations.
If you need this such advanced feature, use v4.4.6 firmware first. Thanks.