<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt">> > Thanks, I'll give it a try and post the debug. Am I wrong to be surprised<br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">> > that there is no answer for the first question, though? There has to be a<br>> > great many users out there using EAP and assigning dynamic VLAN based on<br>> > LDAP attributes.... or, not?<br>> <br>> I know of many - it depends on how you are doing it - are you doing post-auth<br>> in the inner-tunnel, or in the outer virtual-server after EAP has been done?<br>> just assign a standard RADIUS attribute and it will be there for you to use in eg PERL<br>> (so long as you copy-to-tunnel in
your EAP config)<br><br>copy_request_to_tunnel = yes<br><br>As mentioned earlier, I am assigning a standard RADIUS attribute, but the value I'm passing to it is not there when I call it, which is in the post_auth of the outer virtual server.. I figured it made sense to put it there, since I call the LDAP module in the authroize section of the outer virtual server. Should this be done in the inner-tunnel? I guess I'll give that a try too...<br><br>Thanks,<br><br>A.<br><br><br><br><br><br> </div> </div> </div></body></html>