summaryrefslogtreecommitdiffstats
path: root/nova/utils.py
diff options
context:
space:
mode:
authorVishvananda Ishaya <vishvananda@gmail.com>2013-05-20 09:39:59 -0700
committerVishvananda Ishaya <vishvananda@gmail.com>2013-06-04 13:56:42 -0700
commit769782be844e4c74fdc0aad0ff704b06c874c3ad (patch)
tree862f0769eea370ecb401d114968d64daf96de018 /nova/utils.py
parent55ccdbc3bc62dc32161112a77c0fed39e73ee7b4 (diff)
downloadnova-769782be844e4c74fdc0aad0ff704b06c874c3ad.tar.gz
nova-769782be844e4c74fdc0aad0ff704b06c874c3ad.tar.xz
nova-769782be844e4c74fdc0aad0ff704b06c874c3ad.zip
Don't snat all traffic when force_snat_range set
When using /proc/sys/net/bridge/bridge-nf-call-iptables=1, bridged traffic gets snatted even though it is being bridged out to an external gateway. This can lead to asymmetric routes where traffic goes out the fixed network and comes back on the float network and can lead to packets being blocked by firewalls. Work around this problem by only fallback snatting when the traffic is going to one of the force_snat_ranges. If force_snat_range is not set it defaults to the existing behavior of snatting all traffic that doesn't hit an earlier rule. Fixes bug 1182143 Change-Id: If496dad2308a68a6a4a9fd43d695943bc5034ac4
Diffstat (limited to 'nova/utils.py')
0 files changed, 0 insertions, 0 deletions