(PM) Re: Caller-ID with tcp-clear sessions

Christopher Masto (chris@netmonger.net)
Wed, 17 Mar 1999 01:33:20 -0500

On Tue, Mar 16, 1999 at 02:55:24PM -0500, Rob Chandhok wrote:
> > How about setting up a proxy radius server, and have the
> > application server act as the final radius server. That way the
> > application gets both the calling and caller id information to
> > use in authentication. And the application can tell the portmaster
> > to reject the call, rather than having the call established, and
> > then rejected later.
>
> You could easily do this with cistron radius. I think this is a good
> suggestion.

That doesn't really solve the problem. He's basically screwed. There's
no apparent way to find out, when you recieve a TCP-clear connection,
which PM3 port it came from.

There are two things that Livingston should do:

1. Make the information available via SNMP (such as adding an entry to
the livingstonSerialTable indicating the local TCP port).
2. Make the information available via RADIUS. Vendor-specific for now,
but this is basically an oversight in RADIUS itself, so it should
be brought up for standardization.

-- 
Christopher Masto        Director of Operations      NetMonger Communications
chris@netmonger.net        info@netmonger.net        http://www.netmonger.net


Free 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/>