You can't configure the Portmaster to authenticate specific ports from
a separate Radius server, much in the same way you can't configure it
to use a separate DNS server for specific ports.
The next version of the free-to-lucent-product-users Radius server, as
has been stated on this list, will do _realm_ authentication, which
allows you to proxy the authentication. Since they are actually
acknowledging it's presence in a beta form, one would imagine the
release date to be drawing nearer. But I wouldn't hold my breath for
it.
The DNS issue, if you don't want other users beating up your DNS, could
be solved by having the portmaster configured to use a "caching" name
server. Set the cache size pretty high and you're good to go. Then the
only requests to hit your primary DNS server[s] would be queries for
your domains/ip's.
[ note, this also works nicely for remote pops that have a local
gateway as well as a link back to the central location... ]
But now I'm starting to ramble on, so I'll go back to my coffee. :)
-Chris
--
\\\|||/// \ Chris Parker: Systems Administration and Development
\ ~ ~ / \ cparker@starnetusa.net \ cparker@megapop.net
| @ @ | \ www.starnetusa.net \ www.megapop.net
oOo---(_)---oOo--\------------------------------------------------------
\ Without C we would have 'obol', 'basi', and 'pasal'
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.