How to Configure a Cox Router IP Address for Site-to-Site VPN

When setting up a site-to-site VPN between two remote controllers, it's essential to ensure that there is a route on the remote controller pointing to your corporate network's IPsec MAP. This allows local clients to access corporate resources seamlessly.

On the remote controller, the default gateway will be the hop beyond the public IP address or SOHO router performing routing. To facilitate source traffic from the controller's IP address being answerable by resources on the corporate side, it's crucial to have a VLAN 999 with an IP address of the local subnet (which can be a public or private IP address connecting to the SOHO router).

The 'controller-ip' command should point to this IP address or VLAN. It's essential to note that the controller's management IP address cannot be a standard 192.168.1.x as it will not work. Instead, it must be an IP address within your organization's routable range.

For instance, if your company's internal network is 172.16.0.0 and the VLAN at the site is 172.16.2.x, the controller's management IP address should be something like 172.16.2.1.

Furthermore, the Remote Controller's switchip VLAN must be fully routable within your organization. When establishing a site-to-site VPN between a local controller and a headend site, there are specific requirements to ensure it works properly:

* Ensure that the controller is configured with a default route.

* Verify that the provider does not see any MAC addresses coming from the controller to the modem.

In some cases, the issue may be resolved by the provider, but it's essential to troubleshoot further to identify the root cause of the problem. In this scenario, the issue was initially resolved by the provider, but it recurred twice subsequently.

By following these guidelines and troubleshooting steps, you can ensure a seamless site-to-site VPN connection between remote controllers and access corporate resources efficiently.

Cox router ip address