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: switch(packet->code) { case PW_AUTHENTICATION_REQUEST: if (listener->type != RAD_LISTEN_AUTH) goto bad_packet; FR_STATS_INC(auth, total_requests); fun = rad_authenticate; break; case PW_ACCOUNTING_REQUEST: if (listener->type != RAD_LISTEN_ACCT) goto bad_packet; FR_STATS_INC(acct, total_requests); fun = rad_accounting; break; case PW_STATUS_SERVER: if (!mainconfig.status_server) { FR_STATS_INC(auth, total_unknown_types); DEBUG("WARNING: Ignoring Status-Server request due to security configuration"); rad_free(&sock->packet); request->packet = NULL; return 0; } fun = rad_status_server; break; default: bad_packet: FR_STATS_INC(auth, total_unknown_types); DEBUG("Invalid packet code %d sent from client %s port %d : IGNORED", packet->code, client->shortname, packet->src_port); rad_free(&sock->packet); request->packet = NULL; return 0; } /* switch over packet types */ or am I wrong? Best regards, Vyacheslav 2012/8/21 Alan DeKok <aland@deployingradius.com>:
Вячеслав Адаманов wrote:
I use default "tls" server config file. Hmm, but when set type = auth in stdout:
Not much useful.
When change type = acct i get:
Also not much useful.
I'll see if I can take a look at it. No promises, though.
Is it possible to redirect requests for authorization and accounting to other defined virtual servers ?
Put the "listen" section into a "server" section:
server foo { listen { ... }
authorize { ... }
accounting { ... } }
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