(RADIATOR) Framed-IP of 0.0.0.0

[Hugh Irvine]

Hello William -

The only way to understand what is happening is to look at a trace 4 debug 
from Radiator to see in what circumstances this occurs. As it is the NAS that 
sends the accounting packets that are used to maintain the session database, 
it is highly likely that this is a NAS issue.

Note that we have seen similar behaviour occassionally when it is Radiator 
allocating the addresses, and one work-around is to send a copy of the 
address in a Class attribute and use a PreClientHook to restore it.

Obviously if it is the NAS that is allocating the addresses, you will need to 
check with the NAS vendor if there is a fix for the problem.

regards

Hugh


On Thursday 13 September 2001 00:16, William Hernandez wrote:
> Hello everyone,
>
> We're using 2.18.2. Recently we started to see FRAMEDIPADDRESS of
> 0.0.0.0 in RADONLINE. These records create a problem when
> checking for Simultaneous-Use. Is this a problem with the Ascend
> NASes that we use?
>
> Thanks in advance,
> William
>
> ===
> 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.

-- 
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.