Fix Static NAT/Port Forwarding when VM NIC is not the default#13200
Fix Static NAT/Port Forwarding when VM NIC is not the default#13200sudo87 wants to merge 3 commits into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests.
Additional details and impacted files@@ Coverage Diff @@
## main #13200 +/- ##
=============================================
- Coverage 18.08% 3.51% -14.57%
=============================================
Files 6037 464 -5573
Lines 542611 40154 -502457
Branches 66433 7559 -58874
=============================================
- Hits 98136 1413 -96723
+ Misses 433448 38551 -394897
+ Partials 11027 190 -10837
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| if internal_device and internal_vr_ip and internal_device != device: | ||
| self.fw.append(["nat", "front", | ||
| "-A POSTROUTING -o %s -d %s/32 -j SNAT --to-source %s" % | ||
| (internal_device, rule["internal_ip"], internal_vr_ip)]) |
There was a problem hiding this comment.
- this should apply to additional nics of guest VMs only. since there is no issue with first NIC of guest VMs, it is not needed.
- it would be better to provide an option for end users.
bc506f4 to
4a9d0f4
Compare
|
@blueorangutan package |
|
@sudo87 a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 17959 |
|
@blueorangutan package |
|
@sudo87 a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
Description
This PR intends to fix #8366
When CloudStack VR forwards traffic to a VM whose NIC is not the VM's default, the VM may reply via its default NIC (asymmetric routing). To force symmetric routing we SNAT the forwarded packet's source to the VR’s guest IP on the VM subnet so the VM replies on-link back to that VR interface. Also fix the port-forwarding SNAT to pick the correct VR guest IP for the VM's subnet
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?