Freeradius 3.0 on Pfsense 2.3.4 problems
-
You can probably just do a full 64bit install to the CF card and it will be fine for years as long as you remove the SWAP partition and move /var and /tmp to RAM after the install.
Given that you almost certainly can run 64bit it's pointless trying to diagnose the initial issue until you're running 2.4.4p2.
Steve
-
Thanks for the responses. I will be doing the re-install later today/tonight and get back to you tomorrow. I'll try to find the appropriate install instructions to implement the upgrade/re-install.
-
Ok guys I have upgraded to the lastest of Pfsense, so my router is now running 2.4.4-RELEASE-p2 (amd64).
I had done a backup from the old version and restored it to the new version. Since the upgrade I have an additional problem. The PPPoE client that used to connect normally is now connecting and disconnecting every 1 minutes. I had to change the IP address under Freeradius/NAS/Clients to "*" for it to give the behavior it is now doing. If I put the IP address of the PPPoE server in there it does not work, and get a message in System Log, something about "Unknown Client". In the previous version I had the IP address of the PPPoE server. Maybe now I need to put in additional config for it to stay connected?
-
I think we'll need to see some screenshots of you config to diagnose that.
Steve
-
Screen shots of what part of the config?
I have figured out that this problem has to do with Freeradius I noted that if I disable the use of freeradius for authentication my connection to the PPPoE server stays up.
-
Ok well check the logs. It might show why it's disconnecting after a minute.
Otherwise we'll need as much detail as possible here. The PPPoE config and freeradius config at least I would think.
Steve
-
Here are the screenshots of the Freeradius config and PPPoE server. I had disabled Radius authentication to let PPPoE work.
-
To see any possible FreeRadius issue :
Stop FreeRadius in the GUI.
Enter console - option 8.
Start FreeRadius by hand using debug mode.radiusd -X
(that is a capital X)
Note :
To eliminate possible future troubles :
Don't use the 8000 port range. -
here is a sample of what I received when I ran radiusd -X from console:
I had re-enabled PPPoE server to use radius authentication.
-
That same error keeps looping every minute or so.