-
Notifications
You must be signed in to change notification settings - Fork 33
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
option ip_conntrack_max does not set conntrack_max #465
Comments
checking the recent sources (https://git.lede-project.org/?p=project/firewall3.git;a=summary, https://git.lede-project.org/?p=source.git;a=summary) there is no reference to In https://git.lede-project.org/?p=project/firewall3.git;a=commit;h=99499fdbe5221847288a6d18edf1032d2702cff9 the I'm not sure how @pmelange made this configs and got these options from. A fresh build vanilla-lede is not having this section also. |
to me it looks more that out firewall defaults are outdated ... |
Yes, seems like we should update our firewall defaults. I still consider this a bug because we want to set some options and actually don't set them. |
I didn't add the firewall optional manually. It must have been automagically done. I agree, the automagical firewall is a mess. See issue #447. |
Seems like the section is now called But I can't find a conntrack_max option. I will rename the section and remove the conntrack_max option. I think ~16k is a good standard value. Let us consider a increase of the default value later on in the process. |
We enable The |
As @SvenRoederer mentioned westwood was removed 2013, so no need for settings. This is may be ok with us or? |
But I can't find a conntrack_max option. It's almost there, search for conntrack instead of conntrack_max as it is only an option of conntrack. s.a. https://lede-project.org/docs/user-guide/firewall_configuration#notes_on_connection_tracking |
To me it looks like the whole firewalling needs an update. |
Would somebody like to solve this? |
Some of the options are now part of the defaults section. Some are configured in /etc/sysctl.conf. The openwrt defaults are sane. We use these from now on. Addresses: freifunk-berlin/firmware#465
Some of the options are now part of the defaults section. Some are configured in /etc/sysctl.conf. The openwrt defaults are sane. We use these from now on. Addresses: freifunk-berlin/firmware#465
Some of the options are now part of the defaults section. Some are configured in /etc/sysctl.conf. The openwrt defaults are sane. We use these from now on. Addresses: freifunk-berlin/firmware#465
Some of the options are now part of the defaults section. Some are configured in /etc/sysctl.conf. The openwrt defaults are sane. We use these from now on. Addresses: freifunk-berlin/firmware#465
Some of the options are now part of the defaults section. Some are configured in /etc/sysctl.conf. The openwrt defaults are sane. We use these from now on. Addresses: freifunk-berlin/firmware#465
Some of the options are now part of the defaults section. Some are configured in /etc/sysctl.conf. The openwrt defaults are sane. We use these from now on. Addresses: freifunk-berlin/firmware#465
On
Firmware Berlin (Hedy 1.0.0-olsrd0903-alpha rev 0d3a4c6) Generic - ar71xx/generic
aka. Schwalbenweg18-core.olsr the firewall configuration uses the optionip_conntrack_max
:Output from
sysctl -a | grep conntrack
:Seems like the option does not work. Current workaround is using /etc/sysctl.conf.
The text was updated successfully, but these errors were encountered: