Bug #853
closedPPPoE Server radius config not applied
100%
Description
Just playing with pfSense (2.0-BETA4 (i386) built on Thu Aug 26 23:39:42 EDT 2010) and installed the freeradius package to run as a pppoe backend. It wasn't working and I discovered that the radius settings weren't being applied to the mpd conf file. This trivial patch fixes it for me;
--- vpn.inc.old 2010-08-27 21:21:30.000000000 +1200 +++ vpn.inc 2010-08-27 21:21:42.000000000 +1200 @@ -1274,9 +1274,9 @@ $mpdconf .= " set ipcp dns " . join(" ", $syscfg['dnsserver']) . "\n"; } - if (isset ($pppoecfg['radius']['enable'])) { + if (isset ($pppoecfg['radius']['server']['enable'])) { $mpdconf .=<<<EOD - set radius server {$pppoecfg['server']['ip']} "{$pppoecfg['radius']['secret']}" + set radius server {$pppoecfg['radius']['server']['ip']} "{$pppoecfg['radius']['server']['secret']}" set radius retries 3 set radius timeout 10 set auth enable radius-auth
Updated by Jim Pingle over 14 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 37d7de2d2b073545c18d95619d633fdaa5d4d7f4.
Updated by Chris Buechler over 14 years ago
- Category set to PPPoE Server
- Target version set to 2.0
Updated by Anonymous over 14 years ago
Thanks for the super quick fix. I can confirm that this is working now.
There are a few other fields on that page which aren't applied to (ports, update interval, etc.), I'll see if I can sort those out too when I get a chance.
Updated by Chris Buechler almost 14 years ago
- Status changed from Feedback to New
Ports for RADIUS and accounting are still not used
Updated by Ermal Luçi almost 14 years ago
- Status changed from New to Feedback
Added the radius port and accounting port to the config.
https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/c3583058a0c2cd89ceacbbbcceb68a976e07a890
Updated by Ermal Luçi almost 14 years ago
- Status changed from Feedback to Resolved