Hello Martin -
See my other mail, Radiator maintains a set of Identifiers, one per
client IP address / UDP port number pair.
Also keep in mind that the Identifiers are *only* used by the NAS for
requests that are "in flight", ie. requests that have been sent and for
which a response has not
Hello Martin -
Radiator maintains a set of Identifiers for each client IP address /
client UDP port number that it is receiving requests from.
If you do not need duplicate detection at all, just set DupInterval to 0
in your Client clauses.
BTW - here is the code from Client.pm (sub handle_re
Hello Ray -
It sounds like your hook is waiting for the database. You will have to
check what is going on in your database logs and look at tuning the
database so it processes your requests more quickly. You should check
the tuning guide for your database.
regards
Hugh
On Friday, Septembe
Hello Hugh,
Yes, you are right. Your proposed solution matches my original description.
Unfortunately then I omitted some details that make the whole thing a little
bit complicated, like the possibility that a regular auth-req may have
service type 5 too, because it is *really* asking for outb
Hi,
I'm using radiator with a preauth hook clause i'm having a
problem regarding the time it spend when using the preauth hook. In a
10 sec time i been able to process only 20 request, but when I remove
the preauthhook i can process 20 request in 2 sec. The function of a
preauth hook is
hi,
I'm using radiator with a preauth hook clause i'm having a
problem regarding the time it spend when using the preauth hook. In a
10 sec time i been able to process only 20 request, but when I remove
the preauthhook i can process 20 request in 2 sec. The function of a
preauth hook
And another query..
You said the Identifier 'cache' persay is kept for each
Does that mean, if I use IdenticalClients, the cache is for the collection
of RADIUS boxes?
And therefore does that mean under high load it would be preferable to not
use IdenticalClients, and use a separate for each
Hey Hugh,
This is the reply from my supplier :-
The ID of a RADIUS packet is a 1 byte field, range 1-255. It's set by
the NAS so it's likely that different NAS's will set the same ID at the
same time. When proxying, the proxy-state attribute is added and this
becomes the new unique "ID" of the p
Hello Claudio -
This is only for Service-Type = Outbound-User, which indicates
preauthentication according to your description.
Your other normal Handlers would be used for everything else.
Alternatively you could write a PreClientHook to do your checking and
which would add a pseudo-attribu
Hello Martin -
RFC 2865 (and possibly others).
("doc/rfc2865.txt").
regards
Hugh
On Friday, September 6, 2002, at 10:16 AM, Martin Edge wrote:
> Thanks Hugh,
>
> It's what I thought, just thought I'd confirm before raising a ticket
> request with my supplier..
>
> Which RFC does it talk abo
Thanks Hugh,
It's what I thought, just thought I'd confirm before raising a ticket
request with my supplier..
Which RFC does it talk about duplication in ?
Thanks,
Martin
-Original Message-
From: Hugh Irvine [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 06, 2002 10:13 AM
To: Marti
Hello Martin -
As Toomas mentioned (thanks Toomas), it is the Identifier 167 that is
used to detect duplicates during the DupInterval that is defined for
this Client. The DupInterval is a sliding window in time within which
identical Identifiers are considered to be duplicates.
Note that thi
Hello Mariano -
I'm afraid I dont quite understand what you are wanting to do.
Could you give me a bit more detail?
thanks
Hugh
On Friday, September 6, 2002, at 07:26 AM, Mariano Absatz wrote:
> Hi Hugh, long time no see...
>
> I'm planning an installation with a bunch of front-end Radiato
Hello Dan, Hello Everyone -
I can see that many people struggle with MSSQL connectivity, so I just
thought I would mention an alternative approach that is *much* simpler
to implement, which is to install an instance of Radiator on the MSSQL
box. This Radiator instance would receive proxied ra
Hello Hugh,
>Why not use something like this:
>
>
> ..
>
>
>which will match a User-Name that is all numbers as well as the
>Service-Type.
But then I would easily run into the wrong situation when faced with any
username composed by all numbers. Being an access provider I have no con
Hello Mariano, Hello Charly -
Yes, my method allows you to use specific, different versions of Perl as
well.
All I do is this:
cd /the/radiator/distribution
/usr/local/src/Perl/Perl-/bin/perl Makefile.PL; make; make test
..
then when I run Radiator I use the f
FTR,
I also think it's "A Good Thing"(TM) to be able to have a special perl
instalation for some critical perl programs or for programs with quite
specific requirements...
El 5 Sep 2002 a las 11:34, Karl Gaissmaier escribió:
> Hi Hugh and Mike,
>
> > Hello Charly -
> >
> > What I usually do
Hi Hugh, long time no see...
I'm planning an installation with a bunch of front-end Radiator proxies
(using ) to an(other) bunch of Radiator back-end servers
that do the actual authentication against SQL servers.
Now, the front-end farm has the "dispatching" intelligence and the back-end,
the
Paulo Sousa wrote:
>
> Dan
>
> I'm currently use libdbd-sybase-perl (that depends freetds), running
> debian GNU/Linux woody 3.0 :)
> Do u know how i can resolve that???
Not yet.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[
Dan
I'm currently use libdbd-sybase-perl (that depends freetds), running
debian GNU/Linux woody 3.0 :)
Do u know how i can resolve that???
Tk's
Paulo Sousa
On Thu, 5 Sep 2002, Dan Melomedman wrote:
> Paulo Sousa wrote:
> >
> >
> > Hi Dan
> >
> > I'm using a linux box that auths on M$ SQL Ser
Patrick Muldoon(NOC) wrote:
> We use DBD::Sybase with FreeTDS to connect to MSSQL Server 2000 from
> FreeBSD, and it works great, have never had any trouble.
>
> What version of FreeTDS are you using?
>
> You can also do some debugging with FreeTDS to see if it is the one
> hanging.
> http://w
Forgive my ignorance,
I was under the impression that FreeTDS would only work with SQL server
7.0 because as of 2000 microsoft changed the protocol so drastically
that is will no longer work with freetds (which was written for sybase,
essentially).
Sincerely,
Leon Oosterwijk
ISDN-NET Inc.
(
We use DBD::Sybase with FreeTDS to connect to MSSQL Server 2000 from
FreeBSD, and it works great, have never had any trouble.
What version of FreeTDS are you using?
You can also do some debugging with FreeTDS to see if it is the one
hanging.
http://www.freetds.org/userguide/x1873.htm#AEN1877
Mike McCauley wrote:
> Hi Dan,
>
> OK,
>
> here is a new version of SqlDb.pm that implements a new DisconnectAfterQuery
> flag. This will cause AuthBy SQL and other SQL users to disconnect after
> every SQL 'do' and after every 'getOneRow'.
>
> Let me know how you go.
>
> Cheers.
>
Thanks
Paulo Sousa wrote:
>
>
> Hi Dan
>
> I'm using a linux box that auths on M$ SQL Server. :)
>
> Paulo Sousa
>
We have exactly the same problem. You are using FreeTDS?
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTE
Hello,
We are running Radiator 2.17.1. The duplicate checking request we use currently is
only based
on the "Radius Identifier" alone as defined by RFC 2138.
Now we want to change our configuration such that duplicate checking is based on RFC
2865
that will include the "client port (source UDP
Hi Hugh and Mike,
> Hello Charly -
>
> What I usually do is skip the "make install" step altogether, and just
> leave the various versions in seperate directories.
sounds reasonable for your environment but without a "make install"
for example the path to the perl interpreter doesn't gets adju
Identifier: 167
- Original Message -
From: "Martin Edge" <[EMAIL PROTECTED]>
To: "Radiator" <[EMAIL PROTECTED]>
Sent: Thursday, September 05, 2002 9:16 AM
Subject: (RADIATOR) FW: As requested.
> Hey Guys,
>
> On what conditions does a packet appear to Radiator as Duplicate?
>
> Below I
28 matches
Mail list logo
