Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 2 subscribers
  • Views 2549 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Uplink Balancing / Multipath: No Fallback

Xavier2
Hi

ASG220, UTM9 (9.106-17) with two WAN-Interfaces
Uplink Balancing:
Interface1: Weight 100 
Interface2: Weight 0
Persistence Timeout: 1min (smallest possible)

Multipath Rule:
All Services from Internal LAN to Internet IPv4 balanced to just Interface2
with persistence by connection.

In normal operation (both interfaces up) all traffic goes through Interface2. Ok.
With Interface2 disabled all traffic goes through Interface1. Fine too. ;-)

But after Interface2 comes up again some traffic doesn't move back to Interface2, i.e. pings continously sent don't move back.
Why that? There's no connection with ICMP that could be persistent!?

Even worse, traffic from UTM's VoIP-Gateway doesn't move back too.

Best regards
Xavier


This thread was automatically locked due to age.
Parents
  • 0
    Since you're using persistence by connection, have you tried changing the weighting so that both WAN connections are weighted the same?  You might find a five-minute setting for the Persistence-Timeout to be more-robust.

    Cheers - Bob
Reply
  • 0
    Since you're using persistence by connection, have you tried changing the weighting so that both WAN connections are weighted the same?  You might find a five-minute setting for the Persistence-Timeout to be more-robust.

    Cheers - Bob
Children
  • 0 in reply to BAlfson
    Since you're using persistence by connection, have you tried changing the weighting so that both WAN connections are weighted the same?  You might find a five-minute setting for the Persistence-Timeout to be more-robust.

    Cheers - Bob


    Not by now, but why should this succeed?
    Let me explain it with some other words.
    Almost all traffic should flow over Interface1 except for some traffic bound explicitly to Interface2. 
    In case of a failure of Interface2 all traffic should go through Interface1.
    But after coming Interface2 up again the traffic bound to Interface2 should flow through Interface2 as soon as possible.
    But this don't happen. Even constantly sent pings remain on Interface1.

    Xavier