I've tracked down the problem and pushed a fix to the v3.0.x branch on GitHub. Luckily, the issue was simple.
I thought I must be missed something in the setup. So it's just a small bug. Does the fix has a corresponding commit of the v3.0.x branch on GitHub ?
On the down side, it looks like that particular module has been broken for a very long time now. That's unfortunate.
May most people just use the clients.conf file or use mysql to store dynamic clients. By the way, what dos the "rlm" in module names stand for ? I guess "r" stands radius, “m” stands module, then which words does the "l" stands ? On Tue, Feb 26, 2019 at 11:19 PM Alan DeKok <aland@deployingradius.com> wrote:
On Feb 26, 2019, at 8:28 AM, smith john <johnerickson663@gmail.com> wrote:
In fact, I first tried FreeRADIUS 3.0.13 on centos 7.6. Because v3.0.13 doesn't work, I guess that v2 may work. In addition, for all the test, I store the users in mysql, but don't store nas clients in mysql. When store nas clients in mysql, dynamic-clients does work.
So I test v3.0.13 on centos 7.6 again. This is the steps:
That's a good description, thanks.
I've tracked down the problem and pushed a fix to the v3.0.x branch on GitHub. Luckily, the issue was simple.
On the down side, it looks like that particular module has been broken for a very long time now. That's unfortunate.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html