Feature #1482
Captive Portal support for a configurable RADIUS NAS ID
| Status: | Feedback | Start date: | 04/26/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Affected version: | All | Affected Architecture: |
Description
When running network traces to examine the packets sent/received during Captive Portal authentication and accounting with RADIUS,
I noticed that pfSense Captive Portal uses the local host and domain name for the RADIS NAS ID. I can see this is set in /etc/inc/cativeposrtl.inc
in the function getNasID().
Do you intend to make this a configurable option?
This would help users migrating from DD-WRT WiFiGator configurations, such as myself :-)
You could implement the code here - http://mike.eire.ca/2010/08/25/setting-nas-id-on-pfsense/
Thanks, Richard
Associated revisions
Ticket #1482 - set the source to an interface that is inside the subnet definition
IPSEC keep alive pinger using the wrong source IP address
Ticket #1482
History
#1
Updated by Chris Buechler about 2 years ago
- Project changed from pfSense Packages to pfSense
#2
Updated by Chris Buechler about 2 years ago
- Assignee deleted (
Ermal Luçi)
#3
Updated by Richard Gate about 2 years ago
Hi just found out that the code in /etc/inc/radius.inc function putStandardAttributes() does not call the getNasId() function but works out the NAS ID for itself in the same way that getNasId() does. So it will need updating to call getNasId() in a similar way that getNasIp() is a few lines before before.
Hope this helps, Richard
#4
Updated by Jim P about 1 year ago
- Status changed from New to Feedback
There have been NAS IP options for CP in the code base for a while now.
#5
Updated by Richard Gate about 1 year ago
BTW its "NAS ID" not "NAS IP".
Assuming that was a typo, where can you set the "NAS ID" in the CP configuration?
#6
Updated by Michael Newton about 1 year ago
- File nasid.patch
added
We're just putting together our first 2.0 boxes; it's currently untested, but I've attached the patch we're planning to try, based on our patch for 1.23 (that's my web page cited in the original report.) It would be nice to get this option added to the code.
#8
Updated by Michael Newton 4 months ago
Seems the patch I submitted has disappeared; if there is still interest I will submit a pull request at github.com to get this into 2.1.
In the meantime, the patch for 2.01 and 2.02 is here: http://mike.eire.ca/2012/04/17/setting-nas-id-on-pfsense-2/
#9
Updated by Richard Gate 3 months ago
I'd like to see the 2.1 patch get in there. Richard.
#10
Updated by Ermal Luçi 3 months ago
Please send a pull request on github as everyone else since its easier to merge/review/...
#11
Updated by Michael Newton 3 months ago
#12
Updated by Ermal Luçi 3 months ago
Merged thank you for the pull request.