I don't know if this is a bug or not but it is interesting:
My wifi equipment (Xirrus) does not send the radius value for NAS-Port when
using RADIUS MAC (read NOT 802.1x but still RADIUS) This causes an entry not
to be made in the locationlog table in the DB since the port field is not
allowed to be null. The user will be able to register as if everything is
normal but when PF goes to flip the vlan it will fail because of the missing
locationlog entry.
A simple fix for me was to remove the no null restriction from the column in
the table but that may cause problems for wired deployments. A better fix
might be to use the radius attributes to sense if the user is on a wireless
connection and IF the port value is blank, populate it with some generic value
since the actual value is not important to the NAS.
A missing locationlog entry BREAKS packetfence (at least for vlan deployments),
so when one is not made for any reason some type of notification really should
be given to someone.
As time permits I will see if I can cobble together a patch for the community
and Inverse to review, but if someone at inverse or another (more competent)
perl programmer wants to take a crack at it first please be my guest : )
Jake Sallee
Godfather of Bandwidth
System Engineer
University of Mary Hardin-Baylor
900 College St.
Belton, Texas
76513
Fone: 254-295-4658
Phax: 254-295-4221
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
