I have modified eap.conf and added "use_tunneled_reply = yes" in the peap section. I have previously tried this, and obtained the same results. Whenever a client tries to login, they get cycled from authenticating/connecting very quickly. I've posted an example output from a radius debug: http://dpaste.com/112927/ Could you expand on the "set VLAN" option in the post-auth section? I have looked around a bit, but haven't found much of use. Also, I may try a vanilla install of FreeRADIUS, as I'm using the packaged version from the OpenBSD ports tree. There are a few config discrepancies, and I don't understand enough to know how they are having an effect. Thanks again, -William On Sun, Jan 25, 2009 at 12:03, Alan DeKok <aland@deployingradius.com> wrote:
William Graeber wrote:
Here is the output of a client associating immediately after the server starts: http://dpaste.com/112843/
You're not assigning the attributes that tell the server to put the user into a VLAN.
Are you using the *default* configuration files in 2.0.5? It looks like you're not, because editing the "users" file *should* get it to work.
It looks like you need to either:
- set use_tunneled_reply = yes in eap.conf, peap{} sub-section
- add the "set VLAN" configuration to the post-auth section.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html