The whole home behind Prizrak: set it up once on a MikroTik and every device on your network is protected — phones, TVs, consoles. Clients configure nothing. Runs in a RouterOS 7 container.
Version 1.0.0 · changelog. Not sure which image? Run /system/resource print and look at «architecture-name»: arm → armv7, arm64 → arm64, x86_64 → x86_64 (RouterOS x86 / CHR).
Set up on the router — every device on the LAN goes through Prizrak automatically. No app on each phone or laptop.
Transparent gateway: devices just use the internet as usual, their traffic is routed through Prizrak by the router.
The same censorship-resistant transport as the Prizrak apps — to anyone watching the line it looks like ordinary TLS to a web site.
Choose the exit country; if it has no working exit, Prizrak uses the nearest one and comes back on its own.
A ~10 MB static image for the RouterOS 7 container — just the client and CA certificates, nothing else.
One firewall rule routes the LAN through Prizrak; disable it to go direct. Works alongside your usual router rules.
Transparent-gateway mode — the whole LAN goes through Prizrak. About 10 minutes. You need RouterOS 7 with the container package and a USB drive.
Enable containers. Install and enable the container package (System → Packages), then turn on container mode (needs physical access, confirmed by reset or power within 5 min): /system/device-mode/update container=yes.
Copy the image to USB. Plug in a USB drive (it becomes usb1) and copy the right .tar onto it — armv7 for hAP ac², arm64 for RB5009 / hAP ax.
Run the installer. Put deploy/install.rsc next to it, check its variables (drive name, your LAN interface, country) and run /import deploy/install.rsc — it creates the container network, the container and the transparent gateway.
Bind the device. The container writes a binding code; enter it in the Prizrak app: Prizrak VPN → devices. A Prizrak VPN subscription (or free trial) activates the exit.
Route the LAN through it. Once bound, enable the routing rule from install.rsc so the whole LAN goes through Prizrak. To switch the VPN off later, just disable that rule.
# 1) включить режим контейнеров (нужен физический доступ, подтвердить reset/питанием за 5 мин) /system/device-mode/update container=yes # 2) залить образ на USB и запустить сценарий «прозрачный шлюз» # проверь в install.rsc переменные: IMG (имя диска/файла), LANIF (твой мост), COUNTRY /import deploy/install.rsc # 3) код привязки устройства — ввести в приложении: Prizrak VPN → устройства /file print where name~"pz-data/status" /log print where topics~"container"
mikrotik/README-INSTALL.txt and mikrotik/deploy/install.rsc that ship with the project. Proxy mode (SOCKS instead of a gateway) is available too — set cmd="serve 0.0.0.0:1080 DE raw" in the container.Run /system/resource print on the router and look at «architecture-name»: arm means armv7 (e.g. hAP ac²), arm64 means arm64 (e.g. RB5009, hAP ax), x86_64 means the x86 image (RouterOS x86 or CHR on a PC/VM). Pick the matching .tar.
Download the new image, copy it to USB, and re-add the container pointing at the new file (stop and remove the old one first). The device binding and settings live on the USB drive (/data), so they survive the update. The current version and what changed are on the changelog.
Your connection to the Prizrak network uses the same encrypted stealth transport as the apps, and your real IP is hidden from the sites you visit. As with any VPN, for the content itself keep using HTTPS. Details on VPN security are on the Prizrak VPN page.
Any MikroTik on RouterOS 7 with the container feature and enough RAM — ARM32 (armv7), ARM64 and x86 devices. Tested on hAP ac² (armv7); RB5009 and hAP ax use arm64; x86 RouterOS and CHR (Cloud Hosted Router) use the x86_64 image.