Re: (RADIATOR) (Fwd) Re: Radiator / Cisco prepaid calling cards
Hello Craig - There are numerous mentions of VOIP on the archive site: http://www.starport.net/~radiator But what specifically is your question? As always if you send me a copy of your configuration file (no secrets) together with a trace 4 debug from Radiator showing what is happening I will be happy to have a look. BTW - my experience with running new Cisco features and code is that it is a long painstaking process to get things sorted out and working. regards Hugh On Saturday 10 February 2001 02:41, Mike McCauley wrote: > Can anyone help Craig? > > --- Forwarded mail from [EMAIL PROTECTED] > > From: "Craig Thompson" <[EMAIL PROTECTED]> > To: "Mike McCauley" <[EMAIL PROTECTED]> > Date: Thu, 8 Feb 2001 17:29:55 -0500 > Subject: Re: Radiator / Cisco prepaid calling cards > Reply-to: [EMAIL PROTECTED] > > We saw the dictionary entries, but it could be the Cisco is not configured > correctly. Know anyone else doing this that I could contact? > > > Hi Craig, > > > > All the h323 attributes described in that document are supported by > > Radiator. You can also find an example of using them in the Radiator FAQ > > http://www.open.com.au/radiator/faq.html > > > > Cheers. > > > > On Feb 8, 11:53am, Craig Thompson wrote: > > > Subject: Radiator / Cisco prepaid calling cards > > > Can you look at this URL: > > > > > > http://www.cisco.com/warp/public/cc/so/neso/vvda/pctl/distrib/pp > > > cex_qp.htm > > > > > > It describes a service that we are trying to offer. As well, > > > the document (near the bottom) lists their RADIUS interface > > > specs available at this address: > > > > > > http://www.cisco.com/warp/public/cc/cisco/mkt/servprod/packet/di > > > strib/radus_ov.htm. > > > > > > Is this something that Radiator already does? If it doesn't, > > > what would it take to implement it? > > > > > > Thanks so much for your help. > > > > > > > > > > > > Craig Thompson, Manager > > > WingNET Internet Services, > > > P.O. Box 2605 // Cleveland, TN 37320-2605 > > > 423-559-LINK (v) 423-559-5145 (f) > > > http://www.wingnet.net > > > > > >-- End of excerpt from Craig Thompson > > > > -- > > 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, Active Directory etc etc > > on Unix, Win95/8, 2000, NT, MacOS 9, MacOS X > > Craig Thompson, Manager > WingNET Internet Services, > P.O. Box 2605 // Cleveland, TN 37320-2605 > 423-559-LINK (v) 423-559-5145 (f) > http://www.wingnet.net > > > > ---End of forwarded mail from [EMAIL PROTECTED] -- 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.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) AuthLog FILE - FailureFormat: REASON
Hello Mariano -
This will be supported in the next release of Radiator (due out in the next
couple of weeks).
regards
Hugh
On Friday 09 February 2001 08:26, Mariano Absatz wrote:
> Hi there,
>
> I've been almost off this list for some time (I have a backlog of a month
> or so in reading it) and I don't know if this has been discussed yet.
>
> I'm using an AuthLog FILE to log both successes & failures, and I want to
> include the reason for the failure (not only the password).
>
> I went to:
> http://www.open.com.au/radiator/ref.html#22600
> and didn't find anything that looked like that (since the reason for
> failure is not a reply item)
>
> I browsed through the sources (somehow lightly, yes) to see what the logger
> did, but it seems to passing strings through objects in the logging modules
> and is not even using global variables (so I can't use %{GlobalVar:name}
> either).
>
> Is there a way to add the Authentication Failure Reason to the
> "FailureFormat" string?
>
> The relevant portion of my config file follows:
>
> -
> # Log authentication success and failure to a file
>
> Identifier authLogger
> Filename %L/%Y-%m/auth_%d-%q
> LogSuccess 1
> LogFailure 1
> SuccessFormat %l:%n:<>:OK
> FailureFormat %l:%n:%P:FAIL
>
> -
>
> I would like to use something like:
>
> Identifier authLogger
> Filename %L/%Y-%m/auth_%d-%q
> LogSuccess 1
> LogFailure 1
> SuccessFormat %l:%n:<>:OK
> FailureFormat %l:%n:%P:FAIL:(%{Reason})
>
>
> Is it possible?
>
> TIA.
>
> ===
> Archive at http://www.starport.net/~radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
--
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.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
(RADIATOR) (Fwd) Re: Radiator / Cisco prepaid calling cards
Can anyone help Craig? --- Forwarded mail from [EMAIL PROTECTED] From: "Craig Thompson" <[EMAIL PROTECTED]> To: "Mike McCauley" <[EMAIL PROTECTED]> Date: Thu, 8 Feb 2001 17:29:55 -0500 Subject: Re: Radiator / Cisco prepaid calling cards Reply-to: [EMAIL PROTECTED] We saw the dictionary entries, but it could be the Cisco is not configured correctly. Know anyone else doing this that I could contact? > Hi Craig, > > All the h323 attributes described in that document are supported by Radiator. > You can also find an example of using them in the Radiator FAQ > http://www.open.com.au/radiator/faq.html > > Cheers. > > > > On Feb 8, 11:53am, Craig Thompson wrote: > > Subject: Radiator / Cisco prepaid calling cards > > Can you look at this URL: > > > > http://www.cisco.com/warp/public/cc/so/neso/vvda/pctl/distrib/pp > > cex_qp.htm > > > > It describes a service that we are trying to offer. As well, > > the document (near the bottom) lists their RADIUS interface > > specs available at this address: > > > > http://www.cisco.com/warp/public/cc/cisco/mkt/servprod/packet/di > > strib/radus_ov.htm. > > > > Is this something that Radiator already does? If it doesn't, > > what would it take to implement it? > > > > Thanks so much for your help. > > > > > > > > Craig Thompson, Manager > > WingNET Internet Services, > > P.O. Box 2605 // Cleveland, TN 37320-2605 > > 423-559-LINK (v) 423-559-5145 (f) > > http://www.wingnet.net > > > >-- End of excerpt from Craig Thompson > > > > -- > 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, Active Directory etc etc > on Unix, Win95/8, 2000, NT, MacOS 9, MacOS X > Craig Thompson, Manager WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ---End of forwarded mail from [EMAIL PROTECTED] -- 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, Active Directory etc etc on Unix, Win95/8, 2000, NT, MacOS 9, MacOS X === Archive at http://www.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Best Radius
Hello Jaime - On Friday 09 February 2001 06:51, Jaime Torres wrote: > > Good afternoon, I'm looking for an advice. There's a big variety of > authentication daemons to choose from but none of them seem to have all the > characteristics I'm looking for. I want to install&configure a radius > capable of mannaging access of pre-paid users. This users buy a limited > quantity of hours of connection and I expect this radius to validate the > time an user have been connected in the past and decide if the user can or > can't connect depending on it. > > Let me give you a simple example. This client bought 10 hours of connection > and he has been on-line for 9 hours and fifteen minutes. He dials our > number and asks for access permission to the radius. The radius checks the > user's on-line time and decide to give him access. Later that day, when the > user have reached 10 hours of on-line time, he tries to connect again, but > this time the radius won't let him access the service because the hours > limit have been reached. > > I hope Radiator can help me on this. Does it? How does it mannage this > cases? > This is very easy to set up with an SQL database for your user records. There are examples in the documentation and in the goodies directory of the distribution. This topic has also been discussed on the mailing list numerous times, so you should also do a search on the archive site: http://www.starport.net/~radiator regards Hugh -- 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.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) AuthLog FILE - FailureFormat: REASON
Hi there,
I've been almost off this list for some time (I have a backlog of a month or so
in reading it) and I don't know if this has been discussed yet.
I'm using an AuthLog FILE to log both successes & failures, and I want to
include the reason for the failure (not only the password).
I went to:
http://www.open.com.au/radiator/ref.html#22600
and didn't find anything that looked like that (since the reason for failure is
not a reply item)
I browsed through the sources (somehow lightly, yes) to see what the logger
did, but it seems to passing strings through objects in the logging modules and
is not even using global variables (so I can't use %{GlobalVar:name} either).
Is there a way to add the Authentication Failure Reason to the "FailureFormat"
string?
The relevant portion of my config file follows:
-
# Log authentication success and failure to a file
Identifier authLogger
Filename %L/%Y-%m/auth_%d-%q
LogSuccess 1
LogFailure 1
SuccessFormat %l:%n:<>:OK
FailureFormat %l:%n:%P:FAIL
-
I would like to use something like:
Identifier authLogger
Filename %L/%Y-%m/auth_%d-%q
LogSuccess 1
LogFailure 1
SuccessFormat %l:%n:<>:OK
FailureFormat %l:%n:%P:FAIL:(%{Reason})
Is it possible?
TIA.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
(RADIATOR) Best Radius
Good afternoon, I'm looking for an advice. There's a big variety of authentication daemons to choose from but none of them seem to have all the characteristics I'm looking for. I want to install&configure a radius capable of mannaging access of pre-paid users. This users buy a limited quantity of hours of connection and I expect this radius to validate the time an user have been connected in the past and decide if the user can or can't connect depending on it. Let me give you a simple example. This client bought 10 hours of connection and he has been on-line for 9 hours and fifteen minutes. He dials our number and asks for access permission to the radius. The radius checks the user's on-line time and decide to give him access. Later that day, when the user have reached 10 hours of on-line time, he tries to connect again, but this time the radius won't let him access the service because the hours limit have been reached. I hope Radiator can help me on this. Does it? How does it mannage this cases? Thanks for your time, Jaime
