08-27-2008 08:18 AM - edited 07-03-2021 04:23 PM
We are looking at providing internet service to subscribers via wireless 802.11. I am looking at using PPPOE and Radius for authentication. Is this still the best way to handle authentication for fixed wireless subscribers? If so what is the best way to handle the PPPOE and Radius authentication. I have heard a lot of ISP's are using Linux, but I would much rather have a hardware based solution if possible. Does anyone have any thoughts on this? We are somewhat low density probably looking at a few hundred subscribers max.
09-02-2008 09:24 AM
Here is the steps for the authentication which will help you :
Enable PPPoE client functionality on the interface.
It is off by default. The setroute option causes a default
route to be created if no default route exists.
The default route will be the address of the AC.
ip address outside pppoe setroute
Define the VPDN group to be used for PPPoE.
This must be configured first.
vpdn group pppoex request dialout pppoe
Associate the username assigned by ISP to the VPDN group.
vpdn group pppoex localname cisco
Define authentication protocol.
vpdn group pppoex ppp authentication pap
Create a username and password pair for the PPPoE connection.
vpdn username cisco password *********
Enable access to the TACACS+ and RADIUS protocols.
aaa-server RADIUS protocol radius
Associate the partnerauth protocol to RADIUS.
09-02-2008 09:33 AM
I'm actually looking for the server functionality and not the client functionality that you described.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide