Radsec auth and acct on same port
Вячеслав Адаманов
adamanov at gmail.com
Tue Aug 21 16:07:18 CEST 2012
Sorry :
server tls {
listen {
ipaddr = *
port = 2083
type = auth
proto = tcp
clients = radsec
tls {
.....
}
}
authorize {
.....
}
authenticate {
.....
}
post-auth {
.....
}
preacct {
.....
}
accounting {
.....
}
}
2012/8/21 Вячеслав Адаманов <adamanov at gmail.com>:
> With this config i can receive and handle only packets the same type
> as specified listen section:
>
> server tls {
> listen {
> ipaddr = *
> port = 2083
> type = auth
> proto = tcp
> clients = radsec
> tls {
> .....
> }
>
> authorize {
> .....
> }
> authenticate {
> .....
> }
> post-auth {
> .....
> }
> preacct {
> .....
> }
> accounting {
> .....
> }
> }
> }
>
>
> Can I receive packets authorization and accounting on one tls port and
> redirect non-tls packets to the server, authorization and accounting?
>
> Best regards, Vyacheslav
>
>
> 2012/8/21 Alan DeKok <aland at deployingradius.com>:
>> Вячеслав Адаманов wrote:
>>> Sory, I'm not very good at programming.
>>> Very similar to the verification of the type incoming packet in
>>> tls_listen.c start from 357 line:
>>
>> Yes. The verification is there.
>>
>> But if you want to parse "auth+acct", you need to edit more than that.
>>
>> Alan DeKok.
>> -
>> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
>
>
>
> --
> __________________________
> Vyacheslav Adamanov
> 87500, Ukraine, Mariupol,
> st. Apatova 136а
> mob: +38 (067) 621 32 61
> email: adamanov at gmail.com
> www: http://hl.ua
--
__________________________
Vyacheslav Adamanov
87500, Ukraine, Mariupol,
st. Apatova 136а
mob: +38 (067) 621 32 61
email: adamanov at gmail.com
www: http://hl.ua
More information about the Freeradius-Devel
mailing list