No, there is no way to find out what port the connection
may have come from. However, they (Kenneth?) has mentioned they
can modify their application to work within the current
Portmaster/Radius framework.
What they can do:
Set up a proxy server to route requests based upon
Called-Station-Id. Depending up on the Called-Station-Id,
route the authentication request to the appropriate
application server.
The application server can take the Radius authentication
requests, and use the Calling-Station-Id information
in the request to do the preliminary authorization.
Assuming the Calling-Station-Id passes authentication,
the application can then open a ``server'' port (aka
bind to a port, and await a connection), and send
that back as part of the radius authorization reply
(think Login-Service, Login-IP-Host and Login-TCP-Port).
When the PM3 receives the authorization request, it will
establish a connection of type Login-Service to port
Login-TCP-Port on Login-IP-Host).
As further sanity checking, the application can verify
that the connection arriving on Login-TCP-Port comes
from NAS-IP-Address (aka, the portmaster that made
the request.)
As you might gather, given what I currently know about
the application and the usage, I believe the problem is
extremely solvable without further intervention from
Livingston/Lucent.
I'm sure someone might ask why I've put so much thought
into this.. Well, it seemed like an interesting problem, and it
kept my mind busy while sitting in traffic. :-)
-- Eric Schnoebelen eric@cirr.com http://www.cirr.com God Put Me On Earth to Accomplish a Certain Number of Things. Right Now I am so far behind, I will never die. --- Unknown - 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/>