MeshTik turns a full WireGuard mesh setup into a 2-minute job. Describe your nodes once — MikroTik routers, laptops, phones — and get ready-to-paste RouterOS v7 commands plus universal wg-quick configs for every other device in the same mesh. All keys are generated locally in your browser with Curve25519, nothing is uploaded, and it works offline. Free, no account. Download configs individually, as a zip, or scan a QR to import into the WireGuard mobile app.
No reviews yetBe the first to leave a review for MeshTik
love how everything stays in the browser, that was the first thing i checked. one thing that would save me even more time is letting me mark one node as the "hub" and auto-generating the AllowedIPs so the spokes only route through it for internet, instead of a full mesh when i dont need it.
Report
Maker
@sadkz3gy Done, it's live. There's a topology toggle now: switch to hub and spoke, mark one node as the hub, and the spokes only peer with it and reach each other through it. The AllowedIPs get built for you. Thanks for the nudge, this was a good one.
Report
Would be great if MeshTik could detect and warn about overlapping AllowedIPs between nodes when I'm building the mesh, since it's easy to accidentally double up a subnet like 10.0.0.0/24 across two peers and quietly break routing.
Report
Maker
@c_sagd2803 Added this too. If two nodes claim overlapping subnets like your 10.0.0.0/24 example, or a LAN collides with the tunnel range, you now get a warning before you copy anything out. Appreciate the suggestion.
Report
Honestly wish I had this a few months back when I was setting up a WireGuard mesh across three sites, it just spits out RouterOS commands and the wg-quick stuff together which is exactly the annoying part. Also cool that it runs entirely offline so the keys never leave your machine.
Report
Maker
@nerminaydao7wn Ha, I know that exact pain, a three-site setup by hand is pretty much why I built this. Sucks it wasn't around when you needed it, but next time it's got you. And yeah, keeping the keys on your own machine was the one thing I wasn't going to compromise on.
love how everything stays in the browser, that was the first thing i checked. one thing that would save me even more time is letting me mark one node as the "hub" and auto-generating the AllowedIPs so the spokes only route through it for internet, instead of a full mesh when i dont need it.
@sadkz3gy Done, it's live. There's a topology toggle now: switch to hub and spoke, mark one node as the hub, and the spokes only peer with it and reach each other through it. The AllowedIPs get built for you. Thanks for the nudge, this was a good one.
Would be great if MeshTik could detect and warn about overlapping AllowedIPs between nodes when I'm building the mesh, since it's easy to accidentally double up a subnet like 10.0.0.0/24 across two peers and quietly break routing.
@c_sagd2803 Added this too. If two nodes claim overlapping subnets like your 10.0.0.0/24 example, or a LAN collides with the tunnel range, you now get a warning before you copy anything out. Appreciate the suggestion.
Honestly wish I had this a few months back when I was setting up a WireGuard mesh across three sites, it just spits out RouterOS commands and the wg-quick stuff together which is exactly the annoying part. Also cool that it runs entirely offline so the keys never leave your machine.
@nerminaydao7wn Ha, I know that exact pain, a three-site setup by hand is pretty much why I built this. Sucks it wasn't around when you needed it, but next time it's got you. And yeah, keeping the keys on your own machine was the one thing I wasn't going to compromise on.