0000941: The traplog table does not show up the number of traps received but the traps treated by PF. Which is slightly different !... - PacketFence

Bug Tracking System

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000941

PacketFence

core

public

2010-04-05 17:03

2015-02-18 10:55

Reporter

fgaudreault

Assigned To

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

closed

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Summary

0000941: The traplog table does not show up the number of traps received but the traps treated by PF. Which is slightly different !...

Description

We created the traplog table in which we are supposed to store the traps received by PF.
From what I see in pfsetvlan, the traplog_insert() function is called only when PF actually does something on a trap.
This means that in this table we do NOT put numbers about the traps received but about traps treated by PF. Which is way different !!

I may have been totally confused since we created this table but the thing is that I dont care only about how many traps PF treated. yes I care about that but I do also care about how many traps PF received.
One of the reasons is that we have diagnosed many anomalies on different networks just by looking at the switches and ports that send an abnormally high number of traps.

Personnally I dont see the point of storing only treated traps.
Why dont we store all the traps received and then identify those who were treated or not.

Additional Information

traplog_insert() is called in signalHandlerTrapListQueued() after parseTrap() and after we flush all the ignored traps.

Tags

No tags attached.

fixed in git revision

fixed in mtn revision

Attached Files

Relationships

Notes
(0003859) 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
2010-04-05 17:03	rbalzard	New Issue
2011-01-18 12:02	obilodeau	Target Version	=> 2.1.0
2011-03-03 15:15	obilodeau	Target Version	2.1.0 => +1
2011-03-03 15:18	obilodeau	Target Version	+1 => +2
2012-02-29 10:58	obilodeau	Category	future => core
2012-10-19 12:25	fgaudreault	Reporter	rbalzard => 94jaccha95107
2012-10-19 12:25	fgaudreault	Target Version	long-term => general
2012-10-19 12:25	fgaudreault	Reporter	94jaccha95107 => fgaudreault
2015-02-18 10:55	lmunro	Note Added: 0003859
2015-02-18 10:55	lmunro	Status	new => closed