PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001482PacketFencecorepublic2012-07-09 09:032015-02-13 15:42
Reporterfgaudreault 
Assigned To 
PrioritynoneSeveritytextReproducibilityN/A
StatusclosedResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
fixed in git revision
fixed in mtn revision
Summary0001482: Close wireless locationlog on accounting stop packet
DescriptionThis needs to be challenged.

One of the big problem when we want to delete a node that connected on a Wireless SSID is the fact that we just leave the locationlog open forever. The users disconnects, but the locationlog stays open. I am thinking that since we have a working accounting base, we could base our locationlog not using RADIUS request, but using accounting start-stop packets.

Open Locationlog on Accounting Start. Close locationlog on Accounting Stop.

The downside of this would be to force users to enable Accounting on their wireless environment. What do we do for the "el cheapo" devices that cannot do accounting, but supports dynamic vlans? Is that even possible?

Or should we just delete the node and don't care about if the user is connected or not? I mean we can systematically send a CoA packet to de-auth the user even if we don't know if the device is still connected or not...
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-07-09 09:03fgaudreaultNew Issue
2012-07-09 09:04fgaudreaultDescription Updated
2012-08-06 16:05obilodeauNote Added: 0002879
2012-08-06 16:06obilodeauNote Added: 0002880
2012-10-19 11:40fgaudreaultTarget Version => long-term
2015-02-13 15:42lmunroNote Added: 0003807
2015-02-13 15:42lmunroStatusnew => closed

Notes
(0002879)
obilodeau   
2012-08-06 16:05   
Might be worth to try it out and explicitly test against race conditions (late or early stop packets that could affect the outcome of a connection).
(0002880)
obilodeau   
2012-08-06 16:06   
But for node deletion though, I would simply decouple the node and the locationlog table. Allow a locationlog entry to exist even if there's no node. This way deletion could always be allowed.
(0003807)
lmunro   
2015-02-13 15:42   
These bugs have been sitting untouched since 2012.
Closing them and possibly reopening in github tracker where relevant.