[RADIATOR] Dynamically assign VLAN to wireless clients

Johnson, Neil M neil-johnson at uiowa.edu
Fri Nov 12 10:45:22 CST 2010


We are doing something similar, However we are proxying requests via RADIATOR to another RADIUS server and use a ReplyHook to rewrite the Tunnel Parameters.

I can post the files if you like.


-- 
Neil Johnson
Network Engineer
Information Technology Services
The University of Iowa
319 384-0938
neil-johnson at uiowa.edu 


> -----Original Message-----
> From: radiator-bounces at open.com.au [mailto:radiator-
> bounces at open.com.au] On Behalf Of Patrick Renkens
> Sent: Friday, November 12, 2010 10:32 AM
> To: radiator at open.com.au
> Subject: [RADIATOR] Dynamically assign VLAN to wireless clients
> 
> 
> Hi All,
> 
> We would like to dynamically assign VLAN's to wireless clients.
> All of the authentication process (inner and outer tunnel etc.) runs
> OK,
> but the last step should be assigning a dynamic VLAN ID
> (Tunnel-Private-Group-ID) to the client in a short range of ID's.
> 
> Can this be done, and if so, how?
> 
> I already wrote a small PostAuthHook that can generate a random VLAN-ID
> within this short range of ID's. It replaces the default
> Tunnel-Private-Group-ID in the reply-packet with the generated ID, but
> it doesn't do the trick. It does replace the Tunnel-Private-Group-ID
> but
> is has no affect on the process (so it seems).
> 
> The reason for this feature is that the current VLAN is too small and
> we
> prefer to have several VLAN's for the wireless clients instead of a
> much
> larger single VLAN.
> 
> Any other ideas or workarounds are also appreciated.
> 
> Kind regards,
> Patrick Renkens
>   Centre for Information Services (UCI)
>   Radboud University Nijmegen, Netherlands
> 
> 
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator


More information about the radiator mailing list