0001482: Close wireless locationlog on accounting stop packet - PacketFence

Bug Tracking System

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001482

PacketFence

core

public

2012-07-09 09:03

2015-02-13 15:42

Reporter

fgaudreault

Assigned To

Priority

none

Severity

text

Reproducibility

N/A

Status

closed

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Summary

0001482: Close wireless locationlog on accounting stop packet

Description

This 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...

Tags

No tags attached.

fixed in git revision

fixed in mtn revision

Attached Files

Relationships

Notes
(0002879) obilodeau (reporter) 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 (reporter) 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 (administrator) 2015-02-13 15:42	These bugs have been sitting untouched since 2012. Closing them and possibly reopening in github tracker where relevant.

Issue History
Date Modified	Username	Field	Change
2012-07-09 09:03	fgaudreault	New Issue
2012-07-09 09:04	fgaudreault	Description Updated
2012-08-06 16:05	obilodeau	Note Added: 0002879
2012-08-06 16:06	obilodeau	Note Added: 0002880
2012-10-19 11:40	fgaudreault	Target Version	=> long-term
2015-02-13 15:42	lmunro	Note Added: 0003807
2015-02-13 15:42	lmunro	Status	new => closed