B@AP + Captive Portal

[Alex17]

Hi Everyone!

Is it possible to create an internal captive portal using B@AP ?

Follow what i'm thinking:

Non-Authenticated Network - 192.168.30.x - B@EWC (to generate the captive portal)
Authenticated Network1 - 192.168.50.x - B@AP
Authenticated Network2 - 192.168.60.x - B@AP
Authenticated Network3 - 192.168.70.x - B@AP

This will work properly ?

Thanks in advance!

[Doug]

1 second on the controllers server...

[Doug]

The reason why this is done on the initial vlan, Extreme has no control over the device to re-ip when the topology changes. The device driver has to recognize that it changed subnets and renew its ip. Not all devices do this gracefully and can get stuck with the wrong ip. The lower lease timer allows the continuous check from the client. If the old address is no longer available as a result of the switch, the device will re-ip.

[Alex17]

For the B@EWC topology, im using controller dhcp server.
How low I can get ?

[Doug]

I would go as low as you can configure, that first B@ewc vlan is just a place holder until the user is moved to the B@AP vlans. On the B@AP vlan those can have a normal lease (days).

[Scott_Van_Artsd]

We had a similar setup for guests. It worked. We kept them in a separate VLAN with access lists so that they could only access Internet resources and local DHCP. Unauthenticated DHCP scope had a very low lease time, then when they where authenticated they got a IP address at their local site, B@AP. We forced them to use Google DNS so that there was no need to have them access any internal resources once they got their IP address.