
| Anonymous | Login | 2025-10-26 00:15 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 | |||
| 0001431 | PacketFence | core | public | 2012-04-20 14:39 | 2015-02-18 10:55 | |||
| Reporter | obilodeau | |||||||
| Assigned To | ||||||||
| Priority | normal | Severity | minor | Reproducibility | random | |||
| Status | closed | Resolution | open | |||||
| Platform | OS | OS Version | ||||||
| Product Version | ||||||||
| Target Version | investigate | Fixed in Version | ||||||
| Summary | 0001431: trap limiting threading issue | |||||||
| Description | With action=shut, I was getting several emails for the same violation on the same switchport. I think there's a threading issue we'll need to track down. | |||||||
| Steps To Reproduce | 1. Set a ridiculously low trap_limit_threshold value (like 2) 2. Set trap_limit_action to shut 3. Remove the 'snmp-server enable traps port-security trap-rate 1' statement 4. Restart packetfence 5. Hook a PC and make sure it generates a lot of traffic Result: Several emails! Expected: only one email | |||||||
| Tags | No tags attached. | |||||||
| fixed in git revision | ||||||||
| fixed in mtn revision | ||||||||
| Attached Files | ||||||||
Notes |
|
|
(0003876) 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. |
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2012-04-20 14:39 | obilodeau | New Issue | |
| 2012-10-19 12:47 | fgaudreault | Target Version | long-term => investigate |
| 2015-02-18 10:55 | lmunro | Note Added: 0003876 | |
| 2015-02-18 10:55 | lmunro | Status | new => closed |
| Copyright © 2000 - 2012 MantisBT Group |