MikroTik PPPoE Server Setup with RADIUS, Step by Step

A RouterOS v7 PPPoE server configuration script with RADIUS user authentication, accounting and MTU settings, then how billing blocks unpaid users.

November 18, 2026 · 9 min read · Centipid operations

Title card on a pale green background, with line sketches of a router, a cable between two sockets, a monitor and a padlock, under the title MikroTik PPPoE server setup with RADIUS.

A PPPoE server on a MikroTik gives every home subscriber a username and password, one session each, and their own IP address. This guide builds one on RouterOS v7, connects it to RADIUS, and shows how billing then blocks accounts that have not paid.

Every command below is meant to be pasted into a WinBox terminal. Addresses are examples: 192.0.2.10 stands for your RADIUS server and YOUR_RADIUS_SECRET for its shared secret.

PPPoE or Hotspot: which one to use

Use PPPoE when the subscriber has a fixed connection at home or in an office and logs in from their own router. The login is always on, one account holds one session, and each account gets its own IP address.

Use Hotspot for public Wi-Fi where people buy access on a web page or enter a voucher. The login happens in a browser, and a device can come and go.

Most ISPs run both, on different bridges or even different routers. This guide covers PPPoE. For the full comparison, see PPPoE and Hotspot in the Centipid docs and the PPPoE billing page.

If you will use Centipid, skip Steps 1 to 4: it does them for you (see the last section). It builds its own bridge, pool, INTERNET profile, PPPoE server and RADIUS settings, and if an INTERNET profile already exists it re-points it to Centipid's pool. Read the steps to understand what it sets up.

Step 1: a bridge and an IP pool for subscribers

Subscribers plug into one or more ports. Put those ports in a bridge and make a pool of addresses to hand out. The bridge needs no IP address of its own: the profile in Step 2 supplies the router's end of each PPPoE link. Leaving it off also means a device with a fixed address cannot get online without logging in.

/interface bridge add name=pppoe-bridge
/interface bridge port add bridge=pppoe-bridge interface=ether2
/interface bridge port add bridge=pppoe-bridge interface=ether3
/ip pool add name=pppoe-pool ranges=10.50.0.10-10.50.3.250

Change the ports to match your router. Pick a range that is free on your network. If you plan to use Centipid, stay out of 10.8.0.0/16, 10.9.0.0/16 and 10.10.0.0/16: its router tunnels use addresses there.

Do not put the WAN (internet-facing) port or your management port in the bridge.

Subscribers use private addresses, so the router must translate them on the way out. Replace ether1 with your WAN port:

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

Without this rule a clean router connects subscribers but gives them no internet.

Step 2: a PPP profile with a speed limit and one session

A profile is the template every subscriber inherits. It says which address the router uses, where subscriber addresses come from, and how fast they can go.

/ppp profile add name=INTERNET local-address=10.50.0.1 remote-address=pppoe-pool \
    dns-server=1.1.1.1 only-one=yes rate-limit=5M/10M
  • local-address=10.50.0.1 is the router's end of every PPPoE link. It does not have to be on the bridge.
  • only-one=yes stops one account from opening several sessions at once, so a password shared between households does not work twice.
  • rate-limit=5M/10M is upload first, then download: 5 Mbit/s up, 10 Mbit/s down. With RADIUS you will normally leave this out and send the speed per plan instead (Step 4).
  • Do not add an idle timeout. PPPoE is always on, and a quiet but connected customer should not be disconnected.

Step 3: the PPPoE server on the bridge

/interface pppoe-server server add service-name=isp-pppoe interface=pppoe-bridge \
    default-profile=INTERNET authentication=pap,chap \
    max-mtu=1480 max-mru=1480 disabled=no

authentication=pap,chap accepts both PAP (password sent as is, inside the session) and CHAP (a hashed challenge). With RADIUS and a billing system, pap alone is common: every client router supports it. max-mtu and max-mru cap the packet size the server sends (MTU, maximum transmission unit) and accepts (MRU, maximum receive unit). Step 5 explains the value.

Test it before RADIUS is involved. Add one local account and connect a client router or a laptop to ether2:

/ppp secret add name=test1 password=ChangeThisTestPassword service=pppoe profile=INTERNET

On the client router:

/interface pppoe-client add name=test-pppoe interface=ether1 user=test1 \
    password=ChangeThisTestPassword add-default-route=yes disabled=no

Then on the server, check that the session is up:

/ppp active print

You should see test1 with an address from pppoe-pool. Remove the test account (/ppp secret remove [find name=test1]) before the next step, so you know RADIUS answered later.

Step 4: RADIUS and PPP accounting

Add the RADIUS server for PPP, then tell the PPP service to use it.

/radius add service=ppp address=192.0.2.10 secret=YOUR_RADIUS_SECRET \
    timeout=3000ms authentication-port=1812 accounting-port=1813
/radius incoming set accept=yes port=1700
/ppp aaa set use-radius=yes accounting=yes interim-update=30m

