PacketFence - BTS - PacketFence | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001781 | PacketFence | core | public | 2014-04-01 16:01 | 2014-04-01 16:02 |
| Reporter | dwuelfrath | ||||
| Assigned To | dwuelfrath | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Platform | OS | OS Version | |||
| Product Version | 4.1.0 | ||||
| Target Version | Fixed in Version | ||||
| fixed in git revision | |||||
| fixed in mtn revision | |||||
| Summary | 0001781: Wrong workflow when trapping.registration is disabled | ||||
| Description | - Evaluation on whether registration feature is enabled or not (trapping.registration in pf.conf) is made in getRegistrationVlan and that is kind of wrong. That evaluation should be done (at this point) in fetchVlanForNode rather than going in getRegistrationVlan and exiting saying "we do not use registration" and then going in getNormalVlan. - When we are not using registration feature (trapping.registration in pf.conf) and a new node is connecting on the network, no category/role is being assigned to that node so getNormalVlan is unable to successfully assign a VLAN based on that "no role". | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2014-04-01 16:01 | dwuelfrath | New Issue | |||
| 2014-04-01 16:02 | dwuelfrath | Assigned To | => dwuelfrath | ||
| 2014-04-01 16:02 | dwuelfrath | Status | new => assigned | ||
| 2014-04-01 16:02 | dwuelfrath | Product Version | => 4.1.0 | ||
| There are no notes attached to this issue. |