Can I receive packets authorization and accounting on one tls port and redirect non-tls packets to the server, authorization and accounting?
That question makes no sense. Why, no sense. If client send auth and acct at same port.
2012/8/21 Вячеслав Адаманов <adamanov@gmail.com>:
But i started thread with message:
In the specification port 2083/tcp use for authentication and accounting. But in config i can set only one type: home_server tls { ipaddr = 127.0.0.1 port = 2083 type = auth secret = testing123 proto = tcp status_check = none ... } There are any ideas how to implement it?
2.1. TCP port and packet types The default destination port number for RADIUS over TLS is TCP/2083. There are no separate ports for authentication, accounting and dynamic authorisation changes. The source port is arbitrary.
I will be very grateful if you help me with this trouble
2012/8/21 Alan DeKok <aland@deployingradius.com>:
Вячеслав Адаманов wrote:
With this config i can receive and handle only packets the same type as specified listen section:
That is how it works. I just spent 3 messages explaining this.
Can I receive packets authorization and accounting on one tls port and redirect non-tls packets to the server, authorization and accounting?
That question makes no sense.
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@gmail.com www: http://hl.ua
-- __________________________ Vyacheslav Adamanov 87500, Ukraine, Mariupol, st. Apatova 136а mob: +38 (067) 621 32 61 email: adamanov@gmail.com www: http://hl.ua