Thanks Felix,
That is exactly what I ended up doing; however, I don't
feel comfortable having programs bind ports that I don't
want to have bound. I'll live with it, though :) I sure
hope the Radiator guys would consider an option to only
have Radiator bind one port if explicitly asked.
John
t 06:13 PM 9/25/99 +0200, you wrote:
>Hello John,
>
>John Coy wrote:
>>
>> I sent the message below last night -- I think that my
>> main goal is to get Radiator to only bind one socket when
>> intitializing... is there a way to do this? The reason
>> I ask is that I want to run two instances of Radiator --
>> one on port 1812 for auth, and one on port 1813 for
>> accounting. If I try to specify only one port in the
>> radiusd.cfg file, it will default to the 1645 or 1646
>> ports automatically for either auth or acct (depending
>> on which one I omit in the config file)
>>
>> --
>>
>> Is there a way to put the Radiator daemon in accounting-only
>> mode? (ie: not respond to auth requests or bind an auth port?)
>>
>
>I run two instances of Radiator in the same host. The config is:
>
>Auth Radiator: 1812 ( auth )
> 1646 ( not used )
>
>Acct Radiator: 1645 ( not used )
> 1813 ( acct )
>
>All the NAS are configured for a Radius server in the RFC ports 1812 and
>1813, and the old Livingston ports are not used.
>
>You must know that in the actual version, Radiator treats auth and acct
>requests in both ports without any difference.
>
>F�lix
>
>______________________________________________________________________
>DATAGRAMA SERVICIOS GLOBALES IP
>C/ Acer 30 Pho: +34 93 223 00 98
>08038 Barcelona ( SPAIN ) Fax: +34 93 223 12 66
>mailto:[EMAIL PROTECTED] http://www.datagrama.net
>______________________________________________________________________
�
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
