PacketFence - BTS - PacketFence
View Issue Details
0000758PacketFencepublic2009-07-29 10:402011-01-26 15:43
obilodeau 
obilodeau 
normalminoralways
closedfixed 
 
 
0000758: vlan= statement in violations.conf should assume isolationVlan by default (hardcoded)
The vlan statement in violations.conf was introduced in 1.8.4. Before the behavior was to always put a node that has violations in the isolationVlan. vlan= added some flexibility regarding that.

But, on upgrade people tend to forget to add vlan= and the error is not as clear as it could be / should be.

I think that if vlan= is not defined in [default] or in the [switch] where the bad node is in then isolationVlan could be returned. The only problem I see with that is for the 1200001 violation (system scan) where host needs to be in registrationVlan. It is specified in the config but on an upgrade if they forget [default] vlan= statement they will most likely forget this one as well.

An UPGRADE file would have been handy..
No tags attached.
Issue History
2009-07-29 10:40obilodeauNew Issue
2009-08-19 15:55obilodeauStatusnew => assigned
2009-08-19 15:55obilodeauAssigned To => obilodeau
2009-10-26 11:08obilodeauNote Added: 0001363
2009-10-26 11:08obilodeauStatusassigned => resolved
2009-10-26 11:08obilodeauResolutionopen => fixed
2011-01-26 15:43obilodeauStatusresolved => closed

Notes
(0001363)
obilodeau   
2009-10-26 11:08   
this is fixed right now. not quite sure when but I looking at the code and it seems fine