Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multi-wan: support sticky-address route-to #692

Closed
syserr0r opened this issue Jan 21, 2016 · 14 comments
Closed

multi-wan: support sticky-address route-to #692

syserr0r opened this issue Jan 21, 2016 · 14 comments
Assignees
Labels
bug Production bug
Milestone

Comments

@syserr0r
Copy link
Contributor

I believe gateway load balancing should be affected by Settings > Misc > 'Sticky Connections' (See #691 regarding unclear description) (see https://forum.pfsense.org/index.php?topic=49054.msg260494#msg260494 for information from pfsense forums)

If this is the case it does not appear to be working (as can be seen below):
Gif showing the issue
note: the background tab in firefox is refreshing every second
note: there are no proxy settings on either browser

If the 'Sticky Connections' option is not intended to affect outgoing connections then this would be a feature request to add a 'Outgoing Sticky Connections' so that load-balanced multi-WAN is able to function with general web browsing (or other protocols that would expect a consistent IP)

@fichtner fichtner added the feature Adding new functionality label Jan 24, 2016
@fichtner fichtner added this to the 16.7 milestone Jan 24, 2016
@fichtner fichtner self-assigned this Jan 24, 2016
@fichtner
Copy link
Member

We really need to better distinguish between Multi-WAN and Load Balancing everywhere it seems. :)

It looks like the default for Multi-WAN is "route-to" in pf.conf(5), which will do a round-robin per connection, which is what you see. There are, however, pool options for route-to, which can use "sticky-address". Let's try with your setup on IRC next week? :)

@fichtner fichtner changed the title Sticky Gateway Load Balancing multi-wan: support sticky-address route-to Jan 24, 2016
@fichtner
Copy link
Member

fichtner commented Feb 4, 2016

I found the cause... local traffic does not honour gateway settings, see: https://forum.opnsense.org/index.php?topic=2056

I'm marking this [upstream] and will talk to a FreeBSD dev.

@fichtner fichtner added upstream Third party issue and removed feature Adding new functionality labels Feb 4, 2016
@fichtner fichtner removed this from the 16.7 milestone Feb 4, 2016
@syserr0r
Copy link
Contributor Author

syserr0r commented Feb 4, 2016

The traffic isn't originating from the firewall itself in my case, are we sure this is the same issue?

@fichtner
Copy link
Member

fichtner commented Feb 4, 2016

Hmm, no transparent proxy configured?

@syserr0r
Copy link
Contributor Author

syserr0r commented Feb 4, 2016

Correct, no proxy, transparent or otherwise, configured

@fichtner fichtner added bug Production bug and removed upstream Third party issue labels Feb 5, 2016
@fichtner
Copy link
Member

fichtner commented Feb 5, 2016

Ok, my mistake. The functionality is there but for some reason it won't work in your case.

@fichtner
Copy link
Member

fichtner commented Feb 5, 2016

(and I mean really there with rules kewords and all, did we already look through a /tmp/rules.debug dump from you box?)

@syserr0r
Copy link
Contributor Author

syserr0r commented Feb 9, 2016

I don't think we've been through it -- I'll PM a dump.

@fichtner
Copy link
Member

Config does not contain "sticky-address" tags for the respective pf rules, that means the setup tiptoes around the code that adds it. It looks like a config issue at this point, getting to the bottom of this soon enough now. :)

@fichtner fichtner modified the milestones: 16.7, future Feb 15, 2016
@syserr0r
Copy link
Contributor Author

Yay, progress! Let me know if you need anything testing, but bear in mind it's a production firewall.

@fichtner fichtner modified the milestones: 17.1, 16.7 Jul 23, 2016
@fichtner
Copy link
Member

@syserr0r what's the status on this? :)

@syserr0r
Copy link
Contributor Author

I'll try and look at it again in the coming week, but last I looked at it (whch was a fair while ago) the source IP/connection wasn't sticky.

@syserr0r
Copy link
Contributor Author

syserr0r commented Aug 2, 2016

After some very preliminary testing it looks like the source address is staying somewhat sticky so I've rolled it out further and await feedback from our users.

@fichtner
Copy link
Member

Closing this now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Production bug
Development

No branches or pull requests

2 participants