If you run an Internet Service Provider in Uganda, Kenya, or Tanzania, PPPoE (Point-to-Point Protocol over Ethernet) is the gold standard for subscriber authentication, dynamic IP assignment, and bandwidth control. Combined with a powerful ISP billing system, a properly configured MikroTik PPPoE server gives you full control over every subscriber on your network.
What Is PPPoE and Why Do African ISPs Use It?
PPPoE creates a virtual point-to-point connection between your router and each subscriber’s CPE. Every time a subscriber connects, it authenticates against your PPPoE server — enabling your ISP billing system to automatically suspend or reactivate services based on payment status.
- Per-subscriber authentication — unique credentials per subscriber
- Dynamic IP assignment — no manual IP management at scale
- Automatic suspension — unpaid subscribers disconnected instantly
- Bandwidth control — per-plan limits via PPPoE profiles
- Session logging — track uptime, data usage, and reconnection events
Recommended Hardware
- MikroTik hEX S RB760iGS — ideal PPPoE concentrator with SFP port and PoE output
- MikroTik hEX RB750Gr3 — excellent for smaller networks or zone-level distribution
- MikroTik hAP RouterBOARD with PoE — dual-band CPE for subscriber premises
- MikroTik hAP lite Wireless Router — lightweight CPE for residential subscribers
- MikroTik hAP lite RB941-2nD — affordable 2.4GHz CPE for last-mile deployments
- MikroTik RouterBOARD Wireless Router — versatile platform for backbone and distribution
- MikroTik MANTBox 12s — sector AP for subscriber access
- MikroTik MANT 30 PA — PtP backhaul dish
- MikroTik wAP ac — outdoor dual-band AP
- MikroTik RBGPOE PoE Injector — powers outdoor equipment
Cabling: Cat6 Flat Ethernet Cable (indoor) and Cat6 Indoor/Outdoor UTP Cable (outdoor). Browse the full MikroTik Routers collection.
Step 1: Enable the RouterOS API
Your ISP billing system communicates via the RouterOS API:
- Winbox → IP → Services
- Enable api (port 8728) or api-ssl (port 8729)
- Restrict to your billing server’s IP
Step 2: Create a Dedicated API User
- System → Users → +
- Username:
billing-api, permissions:ppp, ip, queue, tool - Allowed Address: billing server IP
Step 3: Configure the PPPoE Server
- PPP → PPPoE Servers → +
- Interface: subscriber-facing (e.g.,
ether2) - Enable One Session Per Host + PAP/CHAP/MS-CHAP2
Step 4: Create PPPoE Profiles
One profile per plan — names must match your ISP billing system exactly:
- PPP → Profiles → +
- Rate Limit: e.g.,
10M/10Mfor a 10 Mbps plan - Remote Address: your subscriber IP pool
Step 5: Create IP Address Pools
- IP → Pool → +
- Name:
PPPoE-Pool-Main, Range:10.10.0.2-10.10.0.254
Step 6: Configure NAT Masquerade
- IP → Firewall → NAT → +
- Chain:
srcnat| Out Interface: WAN | Action:masquerade
Step 7: Integrate with Your ISP Billing System
Connect to your ISP billing platform:
- Enter router IP, API port, username, and password in the billing dashboard
- Map billing plan names to PPPoE profile names (case-sensitive)
- Enable auto-suspend and auto-reactivate for mobile money integration
- Test the API connection from the billing dashboard
Troubleshooting
- Can’t authenticate — verify service name matches on server and client
- IP not assigned — verify pool is linked to the profile
- Billing API unreachable — check firewall not blocking port 8728/8729
- Subscribers not suspended — plan names must match RouterOS profiles exactly (case-sensitive)
Conclusion
A MikroTik PPPoE server combined with an automated ISP billing platform eliminates manual suspension and gives you complete per-subscriber control across Uganda, Kenya, and Tanzania.
Get started with our ISP billing system today →
