Captive Portal redirect FAIL on BlueSecure BSC-2100

[Ric_]

I need to set up the captive portal on my BlueSocket gear. I've never needed it before because I've previously used transparent authentication.

 

I've read through all the documentation and Googled my heart out and everything seems to suggest that you should connect to the wireless network, attempt to go to a web page and then get diverted. This doesn't happen.

 

DNS and ICMP are both working correctly and I can see my test clients are currently in the 'un-registered' role. These clients can access the web login page if I type the IP address into the address bar. Authentication works fine from there too. It's just that this is more of a 'portal' than a 'captive portal'

 

The clients don't even seem to be getting re-directed to the IP address... they just sit looking for the originally requested webpage.

 

If anyone can help I'd be very grateful... this is the ONLY job I have to do today!

Edited February 16, 2010 by Ric_

[ICTNUT]

And this is exactly what we have been trying to do and are in exactly the same boat.

 

Client will connect, access the portal, authenticate and then just sit there.

[_BC_]

What debugging have your tried?

 

I dont have any experience with BlueSocket, but I do have lots with Trapeze and they also use a captive portal. So it should be a similar process.

 

Is there a spare port on the wireless controller? If so, set the port to use the same VLAN that would be used for your captive portal. Plug a laptop into it and see what happens. Can you access the Internet? Do you get DHCP?

[Ric_]

Get in!

 

After trying everything, I wondered if the config was knackered since it had been in place all the way from v4.x (current version is v6.5.0.8 I think). I backed-up the config and performed a factory reset. After some basic setup, the captive portal then seemed to work but nothing else did despite it all being the same as before

 

I thought, why not try reverting, at least I'll have working wireless again. Restored the config and remembered that I'd changed the 'Port of web direction for user logins' to '8081' to get it working on the clean box. This setting is under 'General'->'HTTP'.

 

Bish, bash, bosh it now all works. Now I just have to worry about client certificates and encryption for the 'roaming'# users and it's all gravy!