I am running CentOS 7. I am setting up FreeRADIUS again. Documenting it step-by-step. I am only working the test user at the moment but I am getting the following error: Tue Oct 24 19:30:28 2017 : Debug: (0) User-Name = "bob"Tue Oct 24 19:30:28 2017 : Debug: (0) User-Password = "hello"Tue Oct 24 19:30:28 2017 : Debug: (0) NAS-IP-Address = 10.150.10.40Tue Oct 24 19:30:28 2017 : Debug: (0) NAS-Port = 0Tue Oct 24 19:30:28 2017 : Debug: (0) Message-Authenticator = 0x7c0ca39b4c7952c808f3602792b02eb6Tue Oct 24 19:30:28 2017 : Debug: (0) session-state: No State attributeTue Oct 24 19:30:28 2017 : Debug: (0) Empty authorize section. Using default return values.Tue Oct 24 19:30:28 2017 : ERROR: (0) No Auth-Type found: rejecting the user via Post-Auth-Type = RejectTue Oct 24 19:30:28 2017 : Debug: (0) Failed to authenticate the userTue Oct 24 19:30:28 2017 : Auth: (0) Login incorrect (No Auth-Type found: rejecting the user via Post-Auth-Type = Reject): [bob/hello] (from client localhost port 0)Tue Oct 24 19:30:28 2017 : Debug: (0) Using Post-Auth-Type RejectTue Oct 24 19:30:28 2017 : Debug: (0) Post-Auth-Type sub-section not found. Ignoring.Tue Oct 24 19:30:28 2017 : Debug: (0) Delaying response for 1.000000 secondsTue Oct 24 19:30:28 2017 : Debug: Thread 3 waiting to be assigned a requestTue Oct 24 19:30:28 2017 : Debug: Waking up in 0.6 seconds.Tue Oct 24 19:30:29 2017 : Debug: (0) Sending delayed responseTue Oct 24 19:30:29 2017 : Debug: (0) Sent Access-Reject Id 16 from 10.150.10.40:1812 to 10.150.10.40:43969 length 20Tue Oct 24 19:30:29 2017 : Debug: Waking up in 3.9 seconds.Tue Oct 24 19:30:33 2017 : Debug: (0) Cleaning up request packet ID 16 with timestamp +67Tue Oct 24 19:30:33 2017 : Info: Ready to process requests Here is my config from /etc/raddb/users:bob Auth-Type := Accept Cleartext-Password := "hello" Reply-Message := "Hello, %{User-Name}" I tried not using a client config and then ended up putting in the following: client testing { ipaddr = 10.150.0.0/16 secret = testing123 } radtest bob hello 10.150.10.40:1812 0 testing123Sent Access-Request Id 119 from 0.0.0.0:56648 to 10.150.10.40:1812 length 73 User-Name = "bob" User-Password = "hello" NAS-IP-Address = 10.150.10.40 NAS-Port = 0 Message-Authenticator = 0x00 Cleartext-Password = "hello"Received Access-Reject Id 119 from 10.150.10.40:1812 to 0.0.0.0:0 length 20(0) -: Expected Access-Accept got Access-Reject Is there something I missed in the configuration? Thank you,
On Oct 24, 2017, at 8:36 PM, Andrew Meyer via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
I am running CentOS 7. I am setting up FreeRADIUS again. Documenting it step-by-step. I am only working the test user at the moment but I am getting the following error:
Please post straight text. Your mailer is mangling the text you're posing to the list. But the main thing is:
: Debug: (0) Empty authorize section. Using default return values.
You've edited the default configuration and broken it. Don't do that. Start from the default configuration. It works. Then, make small changes. Test them before making more changes.
Here is my config from /etc/raddb/users:bob Auth-Type := Accept Cleartext-Password := "hello" Reply-Message := "Hello, %{User-Name}"
Don't set "Auth-Type := Accept". It's wrong, and won't do what you want.
Is there something I missed in the configuration?
The default configuration got completely destroyed. This makes the server not work. Use the default configuration. It works. Alan DeKok.
Ok, I did what you said, I started fresh. The only thing I have put in the /etc/raddb/radiusd.conf is a listen directive. So now in the logs i'm getting this: Tue Oct 24 20:26:54 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udpTue Oct 24 20:26:59 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udpTue Oct 24 20:27:04 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udp On Tuesday, October 24, 2017, 7:51:45 PM CDT, Alan DeKok <aland@deployingradius.com> wrote:
On Oct 24, 2017, at 8:36 PM, Andrew Meyer via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
I am running CentOS 7. I am setting up FreeRADIUS again. Documenting it step-by-step. I am only working the test user at the moment but I am getting the following error:
Please post straight text. Your mailer is mangling the text you're posing to the list. But the main thing is:
: Debug: (0) Empty authorize section. Using default return values.
You've edited the default configuration and broken it. Don't do that. Start from the default configuration. It works. Then, make small changes. Test them before making more changes.
Here is my config from /etc/raddb/users:bob Auth-Type := Accept Cleartext-Password := "hello" Reply-Message := "Hello, %{User-Name}"
Don't set "Auth-Type := Accept". It's wrong, and won't do what you want.
Is there something I missed in the configuration?
The default configuration got completely destroyed. This makes the server not work. Use the default configuration. It works. Alan DeKok.
So I also added a client config and told it to allow my network to have the ability to communicate w/ FreeRADIUS. Tue Oct 24 21:17:58 2017 : Auth: (0) Login incorrect (No Auth-Type found: rejecting the user via Post-Auth-Type = Reject): [bob/hello] (from client ASM port 0) Tue Oct 24 21:18:04 2017 : Auth: (1) Login incorrect (No Auth-Type found: rejecting the user via Post-Auth-Type = Reject): [bob/hello] (from client ASM port 0) There is something i'm missing. I feel like it needs to be in the /etc/raddb/users file. Like a default config statement. On Tuesday, October 24, 2017, 8:27:47 PM CDT, Andrew Meyer via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote: Ok, I did what you said, I started fresh. The only thing I have put in the /etc/raddb/radiusd.conf is a listen directive. So now in the logs i'm getting this: Tue Oct 24 20:26:54 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udpTue Oct 24 20:26:59 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udpTue Oct 24 20:27:04 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udp On Tuesday, October 24, 2017, 7:51:45 PM CDT, Alan DeKok <aland@deployingradius.com> wrote:
On Oct 24, 2017, at 8:36 PM, Andrew Meyer via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
I am running CentOS 7. I am setting up FreeRADIUS again. Documenting it step-by-step. I am only working the test user at the moment but I am getting the following error:
Please post straight text. Your mailer is mangling the text you're posing to the list. But the main thing is:
: Debug: (0) Empty authorize section. Using default return values.
You've edited the default configuration and broken it. Don't do that. Start from the default configuration. It works. Then, make small changes. Test them before making more changes.
Here is my config from /etc/raddb/users:bob Auth-Type := Accept Cleartext-Password := "hello" Reply-Message := "Hello, %{User-Name}"
Don't set "Auth-Type := Accept". It's wrong, and won't do what you want.
Is there something I missed in the configuration?
The default configuration got completely destroyed. This makes the server not work. Use the default configuration. It works. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
right, from a fresh install. ensure bob in the users file is enabled, then run eg radtest from the local system. that will work. now, add a remote client to the clients.conf , ensure your system firewall is allowing UDP 1812 inbound from that remote IP and run the test from that remote IP (eg simulating a NAS). by default the server will be listening on 1812 on all its interfaces alan
On Oct 24, 2017, at 9:27 PM, Andrew Meyer via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
Ok, I did what you said, I started fresh. The only thing I have put in the /etc/raddb/radiusd.conf is a listen directive. So now in the logs i'm getting this: Tue Oct 24 20:26:54 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udpTue Oct 24 20:26:59 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udpTue Oct 24 20:27:04 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udp]
You've been told repeatedly to fix your messages so that the contents aren't mangled. Despite that, you're still not following instructions. If you don't care enough to post READABLE logs, I don't care to answer your questions. Alan DeKok.
Alan, My apologies. Yahoo defaults to Rich Text and there is no way to set the default to plain text that I can see. However here is my output in plain text. Hope this is legible now. So I also added a client config and told it to allow my network to have the ability to communicate w/ FreeRADIUS. Tue Oct 24 21:17:58 2017 : Auth: (0) Login incorrect (No Auth-Type found: rejecting the user via Post-Auth-Type = Reject): [bob/hello] (from client ASM port 0) Tue Oct 24 21:18:04 2017 : Auth: (1) Login incorrect (No Auth-Type found: rejecting the user via Post-Auth-Type = Reject): [bob/hello] (from client ASM port 0) On Wednesday, October 25, 2017 5:31 AM, Alan DeKok <aland@deployingradius.com> wrote:
On Oct 24, 2017, at 9:27 PM, Andrew Meyer via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
Ok, I did what you said, I started fresh. The only thing I have put in the /etc/raddb/radiusd.conf is a listen directive. So now in the logs i'm getting this: Tue Oct 24 20:26:54 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udpTue Oct 24 20:26:59 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udpTue Oct 24 20:27:04 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udp]
You've been told repeatedly to fix your messages so that the contents aren't mangled. Despite that, you're still not following instructions. If you don't care enough to post READABLE logs, I don't care to answer your questions. Alan DeKok.
Ok, in doing more reading I have made a symbolic link for the default config: cp -v /etc/raddb/sites-available/default /etc/raddb/sites-enabled/ It then started to complain about not having the authentication modules. So I start to copy those over as well. I think I'm heading in the right direction. (Also had to allow freeradius through SELinux) Here is the latest i'm seeing in my logs: Wed Oct 25 10:42:09 2017 : Error: rlm_eap_tls: Failed initializing SSL context Wed Oct 25 10:42:09 2017 : Error: rlm_eap (EAP): Failed to initialise rlm_eap_tls Wed Oct 25 10:42:09 2017 : Error: /etc/raddb/mods-enabled/eap[14]: Instantiation failed for module "eap" On Wednesday, October 25, 2017 8:30 AM, Andrew Meyer via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote: Alan, My apologies. Yahoo defaults to Rich Text and there is no way to set the default to plain text that I can see. However here is my output in plain text. Hope this is legible now. So I also added a client config and told it to allow my network to have the ability to communicate w/ FreeRADIUS. Tue Oct 24 21:17:58 2017 : Auth: (0) Login incorrect (No Auth-Type found: rejecting the user via Post-Auth-Type = Reject): [bob/hello] (from client ASM port 0) Tue Oct 24 21:18:04 2017 : Auth: (1) Login incorrect (No Auth-Type found: rejecting the user via Post-Auth-Type = Reject): [bob/hello] (from client ASM port 0) On Wednesday, October 25, 2017 5:31 AM, Alan DeKok <aland@deployingradius.com> wrote:
On Oct 24, 2017, at 9:27 PM, Andrew Meyer via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
Ok, I did what you said, I started fresh. The only thing I have put in the /etc/raddb/radiusd.conf is a listen directive. So now in the logs i'm getting this: Tue Oct 24 20:26:54 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udpTue Oct 24 20:26:59 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udpTue Oct 24 20:27:04 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udp]
You've been told repeatedly to fix your messages so that the contents aren't mangled. Despite that, you're still not following instructions. If you don't care enough to post READABLE logs, I don't care to answer your questions. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
well, cp -v is not same as ln -s (command) :) try setting selinux to permissive mode first. Eero 2017-10-25 21:01 GMT+03:00 Andrew Meyer via Freeradius-Users < freeradius-users@lists.freeradius.org>:
Ok, in doing more reading I have made a symbolic link for the default config: cp -v /etc/raddb/sites-available/default /etc/raddb/sites-enabled/
It then started to complain about not having the authentication modules. So I start to copy those over as well.
I think I'm heading in the right direction. (Also had to allow freeradius through SELinux)
Here is the latest i'm seeing in my logs: Wed Oct 25 10:42:09 2017 : Error: rlm_eap_tls: Failed initializing SSL context Wed Oct 25 10:42:09 2017 : Error: rlm_eap (EAP): Failed to initialise rlm_eap_tls Wed Oct 25 10:42:09 2017 : Error: /etc/raddb/mods-enabled/eap[14]: Instantiation failed for module "eap"
On Wednesday, October 25, 2017 8:30 AM, Andrew Meyer via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
Alan, My apologies. Yahoo defaults to Rich Text and there is no way to set the default to plain text that I can see. However here is my output in plain text. Hope this is legible now.
So I also added a client config and told it to allow my network to have the ability to communicate w/ FreeRADIUS. Tue Oct 24 21:17:58 2017 : Auth: (0) Login incorrect (No Auth-Type found: rejecting the user via Post-Auth-Type = Reject): [bob/hello] (from client ASM port 0) Tue Oct 24 21:18:04 2017 : Auth: (1) Login incorrect (No Auth-Type found: rejecting the user via Post-Auth-Type = Reject): [bob/hello] (from client ASM port 0)
On Wednesday, October 25, 2017 5:31 AM, Alan DeKok < aland@deployingradius.com> wrote:
On Oct 24, 2017, at 9:27 PM, Andrew Meyer via Freeradius-Users < freeradius-users@lists.freeradius.org> wrote:
Ok, I did what you said, I started fresh. The only thing I have put in the /etc/raddb/radiusd.conf is a listen directive. So now in the logs i'm getting this: Tue Oct 24 20:26:54 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udpTue Oct 24 20:26:59 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udpTue Oct 24 20:27:04 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udp]
You've been told repeatedly to fix your messages so that the contents aren't mangled. Despite that, you're still not following instructions.
If you don't care enough to post READABLE logs, I don't care to answer your questions.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/ list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/ list/users.html
My thought was to copy them instead of doing a symbolic link in case I had to trash the file. On Wednesday, October 25, 2017 2:21 PM, Eero Volotinen <eero.volotinen@iki.fi> wrote: well, cp -v is not same as ln -s (command) :) try setting selinux to permissive mode first. Eero 2017-10-25 21:01 GMT+03:00 Andrew Meyer via Freeradius-Users <freeradius-users@lists.freeradius.org>: Ok, in doing more reading I have made a symbolic link for the default config:
cp -v /etc/raddb/sites-available/ default /etc/raddb/sites-enabled/
It then started to complain about not having the authentication modules. So I start to copy those over as well.
I think I'm heading in the right direction. (Also had to allow freeradius through SELinux)
Here is the latest i'm seeing in my logs: Wed Oct 25 10:42:09 2017 : Error: rlm_eap_tls: Failed initializing SSL context Wed Oct 25 10:42:09 2017 : Error: rlm_eap (EAP): Failed to initialise rlm_eap_tls Wed Oct 25 10:42:09 2017 : Error: /etc/raddb/mods-enabled/eap[ 14]: Instantiation failed for module "eap"
On Wednesday, October 25, 2017 8:30 AM, Andrew Meyer via Freeradius-Users <freeradius-users@lists. freeradius.org> wrote:
Alan, My apologies. Yahoo defaults to Rich Text and there is no way to set the default to plain text that I can see. However here is my output in plain text. Hope this is legible now.
So I also added a client config and told it to allow my network to have the ability to communicate w/ FreeRADIUS. Tue Oct 24 21:17:58 2017 : Auth: (0) Login incorrect (No Auth-Type found: rejecting the user via Post-Auth-Type = Reject): [bob/hello] (from client ASM port 0) Tue Oct 24 21:18:04 2017 : Auth: (1) Login incorrect (No Auth-Type found: rejecting the user via Post-Auth-Type = Reject): [bob/hello] (from client ASM port 0)
On Wednesday, October 25, 2017 5:31 AM, Alan DeKok <aland@deployingradius.com> wrote:
On Oct 24, 2017, at 9:27 PM, Andrew Meyer via Freeradius-Users <freeradius-users@lists. freeradius.org> wrote:
Ok, I did what you said, I started fresh. The only thing I have put in the /etc/raddb/radiusd.conf is a listen directive. So now in the logs i'm getting this: Tue Oct 24 20:26:54 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udpTue Oct 24 20:26:59 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udpTue Oct 24 20:27:04 2017 : Error: Ignoring request to auth address 10.150.10.40 port 1812 from unknown client 10.150.10.40 port 35086 proto udp]
You've been told repeatedly to fix your messages so that the contents aren't mangled. Despite that, you're still not following instructions.
If you don't care enough to post READABLE logs, I don't care to answer your questions.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/ list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/ list/users.html
how did you install the server? I ask because if you do 'make install' it puts ALL the required files into the required places.... all modules, virtual servers, config files etc. I would never ever even consider trying to install the config files by hand - and thats even after a decade of using the software. alan
I installed from CentOS repos. Might have been EPEL. On Wednesday, October 25, 2017 4:21 PM, Alan Buxey <alan.buxey@gmail.com> wrote: how did you install the server? I ask because if you do 'make install' it puts ALL the required files into the required places.... all modules, virtual servers, config files etc. I would never ever even consider trying to install the config files by hand - and thats even after a decade of using the software. alan
On Oct 25, 2017, at 5:29 PM, Andrew Meyer via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
I installed from CentOS repos. Might have been EPEL.
Then someone destroyed the configuration after it was installed. This shouldn't be difficult. By breaking the configuration, you've made work for yourself, and wasted days trying to debug problems which should never have existed. Don't try to "fix" a broken configuration. Delete *everything*, and re-install from scratch. Doing anything else is wasting your time, and ours. Alan DeKok.
So I deleted everything like you suggested. I then went back into the /etc/raddb/radiusd.conf andmade the following change: server radius01 { listen { ipaddr = 127.0.0.1 type = auth } # listen { # ipaddr = 10.150.10.40 # type = auth # } # listen { ipaddr = 127.0.0.1 type = acct } # listen { # ipaddr = 10.150.10.40 # type = acct # } } debug_level=2 I then ran a raidusd -X and tested in another window. Here is my output: radtest -4 -x bob hello localhost 2 testing123 Sent Access-Request Id 88 from 0.0.0.0:53632 to 127.0.0.1:1812 length 73 User-Name = "bob" User-Password = "hello" NAS-IP-Address = 10.150.10.40 NAS-Port = 2 Message-Authenticator = 0x00 Cleartext-Password = "hello" Received Access-Reject Id 88 from 127.0.0.1:1812 to 0.0.0.0:0 length 20 (0) -: Expected Access-Accept got Access-Reject On Wednesday, October 25, 2017 5:28 PM, Alan DeKok <aland@deployingradius.com> wrote: On Oct 25, 2017, at 5:29 PM, Andrew Meyer via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
I installed from CentOS repos. Might have been EPEL.
Then someone destroyed the configuration after it was installed. This shouldn't be difficult. By breaking the configuration, you've made work for yourself, and wasted days trying to debug problems which should never have existed. Don't try to "fix" a broken configuration. Delete *everything*, and re-install from scratch. Doing anything else is wasting your time, and ours. Alan DeKok.
How about reading : http://wiki.freeradius.org/guide/Getting%20Started instead of doing something "random" So delete everything. reinstall radius and follow that guide until you get first Access-Accept ? Eero 2017-10-26 4:16 GMT+03:00 Andrew Meyer via Freeradius-Users < freeradius-users@lists.freeradius.org>:
So I deleted everything like you suggested. I then went back into the /etc/raddb/radiusd.conf andmade the following change:
server radius01 { listen { ipaddr = 127.0.0.1 type = auth }
# listen { # ipaddr = 10.150.10.40 # type = auth # } # listen { ipaddr = 127.0.0.1 type = acct }
# listen { # ipaddr = 10.150.10.40 # type = acct # } }
debug_level=2
I then ran a raidusd -X and tested in another window.
Here is my output: radtest -4 -x bob hello localhost 2 testing123 Sent Access-Request Id 88 from 0.0.0.0:53632 to 127.0.0.1:1812 length 73 User-Name = "bob" User-Password = "hello" NAS-IP-Address = 10.150.10.40 NAS-Port = 2 Message-Authenticator = 0x00 Cleartext-Password = "hello" Received Access-Reject Id 88 from 127.0.0.1:1812 to 0.0.0.0:0 length 20 (0) -: Expected Access-Accept got Access-Reject
On Wednesday, October 25, 2017 5:28 PM, Alan DeKok < aland@deployingradius.com> wrote:
On Oct 25, 2017, at 5:29 PM, Andrew Meyer via Freeradius-Users < freeradius-users@lists.freeradius.org> wrote:
I installed from CentOS repos. Might have been EPEL.
Then someone destroyed the configuration after it was installed.
This shouldn't be difficult. By breaking the configuration, you've made work for yourself, and wasted days trying to debug problems which should never have existed.
Don't try to "fix" a broken configuration. Delete *everything*, and re-install from scratch.
Doing anything else is wasting your time, and ours.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/ list/users.html
On Thu, 2017-10-26 at 01:16 +0000, Andrew Meyer via Freeradius-Users wrote:
So I deleted everything like you suggested. I then went back into the /etc/raddb/radiusd.conf and made the following change:
What version of FreeRADIUS are you using, and how are you installing it, what OS? In the standard config, those settings go in sites-available/default, and are there by default. So once again you shouldn't be doing that. Follow the getting started guide. You need to do very little for the test you are running to work. The default configuration already has a virtual server defined, so there's no reason to add that. The default config already listens on localhost, there's no reason to add that. The only thing that's not enabled in the default config is a user, as that would be a security issue. So you just need to add that. Really, it should be this simple: Download and unpack the source for 3.0.15 from http://freeradius.org/re leases/ ./configure make make install edit the users file (/usr/local/etc/raddb/users) and add a new user 'bob' as a line at the top, like: bob Cleartext-Password := "hello" start the daemon /usr/local/sbin/radiusd -X and run radtest /usr/local/bin/radtest bob hello 127.0.0.1 0 testing123 That's it. -- Matthew
On Oct 25, 2017, at 9:16 PM, Andrew Meyer <andrewm659@yahoo.com> wrote:
So I deleted everything like you suggested. I then went back into the /etc/raddb/radiusd.conf andmade the following change:
The "man" pages, web pages, wiki, and messages on this list describe how to install and configure the server. They go through simple tests. You have chosen to follow none of that.
I then ran a raidusd -X and tested in another window.
Here is my output: radtest -4 -x bob hello localhost 2 testing123
That's not "radiusd -X". Once again, you've made life difficult for yourself. Once again, you've refused to follow simple instructions. I'm done. Alan DeKok.
So I want to apologize for this. I stood up a new installation of CentOS in a VM and tested this w/ default config. It looks like I have a botched installation. I need to completely reinstall the OS. Sorry for the trouble. Thanks! On Thursday, October 26, 2017 6:55 AM, Alan DeKok <aland@deployingradius.com> wrote:
On Oct 25, 2017, at 9:16 PM, Andrew Meyer <andrewm659@yahoo.com> wrote:
So I deleted everything like you suggested. I then went back into the /etc/raddb/radiusd.conf andmade the following change:
The "man" pages, web pages, wiki, and messages on this list describe how to install and configure the server. They go through simple tests. You have chosen to follow none of that.
I then ran a raidusd -X and tested in another window.
Here is my output: radtest -4 -x bob hello localhost 2 testing123
That's not "radiusd -X". Once again, you've made life difficult for yourself. Once again, you've refused to follow simple instructions. I'm done. Alan DeKok.
participants (5)
-
Alan Buxey -
Alan DeKok -
Andrew Meyer -
Eero Volotinen -
Matthew Newton