PacketFence - BTS - PacketFence | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001824 | PacketFence | refactoring | public | 2014-09-12 09:12 | 2014-09-12 09:12 |
| Reporter | juanvalencia | ||||
| Assigned To | |||||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | Linux | OS | CentOS | OS Version | 6.5 |
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| fixed in git revision | |||||
| fixed in mtn revision | |||||
| Summary | 0001824: VoiP phones don't get complete information when they are autoreg for a different method than dhcp. | ||||
| Description | When you connect a VoIP phone and this is autoregister for a method like radius attributes, PF doesn't update OS info because when it detects that is a VoIP base on dhcp it is already register and PF rejects to do something. The same thing happens when is an autoregister violation created. | ||||
| Steps To Reproduce | * Configure a switch to use MAB. * Connect a Phone capable to send Radius attributes of VoIP. * The VoIP is immediately autor-egistered because the Radius Attributes. * The VoIP ask for DHCP, and PF detects that is form the category of VoIP Phones/Adapters. * PF says the device is already auto-register do nothing. | ||||
| Additional Information | PF should update the info of the node in every step that obtains info from the device, even if there is no action to do whit it. In this case the portion of the code, I think in pfsetvlan.pm that rejects to auto-register the device should obtain all the info and pushed into the node_info in the DB. | ||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2014-09-12 09:12 | juanvalencia | New Issue | |||
| There are no notes attached to this issue. |