(RADIATOR) Radiator freezing intermitantly

[Hugh Irvine]

Hello Brian -

On machines with multiple interfaces, this is usually due to the radius 
response being sent back to the client from a different IP address to 
that from which the request was received (ie the response was sent via 
a different interface).

Using a sniffer to check the packet flow is usually very helpful 
(snoop, tcpdump, ethereal, ...).

regards

Hugh


On Friday, Jun 20, 2003, at 23:12 Australia/Melbourne, Brian Fisk wrote:

> We had more troubles yesterday and the problem that is happening is 
> when we
> have radiator setup to bind on a secondary ip of the machine.  When I 
> took
> out the bind address statement, which should make radiator listen on 
> all
> ip's, it still wouldn't work.  I had to set our dialup equipment to 
> use the
> base ip of the machine and then it started working.  When a user tried 
> to
> dial up, they would authenticate, as I could see in my authlog, but the
> dialup equipment kept authenticating them for around 3-4 times before 
> it
> hung up on them.  The dialup equipment (total control) was giving me 
> error
> messages that according to the total control website, said that the 
> secret
> key was a mismatch.  I think it's an ip issue with the machine but we 
> will
> find out more from testing on monday.
>
> Brian Fisk
>
>
>
> ----- Original Message -----
> From: "Hugh Irvine" <hugh at open.com.au>
> To: "Brian Fisk" <bfisk at lazerlink.com>
> Cc: <radiator at open.com.au>
> Sent: Thursday, June 19, 2003 8:03 PM
> Subject: Re: (RADIATOR) Radiator freezing intermitantly
>
>
>>
>> Hello Brian -
>>
>> I will need to see a copy of the configuration file (no secrets)
>> together with a trace 4 debug from Radiator showing what is happening.
>>
>> There is also a FAQ item regarding Redhat 8 here:
>>
>> http://www.open.com.au/radiator/faq.html#127
>>
>> regards
>>
>> Hugh
>>
>>
>> On Friday, Jun 20, 2003, at 02:20 Australia/Melbourne, Brian Fisk 
>> wrote:
>>
>>> I have been running radiator on the same server for the last 3 years
>>> and it
>>> worked perfect.  I am now setting up radiator 3.6 on another server
>>> using
>>> the old config file which was version 2.18.1
>>>
>>> I am noticing that radiator will just freeze up for a period of 5
>>> minutes or
>>> so.  Is there any incompatabilities between the versions for the 
>>> config
>>> file, or can someone suggest a way of logging to diagnose the 
>>> problem?
>>>
>>> I am running Redhat 8.0 Linux server1 2.4.18-24.8.0smp #1 SMP Fri Jan
>>> 31
>>> 06:03:47 EST 2003 i686 i686 i386 GNU/Linux)
>>>
>>>
>>> ===
>>> Archive at http://www.open.com.au/archives/radiator/
>>> Announcements on radiator-announce at open.com.au
>>> To unsubscribe, email 'majordomo at open.com.au' with
>>> 'unsubscribe radiator' in the body of the message.
>>>
>>>
>>
>> NB: have you included a copy of your configuration file (no secrets),
>> together with a trace 4 debug showing what is happening?
>>
>> -- 
>> Radiator: the most portable, flexible and configurable RADIUS server
>> anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
>> -
>> Nets: internetwork inventory and management - graphical, extensible,
>> flexible with hardware, software, platform and database independence.
>>
>>
>
>

NB: have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.