i have a problem.
My CapsMan Controller is on an internet line with a dynamic ip (i get a new ip every 24hours)
now i would like to use the controller for CAPs on other internet lines.
I have set the CapsMan Addresses field to the actual dynamic IP of my Controller and the CAP ist connecting and all is ok.
But tomorrow my Controller will have a new dynamic ip and i need to change this Controller IP in the CAP.
Why cant i use a dyndns name in the CapsMan Addresses field on the CAP?
Whenever the connection between the CAPsMAN and a CAP site breaks, the wireless interfaces at the CAP go down. This includes the moment when the address of the site changes no matter what else you do.
You can work around the problem that the CAPsMAN address cannot be configured as a dns name by establishing a VPN tunnel which does allow to use a dns name to indicate the server or peer. In recent versions, IPsec can do that, maybe other tunnels (PPTP) can do the same. But such workaround does not prevent the CAP-CAPsMAN connection from breaking for a while at each change of site IP address at either end, as described above.
NB: I believe you use local forwarding on the CAPs, or do not permit internet access to the wireless clients - otherwise each packet between your wireless client and the internet passes through your CAPsMAN site uplink twice.
i now wrote a script that will man an dns lookup of the DNS name from the CAPsMAN controller and then writes the IP to the CAPs settings.
the script only updates the IP in the setting when it has changed.
:local DNSNAME caps.xxx.de
:global previousIP
:local currentIP [:resolve $DNSNAME]
if ($previousIP != $currentIP) do={
/interface wireless cap set caps-man-addresses=$currentIP
set previousIP $currentIP
:log info ("UPDATE CAPsMAN IP from " . $previousIP . " to " . $currentIP);
}