Right now, if you are the recipient of a TCP-Clear connection, you know
(because the operating system tells you):
TCP server's port and IP address
NAS's port and IP address
If the TCP server's port and IP address are always the same, and there
are many users coming from each NAS, the only variable you can use as
a key is the NAS's ephemeral port number.
RADIUS tells you:
Login-IP-Host (TCP server's IP address)
Login-TCP-Port (TCP server's port)
NAS-IP-Address
What RADIUS Accounting is missing is what might be called NAS-TCP-Port.
If I want a RADIUS server to store accounting records and allow my
TCP-Clear service to look them up when someone connects to it, it needs
this information.
RADIUS is the cleanest way to do it. It should also be in SNMP, just for
completeness' sake (of course this is already in there in the tcpConnTable,
but what is needed is a way to link a TCP connection to a livingstonSerial
entry. But I'd hate to have to walk tables to get this.. it belongs
in RADIUS Accounting too.
Another possibility is an ident service, but let's not go there. :-)
-- 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/>