GitHub user Ryan-AccuWeb-Cloud added a comment to the discussion: Cloudstack 4.22 - Configuration Wizard failing - Fix Error
Hi Mike, Yes, **10.10.10.1** is the gateway for the guest network. For communication between `10.10.10.0/24` and your internal `172.16.0.0/16` network, routing needs to be configured in both directions. For example: ```text VM: 10.10.10.25 VR Internal IP: 172.16.0.100 Core Router: 172.16.0.1 ``` The Virtual Router should have a route for: ```text 172.16.0.0/16 → 172.16.0.1 ``` And the core router needs a return route: ```text 10.10.10.0/24 → 172.16.0.100 ``` The return route is important; otherwise, traffic can reach the internal network but the response won't know how to get back to the VM. For the domain controllers, make sure the VMs use the DCs for DNS and that the DC network has the appropriate return route as well. Also, regarding the disabled entries: even though they're disabled, they can still remain in the database and cause the wizard to detect conflicting entries. Keeping those queries handy is a good idea. Ryan | AccuWeb Cloud Cloud Infrastructure Support Engineer GitHub link: https://github.com/apache/cloudstack/discussions/13956#discussioncomment-18360143 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
