I wrote a mistake. Roaring server PPPoe is a based-linux server pppoe, and it has to be between AP and radius-server. Clients must use a pppoe client like http://user.cs.tu-berlin.de/~normanb/ We already use this solution to authenticate my wireless clients.
Another solution is a "captive portal". Put these words in Google or read this http://www.personaltelco.net/index.cgi/CaptivePortal Tico > well, Tico, that's not sufficient... > > you will have to install a PPP server, too, where all the clients will > be actually connecting to. you will have to block any other access > (without this server connection) by some means (e.g. private ip > addresses). this PPP server will have to have a RADIUS-module in order > to report all this activity to the radius-server (does the roaring > server do that?) you basically install a PPP-tunnel over your wireless > network, resulting in bigger and unnecessary overhead. to avoid this, > the 802.1X has been actually invented. > > except, to remain at the same example: that's like putting the > 2-seat-cessna into a 747 jumbo flying it across the ocean to the NY and > "decapsulating" it overthere. of course, you could say that your cessna > made the distance... > > > Tico Kamide wrote: > > > > Your clients (in their machines) will need to run a client like this: > > http://www.roaringpenguin.com/pppoe/ > > Your AP, as you said, is just a jub... - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
