On 04/14/2014 07:07 AM, Adam O'Reilly wrote:
> Just wanting to find out the reasoning behind this:
> 200 my $bsid = $p->get_attr('WiMAX-BS-ID');
> 201 ($napid, $bsid) = unpack('a3 a3', $bsid)
>
> The reason is we are seeing WiMAX-BS-ID come in like this
> WiMAX-BS-ID = 0000000XX0000XX001
>
> (Removed the identifying parts)
>
> The AuthWimax Code then inserts irt into the device_session table as:
>
> bsid: 000
>
> Any help would be greatly appreciated.
I think the reason is this:
http://resources.wimaxforum.org/sites/wimaxforum.org/files/technical_document/2009/07/WMF-T33-001-R010v04_Network-Stage3-Base.pdf
Section 5.4.2.46 BS-ID says about the attribute value:
Octet-String (6 Octets). Representing NAP operator identifier
(first 3 Octets) and the Base Station ID (next 3 Octets).
Looking at a more recent doc,
WMF-T33-001-R015v03
WMF Approved
(2011-11-14)
the same definition is also there, unchanged.
Maybe your equipment has a configuration option to use different format?
Thanks,
Heikki
--
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
