Here are my questions: 1. Would a single RADIUS server box be capable of doing both of above (taking into consideration the 2 different IP networks)? If so, how? I still havent bought/built this box either (any suggestions--Mikrotik?).
Radius is a means of authenticating (and accounting) subscribers .... your radius server can be nearly anywhere, as long as your radius clients (access points / routers) have connectivity to it.
IP networks are mostly irrelevant to your Radius server. Your Radius clients (again the router and/or access point) can distribute to the appropriate IP information to the subscriber.
This may vary somewhat if you have a special set-up (ie: static IP addresses. which are typically defined at the radius server)
2. I want to allow my clients to login to a local webpage and see THEIR bandwidth page only (authenticated with ASP). How could a client access these HTML pages if they are on different networks (client = 10.10.10.x network and my CONFIG PC = 11.168.0.x network)?
I believe standard IP routing will let your 10.10.10.x subscribers view the 11.168.0.x web server.
Firewalls, .htaccess, scripting language (asp, javascript, etc). can be used easily to limit access to just what you want.
-Rob
----------ANNOUNCEMENT---------- Don't forget to register for WISPCON IV http://www.wispcon.info/us/wispcon-iv/wispcon-iv.htm
The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname>
To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges)
Archives: http://archives.part-15.org
