(RADIATOR) radiusd segfaults on Access-Request via SQL

[Justin White-Lowther]

Here's the result of running Radiator at trace 4 from the command line,
then running radpwtst:

--

[root at pavilion ocelot]# perl /usr/bin/radiusd -config_file
/etc/radiator/platypus.cfg
Thu Aug 22 16:55:54 2002: INFO: Server started: Radiator 3.2 on
pavilion.cisnet.com
Thu Aug 22 16:56:09 2002: DEBUG: Packet dump:
*** Received from 127.0.0.1 port 32772 ....
Code:       Access-Request
Identifier: 219
Authentic:  1234567890123456
Attributes:
        User-Name = "mikem"
        Service-Type = Framed-User
        NAS-IP-Address = 203.63.154.1
        NAS-Port = 1234
        Called-Station-Id = "123456789"
        Calling-Station-Id = "987654321"
        NAS-Port-Type = Async
        User-Password =
"<159><249>:<201><175>\<4><246><188>8<9><160><216>}x<153>"

Thu Aug 22 16:56:09 2002: DEBUG: Handling request with Handler
'Realm=DEFAULT'
Thu Aug 22 16:56:09 2002: DEBUG:  Deleting session for mikem,
203.63.154.1, 1234
Thu Aug 22 16:56:09 2002: DEBUG: Handling with
Radius::AuthPLATYPUS
Thu Aug 22 16:56:09 2002: DEBUG: Handling with Radius::AuthPLATYPUS:
Segmentation fault

--

Here's the configuration file, but it's just the sample with a bare
minimum of modifications.  (Most comments are deleted here for brevity.)
The same results occur with the configuration file borrowed from our old
radius server's version of Radiator.

--

# platypus.cfg
#
# Example Radiator configuration file that allows you to
# authenticate from and store accounting to the Platypus database
# from Boeardtown (see http://www.boardtown.com)
#
# You should consider this file to be a starting point only
# $Id: platypus.cfg,v 1.3 1999/03/18 06:26:29 mikem Exp $

Foreground
LogStdout
LogDir          /var/log/radius
DbDir           /etc/radiator
Trace           4

# You will probably want to change this to suit your site.
<Client DEFAULT>
        Secret  mysecret
        DupInterval 0
</Client>

<Realm DEFAULT>
        <AuthBy PLATYPUS>
                DBSource        dbi:ODBC:Platypus
                DBUsername      platnewuser
                DBAuth          platacct

        </AuthBy>
</Realm>


-- 

Justin White-Lowther



On Thu, 22 Aug 2002, Hugh Irvine wrote:

> 
> Hello Justin -
> 
> Please send me a copy of the configuration file (no secrets) together 
> with a trace 4 debug from Radiator and a copy of the error output from 
> Perl when it crashes (run radiusd from the command line).
> 
> regards
> 
> Hugh
> 
> 
> On Thursday, August 22, 2002, at 12:41 AM, Justin White-Lowther wrote:
> 
> >
> > Greetings,
> >
> > I'm attempting to set up Radiator 3.2 on a Mandrake Linux 8.2 system to
> > authenticate with Platypus.  Perl 5.6.1, the Perl DBI 1.30 and DBD-ODBC
> > 0.43 modules and associated iODBC and OpenLink driver claim to be
> > installed correctly, and communication with the database is possible
> > through their own tests.  However, when I try radpwtst, radiusd 
> > segfaults
> > just after the "sending Access-Request"  message appears.  This error
> > occurs even with a minimal configuration file, with RPM and with 
> > tarball.
> >
> > Any solutions or possible avenues for finding a solution would be much
> > appreciated!
> >
> > --
> > Justin White-Lowther
> >
> > ===
> > 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: I am travelling this week, so there may be delays in our 
> correspondence.
> 
> --
> 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.