Hello please I need a little clarification on how to implement a central site PPPoE authentication with Freeradius and Mysql.
The important thing is: do I need a PPPoE server on each AP or is possible to have a single PPPoE concentrator in the central site as stated in this article http://wiki.mikrotik.com/wiki/EoIP?
I read also this article http://wiki.mikrotik.com/wiki/RouterOs_MySql_Freeradius, but it is not the ultimate source of info for me. My scenario is:
central-site-lan—local mtik<-----wireless----->remote Mtik1—lan—remote Mtik2—wlan/AP << client cpe
|
|
Server/freeradius/mYSQL
Many thanks in advance for your help.
regards
Alessandro
It is more efficient to keep PPPoE concentrators closer to the access points.
why?
-Tunneling adds overhead, which can bite into your limited wireless bandwidth.
-Wireless bridges, as a rule, hate tiny packets, and PPPoE makes plenty of them.
-Having a single PPPoE concentrator means that you’ll have to have a large, flat network, where every broadcast packet (e.g. PADI and PADO, ARP, various retarded discovery protocols, etc) will be heard by every CPE device. Ever heard of broadcast storms?
-You can run IP packing (M3P) from remote Tiks to the local one, which would help utilize the bandwidth more efficiently.
-You can still use a central RADIUS server, located on your local network. Freeradius will talk to an arbitrary number of NASes.
so…
Yes, it is possible (and cheaper) to run a single PPPoE concentrator for your entire network, but it is somewhat wasteful, and more dangerous. Also, if you’re planning on using shaping (e.g. rate-limiting individual subscribers) and you might have more than say… 600 or so users, you’ll have a tough time running them on the same PPPoE server. You will likely run into what we’ve been running into with Mikrotik - constant lock-ups of the PPPoE process on the Tiks when a bunch of subs hit them all at once (and this is on all-Intel 3ghz Xeon boxes). Because of this little “feature”, we’re now forced to switch to another, more expensive PPPoE solution for our larger sites (which totally sucks, because Mikrotik’s management UI is hard to beat… hello, dev team! help!).