On Thu, 8 Feb 2007, Oxiel Contreras wrote: > The Access-Accept part of radiusd -X is now sending the switch the correct > information: > > modcall[authenticate]: module "eap" returns ok for request 8 > modcall: leaving group authenticate (returns ok) for request 8 > Sending Access-Accept of id 1 to 192.168.10.20 port 1068 > Tunnel-Type:0 += VLAN > Tunnel-Medium-Type:0 += IEEE-802 > Tunnel-Private-Group-Id:0 += "3" > MS-MPPE-Recv-Key = > 0x2c003c698c883936e741aeed8974f40eb012d38af20400bdd0815dac46dc2e0b > MS-MPPE-Send-Key = > 0x92807250a6760157aa6a39f9a05239c3d28bce8c5b7dc3563bd2ddc7cae2893e > EAP-Message = 0x030a0004 > Message-Authenticator = 0x00000000000000000000000000000000 > User-Name = "MYDOMAIN\\jose" > Finished request 8 > > But still the VLAN is not assigned, what else can it be ?
Have you checked the documentation for the Omniswitch to verify that it supports this? If I send back the same attributes on my wireless access points, it works perfectly (we do this in production). The AP's, however, support that. -j -- Jeremy L. Gaddis, MCP, GCWN [EMAIL PROTECTED] LinuxWiz Consulting http://linuxwiz.net - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
