0001449: Configuration checkup triggers false positive warnings on SNMPv3 Trap configuration - PacketFence

Bug Tracking System

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001449

PacketFence

configuration

public

2012-05-11 08:38

2015-02-13 15:42

Reporter

fgaudreault

Assigned To

Priority

high

Severity

tweak

Reproducibility

always

Status

closed

Resolution

open

Platform

OS Version

Product Version

3.3.2

Target Version

investigate

Fixed in Version

Summary

0001449: Configuration checkup triggers false positive warnings on SNMPv3 Trap configuration

Description

If you set SNMPTrap to 3 in the configuration file, the checkup will show multiple configuration warnings about missing configuration line for SNMPv3 Trap auth/priv. However, the configuration are properly handled by PF is you do a pfcmd switchconfig.

ie.
WARNING - switches.conf | SNMPAuthProtocolTrap is missing for switch 10.0.0.3
WARNING - switches.conf | SNMPAuthPasswordTrap is missing for switch 10.0.0.3
WARNING - switches.conf | SNMPPrivProtocolTrap is missing for switch 10.0.0.3
WARNING - switches.conf | SNMPPrivPasswordTrap is missing for switch 10.0.0.3

But it is properly configured :
SNMPAuthProtocolTrap = MD5
SNMPAuthPasswordTrap = authpwdread
SNMPPrivProtocolTrap = DES
SNMPPrivPasswordTrap = privpwdread

And in switchconfig tells us:
SNMPVersionTrap|SNMPCommunityTrap|SNMPUserNameTrap|SNMPAuthProtocolTrap|SNMPAuthPasswordTrap|SNMPPrivProtocolTrap|SNMPPrivPasswordTrap|SNMPVersion|SNMPCommunityRead|SNMPCommunityWrite|
3|public||MD5|authpwdread|DES|privpwdread|2c|public|private

Tags

No tags attached.

fixed in git revision

fixed in mtn revision

Attached Files

Relationships

Notes
(0002727) obilodeau (reporter) 2012-05-14 09:26	increased priority since it's an easy fix

(0003142) fgaudreault (viewer) 2012-10-19 11:56	Should be investigated, and fixed in a minor release.

(0003801) lmunro (administrator) 2015-02-13 15:42	These bugs have been sitting untouched since 2012. Closing them and possibly reopening in github tracker where relevant.

Issue History
Date Modified	Username	Field	Change
2012-05-11 08:38	fgaudreault	New Issue
2012-05-14 09:26	obilodeau	Note Added: 0002727
2012-05-14 09:26	obilodeau	Priority	low => high
2012-05-14 09:26	obilodeau	Severity	minor => tweak
2012-05-14 09:26	obilodeau	Target Version	=> +1
2012-10-19 11:56	fgaudreault	Target Version	general => investigate
2012-10-19 11:56	fgaudreault	Note Added: 0003142
2015-02-13 15:42	lmunro	Note Added: 0003801
2015-02-13 15:42	lmunro	Status	new => closed