| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001732 | PacketFence | radius | public | 2013-10-10 14:46 | 2013-10-10 14:47 |
|
| Reporter | dwuelfrath | |
| Assigned To | dwuelfrath | |
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | assigned | Resolution | open | |
| Platform | | OS | | OS Version | |
| Product Version | 4.0.6-2 | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0001732: Using NAS-IP-Address for managing RADIUS equipment |
| Description | We are currently validating is a network equipment is managed by PacketFence (IP is part of switches list) by using the NAS-IP-Address in the RADIUS request. We are using the incoming IP of the Access-Request to do the secret check (which is OK) but after that, we use the NAS-IP-Address to refer to that network equipment. |
| Additional Information | NAS-IP-Address should not be used to initiate communication with network equipment. We should base ourselves on the incoming IP address used for the Access-Request at all time.
Will have to "refactor" the flow of RADIUS to make the correct distinguition between the two. |
| Tags | No tags attached. |
|
| fixed in git revision | |
| fixed in mtn revision | |
|
| Attached Files | |
|
Relationships 
Relationships 