Hi @EmuAGR 

Thanks for posting in our business forum.

Are you in Controller mode? There is an option. Have you tried this?

Do you rule out the chance that the session is established on WAN3 when the primary is down and it continues on WAN3 after the recovery?

Thanks for the reply @Clive_A ,

It seems that "Backup Mode" addresses exactly my issue. I'm using standalone mode, though, I see both "Mode" options (with a third timed one) but no "Backup Mode".

I'll test this again focusing to see if they're old sessions as you suggested.

  @Clive_A I can confirm that new sessions are still being sent through secondary WAN3 several minutes (edit: an hour still) after primary WAN1 comes online.

I tested with both with speedtest (<1 Gbps) and traceroute (second hop goes to WAN3 ISP).

EDIT:

To be honest, keeping old sessions seems reasonable, but right now it's switching to the secondary WAN3 indefinitely. I'd rather have the choice to terminate sessions and switch to primary (good for LTE WAN) or keep old sessions and switch new ones to primary (good for connectivity if asymmetry isn't too high).

The behaviour I would expect:

• No load balancing, no failover:
  • Use a random WAN statically, in case of failure remove that WAN row from the routing table and whatever happens.
• Load balancing:
  • Randomly distribute sessions between WANs. [Worst]
  • Weighted Round-Robin between them considering fixed throughput [this is what I think the router does currently], or...
  • Even better, use the WAN with fastest throughput available (approx) when deciding (keeping track of the current usage against a fixed speed. [Possible enhancement!]
• Failover:
  • Same priority:
    • Failure of a primary WAN switches to another random primary WAN, keeps all traffic in the new WAN indefinitely.
  • Different priority:
    • If any/all primary are down (selectable as it is now), switch to secondary WAN and route back to primary when it recovers and two options:
      • Keep old sessions in the secondary to avoid connectivity interruptions. [Good for unmetered/fiber secondary.]
      • Kill old sessions and route back everything to the primary. [Good for metered/LTE/slow secondary.]

  @Clive_A  I have the same problem, can you follow up on the bug?

Hi @Nebur692 

Nebur692 wrote

  @Clive_A  I have the same problem, can you follow up on the bug?

What kind of mode do you use? Standalone or controller?

Did you enable "Always Link Primary"?

Firmware version of your device, if you have a controller, specify it as well.

Hello  @Clive_A !

I see you enabled load balancing, that's a completely different test case than what I introduced in my first post, as with failover and without load balancing the WANs aren't used alternatively (unlike you've shown) unless one fails.

I'm not using load balancing because my WANs are very asymmetrical and the secondary doesn't have dual stack.

Hi @EmuAGR 

EmuAGR wrote

Hello  @Clive_A !

 

I see you enabled load balancing, that's a completely different test case than what I introduced in my first post, as with failover and without load balancing the WANs aren't used alternatively (unlike you've shown) unless one fails.

 

I'm not using load balancing because my WANs are very asymmetrical and the secondary doesn't have dual stack.

The original post, the very first, did not mention this. If you don't have Load Balancing, then failover isn't gonna be prioritized. I don't see the reason why it should switch back. Then this is just a failover without load balancing.

If you search for the correct steps to enable failover, load balance is required. Then there is nothing wrong with the feature but your application is special and the feature does not fit your purpose.

  @Clive_A  I'll test then as you suggested, with load balancing enabled.

But I think that load balancing with primary-secondary shouldn't have used the secondary until after the primary was down (as per the wording of the option was implying).

Hi @EmuAGR

When failover is enabled, backup WAN is offline until the Online Detection fails to ping through primary and tells the router to switch over. It's been like this ever since the Omada router was released years ago.