Hello Robert -
On Mon, 17 Apr 2000, Robert Saunders wrote:
> We are required to send port filters to our up stream provider using the
> format below:
>
> Ascend-Data-Filter="ip in forward tcp est"
> Ascend-Data-Filter="ip in forward dstip 254.170.212.0/24"
> Ascend-Data-Filter="ip in drop tcp dstport = 25"
> Ascend-Data-Filter="ip in forward"
>
> When using the ReplyHook put into the <Auth RADIUS> section as follows:
>
> ReplyHook sub { ${$_[0]}->add_attr('Ascend-Data-Filter',\
> 'ip in forward tcp est');\
> ${$_[0]}->add_attr('Ascend-Data-Filter',\
> 'ip in forward dstip 199.170.121.0/24');\
> ${$_[0]}->add_attr('Ascend-Data-Filter',\
> 'ip in drop tcp dstport = 25');\
> ${$_[0]}->add_attr('Ascend-Data-Filter',\
> 'ip in forward');}
> The values needed are not returned in the reply packet. I have checked it
> by starting Radiator from a terminal, with foreground set and trace = 4.
> When using multiple AddToReply instead of RelyHook using the attributes as
> above, only the first value is added to the reply.
> Any help would be appreciated.
>
With a ReplyHook (and with several others), you are dealing with *two* packets.
The first one, ${$_[0]} is the request packet from the NAS to Radiator, and the
second one, ${$_[1]} is the reply packet to be returned from Radiator to the
NAS. Obviously, your hook code above, is adding the *reply* attributes to the
*request* packet and hence is not doing what you expect.
Have a look at section 19.0 in the Radiator 2.15 reference manual for a more
complete discussion of hooks and execution sequence. There is also a set of
example hooks in the patches area that may be of help:
http://www.open.com.au/radiator/downloads/patches-2.15/hooks.txt
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
