Hi, > rad_recv: Access-Request packet from host 10.32.2.39 port 1645, id=199, > length=136 User-Name = "fcanales" Framed-MTU = 1400 Called-Station-Id = > "001d.4551.7da0" Calling-Station-Id = "5894.6b0d.e86c" Service-Type = > Login-User Message-Authenticator = 0x645687565f9d60e3b76f5ffac29b74a1 > EAP-Message = 0x0202000d016663616e616c6573 NAS-Port-Type = Wireless-802.11 > NAS-Port = 59460 NAS-IP-Address = 10.32.2.39 NAS-Identifier = "ap-Reco32" > The one that does not work: > rad_recv: Access-Request packet from host 10.32.2.81 port 32768, id=113, > length=232 User-Name = "fcanales" Calling-Station-Id = "58-94-6b-0d-e8-6c" > Called-Station-Id = "30-37-a6-4b-9f-90:IReconquista" NAS-Port = 1 > Cisco-AVPair = "audit-session-id=0a2002510000000f4eaaf051" NAS-IP-Address > = 10.32.2.81 NAS-Identifier = "Iplan_wcs" Airespace-Wlan-Id = 1 > Service-Type = Framed-User Framed-MTU = 1300 NAS-Port-Type = > Wireless-802.11 Tunnel-Type:0 = VLAN Tunnel-Medium-Type:0 = IEEE-802 > Tunnel-Private-Group-Id:0 = "60" EAP-Message = > 0x0202000d016663616e616c6573 Message-Authenticator = > 0x77344c030301e2389311b1dde163a5b7 > The differencies in "Calling-Station-Id", "Called-Station-Id" and " > Service-Type", for example. > Is it posible that WCL is sending the information in a way that Radius > cannot process?
no. its just sending them in the way its been configured...we use VLAN override with our cisco wireless controllers fine - and have done for years - even back in the FreeRADIUS 1.x days ....you just need to see what is different in your config between the bare AP and the wireless controller - and if you are talking about huntgroups then that might be east to spot - check the config files in FreeRADIUS config for how you have defined that AP IP 10.32.2.39 - compared to the wireless controller - 10.32.2.81 ...it might be something simple in your $RADDB/huntgroups file, for example. alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html