[RADIATOR] Change Default Size for Capabilities Field
James Austin
austinjw at crystalcomltd.com
Thu Sep 25 18:04:54 CDT 2014
Heikki,
This is what I see in the Radius/AuthWIMAX.pm file WiMAX-Capability section.
# Set the WiMAX-Capability
my $hotline_capability = 0;
$hotline_capability |= $Radius::WiMAXTLV::CAPABILITY_HOTLINE_PROFILE
if $self->{ProfileHotlining};
$hotline_capability |= $Radius::WiMAXTLV::CAPABILITY_HOTLINE_RULE
if $self->{RulebasedHotlining};
$hotline_capability |= $Radius::WiMAXTLV::CAPABILITY_HOTLINE_HTTP_REDIRECTION
if $self->{HTTPRedirectionHotlining};
$hotline_capability |= $Radius::WiMAXTLV::CAPABILITY_HOTLINE_IP_REDIRECTION
if $self->{IPRedirectionHotlining};
my $wimax_capability = Radius::WiMAXTLV->new();
$wimax_capability->add($Radius::WiMAXTLV::CAPABILITY_RELEASE,
$wimax_release);
$wimax_capability->add($Radius::WiMAXTLV::CAPABILITY_ACCOUNTING_CAPABILITIES,
pack('C', 1)); # no accounting yet
$wimax_capability->add($Radius::WiMAXTLV::CAPABILITY_HOTLINING_CAPABILITIES,
pack('C', $hotline_capability));
$wimax_capability->add($Radius::WiMAXTLV::CAPABILITY_IDLE_MODE_NOTIFICATION_CAPABILITIES,
pack('C', 0)); # no idle mode yet
$reply->add_attr('WiMAX-Capability', $wimax_capability->pack());
I changed the value in the italicized line from ('C',0) to ('C',1). If this is what you are referring to it still does not enable accounting. The sniffer stills show no accounting and the debug does not show any accounting related requests.
By the way the version of radiator we are running is 4.8.
Any other suggestions short of upgrading Radiator??
Regards,
Manager Technology & Projects
Crystal Communications Ltd.
281-300-8294 Mobile
281-361-5199 Office
________________________________________
From: Heikki Vatiainen [hvn at open.com.au]
Sent: Thursday, September 25, 2014 3:03 PM
To: James Austin; radiator at open.com.au
Subject: Re: [RADIATOR] Change Default Size for Capabilities Field
On 09/25/2014 04:40 PM, James Austin wrote:
> I have a zip file containing attached 4 files.
It was a bit too large for the public radiator list so it did not go
through.
It appears you are running Radiator 4.9 or earlier.
WiMAX-Accounting-Capabilities in the WiMAX-Cabability attribute is set
to 0 for no accounting. This was changed in Radiator 4.10.
The client was using 1 for IP-Session-Based in the request. You can
upgrade or change the accounting capabilities value in
Radius/AuthWIMAX.pm look for WiMAX-Capability.
This might fix the problem.
Thanks,
Heikki
> 1. Wireshark trace of working NAS.
> 2. Wireshark trace of non-working Radiator NAS.
> 3. Radiator config file.
> 4 Level 5 debug of Radiator.
>
> What are seeing from the Wireshark trace and Level 5 debug of Radiator is no accounting information. This is required of the Wimax product to achieve authentication.
>
> Also note that Radiator access-accept is showing no accounting and we suspect this is the root cause.
>
> Thanks for your help,
>
> James Austin
> Manager Technology & Projects
> Crystal Communications Ltd.
> 281-300-8294 Mobile
> 281-361-5199 Office
--
Heikki Vatiainen <hvn at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.open.com.au/pipermail/radiator/attachments/20140925/bfe99870/attachment.html
More information about the radiator
mailing list