PacketFence - BTS - PacketFence |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0001231 | PacketFence | core | public | 2011-07-04 20:46 | 2011-10-24 20:24 |
|
Reporter | obilodeau | |
Assigned To | obilodeau | |
Priority | high | Severity | minor | Reproducibility | sometimes |
Status | closed | Resolution | fixed | |
Platform | | OS | | OS Version | |
Product Version | | |
Target Version | 3.0.0 | Fixed in Version | 3.0.0 | |
fixed in git revision | |
fixed in mtn revision | f962d04cf33709f183fed5d23cc1a04b826430b0 |
|
Summary | 0001231: Custom VLAN assignments relying on connection_type will fail on "unknown" nodes |
Description | After a migration, it is possible for vlan-reassignment to be triggered with an Unknown connection_type.
Unknown vlan constant is a string instead of a numeric constant like all the other connection type constants. So when testing against connection_type in custom code it will issue warnings which ends-up in the web node edit dialog because it matches the line xxx\. regexp.
fix: make the unknown constant numeric:
use constant UNKNOWN => 0b00000000; |
Steps To Reproduce | |
Additional Information | |
Tags | No tags attached. |
Relationships | |
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2011-07-04 20:46 | obilodeau | New Issue | |
2011-07-05 10:04 | obilodeau | mtn revision | => f962d04cf33709f183fed5d23cc1a04b826430b0 |
2011-07-05 10:04 | obilodeau | Note Added: 0002101 | |
2011-07-05 10:04 | obilodeau | Status | new => resolved |
2011-07-05 10:04 | obilodeau | Fixed in Version | => +1 |
2011-07-05 10:04 | obilodeau | Resolution | open => fixed |
2011-07-05 10:04 | obilodeau | Assigned To | => obilodeau |
2011-09-21 22:20 | obilodeau | Fixed in Version | +1 => 3.0.0 |
2011-09-21 22:20 | obilodeau | Note Added: 0002274 | |
2011-09-21 22:21 | obilodeau | Status | resolved => closed |
2011-10-24 20:24 | obilodeau | Target Version | +1 => 3.0.0 |