UISP–Mikrotik PPPOE Integration
Budget: $30 – $250 USD
I need to wire UISP directly into my MikroTik router so that every PPPOE account is created, authenticated, suspended, or unsuspended from inside UISP without me having to touch RouterOS manually.
Scope
• Authentication is the only feature that must flow between the two platforms for now, but it has to cover the full life-cycle: create user, apply profile, suspend, unsuspend, and delete.
• The workflow starts in UISP; once I hit “Add client” there, the router should receive the PPPOE credentials automatically and start serving.
• All current subscribers—about a 30—have to be imported in bulk from the router into UISP so that future actions remain seamless. No data loss is acceptable.
Technical expectations
• MikroTik RouterOS API or CLI scripting may be used, as long as the end result is stable after upgrades.
• UISP’s native hooks or web-hooks can be leveraged; I simply want a clean, documented link between the two systems.
• Any middle-layer (e.g., an external RADIUS or small python/PHP service) is fine if you document installation and give me basic instructions to restart or back it up.
Acceptance criteria
1. Creating, suspending, and unsuspending a user in UISP instantly reflects on the MikroTik PPPOE server.
2. Existing users are imported and visible in UISP with their current status.
3. Clear README covering setup, dependencies, and how to add future fields or speed profiles.
4. A brief hand-off session to walk through the code and demonstrate each function live.
If you have previously linked UISP (or UNMS) with MikroTik for PPPOE, a short note on your approach will help me gauge fit.
Scope
• Authentication is the only feature that must flow between the two platforms for now, but it has to cover the full life-cycle: create user, apply profile, suspend, unsuspend, and delete.
• The workflow starts in UISP; once I hit “Add client” there, the router should receive the PPPOE credentials automatically and start serving.
• All current subscribers—about a 30—have to be imported in bulk from the router into UISP so that future actions remain seamless. No data loss is acceptable.
Technical expectations
• MikroTik RouterOS API or CLI scripting may be used, as long as the end result is stable after upgrades.
• UISP’s native hooks or web-hooks can be leveraged; I simply want a clean, documented link between the two systems.
• Any middle-layer (e.g., an external RADIUS or small python/PHP service) is fine if you document installation and give me basic instructions to restart or back it up.
Acceptance criteria
1. Creating, suspending, and unsuspending a user in UISP instantly reflects on the MikroTik PPPOE server.
2. Existing users are imported and visible in UISP with their current status.
3. Clear README covering setup, dependencies, and how to add future fields or speed profiles.
4. A brief hand-off session to walk through the code and demonstrate each function live.
If you have previously linked UISP (or UNMS) with MikroTik for PPPOE, a short note on your approach will help me gauge fit.
Related categories:
PHP
Python
System Admin
Linux
Software Architecture
Network Administration
Scripting
Documentation
Automation
API Development