PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001136PacketFencehardware modulespublic2010-12-14 10:292015-02-18 10:55
Reporterobilodeau 
Assigned To 
PrioritynormalSeverityminorReproducibilitysometimes
StatusclosedResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
fixed in git revision
fixed in mtn revision
Summary0001136: potential floating network devices issues with write mem and reboots
Description1. Switch config was written when a floating device was plugged in.
It means that it holds a config with down traps enabled and the floating device port doesn't have port-security.

2. Floating device is removed and another normal device authorized properly.
It means that the packetfence database no longer thinks that the last device on a given switch-port is a floating device.

3. The switch is rebooted. Config without port-security is restored.

4. The switch-port will most likely be in the wrong VLAN and no down traps will cause PacketFence to re-enable port-security (since the last entry in it's database is not a floating device)

To fix:
- write to memory when you pass between a floating device configured port and a non floating device configured port
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-12-14 10:29obilodeauNew Issue
2011-01-18 11:41obilodeauTarget Version => 2.1.0
2011-03-03 15:15obilodeauTarget Version2.1.0 => +1
2011-03-03 15:18obilodeauTarget Version+1 => +2
2015-02-18 10:55lmunroNote Added: 0003889
2015-02-18 10:55lmunroStatusnew => closed

Notes
(0003889)
lmunro   
2015-02-18 10:55   
Obsolete bug tracker entries.
PF 4 introduced changes that either make these irrelevant or impossible to reproduce.

New issues are moving to github issues.