PPPoE Monitor

To deploy a PPPoE monitor that tracks connection uptime and flags stability issues, you must target the router or gateway establishing the PPPoE tunnel or use an external ping/ping-back monitor. Traditional HTTP-based monitors fail here because PPPoE is a Layer 2 network protocol wrapper that handles WAN authentication rather than web services.

Depending on your network infrastructure, you can deploy this via local router scripting, a self-hosted Docker agent, or network protocol monitoring. Method 1: Router-Native Scripting (MikroTik / OpenWrt)

The most accurate metrics come straight from your gateway because it handles the PPPoE interface directly. For MikroTik RouterOS

You can write a simple script to grab the exact uptime value from the PPPoE client and push it to a logger or webhook:

Navigate to System > Scripts and create a new script named pppoe-status.

Add the following script to pull the specific interface data:

{ /interface pppoe-client :local pppoeUptime ([monitor pppoe-out1 once as-value]->“uptime”) :log info “Current PPPoE Uptime: $pppoeUptime” } Use code with caution.

Go to System > Scheduler and create a task to trigger this script every 5 or 10 minutes. For OpenWrt / Linux Routers

OpenWrt keeps track of interface changes natively. You can parse JSON data via the CLI: SSH into your router. Query the raw interface status: ifstatus wan | jsonfilter -e ‘@.uptime’ Use code with caution.

To automate alerts, hook into /etc/ppp/ip-up and /etc/ppp/ip-down directory scripts. Any script dropped here executes automatically the split second your PPPoE link drops or recovers. Method 2: Self-Hosted Docker Monitor (Uptime Kuma) github.com PPPoE Connection Status RouterOS Script – GitHub