PacketFence - BTS - PacketFence
View Issue Details
0000966PacketFencepublic2010-04-22 11:282012-10-19 10:18
obilodeau 
 
normalminorhave not tried
resolvedfixed 
 
 
0000966: node expiration with expire.node=... won't work in routed VLAN
expire.node triggers node_cleanup from pfmon

several problems:
- uses node_delete which doesn't delete in vlan-isolation if there's an open locationlog entry (and we know there are tons of that)
- the expiration is calculated on last_arp field in the node table, last_arp won't be triggered in routed environment

Hints for solution:
- Add a last_activity field to the node table that is updated based on different mechanism (ie: arp, dhcp, mac activity, on connection with radius stuff, captive portal, etc.)
- we should auto-close locationlog entries after 1 day when they are of type except snmp-traps and MAB because the client need to periodically re-auth anyway (configurable)
No tags attached.
Issue History
2010-04-22 11:28obilodeauNew Issue
2010-04-22 11:28obilodeauStatusnew => assigned
2010-04-22 11:28obilodeauAssigned To => obilodeau
2010-04-22 11:30obilodeauTarget Version => 1.10.0
2010-11-19 14:25obilodeauTarget Version1.10.0 => 2.0.0
2011-01-18 09:47obilodeauTarget Version2.0.0 => 2.1.0
2011-03-03 15:16obilodeauTarget Version2.1.0 => +1
2011-03-03 15:18obilodeauTarget Version+1 => +2
2012-08-06 16:01obilodeauNote Added: 0002878
2012-09-10 14:33fgaudreaultNote Added: 0003034
2012-09-10 14:39fgaudreaultNote Added: 0003036
2012-09-10 14:39fgaudreaultStatusassigned => resolved
2012-09-10 14:39fgaudreaultResolutionopen => fixed
2012-10-19 10:18fgaudreaultAssigned Toobilodeau =>
2012-10-19 10:18fgaudreaultTarget Version+2 =>

Notes
(0002878)
obilodeau   
2012-08-06 16:01   
Reminder sent to: fgaudreault

With your node expiration changes, can this be closed?
(0003034)
fgaudreault   
2012-09-10 14:33   
I think so yes.
(0003036)
fgaudreault   
2012-09-10 14:39   
Not relevant anymore. We now use last_dhcp to trigger the node_expire.