Skip to content
Snippets Groups Projects
Commit 0a6ff9b0 authored by Zuul's avatar Zuul Committed by Gerrit Code Review
Browse files

Merge "Do not set net.ipv4.ip_forward sysctl"

parents f1cbff6b 1bfed045
No related branches found
No related tags found
No related merge requests found
......@@ -25,7 +25,6 @@
sysctl_set: "{{ should_set }}"
sysctl_file: "{{ kolla_sysctl_conf_path }}"
with_items:
- { name: "net.ipv4.ip_forward", value: 1}
- { name: "net.ipv4.conf.all.rp_filter", value: "{{ neutron_l3_agent_host_rp_filter_mode }}"}
- { name: "net.ipv4.conf.default.rp_filter", value: "{{ neutron_l3_agent_host_rp_filter_mode }}"}
- { name: "net.ipv4.neigh.default.gc_thresh1", value: "{{ neutron_l3_agent_host_ipv4_neigh_gc_thresh1 }}"}
......
---
security:
- |
Fixes ``net.ipv4.ip_forward`` not to be enabled by Kolla Ansible
on the default network namespace.
It was enabled on hosts with Neutron L3 Agent (thus in most common
setups with OVS and/or Linux Bridge, but not OVN) and allowed,
unless users had extra iptables rules to avoid that, any traffic
to be accepted for forwarding (as long as it was routable and passed
other checks).
Users of existing setups are advised to re-evaluate whether they
need this sysctl enabled and disable if not necessary.
Kolla Ansible will simply no longer try to set this sysctl at all.
Neutron L3 Agent handles forwarding enablement per managed
namespace.
`LP#1945453 <https://launchpad.net/bugs/1945453>`__
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment