Calling station attribute CP work with Multi-Wan $200
-
I set multi wan one a device using radius in captive portal. The problem is if I fail over the the backup wan connection the calling station attribute IP has to be manually changed. So when a failover occurs we have to manually log into the router and change the attribute. When it fails back we have to switch and save again. This should be an automated process.
-
when a failover occurs we have to manually log into the router and change the attribute.
Why? You access the radius server over the WAN link and the radius server requires the calling station to match the source IP address of the system accessing the server??
-
The Radius server requires the calling station to be the IP of the WAN connection. If the WAN changes due to WAN failover then the field needs to be updated otherwise the Radius fails and any Captive portal users are not able to connect. This then requires someone to manually log in and change the calling station attribute. When it fails back someone again needs to login and switch it back.
This needs to be automated.
-
Not sure if this either simplifies or complicates things but I may need to do this in conjunction with Multiwan Ipsec vpn failover.
-
This needs to be automated.
I can help on this.
What field you need to change if wan is offline?
