Swaminathan Vasudevan 30f35e08f9 Packets getting lost during SNAT with too many connections ... We have a problem with SNAT with too many connections using the same source and destination on the network nodes. In addition we can see in the conntrack table that the who "instert_failed" increases. This might be a generic problem with conntrack and linux. We suspect that we encounter the following "limitation / bug" in the kernel. There seems to be a workaround to alleviate this behavior by setting the -random-fully flag in iptables for port consumption. This patch fixes the problem by adding the --random-fully to the SNAT rules. Change-Id: I246c1f56df889bad9c7e140b56c3614124d80a19 Closes-Bug: #1814002		2019-04-12 10:12:04 -04:00
..
__init__.py	Update License Headers to replace Nicira with VMware	2014-02-27 08:11:15 +00:00
_constants.py	Packets getting lost during SNAT with too many connections	2019-04-12 10:12:04 -04:00
_deprecate.py	Fix flake8 N534 untranslated exception message	2018-10-19 15:46:04 -04:00
cache_utils.py	Remove deprecated cache_url	2017-11-10 00:47:19 -05:00
config.py	remove neutron.common.rpc	2019-02-06 11:05:55 -07:00
eventlet_utils.py	Windows: fix exec calls	2018-02-01 17:05:28 +02:00
ipv6_utils.py	Allow Ipv6 addresses for nova_metadata_host	2018-10-11 02:07:05 +00:00
profiler.py	Make code follow log translation guideline	2017-08-14 02:01:48 +00:00
test_lib.py	Revert "Removed test_lib module"	2015-06-29 08:27:41 +00:00
utils.py	Packets getting lost during SNAT with too many connections	2019-04-12 10:12:04 -04:00