Can anyone tell me why I am getting trashed passwords when attempting to authenticate? Login incorrect: [nickm/d\313f`&\247+>4\203\360/\367] Nick Marino - IT Solutions
what does radiusd.conf says about encryption lines? it is not really trashes, it is encrypted. -----Original Message----- From: freeradius-users-bounces+mnisay=aim-consultants.com@lists.freeradius.org [mailto:freeradius-users-bounces+mnisay=aim-consultants.com@lists.freeradius .org] On Behalf Of Nick Marino Sent: Tuesday, February 07, 2006 10:39 AM To: freeradius-users@lists.freeradius.org Subject: Auth question Can anyone tell me why I am getting trashed passwords when attempting to authenticate? Login incorrect: [nickm/d\313f`&\247+>4\203\360/\367] Nick Marino - IT Solutions - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.2/252 - Release Date: 2/6/2006 -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.2/252 - Release Date: 2/6/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.2/252 - Release Date: 2/6/2006
Can anyone tell me why I am getting trashed passwords when attempting to authenticate?
Login incorrect: [nickm/d\313f`&\247+>4\203\360/\367] Looks like your secrets in clients.conf don't match what your NAS has.
-- Lewis Bergman Texas Communications 4309 Maple St. Abilene, TX 79602-8044 Off. 325-691-1301 Cell 325-439-0533 fax 325-695-6841
Nick Marino - IT Solutions ----- Original Message ----- From: "Lewis Bergman" <lbergman@wtxs.net> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Tuesday, February 07, 2006 5:56 AM Subject: [radius] Re: Auth question
Can anyone tell me why I am getting trashed passwords when attempting to authenticate?
Login incorrect: [nickm/d\313f`&\247+>4\203\360/\367] Looks like your secrets in clients.conf don't match what your NAS has.
No the secret in my clients.conf is the same as whats in my NAS, I even reset the password on the nas to be sure. Wierd thing is if I do a test on the user account using Dialup Admin it works perfectly and the password is handled properly. Only when NAS send the request to FR does it generate that garbled password.
Maybe you are not loading the right dictionary for your NAS? On Feb 7, 2006, at 4:36 PM, Nick Marino wrote:
Nick Marino - IT Solutions ----- Original Message ----- From: "Lewis Bergman" <lbergman@wtxs.net> To: "FreeRadius users mailing list" <freeradius- users@lists.freeradius.org> Sent: Tuesday, February 07, 2006 5:56 AM Subject: [radius] Re: Auth question
Can anyone tell me why I am getting trashed passwords when attempting to authenticate?
Login incorrect: [nickm/d\313f`&\247+>4\203\360/\367] Looks like your secrets in clients.conf don't match what your NAS has.
No the secret in my clients.conf is the same as whats in my NAS, I even reset the password on the nas to be sure. Wierd thing is if I do a test on the user account using Dialup Admin it works perfectly and the password is handled properly. Only when NAS send the request to FR does it generate that garbled password.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/ list/users.html
Nick Marino - IT Solutions ----- Original Message ----- From: "futhwo" <futhwo@gmail.com> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Tuesday, February 07, 2006 9:57 AM Subject: Re: [radius] Re: Auth question
Maybe you are not loading the right dictionary for your NAS?
On Feb 7, 2006, at 4:36 PM, Nick Marino wrote:
that could be possible, the only one that is being included is the compat and freeradius and other than whats in the main dictionary file itself. When I try to include the ascend dictionary it throws errors about duplicate values.
"Nick Marino" <nickm@kryptontech.com> wrote:
that could be possible, the only one that is being included is the compat and freeradius and other than whats in the main dictionary file itself.
The dictionaries have nothing to do with the passwords or shared secrets.
When I try to include the ascend dictionary it throws errors about duplicate values.
The ascend dictionary should be included by default, but not all of it. Because there *are* duplicate values. Alan DeKok.
Nick Marino - IT Solutions ----- Original Message ----- From: "Alan DeKok" <aland@ox.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Tuesday, February 07, 2006 11:49 AM Subject: Re: [radius] Re: Auth question
"Nick Marino" <nickm@kryptontech.com> wrote:
that could be possible, the only one that is being included is the compat and freeradius and other than whats in the main dictionary file itself.
The dictionaries have nothing to do with the passwords or shared secrets.
When I try to include the ascend dictionary it throws errors about duplicate values.
The ascend dictionary should be included by default, but not all of it. Because there *are* duplicate values.
Alan DeKok.
Yes thank you. I already corrected that problem.
"Nick Marino" <nickm@kryptontech.com> wrote:
Only when NAS send the request to FR does it generate that garbled password.
Then the shared secret is wrong. Or, there's a bug in the server that mangles the password only for that NAS. Which is more likely? Alan DeKok.
Nick Marino - IT Solutions ----- Original Message ----- From: "Alan DeKok" <aland@ox.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Tuesday, February 07, 2006 11:50 AM Subject: Re: [radius] Re: Auth question
"Nick Marino" <nickm@kryptontech.com> wrote:
Only when NAS send the request to FR does it generate that garbled password.
Then the shared secret is wrong.
Or, there's a bug in the server that mangles the password only for that NAS.
Which is more likely?
Alan DeKok. -
Its more likely that the password is wrong but, I am sure that they are the same. Like I said I even reset the password in the nas to make sure. I will check again but I dont think that is the problem. Shared secret has been the same in the nas for 3 years now and it has always worked. This just started after upgrading to the newest version of FR 1.1.0. Is there a place that I am missing that should have the shared secret in it that I havent changed. I hate to ask but exactly what all files need the shared password in it. clients.conf and where else? This just started after upgrading to the newest version of FR.
The only files I know of that use the secret password are clients.conf and proxy.conf. Make sure your clients.conf has an entry for your NAS with the correct IP address and the correct secret. I don't think you'll need to touch the proxy.conf file; its used for proxying RADIUS requests that successfully reach you to another RADIUS server, and you apparently aren't receving requests successfully. On 2/7/06, Nick Marino <nickm@kryptontech.com> wrote:
Nick Marino - IT Solutions ----- Original Message ----- From: "Alan DeKok" <aland@ox.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Tuesday, February 07, 2006 11:50 AM Subject: Re: [radius] Re: Auth question
"Nick Marino" <nickm@kryptontech.com> wrote:
Only when NAS send the request to FR does it generate that garbled password.
Then the shared secret is wrong.
Or, there's a bug in the server that mangles the password only for that NAS.
Which is more likely?
Alan DeKok. -
Its more likely that the password is wrong but, I am sure that they are the same. Like I said I even reset the password in the nas to make sure. I will check again but I dont think that is the problem.
Shared secret has been the same in the nas for 3 years now and it has always worked. This just started after upgrading to the newest version of FR 1.1.0.
Is there a place that I am missing that should have the shared secret in it that I havent changed. I hate to ask but exactly what all files need the shared password in it. clients.conf and where else?
This just started after upgrading to the newest version of FR.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Yes I dont think its a NAS problem at all. The garbled password you are seeing that I sent is the users actual password. When that request comes from the nas and rlm_pap tries you auth it, the password is showing up like that. if you look at what I posted you will see it is a username/password pair and the password is getting garbled. Login incorrect: [nickm/d\313f`&\247+>4\203\360/\367] Also I stated if I test it from Dialup admin using the same shared secret for nas it works fine and the password is not garbled. Only when it comes from the nas to FR. The packets are being accepted from the nas, that is not the issue. To prove to myself, I set in the users file DEFAULT = Authtype := Accept so it will let everyting thing go through and it does. The packets come from the NAS and althought they still have garbled passwords when FR process it in rlm_pap it allows them to connect due to the DEFUALT I have set in the users file. At that point the user logs in and they show up in Dialup admin as they should. Even the accounting packets work from that point on. Nick Marino - IT Solutions ----- Original Message ----- From: "Andrew Browning" <drew826@gmail.com> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Tuesday, February 07, 2006 1:56 PM Subject: Re: [radius] Re: Auth question
The only files I know of that use the secret password are clients.conf and proxy.conf. Make sure your clients.conf has an entry for your NAS with the correct IP address and the correct secret. I don't think you'll need to touch the proxy.conf file; its used for proxying RADIUS requests that successfully reach you to another RADIUS server, and you apparently aren't receving requests successfully.
On 2/7/06, Nick Marino <nickm@kryptontech.com> wrote:
Nick Marino - IT Solutions ----- Original Message ----- From: "Alan DeKok" <aland@ox.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Tuesday, February 07, 2006 11:50 AM Subject: Re: [radius] Re: Auth question
"Nick Marino" <nickm@kryptontech.com> wrote:
Only when NAS send the request to FR does it generate that garbled password.
Then the shared secret is wrong.
Or, there's a bug in the server that mangles the password only for that NAS.
Which is more likely?
Alan DeKok. -
Its more likely that the password is wrong but, I am sure that they are the same. Like I said I even reset the password in the nas to make sure. I will check again but I dont think that is the problem.
Shared secret has been the same in the nas for 3 years now and it has always worked. This just started after upgrading to the newest version of FR 1.1.0.
Is there a place that I am missing that should have the shared secret in it that I havent changed. I hate to ask but exactly what all files need the shared password in it. clients.conf and where else?
This just started after upgrading to the newest version of FR.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.2/252 - Release Date: 2/6/2006
"Nick Marino" <nickm@kryptontech.com> wrote:
Its more likely that the password is wrong but, I am sure that they are the same.
If the password is wrong, then you'll see the wrong password, rather than ranbom binary nonsense.
Shared secret has been the same in the nas for 3 years now and it has always worked. This just started after upgrading to the newest version of FR 1.1.0.
That's not good. What happens when you use radclient from 1.0.5 to the 1.1.0 server?
Is there a place that I am missing that should have the shared secret in it that I havent changed. I hate to ask but exactly what all files need the shared password in it. clients.conf and where else?
Nowhere else. Alan DeKok.
participants (6)
-
Alan DeKok -
Andrew Browning -
futhwo -
Lewis Bergman -
mnisay -
Nick Marino