What each line does:

  • /radius add points the router at your RADIUS server. 1812 is the port for logins and 1813 for accounting. The secret must match the server's entry for this router exactly.
  • /radius incoming lets the RADIUS server send the router a disconnect or speed-change request. This is how an unpaid or changed account takes effect on a session that is already up. The port must match the port your RADIUS server sends those requests to: 3799 is the standard, many tools use 1700, and Centipid uses 1700. The router's input firewall must also allow that UDP port from the RADIUS server.
  • use-radius=yes sends PPP logins to RADIUS. accounting=yes sends usage records.
  • interim-update=30m makes the router report each live session every 30 minutes. RouterOS defaults to 0s, which sends only a start and a stop record unless the RADIUS server asks for its own interval (the Acct-Interim-Interval attribute). Without regular updates, billing cannot see usage or tell a live session from a dead one.

Your RADIUS server returns the speed for each account in the Mikrotik-Rate-Limit attribute, for example 5M/10M. It overrides the profile's rate-limit. For the server side, see how a MikroTik RADIUS server handles subscriber access.

Now add a test account on the RADIUS server and repeat the client test from Step 3.

Step 5: MTU and MRU

PPPoE adds an 8-byte header inside each Ethernet frame. On a 1500-byte Ethernet link, that leaves 1492 bytes for the subscriber's packet at most. The MTU is the largest packet the link sends, and the MRU the largest it accepts. RouterOS uses 1480 by default for both max-mtu and max-mru, and 1480 is a safe value for most networks. Set the same value on both so the two directions agree.

Large packets that do not fit cause the classic PPPoE symptom: the connection works, small pages load, and big downloads or some HTTPS sites hang. The fix is to shrink the size TCP asks for. PPP profiles already do this by default (change-tcp-mss=yes), so the two rules below, one for each direction, are a backup for setups where it is off or traffic takes another path:

/ip firewall mangle add chain=forward protocol=tcp tcp-flags=syn \
    out-interface=all-ppp action=change-mss new-mss=clamp-to-pmtu passthrough=yes
/ip firewall mangle add chain=forward protocol=tcp tcp-flags=syn \
    in-interface=all-ppp action=change-mss new-mss=clamp-to-pmtu passthrough=yes

To check the real limit from a connected client router, ping the server end of the link. RouterOS size is the whole IP packet, headers included:

/ping 10.50.0.1 size=1480 do-not-fragment count=3
/ping 10.50.0.1 size=1481 do-not-fragment count=3

The first should answer and the second should fail. If the first fails too, your real MTU is lower, often because another tunnel or a fibre ONT (optical network terminal) sits in the path. Lower the ping size until it answers, then set max-mtu and max-mru to that number.

Common errors

Turn on logging while you test:

/system logging add topics=ppp,debug
/system logging add topics=radius,debug

Then read it with /log print where topics~"ppp" or topics~"radius".

  • The client says no PPPoE server found. The client is on the wrong port, or the port is not in the bridge, or service-name on the client does not match the server's. Leave the client's service name empty to match any.
  • Authentication failed. The username or password is wrong, or RADIUS refused it. Check the RADIUS server's log before the router's.
  • RADIUS does not answer. The two usual causes are a shared secret that differs even by one character, and a firewall in front of the RADIUS server blocking UDP 1812 or 1813. Allow both from the router's address.
  • Sessions connect but accounting is empty. accounting=yes or interim-update is missing in /ppp aaa.
  • Big downloads stall. MTU. Go back to Step 5.
  • A second login with the same account is refused. That is only-one=yes working.

Doing it with Centipid

Running RADIUS yourself means keeping the server up, the secrets in step across every router, and a plan to cut off unpaid users by hand. Centipid does that part, and builds the router side for you.

  1. Add the router. In Centipid, add a MikroTik router. It gives you one script to paste into a WinBox terminal. The script joins the router to Centipid over a tunnel, adds the RADIUS server for ppp and hotspot (timeout 3000 ms, ports 1812 and 1813, with the secret filled in), turns on RADIUS incoming, and runs /ppp aaa set use-radius=yes accounting=yes interim-update=30m. It is the same RADIUS setup as Step 4.
  2. Pick PPPoE and the ports. Once the router is online, you choose the services and the bridge ports. Centipid then creates centipid-bridge, the pool centipid-pool, the INTERNET profile with only-one=yes, and a server called centipid-pppoe on the bridge with authentication=pap. It is Steps 1 to 3 without the typing.
  3. Make packages. A package holds the price, the speed and the length of the subscription. A subscriber gets a package, and their speed reaches the router through RADIUS the moment they log in. Changing a subscriber's package reconnects their session once, at the new speed.
  4. Let expiry run. When a PPPoE subscription expires, the subscriber stays connected but is held at 1 kbit/s in each direction, and the router blocks their traffic until they pay. After they pay, the restriction is lifted.

Centipid also audits each router against this setup. If the RADIUS entry, the PPP RADIUS setting or the PPPoE server drift from what it expects, the audit marks the check as failed and shows the command that fixes it. See MikroTik provisioning and RADIUS authentication for the detail.

What it costs

Centipid charges $0.25 per active PPPoE subscriber a month. Once you pass 500 subscribers the rate falls to $0.20 for all of them, and past 1,000 to $0.15. Suspended and expired accounts are not charged. In Kenya the same rates are KES 25, KES 20 and KES 15. There is a monthly minimum of $5 (KES 500 in Kenya). Every plan starts with a 14-day trial and no card. If you stay, the first invoice covers those 14 days. Leave inside the trial and you pay nothing. See pricing for the rest.

Where to go next

See it on your own network