Sticky connections: forum login

[Floh]

Hi,
I'm using multiWAN for loadbalancing the gateway. Unfortunatelly my browser "forget" that I already logged in a forum in some pages later (e.g. I want reply a post). In that case using sticky connections should be helpful.

But still I have to relogin a forum. So what could it be wrong?

Please confirm if I understood right:
Sticky connections means, that if someone use his browser to visit a host. As long as session run (this means as long as someone use that host), same WAN (WAN1 or WAN2) will be used till browser is closed. Is that right?

cu Floh

[dhatz]

In pfsense 2.0 "Sticky" keeps a client_ip+gateway_ip association for as long as a connection state is active, so as long as your browser holds the connection open.

The upcoming v2.1 includes a feature that allows configurable timeout period.

[Nachtfalke]

@Floh:

Hi,
I'm using multiWAN for loadbalancing the gateway. Unfortunatelly my browser "forget" that I already logged in a forum in some pages later (e.g. I want reply a post). In that case using sticky connections should be helpful.

But still I have to relogin a forum. So what could it be wrong?

Please confirm if I understood right:
Sticky connections means, that if someone use his browser to visit a host. As long as session run (this means as long as someone use that host), same WAN (WAN1 or WAN2) will be used till browser is closed. Is that right?

cu Floh

The problem probably is that you read the post - this takes time - and then the connection will be closed and after browsing to a new page the Multi-WAN is using the other GW.

You could create an Alias for networks/IPs and add the forum IP. Then create a firewall rule with one gateway or a failovber GW group with this as destination IP.

[costasppc]

We had that issue as well.

We set port 443 to use a failover group of gateways, not the round robin load balancing group, and so we did for port 8443 (Plesk).

Best regards

Kostas

[Floh]

Hi, thank you for your replies. Ok, I'll think about setup a rule for this issue.

cu Floh

[w00t]

@Floh:

Hi, thank you for your replies. Ok, I'll think about setup a rule for this issue.

cu Floh

You often get logged out on sites using HTTPS. To solve this problem you can, as stated above, create a rule for HTTPS to only use for example WAN1 instead of the multiWAN-gateway.

You can also create a new pool of(a seperate aside from you regular pool/loadbalance), for example, WAN1 and WAN2 but with failover instead of loadbalance, and configure the rule for HTTPS traffic to that gateway. Like this you will keep redundancy.