Edgerouter X (load balancing -Sticky)

Soldato
Joined
11 Jun 2003
Posts
7,613
Location
The Shadows (london)
Hi all,

does anyone have experience with the sticky mode for load balancing?

  • dest-addr Traffic sessions will be on the same WAN interface based on the destination address.
  • dest-port Traffic sessions will be on the same WAN interface based on the destination port.
  • source-addr Traffic sessions will be on the same WAN interface based on the source address.
  • source-port Traffic sessions will be on the same WAN interface based on the source port.
  • proto Traffic sessions will be on the same WAN interface based on the protocol.
how many of these should I enable to keep my connections stable?

I've tried combinations of the first 4 and all 5 and for some reason, it works some days better than others.

The main issue I'm having is that the active connections are switching from one WAN to the other midstream and it's causing me buffering during streaming or interrupts on other sites.

should I try just the source or just destination for better results?
 
They're combined in a logical AND, so if you set all the first four, you only make connections with the same source IP, dest IP, source port and dest port stick to the same WAN. The inclusion of source port pretty much guarantees nothing is going to be sticky, at least for common scenarios. Source ports are almost always random, so you rarely want to take them into account for sticky.

Nothing with switch mid-stream, for the networking definition of stream (like a single TCP or UDP connection). For a single video stream (which generally encompasses multiple TCP streams), you'll want at least source-addr and dest-addr. Possibly plus dest-port, but as it's likely to be the same port regardless, that probably won't matter either way.

in case anyone else is having the same issue;
this is the answer I got back from UI and it seems to have solved the issue
 
Back
Top Bottom