Hej!
Finns det möjlighet att konfigurera Integrity VPN på en MikroTik-router? Jag har en WireGuard-konfiguration.
Hur gör man i så fall? Jag har försökt flera gånger och även sökt information, men har tyvärr inte lyckats ännu.
Tack
Sätta upp i Mikrotik router??
Re: Sätta upp i Mikrotik router??
"MikroTik routers support WireGuard natively in RouterOS v7.1 and later"
claude kompis kanske kan hjälpa dig.
*Requirements
1 Create the WireGuard interface — In Winbox or the terminal, go to Interfaces → WireGuard → Add New. RouterOS will auto-generate a key pair.
2 Configure the interface
3 Add a peer — Under the WireGuard interface, add a peer with:
Routing — Add a route to send traffic through the WireGuard interface, or adjust your routing table as needed.
Via terminal (quick example)
Tips
claude kompis kanske kan hjälpa dig.
*Requirements
- RouterOS 7.1+ (WireGuard support was added in this version)
- A MikroTik device capable of running RouterOS v7
1 Create the WireGuard interface — In Winbox or the terminal, go to Interfaces → WireGuard → Add New. RouterOS will auto-generate a key pair.
2 Configure the interface
- Set a listen port (default: 13231)
- Note the auto-generated public key (you'll need it for the VPN server)
3 Add a peer — Under the WireGuard interface, add a peer with:
- The server's public key
- Endpoint (server IP + port)
- Allowed addresses (e.g. 0.0.0.0/0 to route all traffic, or a specific subnet)
- Persistent keepalive (e.g. 25 seconds, useful behind NAT)
Routing — Add a route to send traffic through the WireGuard interface, or adjust your routing table as needed.
Via terminal (quick example)
Code: Select all
/interface wireguard add name=wg0 listen-port=13231
/interface wireguard peers add interface=wg0 public-key="<server-pubkey>" \
endpoint-address=<server-ip> endpoint-port=51820 \
allowed-address=0.0.0.0/0 persistent-keepalive=25
/ip address add address=10.0.0.2/24 interface=wg0- Use /interface wireguard print to see your router's public key to register with the server.
- MikroTik's WireGuard implementation is solid but lacks some helper tooling (like wg-quick), so routing and DNS split-tunneling need manual configuration.
- If you're routing all traffic through the VPN, make sure to handle DNS settings explicitly to avoid leaks.