non-authentication port

Leandro Pereira de Lima e Silva - ViaLink leandro at vialink.com.br
Mon Jun 19 05:19:15 CEST 2006


Alan,

thank you very much for your help. I saw in sniffer packets going to 
1812 and 1813, so I presumed that auth and acct ports were correct.
Today I modified freeradius source to show me the destination port in 
the error and got a little surprise.

They were sending auth to 1813 and acct to 1812.

To bypass this problem I set port = 1234 and used listen directive to 
open 1812 to acct and 1813 to auth.
I will make a request for them (to my dial-up backbone) to correct the 
port in NAS.
I will send my little patch to freeradius too, this little new 
information in log ended up helping a lot.

Best regards, Leando.

Alan DeKok escreveu:
> Leandro Pereira de Lima e Silva - ViaLink <leandro at vialink.com.br> wrote:
>   
>> Alan, it's going to 1812. As we can see at the log that I posted, it's 
>> coming from port 49852.
>>     
>
>   OK.  I've never seen that problem before, so I'm not sure what to
> say.
>
>   Alan DeKok.
>
> - 
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
>   


-- 
Leandro Pereira de Lima e Silva
http://www.vialink.com.br/
"A verdadeira medida do caráter de um homem é o que ele faria se soubesse que nunca seria descoberto." -- Thomas B. Macaulay




More information about the Freeradius-Users mailing list