#1a You can also need to have a VLAN 999 that has the ip address of the local subnet (THAT can be 192.168.1.x) which could either be a public ip address or a private ip address that connects to the SOHO router. This is so that source traffic, like the controller's ip address will easily be answerable by resources on the corporate side when pings, radius and SNMP are put into place. Make sure that you have the "controller-ip" command point to this ip address or VLAN. It cannot be the garden-variety 192.168.1.x, otherwise it will not work. For example, if your company's internal network is 172.16.0.0 and the VLAN at that site is 172.16.2.x, the controller's management ip address must be something like 172.16.2.1. #1 The Remote Controller's switchip VLAN must be one that is fully routable within your organization. If you are trying to do a site-to-site VPN, between a controller at a local site and a headend site, there are a few requirements to make it work properly: Is there anything else on the controller side that could be causing this? I'll watch this thread closely going forward. I'm going to be onsite later today to troubleshoot some more. The local controller is the default gateway for all wired & wireless clients. It is a local controller and has an IPSEC tunnel back to the master at another site. The controller is configured with a default route.
COX 255 255 255 40 DEFAULT GATEWAY MAC
The provider pretty blames our equipment every time, but I can't argue with the fact that they do not see any MAC addresses coming from the controller to the modem. The issue was resolved by the provider, but we have actually encountered the same issue twice since then. Guys, sorry for not getting back to you on this.
0 kommentar(er)
