Open btzq opened 1 month ago
@btzq it looks like a route to 10.26.8.0/254 is missing in the VPC VR. you can retry aftering adding a route manually.
ip route add 10.26.8.0/24 via 10.26.1.254
Hey @weizhouapache , but this would require operator to manually intervene, right? And if the router is destroyed (eg. CleanUp), this setting will dissapear, and it will need to be re-added manually.
Is there another way to do it?
Hey @weizhouapache , but this would require operator to manually intervene, right? And if the router is destroyed (eg. CleanUp), this setting will dissapear, and it will need to be re-added manually.
@btzq correct.
Is there another way to do it?
no. currently static routes only applies on VPC private gateway. https://cloudstack.apache.org/api/apidocs-4.19/apis/createStaticRoute.html
We have plan to extend it to support VPC and isolated networks. probably next major release (4.21).
@weizhouapache i see, looking forward to this enhancement then!
Should i close this ticket? Or leave it open to track this request?
@weizhouapache i see, looking forward to this enhancement then!
Should i close this ticket? Or leave it open to track this request?
you can keep it open.
btw: have you tested the manual static route ? does it work in your case ?
@weizhouapache We tried your solution and it did not work.
After we've added the route, the VR is able to reach the destination, but source to destination still wouldnt work.
@weizhouapache We tried your solution and it did not work.
After we've added the route, the VR is able to reach the destination, but source to destination still wouldnt work.
What are the network acl rules of the vpc tier ? Allow all ?
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
Advanced Networking VPC VNF + L2 Network
OS / ENVIRONMENT
SUMMARY
We have 1 VPC and 1 L2 Network connected together with a VNF (PFsense) in between.
Results Summary:
Background: We’ve allowed any on the VNF firewall rules as attached in the screenshot below:
Traffic is allowed any on 10.26.1.254 interface
Traffic is allowed any on 10.26.8.254
We then run some tests.
Test 1: From L2 VM (10.26.8.230) to VPC VM (10.26.1.250)
Results: Ping and traceroute test from 10.26.8.230 to 10.26.1.250 works as expected. (PASS)
Test 2: From VPC VM (10.26.1.250) to L2 VM (10.26.8.230)
Results: Ping and traceroute test from 10.26.1.250 to 10.26.8.230 is not possible (FAILED)
Test 3: From L2 VM (10.26.8.230) to Private Gateway VM (10.88.5.82) Results: Ping and traceroute test from 10.26.8.230 to 10.88.5.82 works as expected (PASS)
Test 4: From Private Gateway VM (10.88.5.82) to L2 VM (10.26.8.230)
Results: Ping and traceroute test from 10.88.5.82 to 10.26.8.230 does not work (FAILED)
We've been trying to debug Tests 2 and 4 for a while now with no sucess. Anyone has any ideas? Or is Cloudstack designed not to allow this to be possible?
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS