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!

[Alex17]

How the controller will change the user from 192.168.30.X (non-auth network) to 192.168.50.X (auth network). Since B@AP do not allow Layer 3 ?

Thanks!

[Ronald_Dvorak]

Set the lease time of 192.168.30.X very low so that the clients check the DHCP very fast do detect the new subnet.

[AntonS]

hy,
i had a setup like this that was working, but there were small differences.

non authenticated network was routed vns - next hop routing
authenticated network was B@AP tagged

i had a seperat vlan so that "guest" traffic was not on my LAN

in the non authenticated profile you have to work with policies!

the setup made problems because the client has to change ip when switching from not-auth to auth network. some clients (ios sometimes also android) make problem with such setup