PacketFence
Bug Tracking System

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001229PacketFencecorepublic2011-06-30 09:512011-09-21 22:21
Reporterumhb 
Assigned Toobilodeau 
PrioritynormalSeverityblockReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version2.2.1 
Target VersionFixed in Version3.0.0 
Summary0001229: No locationLog entry is created if the NAS-Port field is blank in the RADIUS request
DescriptionIf a user's equipment does not send port information in the radius request the locationlog table in the database will not allow an entry to be created for the clients on that device since the "port" column is not allowed to be null.
Additional Informationemail snippet from the support list:

====================================
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.
====================================
TagsNo tags attached.
fixed in git revision
fixed in mtn revisiona804c0b99962e995fde6f86c36d76f837086f1bc
Attached Files

- Relationships

-  Notes
(0002205)
obilodeau (reporter)
2011-09-14 15:16

Fixed on july 14 in stable branch. Will be part of the upcoming 3.0.
(0002275)
obilodeau (reporter)
2011-09-21 22:20

fix released in 3.0

- Issue History
Date Modified Username Field Change
2011-06-30 09:51 umhb New Issue
2011-09-14 15:16 obilodeau mtn revision => a804c0b99962e995fde6f86c36d76f837086f1bc
2011-09-14 15:16 obilodeau Note Added: 0002205
2011-09-14 15:16 obilodeau Status new => resolved
2011-09-14 15:16 obilodeau Fixed in Version => +1
2011-09-14 15:16 obilodeau Resolution open => fixed
2011-09-14 15:16 obilodeau Assigned To => obilodeau
2011-09-21 22:20 obilodeau Fixed in Version +1 => 3.0.0
2011-09-21 22:20 obilodeau Note Added: 0002275
2011-09-21 22:21 obilodeau Status resolved => closed


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker