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

'Sticky Connections' in Settings > Misc has unclear description #691

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

'Sticky Connections' in Settings > Misc has unclear description #691

syserr0r opened this issue Jan 21, 2016 · 3 comments
Assignees
Labels
cleanup Low impact changes
Milestone

Comments

@syserr0r
Copy link
Contributor

The description seems to imply this only applies to the load balancer, however I believe this also applies to outgoing gateway connections (see: https://forum.pfsense.org/index.php?topic=49054.msg260494#msg260494)

Whichever is the correct function needs to be clearly described, as this does not appear to be the case at the moment.

Image for reference, with some of the possibly unclear sections underlined.
Image for reference

PS: I hope I'm not nit-picking here, you are doing an excellent job with this fork!

@fraenki
Copy link
Member

fraenki commented Jan 21, 2016

According to the pf.conf documentation it affects all connections:

     set timeout
       src.track  Length of time to retain a source tracking entry after
                  the last state expires.

However, the variable used in the source code $config['system']['lb_use_sticky'] also reflects the misleading description from the WebGUI.

@syserr0r
Copy link
Contributor Author

I think there are two issues here: first is the timeout which is global as you say; second is the toggle for 'Sticky Connections' which I believe also adds sticky-address to the outgoing rules.

Output of: pfctl -sr | grep stick:

pass in quick on em2 route-to { (em0 1.2.3.4), (em4 2.3.4.5) } round-robin sticky-address inet from 192.168.1.0/24 to any flags S/SA keep state label "USER_RULE: Default allow LAN to any rule"
pass in quick on em2 route-to { (em0 1.2.3.4), (em4 2.3.4.5) } round-robin sticky-address inet from 192.168.2.0/24 to any flags S/SA keep state label "USER_RULE: Default allow LAN to any rule"
pass in quick on em5 route-to { (em0 1.2.3.4), (em4 2.3.4.5) } round-robin sticky-address inet from 192.168.6.0/24 to any flags S/SA keep state label "USER_RULE: Allow LUNCHROOM IPv4 to Any"

*Note: WAN GW IP replaced with 1.2.3.4 and WAN2 GW IP replaced with 2.3.4.5

@syserr0r
Copy link
Contributor Author

I believe it would also be wise to mention the timeout is in seconds.

@fichtner fichtner self-assigned this Feb 4, 2016
@fichtner fichtner added the feature Adding new functionality label Feb 4, 2016
@fichtner fichtner added this to the 16.7 milestone Feb 4, 2016
@fichtner fichtner added cleanup Low impact changes and removed feature Adding new functionality labels Feb 16, 2016
fichtner added a commit that referenced this issue May 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cleanup Low impact changes
Development

No branches or pull requests

3 participants