You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/07/01 11:48:26 UTC

[jira] [Commented] (CLOUDSTACK-7027) Leftover of SNAT rule was causing network down under L3 switch

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-7027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048706#comment-14048706 ] 

ASF subversion and git services commented on CLOUDSTACK-7027:
-------------------------------------------------------------

Commit f45c9f9d2f4185a5e8fb631065700d6dc5987ae4 in cloudstack's branch refs/heads/master from Jayapal
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f45c9f9 ]

CLOUDSTACK-7027: Removing left over static nat rule


> Leftover of SNAT rule was causing network down under L3 switch
> --------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7027
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7027
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.0.0
>            Reporter: Jayapal Reddy
>            Assignee: Jayapal Reddy
>             Fix For: 4.4.0
>
>
> Reproducing steps:
> 1. Add additional public range.
> 2. acquire public ips 
> 3. configure pf/firewall rules on public ip
> 4. observe that SNAT rules on public ip in 'iptables -t nat -L -nv'
> 5. remove ip/rules on that ip (select the max ip from the acquired pool) 
> 6. Repeat the acquire, config rule, remove rules. 
> You can observe SNAT rules for removed ip on router.



--
This message was sent by Atlassian JIRA
(v6.2#6252)