Hi
we are trying to implement a centralised captive portal selection based on host-ip (We are using a two level address allocation scheme)
However we are blocked by the fact that host-ip is set to 0.0.0.0 at login time, while it is correctly set (too late for us) in alogin request , why is that? Is there a workaround?
Below traces on receiving end of requests forwarded by HS router portal configuration:
2016-05-13 11:53:06: 1. State: login| Base-Dir: captive_portal/BWSWHS| New Base: captive_portal/BWSWHS0.0.0.0| Host-ip: 0.0.0.0| Client: 10.19.0.180
2016-05-13 11:53:06: 1. State: alogin| Base-Dir: captive_portal/BWSWHS| New Base: captive_portal/BWSWHS10.16.27.213| Host-ip: 10.16.27.213| Client: 10.19.0.180
We are seeing both on
A CCR1036-12G-4S running 6.34
A CCR1009-8G-1S running 6.35.2
Remote Portal invocation snippet: