Hello William -


This sounds like a NAS configuration issue, as the Radiator Client clauses are based on the source IP address for a request. It seems strange that an access request would use a different source IP address compared to an accounting request from the same device.

regards

Hugh


On Friday, Mar 28, 2003, at 05:08 Australia/Melbourne, William Hernandez wrote:


Hello everyone,

The NASIDENTIFIER column in RADONLINE and the NAS-IP-Address line in the
accounting detail file for our users who connect via Total Control NASes
shows as the NASes private ip address. We would like this to show as the
public ip address.


A related problem is that accounting requests are falling through to the
DEFAULT client clause instead of being handled by the client clause with
the NASes hostname. Access requests are handled correctly.


Is this a Radiator issue or is this a Total Control issue?

Thanks in advance,

William Hernández
Radiator 3.3.1
RH 7.3
Perl 5.6.1
TotalControl HiPerArc


=== Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.



NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening?

--
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 [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

Reply via email to