Re: (RADIATOR) Probs with AccountingHandled

1999-06-15 Thread Anonymous

Hello Bernd,

Thanks for sending us this information. Given your configuration, I think your
proposed solution (with AuthBy TEST) is the best.

We will considermaking some changes for the next release so that Radiator will
acknowledge those types of accounting messages, even if there is are no AuthBy
clauses in a Realm.

Thanks for raising this issue with us.
Cheers.

On Jun 16, 12:45am, Bernd Strehhuber wrote:
> Subject: Re: (RADIATOR) Probs with AccountingHandled
> Hi Mike,
>
> Mike McCauley <[EMAIL PROTECTED]> wrote:
> > This looks like a message from the NAS saying it rebooted or restarted.
>
> yes, the message looks like a reboot message, but the NAS has an uptime of
> about 30 days. I don't know, why this message is send out. ;-)
>
> > Its a bit hard to say without seeing your configuration file, but it sounds
> > like a reasonable response. The best solution would be to arrange for such
> > "realmless" requests to be handled by one of your existing Handlers.
>
> Lets have a short look over my radius.cfg:
>
> 
> # Section 1
> # general things
>
> port, logfiles, pidfiles, dictionary etc.
> 
> # Section 2
> # Clients
>
> 
> Secret  
> DupInterval 120
> IdenticalClients aaa.bbb.ccc.ddd
> 
> 
> # Section 3
> # Realm
>
> 
> MaxSessions 2
> AcctLogFileName %L/cg1.detail
> PasswordLogFileName %L/cg1.log
> RejectHasReason
>
> 
> Filename%D/cg1.db
> 
>
> 
>
> 
> 
> 
>
> 
>
> Each Request come from another Radiator, which acts as a Proxy
> (with Auth RADIUS), and each Request with an Username is rewriten
> to exactly one customergroup. So there is one realm which fits.
>
> I think, the best is to have a DEFAULT Realm which only ACKs the Accounting
> Packets (and not even one Auth-Packet ;-) and logs them into a detail
> Logfile.
>
> But
>
> 
>   AcctLogFileName %L/stupid.detail
>   AccountingHandled
> 
>
> logs the Accounting Requests and doesn't ACK them.
>
> Regards,
>  Bernd
>
> ===
> Archive at http://www.thesite.com.au/~radiator/
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
>-- End of excerpt from Bernd Strehhuber



-- 
Mike McCauley   [EMAIL PROTECTED]
Open System Consultants Pty. LtdUnix, Perl, Motif, C++, WWW
24 Bateman St Hampton, VIC 3188 Australia   http://www.open.com.au
Phone +61 3 9598-0985   Fax   +61 3 9598-0955

Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8, 
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.



Re: (RADIATOR) Probs with AccountingHandled

1999-06-15 Thread Anonymous

Hi Mike,

Mike McCauley <[EMAIL PROTECTED]> wrote:
> This looks like a message from the NAS saying it rebooted or restarted.

yes, the message looks like a reboot message, but the NAS has an uptime of
about 30 days. I don't know, why this message is send out. ;-)

> Its a bit hard to say without seeing your configuration file, but it sounds
> like a reasonable response. The best solution would be to arrange for such
> "realmless" requests to be handled by one of your existing Handlers.

Lets have a short look over my radius.cfg:


# Section 1
# general things

port, logfiles, pidfiles, dictionary etc.

# Section 2
# Clients


Secret  
DupInterval 120
IdenticalClients aaa.bbb.ccc.ddd


# Section 3
# Realm


MaxSessions 2
AcctLogFileName %L/cg1.detail
PasswordLogFileName %L/cg1.log
RejectHasReason


Filename%D/cg1.db










Each Request come from another Radiator, which acts as a Proxy
(with Auth RADIUS), and each Request with an Username is rewriten
to exactly one customergroup. So there is one realm which fits.

I think, the best is to have a DEFAULT Realm which only ACKs the Accounting
Packets (and not even one Auth-Packet ;-) and logs them into a detail
Logfile.

But


  AcctLogFileName %L/stupid.detail
  AccountingHandled


logs the Accounting Requests and doesn't ACK them.

Regards,
 Bernd

===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.



Re: (RADIATOR) Probs with AccountingHandled

1999-06-14 Thread Anonymous

Hello Bernd,

On Jun 11,  6:15pm, Bernd Strehhuber wrote:
> Subject: (RADIATOR) Probs with AccountingHandled
> Hi,
>
> at my setup each customer group has his own Realm. I use 'RewriteUsername'
> to control this. Now, from time to time (no reboot or anything like
> this is done), my NAS (Livingston PM3) send the following Accounting
> Request out:
>
> Acct-Session-Id = ""
> NAS-IP-Address = 
> Acct-Status-Type = Start
> Acct-Delay-Time = 6
> Timestamp = 929071869
>
> As you can see, no username is in this request, so my rewriting doesn't work
> and the request doesn't end up in one of my Realms. It is ignored by
> Radiator an die NAS keeps retransmitting.
This looks like a message from the NAS saying it rebooted or restarted.

>
> Therefor I created a "special Handler":
>
> 
> AcctLogFileName %L/stupid.detail
> AccountingHandled
> 
>
> But Radiator (version 2.13.1) still ignore the Request. Inserting a simple
>
> 
> 
>
> in the above Realm fixes the Problem. Is this normal? Is there a better
> solution for my problem?

Its a bit hard to say without seeing your configuration file, but it sounds
like a reasonable response. The best solution would be to arrange for such
"realmless" requests to be handled by one of your existing Handlers.

Hope that helps.
Cheers.

-- 
Mike McCauley   [EMAIL PROTECTED]
Open System Consultants Pty. LtdUnix, Perl, Motif, C++, WWW
24 Bateman St Hampton, VIC 3188 Australia   http://www.open.com.au
Phone +61 3 9598-0985   Fax   +61 3 9598-0955

Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8, 
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.