That seems essentially equivalent to:
> The best solution we've come up with so far is for the application
> server to monitor a large number of server sockets (either ports or IP
> addresses on virtual interfaces) and have the RADIUS server round-robin
> through them somehow. This is...sub-optimal. Any advice would
> be appreciated.
Except it's even more complicated.
I think the fact that RADIUS accounting sends only three of the four
variables which are needed to identify a TCP connection is an oversight
that should be corrected by the IETF at some point.
-- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.netFree yourself, free your machine, free the daemon -- http://www.freebsd.org/ - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>