Hi everyone: I'm using Ipswitch's What's Up Gold to monitor my network. I have it set to notify me when certain things in my network go down etc... I have it set to monitor Freeradius. I put an entry into my clients.conf file to give the What's Up Gold computer access to send a request to Freeradius. Here is what's happening... my What's Up Gold keeps telling me that my Freeradius is down when indeed it's not. I'm guessing that when a request gets sent from What's Up Gold to Freeradius, it is not getting there or something. I checked my radius logs and here is an example of an entry i get when What's Up Gold sends a request to Freeradius... Mon Oct 3 10:22:44 2005 : Auth: Login incorrect: [TEST/L\200\212\3101\215\277&\320\350\345\373\351\201\031\215] (from client old port 0) I don't know if the above will help any, but i thought i should include it in this post. Also, this problem does not always happen. It's kind of sporradic. There are lots of times when What's Up Gold sends a request to Freeradius and i get no errors. My worry is this... are my customers having to dial up several times before getting connected? Since Freeradius won't accept all requests from What's Up Gold, who's to say that it is accepting dial in requests from all of my customers all of the time? Any help or insight would be very much appreciated. Thanks! Linda Pagillo Director of Technical Services N2 The Net, LLC lpagillo@n2thenet.com 931-372-9179
Linda Pagillo said:
Hi everyone:
I'm using Ipswitch's What's Up Gold to monitor my network. I have it set to notify me when certain things in my network go down etc... I have it set to monitor Freeradius. I put an entry into my clients.conf file to give the What's Up Gold computer access to send a request to Freeradius. Here is what's happening... my What's Up Gold keeps telling me that my Freeradius is down when indeed it's not. I'm guessing that when a request gets sent from What's Up Gold to Freeradius, it is not getting there or something. I checked my radius logs and here is an example of an entry i get when What's Up Gold sends a request to Freeradius...
Mon Oct 3 10:22:44 2005 : Auth: Login incorrect: [TEST/L\200\212\3101\215\277&\320\350\345\373\351\201\031\215] (from client old port 0)
I don't know if the above will help any, but i thought i should include it in this post.
Also, this problem does not always happen. It's kind of sporradic. There are lots of times when What's Up Gold sends a request to Freeradius and i get no errors.
My worry is this... are my customers having to dial up several times before getting connected? Since Freeradius won't accept all requests from What's Up Gold, who's to say that it is accepting dial in requests from all of my customers all of the time?
Any help or insight would be very much appreciated. Thanks! run it in debug mode and watch what happens when it fails. -- Lewis Bergman Texas Communications 4309 Maple ST. Abilene, TX 79602 325-691-3301
Good morning Mr. DeKok: Thank you for your reply. Could you please tell me what i need to do to correct this issue? Which file do i have to fix? ----- Original Message ----- From: "Alan DeKok" <aland@ox.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Monday, October 03, 2005 6:29 PM Subject: Re: What's Up Gold and Freeradius
"Linda Pagillo" <linda@n2thenet.com> wrote:
Mon Oct 3 10:22:44 2005 : Auth: Login incorrect: = [TEST/L\200\212\3101\215\277&\320\350\345\373\351\201\031\215] (from = client old port 0)
The shared secret on the RADIUS client is wrong.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Good morning Mr. DeKok:
Thank you for your reply. Could you please tell me what i need to do to correct this issue? Which file do i have to fix?
clients.conf is where you put the shared secret for the client to use. So, either fix the shared secret there to match your client, or change the client to match the secret listed there.
----- Original Message ----- From: "Alan DeKok" <aland@ox.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Monday, October 03, 2005 6:29 PM Subject: Re: What's Up Gold and Freeradius
"Linda Pagillo" <linda@n2thenet.com> wrote:
Mon Oct 3 10:22:44 2005 : Auth: Login incorrect: = [TEST/L\200\212\3101\215\277&\320\350\345\373\351\201\031\215] (from = client old port 0)
The shared secret on the RADIUS client is wrong.
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
Mr. Dekok: I forgot to add this... I don't mean to question your knowledge because i know you are the programmer, but you said that the shared secret on the RADIUS client is wrong. Wouldn't this cause radius not to respond to What's Up Gold all the time instead of only some of the time? Thanks again. ----- Original Message ----- From: "Alan DeKok" <aland@ox.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Sent: Monday, October 03, 2005 6:29 PM Subject: Re: What's Up Gold and Freeradius
"Linda Pagillo" <linda@n2thenet.com> wrote:
Mon Oct 3 10:22:44 2005 : Auth: Login incorrect: = [TEST/L\200\212\3101\215\277&\320\350\345\373\351\201\031\215] (from = client old port 0)
The shared secret on the RADIUS client is wrong.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
"Linda Pagillo" <linda@n2thenet.com> wrote:
I forgot to add this... I don't mean to question your knowledge because i know you are the programmer, but you said that the shared secret on the RADIUS client is wrong. Wouldn't this cause radius not to respond to What's Up Gold all the time instead of only some of the time? Thanks again.
If the shared secret is wrong, then the server can't tell (due to poor design of the RADIUS protocol), and it will respond with Access-Reject. But yes, if you don't change the configuration of the server or the client, then the behavior should always be the same. I don't know why it's different. The log message you posted, however, is pretty definitive. Nonsense characters in the password are almost always caused by an incorrect shared secret. Alan DeKok.
participants (4)
-
Alan DeKok -
Dusty Doris -
Lewis Bergman -
Linda Pagillo