ISP-A signs contract with NATL-PROVIDER.COM to use and resell their ports.
NATL-PROVIDER.COM will forward all USERNAME@ISP-A.NET requests to ISP-A's
ISP-A receives a list of 18 RADIUS servers, which are added to the RadiusNT
RadRoamServers table. Also, 18 entries are made into the RadRoamDomains
table, with each one pointing to a different NATL-PROVIDER.COM
RadRoamServer. Everything works fine.
As a reseller, ISP-A reaches an agreement with ISP-B allowing ISP-B.NET
customers to use ports provided by NATL-PROVIDER.COM along with ISP-A's
existing ports. Their customers will logon using the USERNAME@ISP-B.NET
NATL-PROVIDER.COM will now forward all USERNAME@ISP-A.NET and
USERNAME@ISP-B.NET requests to ISP-A's RadiusNT server. ISP-A will then
forward all USERNAME@ISP-B.NET requests to ISP-B's Radius server, which is
behind a firewall.
In return, ISP-B adds the IP Address and secret of ISP-A's Radius server to
receive and send requests.
ISP-A adds the IP Address and shared secret of ISP-B's Radius server to the
RadRoamServers table and adds ISP-B.NET to the RadRoamDomains table pointing
to the corresponding RadRoamServer entry.
Is this all that needs to be done, or does ISP-A need to add the 18 Radius
servers again, and 18 entries in the RadRoamDomains table?
And, what is the most effective way to track ISP-B's usage of ISP-A's local
For more information about this list (including removal) go to: