PPPoE

MikroTik PPPoE Server Setup for Small ISPs

Build a PPPoE server on MikroTik for an ISP or building network: address pool, speed profiles, user secrets, NAT, MTU and how to check active users.

Commands in this article follow RouterOS v7 documentation but have not yet been marked as lab-tested on this site. Always test changes in a lab or maintenance window and keep a backup.

Problem

You run a small ISP, a building network or a hostel and want each customer to log in with a username and password and get a fixed speed package.

Symptoms

  • Clients' routers cannot find the PPPoE service.
  • Users connect but get no internet, or some websites do not load.

Likely causes

A PPPoE server needs an address pool, a PPP profile, a PPPoE server on the customer-facing interface, user secrets and NAT. Many "some sites do not open" problems are MTU/MSS issues.

Prerequisites

  • Customer-facing interface or bridge, for example ether2.
  • Internet on the router (WAN on ether1).

Solution (WinBox / CLI)

1. Address pool and profile. In a PPP profile, rate-limit is written from the router's side as rx/tx, so 5M/10M means the customer uploads at 5 Mbps and downloads at 10 Mbps:

RouterOS CLI
/ip pool add name=pppoe-pool ranges=10.20.0.2-10.20.3.254
/ppp profile add name=10M local-address=10.20.0.1 remote-address=pppoe-pool rate-limit=5M/10M dns-server=8.8.8.8,1.1.1.1 only-one=yes

2. PPPoE server:

RouterOS CLI
/interface pppoe-server server add service-name=myisp interface=ether2 default-profile=10M one-session-per-host=yes disabled=no

3. Customers:

RouterOS CLI
/ppp secret add name=client001 password=StrongPass1 service=pppoe profile=10M
/ppp secret add name=client002 password=StrongPass2 service=pppoe profile=10M

4. NAT for customers:

RouterOS CLI
/ip firewall nat add chain=srcnat src-address=10.20.0.0/22 out-interface=ether1 action=masquerade

The PPP profile's change-tcp-mss option (default on) fixes most "some sites do not open" issues caused by the smaller PPPoE MTU.

Verification

RouterOS CLI
/ppp active print
/interface pppoe-server print
/queue simple print

Each connected user appears in active and gets a dynamic simple queue with the profile speed.

Common errors

  • The customer router uses a different service name: leave the service name empty on the client, or match it exactly.
  • Wrong interface: the PPPoE server must face the customers, not the ISP.
  • FastTrack enabled: dynamic queues stop limiting speed.
  • Same username on two routers: only-one=yes blocks the second login.

Rollback

RouterOS CLI
/interface pppoe-server server disable [find service-name=myisp]
Go deeper in class

This topic is covered hands-on in MTCUME — MikroTik Certified User Management Engineer.

View MTCUME
WhatsApp