- Reachable
- yes, 41 ms via Relay
- RouterOS
- 7.14.2 → 7.15.3 available
- Last backup
- 2 h ago, 212 KB
- Free flash
- 3.1 MB of 16 MB
Features
Three buttons do all the work: Check, Backup now, Update now. Everything else, the schedules, the Relay tunnel and the alerts, is there so you rarely have to press them.
Part 1 of 3
Three buttons
Everything EdgeOwl does for a router is one of these three actions. Press them when you want; most days you won't have to.
One press, the whole picture
Reachability, version, available update, last backup age, free flash — and five security checks, like “is Winbox open to the internet?”
Check runs on its own after every job and on a schedule, so the dashboard is rarely more than a night old. Press it whenever you want a fresh answer.
Five security checks
- 1Winbox open to the internet. The management port answers on the WAN side.
- 2Default admin user still active. The factory account was never renamed or disabled.
- 3Unused services left on. Telnet, FTP, API or www reachable from outside.
- 4Known vulnerability in this version. The running RouterOS has a published CVE fixed in a later release.
- 5No firewall drop from WAN. The input chain lets new connections in from the internet.
[TODO: confirm the five checks with engineering] The brief names only the first one.
Every night. Or right now.
Full export and binary backup, encrypted within seconds with your key. Every night on schedule, or whenever you press the button.
- Two files per run: the readable export (.rsc) and the binary backup (.backup).
- Encrypted with age (X25519) using your key. We store the encrypted files in AWS Frankfurt and cannot open them.
- Nightly at a time you choose, in the router's own time zone. Press the button before any change you are not sure about.
- Download any copy from the dashboard and restore it without us: age -d -i key.txt backup.rsc.age.
02:00:01 connect ............................ ok (203.0.113.7:22) 02:00:02 /export ............................ ok (14.2 KB) 02:00:04 /system backup save ................ ok (212 KB) 02:00:05 encrypt with age ................... ok (age1q8…k4m) 02:00:06 store eu-central-1 ................. ok 02:00:07 done · next run tomorrow 02:00
Backup first, always
Backup first, always. Then update inside the device's own channel, reboot, verify it came back. You watch every step live.
- If the backup fails, the update does not run.
- Only inside the device's own channel: stable stays stable, long-term stays long-term. Never a jump across major versions automatically.
- After the reboot EdgeOwl waits for the router, runs Check and compares the version. If it does not come back, you get an alert with the last backup ready to restore.
- RouterOS 7 today. RouterOS 6 coming soon; until then we can help you move: migration to v7 is a separate assisted service.
Updates never start on their own. You press the button or approve a scheduled window.
10:41:03 backup export ...................... ok (14 KB) 10:41:05 backup binary ...................... ok (212 KB) 10:41:06 channel: stable · 7.15.3 available 10:41:07 /system package update install ..... ok 10:41:40 reboot ............................. waiting ▍ verify version ..................... pending check .............................. pending
Part 2 of 3
Automatic, on a schedule
You don't run the three buttons by hand every day. Backups and updates run on a schedule we switch on for every router, and Check runs after every job.
Schedules you can change
We switch the schedule on for every new router with our recommended settings; you change it in the dashboard whenever you like.
- Backups: we recommend 2–3 a week. You can go up to once a day. Pick the days and the hour in the router's own time zone.
- Updates: we recommend once a week. A new RouterOS release waits for your update day; you get a notification first, and on that day it installs, backup first, always.
- Turn a schedule off per router if you prefer to press the buttons yourself.
[TODO: critical security updates — same-day policy to confirm]
Part 3 of 3
Everything around them
Two things make the buttons work everywhere and keep you informed: the Relay tunnel for routers without a public IP, and alerts that only speak up when something needs you.
No public IP? No problem.
Router behind NAT or CGNAT? EdgeOwl Relay connects it through an outbound tunnel. Included in every plan.
- The router opens the tunnel itself: SSTP on RouterOS 7. No port forwarding, nothing to open on the firewall.
- Relay servers run at Hetzner in Germany. Only EdgeOwl jobs travel through the tunnel.
- Enable it per device in the settings. Turn it off and the tunnel is gone.
- RouterOS 7
- SSTP, TCP 443 out
- Inbound ports
- none
Telegram and email alerts
EdgeOwl tells you when something needs attention. Not every night, only when a job fails, a device stops answering or an update is waiting.
- Backup failed, update failed, device unreachable, new RouterOS in the device's channel.
- One message per event, with the device name and the next step. No daily digest unless you ask for one.
- Connect a Telegram chat per client, so each client sees only their own routers.
warehouse did not answer the 02:00 check.
RB750Gr3 · RouterOS 7.14.2 · last backup 3 d ago · Relay off
Last reachable: yesterday 23:12. The backup from 31 Oct is ready to restore.