0001136: potential floating network devices issues with write mem and reboots - PacketFence

Bug Tracking System

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001136

PacketFence

hardware modules

public

2010-12-14 10:29

2015-02-18 10:55

Reporter

obilodeau

Assigned To

Priority

normal

Severity

minor

Reproducibility

sometimes

Status

closed

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Summary

0001136: potential floating network devices issues with write mem and reboots

Description

1. 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

Tags

No tags attached.

fixed in git revision

fixed in mtn revision

Attached Files

Relationships

Notes
(0003889) 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-12-14 10:29	obilodeau	New Issue
2011-01-18 11:41	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
2015-02-18 10:55	lmunro	Note Added: 0003889
2015-02-18 10:55	lmunro	Status	new => closed