[
https://issues.apache.org/jira/browse/CLOUDSTACK-8934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952759#comment-14952759
]
ASF GitHub Bot commented on CLOUDSTACK-8934:
--------------------------------------------
Github user wilderrodrigues commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/923#discussion_r41730481
--- Diff: systemvm/patches/debian/config/opt/cloud/bin/configure.py ---
@@ -123,24 +129,29 @@ def add_rule(self, cidr):
" -p %s " % rule['protocol'] +
" -m %s " % rule['protocol'] +
" --dport %s -j RETURN" % rnge])
+
+ logging.debug("Current ACL IP direction is ==> %s",
self.direction)
if self.direction == 'egress':
- self.fw.append(["filter", "", " -A FW_OUTBOUND -j
FIREWALL_EGRESS_RULES"])
+ self.fw.append(["filter", "", " -A FW_OUTBOUND -j
FW_EGRESS_RULES"])
--- End diff --
No, I renamed to make it consistent with the default rules, which can be
found in the iptables-router file. That file is installed with cloud early
config then afterwards the rules are replaced.
In addition, the code was also refering to FW_OUTBOUND, not
FIREWALL_OUTBOUND. The use of FW cs FIREWALL doens't look consistent. Now we
have only FW.
I hope it's clear. I am at home today... A bit ill. So typing from my mobile
Cheers,
Wilder
> Default routes not configured for rVPC and RVR
> ----------------------------------------------
>
> Key: CLOUDSTACK-8934
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8934
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Wilder Rodrigues
> Assignee: Wilder Rodrigues
> Priority: Blocker
>
> User VMs cannot reach the outside world due to missing default routes in
> Redundant VPCs and Redundant Isolated Networks.
> In order to work it around I had to:
> route add default gw 192.168.23.1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
