Skip to content

Allow traffic from private gateway to internet#5397

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ravening wants to merge 1 commit into from
Closed

Allow traffic from private gateway to internet #5397

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion systemvm/debian/opt/cloud/bin/cs/CsAddress.py
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -504,7 +504,7 @@ def fw_vpcrouter(self):
self.fw.append(["filter", "front", "-A FORWARD -s %s -d %s -j ACL_INBOUND_%s" %
(self.address["network"], address["network"], address["device"])])
# Accept packet from private gateway if VPC VR is used as gateway
self.fw.append(["filter", "", "-A FORWARD -s %s ! -d %s -j ACCEPT" %
self.fw.append(["filter", "front", "-A FORWARD -s %s ! -d %s -j ACCEPT" %

@weizhouapacheweizhouapacheSep 22, 2021

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ravening
can you move this to line 497 and test it ?

@raveningraveningSep 22, 2021

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@weizhouapache without the front keyword?

@weizhouapacheweizhouapacheSep 22, 2021

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ravening
without front might not fix your problem. try with front

@raveningraveningSep 22, 2021

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@weizhouapache still works... the rule is still being added at the beginning of the FORWARD chain

@weizhouapacheweizhouapacheSep 22, 2021

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ravening before 'ACL_INBOUND_ethX' ?

@raveningraveningSep 22, 2021

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@weizhouapache yes

# iptables -L FORWARD --line-numbers
Chain FORWARD (policy DROP)
num target prot opt source destination
1 ACCEPT all -- 10.32.18.192/27 !10.32.18.192/27
2 ACL_INBOUND_eth3 all -- 10.32.18.192/27 10.0.0.0/24
3 ACL_INBOUND_eth2 all -- 10.0.0.0/24 10.32.18.192/27
4 ACL_INBOUND_eth4 all -- 10.32.18.192/27 10.0.1.0/24
5 ACL_INBOUND_eth2 all -- 10.0.1.0/24 10.32.18.192/27

@weizhouapacheweizhouapacheSep 22, 2021

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ravening
as you see in the rules, rule 2 and 4 will always be ignored.
can you send me the whole iptables rules by email (no matter if this PR is applied) ?

(self.address['network'], self.address['network'])])

if self.get_type() in ["public"]:
Expand Down