Feature #1191
closed
Enable dynamic VLAN assignment at Captive Portal
0%
Description
Idea:
The Captive Portal Interface assigns an IP via the internal DHCP Server whitch lease time is limited to 10-30 seconds. If the client authenitcates at the CP, the radius server sends the ID of the VLAN the client should assigned to. Now the PFsense creates a bridge between the clients MAC and the Interface the VLAN is configured to (maybe a list at the CP-Option page like: VLAN 1 is LAN IF, VLAN 2 is OPT1 IF ...). After the clients DHCP lease ends it asks for a new IP, whitch is returned by the DHCP Server at the chosen IF. Now the client is authenticated.
Idea from: http://www.alliedtelesis.com/media/datasheets/howto/howto_aw+_use_web_authentication.pdf
Updated by Chris Buechler about 12 years ago
- Status changed from New to Needs Patch
Updated by A FL over 5 years ago
Well, what you are describing is a VLAN-Based captive portal.
There are two kinds of Captive portals in the world: VLAN based one and NAT based one. PfSense captive portal is currently using NAT.
Since this mechanism is the core of how the captive portal works, update this would basically mean create a completely new captive portal.
I would vote for closing this issue, because it's not planned to change the base of how does captive portal works.
@J L : If you are looking for a VLAN-based captive portal, you could have a look to open source NAC (Network Access Control) solutions such as PacketFence.
Updated by Jim Pingle over 5 years ago
- Status changed from Needs Patch to Closed