Anonymous | Login | 2024-08-24 20:56 EDT | ![]() |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||
0001397 | PacketFence | core | public | 2012-03-09 12:40 | 2015-02-18 10:55 | |||
Reporter | fgaudreault | |||||||
Assigned To | ||||||||
Priority | low | Severity | minor | Reproducibility | have not tried | |||
Status | closed | Resolution | open | |||||
Platform | OS | OS Version | ||||||
Product Version | 3.2.0 | |||||||
Target Version | investigate | Fixed in Version | ||||||
Summary | 0001397: Race condition with floating device fast reboots | |||||||
Description | When a floating network device (non-poe) reboots (such as APs), the up trap is received by PF before we can re-enable port-security properly. There is a race condition between setting port-security on the port, and the reception of the UP trap. To avoid this kind of behavior, we should check if the node is a floating device also on UP traps after we get the mac from a switchport. | |||||||
Tags | No tags attached. | |||||||
fixed in git revision | ||||||||
fixed in mtn revision | ||||||||
Attached Files | ||||||||
![]() |
|
(0003858) lmunro (administrator) 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. |
![]() |
|||
Date Modified | Username | Field | Change |
2012-03-09 12:40 | fgaudreault | New Issue | |
2012-03-09 12:41 | fgaudreault | Description Updated | |
2012-10-19 12:23 | fgaudreault | Target Version | => investigate |
2015-02-18 10:55 | lmunro | Note Added: 0003858 | |
2015-02-18 10:55 | lmunro | Status | new => closed |
Copyright © 2000 - 2012 MantisBT Group |