Astara

source IP is wrong sometimes

Bug #1550541 reported by Mark McClain
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Astara
Fix Released
Medium
Mark McClain
Astara mitaka-rc1

Bug Description

There is an extra SNAT rule which catches are traffic that originates from the appliance. As a result, the source IP selected is the public interface instead of the IP from within the proper subnet. Phil Hopkins and Eric Lopez helped to isolate this bug.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to astara-appliance (master)

Fix proposed to branch: master
Review: https://review.openstack.org/285566

Changed in astara:
status: Confirmed → In Progress
Adam Gandelman (gandelman-a)
Changed in astara:
milestone: none → mitaka-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to astara-appliance (master)

Reviewed: https://review.openstack.org/285566
Committed: https://git.openstack.org/cgit/openstack/astara-appliance/commit/?id=5994b8b148dbe827339b8fa96ec895041ae8dcf9
Submitter: Jenkins
Branch: master

commit 5994b8b148dbe827339b8fa96ec895041ae8dcf9
Author: Mark McClain <email address hidden>
Date: Fri Feb 26 17:02:42 2016 -0500

    do not apply SNAT when packet is generated by appliance

    SNAT was incorrectly applied to traffic originating from the appliance.
    This change marks the traffic so that the NAT rule is skipped and adds
    clarifying comments to SNAT code.

    Change-Id: Ifa6ea089c5bff6c57f4ba22095ef357eeb1ff786
    Closes-Bug: 1550541

Changed in astara:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.