And what if you entirely disable iptables/ipset out from your OpenStack "all-in-one" environment?
That rule will not appear anywhere...
Don't we have a better solution for this? I mean, why the bad checksum occur in first place?
My environment looks like this:
--- ml2_conf.ini:
[securitygroup] enable_security_group = False enable_ipset = False firewall_driver = neutron.agent.firewall.NoopFirewallDriver ---
--- No "security_group_api" at nova.conf. ---
There are almost no iptables rules in my environment... No Security Groups as well...
So, I am unable to use LinuxBridge in a "all-in-one" setup. :-(
I'm glad that only cirros seems to be affected by this problem, but, this is still a problem when we don't use iptables.
Best! Thiago
And what if you entirely disable iptables/ipset out from your OpenStack "all-in-one" environment?
That rule will not appear anywhere...
Don't we have a better solution for this? I mean, why the bad checksum occur in first place?
My environment looks like this:
---
ml2_conf.ini:
[securitygroup] security_ group = False agent.firewall. NoopFirewallDri ver
enable_
enable_ipset = False
firewall_driver = neutron.
---
--- group_api" at nova.conf.
No "security_
---
There are almost no iptables rules in my environment... No Security Groups as well...
So, I am unable to use LinuxBridge in a "all-in-one" setup. :-(
I'm glad that only cirros seems to be affected by this problem, but, this is still a problem when we don't use iptables.
Best!
Thiago