PacketFence - BTS - PacketFence
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000809PacketFencepublic2009-10-05 17:422011-01-26 15:43
Reporterobilodeau 
Assigned Toobilodeau 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
fixed in git revision
fixed in mtn revision
Summary0000809: uplink parameter in switches.conf is case sensitive and our sample config doesn't write dynamic right
DescriptionIn the code we check for Dynamic in the uplink parameter but in the sample config its written dynamic. This leads to warnings in the logs and maybe a bad evaluation of uplink vs non-uplink ports.

Why is this parameter case sensitive anyway?
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0000795closed obilodeau Warning in vlan.pm 
related to 0000831closed obilodeau not careful enough when validating uplink parameter in switches.conf causes threads to hang later 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-10-05 17:42obilodeauNew Issue
2009-10-05 17:43obilodeauStatusnew => assigned
2009-10-05 17:43obilodeauAssigned To => obilodeau
2009-10-05 17:43obilodeauRelationship addedrelated to 0000795
2009-10-05 18:14obilodeauNote Added: 0001318
2009-10-05 18:14obilodeauStatusassigned => resolved
2009-10-05 18:14obilodeauResolutionopen => fixed
2009-10-28 14:08obilodeauRelationship addedrelated to 0000831
2011-01-26 15:43obilodeauStatusresolved => closed

Notes
(0001318)
obilodeau   
2009-10-05 18:14   
Parameter is now case-insensitive as per monotone revision: cae402389397a76147bc5b1412aec33d9a7b044b

http://mtn.inverse.ca/revision/info/cae402389397a76147bc5b1412aec33d9a7b044b [^]