[RADIATOR] Radiator/AuthWimax.pm BS ID Questions

2014-04-13 Thread Adam O'Reilly
Hello Everyone,

 

Just wanting to find out the reasoning behind this:

22 # $Id: AuthWIMAX.pm,v 1.21 2012/12/13 20:19:47 mikem Exp $

.

200 my $bsid = $p-get_attr('WiMAX-BS-ID');

201 ($napid, $bsid) = unpack('a3 a3', $bsid)

202 if (defined $bsid);

 

The reason is we are seeing WiMAX-BS-ID come in like this

 

WiMAX-BS-ID = 000XXXX001

 

(Removed the identifying parts)

 

The AuthWimax Code then inserts irt into the device_session table as:

 

  bsid: 000

 

Any help would be greatly appreciated.

 

Thanks

 

Adam

___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator

Re: [RADIATOR] Help Radiator wimax Session Table

2012-06-29 Thread Adam O'Reilly
The key_expires field doesn't seem to be very helpful here are a few
examples:

key_expires: 10
key_expires: 2147483647
key_expires: 621
key_expires: 400

Can you explain how I would derive if the key is expired or not.

-Original Message-
From: radiator-boun...@open.com.au [mailto:radiator-boun...@open.com.au] On
Behalf Of Heikki Vatiainen
Sent: Friday, 29 June 2012 11:00 PM
To: radiator@open.com.au
Subject: Re: [RADIATOR] Help Radiator wimax Session Table

On 06/29/2012 03:56 AM, Adam O'Reilly wrote:

 We are investigating a problem on our wimax sessions table: device_session
 
 As it is getting quite large is there an option to clean up this table
 when the wimax session is torn down.

Radiator does not have a built-in cleanup for the old entries, so you
would need e.g., a cron job for this. Column key_expires is set to
time() + KeyLifetime so you could consider cleaning up old rows based on
this column.

-- 
Heikki Vatiainen h...@open.com.au

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, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
NetWare etc.
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator

___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator


[RADIATOR] Help Radiator wimax Session Table

2012-06-28 Thread Adam O'Reilly
Hello,

 

We are investigating a problem on our wimax sessions table: device_session

 

As it is getting quite large is there an option to clean up this table when
the wimax session is torn down.

 

Thanks

Adam O'Reilly

 

 

___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator

[RADIATOR] Radiator Crashing when assigning IPv6

2011-12-29 Thread Adam O'Reilly
Hello,

I am having some problems assigning a delegated IPv6 prefix.

The request is getting through the PostAuthHook File without any errors and
is being accepted but radiator crashes before sending a request back to the
BRAS.

This is how I am assigning the prefix:

$cfg::rp-add_attr('Delegated-IPv6-Prefix', PREFIX/48);

I am using Trace 5 and nothing about the crash is being logged.

I am using Radiator 4.9 and the latest patches.

Could someone let me know how to get more debug or help with assigning the
ipv6 prefix.

Here is a log snipit:

Fri Dec 30 08:54:20 2011: DEBUG: Finished reading configuration file
'/usr/local/radiator/conf/radius.cfg'
Fri Dec 30 08:54:20 2011: DEBUG: Reading dictionary file
'/usr/local/radiator/conf/dictionary.adnap'
Fri Dec 30 08:54:20 2011: DEBUG: Creating authentication port 0.0.0.0:1812
Fri Dec 30 08:54:20 2011: DEBUG: Creating accounting port 0.0.0.0:1813
Fri Dec 30 08:54:20 2011: NOTICE: Server started: Radiator 4.9 on testrad1
Fri Dec 30 08:54:24 2011: DEBUG: Packet dump:
*** Received from 127.0.0.1 port 37243 

Packet length = 108
01 cc 00 6c 59 af 41 25 82 5e 7e bc f4 b2 d6 79
b8 8b ab e4 01 07 6d 69 6b 65 6d 06 06 00 00 00
02 04 06 cb 3f 9a 01 20 0e 32 30 33 2e 36 33 2e
31 35 34 2e 31 05 06 00 00 04 d2 1e 0b 31 32 33
34 35 36 37 38 39 1f 0b 39 38 37 36 35 34 33 32
31 3d 06 00 00 00 00 02 12 e1 24 db 96 42 65 f4
2d 5f ed af 40 fe 30 88 04 7e 03 34
Code:   Access-Request
Identifier: 204
Authentic:  Y175A%130^~188244178214y184139171228
Attributes:
User-Name = mikem
Service-Type = Framed-User
NAS-IP-Address =
NAS-Identifier = 
NAS-Port = 1234
Called-Station-Id = 123456789
Calling-Station-Id = 987654321
NAS-Port-Type = Async
User-Password = 225$219150Be244-_237175@25401364
Operator-Name = 4

Fri Dec 30 08:54:24 2011: DEBUG: Handling request with Handler
'Client-Identifier = , Request-Type = Access-Request', Identifier ''
Fri Dec 30 08:54:24 2011: DEBUG: Rewrote user name to mikem
Fri Dec 30 08:54:24 2011: DEBUG: Rewrote user name to mikem
Fri Dec 30 08:54:24 2011: DEBUG: Rewrote user name to mikem
Fri Dec 30 08:54:24 2011: DEBUG:  Deleting session for mikem,, 1234
Fri Dec 30 08:54:24 2011: DEBUG: Handling with AuthINTERNAL: AuthAccept
Fri Dec 30 08:54:24 2011: DEBUG: AuthBy INTERNAL result: ACCEPT, Fixed by
DefaultResult
Fri Dec 30 08:54:24 2011: NOTICE: Started Post Authentication Hook for mikem
Fri Dec 30 08:54:24 2011: NOTICE: Auto accepting loging for mikem
Fri Dec 30 08:54:24 2011: NOTICE: DEBUG 1
Fri Dec 30 08:54:24 2011: NOTICE: DEBUG 2
Fri Dec 30 08:54:24 2011: NOTICE: DEBUG 3
Fri Dec 30 08:54:24 2011: DEBUG: Access accepted for mikem


Thanks Adam O'Reilly
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator