Bug 989626

Summary: Configurable External Gateway Modes
Product: Red Hat OpenStack Reporter: Perry Myers <pmyers>
Component: openstack-neutronAssignee: Terry Wilson <twilson>
Status: CLOSED ERRATA QA Contact: Assaf Muller <amuller>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: chrisw, hateya, lpeer, mlopes, sclewis, sradvan, twilson, yeylon
Target Milestone: Upstream M2Keywords: FutureFeature, OtherQA, Reopened
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/neutron/+spec/l3-ext-gw-modes
Whiteboard:
Fixed In Version: openstack-neutron-2013.2-0.3.b2.el6ost Doc Type: Enhancement
Doc Text:
Allow disabling the default SNAT behavior on external networks.
Story Points: ---
Clone Of:
: 1046070 (view as bug list) Environment:
Last Closed: 2013-12-23 13:36:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1010323    
Bug Blocks: 975499, 1046070    

Comment 3 Assaf Muller 2013-12-19 15:45:29 UTC
Failed my verification on RHOS 4.0.

I had an instance connected to a router. The instance was able to ping google.com.

I used tcpdump on the hypervisor and saw that the source IP for the packets as they were leaving the hypervisor was the IP that the virtual router was allocated.

I then cleared the gateway, and the pings were failing.
I then ran:
router-gateway-set --disable-snat r1 public

And the pings were succeeding, and the source IP was (again) the source IP of the virtual router. The expected result was that the pings were supposed to fail, as the ICMP request was supposed to leave the hypervisor with a source IP of the instance itself, as the NAT was not supposed to take place (But was).

Comment 5 errata-xmlrpc 2013-12-20 00:16:16 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2013-1859.html

Comment 6 Assaf Muller 2013-12-22 12:57:03 UTC
Reopening. I don't know why the bug was closed as the last message (By me) states that the bug failed verification.