Modify LAN IP addresses in WireGuard setup guide#935
Modify LAN IP addresses in WireGuard setup guide#935
Conversation
Updated the source and destination addresses for LAN communication in the Mikrotik WireGuard setup instructions.
|
What is the exact part of the NAT section with the errors, and what are the errors? |
I am not sure now. I tried the whole guied step by step and it still does not work. Ping goes, but dns does not work as expected. I applied the guide to fresh reset my Mikrotik 7.21 with default AP configuration, 192.168.88.0 network. I don't know what breaks routing or dns queries. |
|
I have tested the current Mikrotik setup steps on a RouterOS 7.21.3 system using two different private address spaces:
Both WireGuard connections were successful. There are minimal differences between the guide for 7.19.1 and 7.21.3. In the "Configuring WireGuard interface and peer" section, skip steps 6 and 7 because the interface is created automatically. In the "Configuring Routing and Firewall" section's step 5, use You might consider using the IVPN App or a manual WireGuard connection on a computer system to determine the connection settings, like the VPN server and port, that are working for the conditions between your location and our VPN servers, then use those settings in the router to see if the connection is successful. |
|
What initial Mikrotik setup do you use? What are default firewall settings?
…On Mon, Apr 6, 2026, 21:40 jordan-ivpn ***@***.***> wrote:
*jordan-ivpn* left a comment (ivpn/ivpn.net#935)
<#935 (comment)>
I have tested the current Mikrotik setup steps on a RouterOS 7.21.3 system
using two different private address spaces:
- 10.0.0.0/24
- 192.168.88.0/24
Both WireGuard connections were successful.
There are minimal differences between the guide for 7.19.1 and 7.21.3. In
the "*Configuring WireGuard interface and peer*" section, skip steps 6
and 7 because the interface is created automatically. In the "*Configuring
Routing and Firewall*" section's step 5, use %wg1 instead of wg1 for the
gateway.
You might consider using the IVPN App or a manual WireGuard connection on
a computer system to determine the connection settings, like the VPN server
and port, that are working for the conditions between your location and our
VPN servers, then use those settings in the router to see if the connection
is successful.
—
Reply to this email directly, view it on GitHub
<#935 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA663HBKTZF752P3QDBIPVT4UP2YTAVCNFSM6AAAAACWKOV3RKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCOJUGI2TMOBWGQ>
.
You are receiving this because you were mentioned.Message ID: <ivpn/ivpn.
***@***.***>
|
OK, I will try again with my wg server and if it fails I will try IVPN account |
|
https://help.mikrotik.com/docs/spaces/ROS/pages/328151/First+Time+Configuration Specifically, this command to reset everything: ... from: You might prefer to make a backup prior to running the command above, if you elect to run the command above. Then, the commands from these four sections: Once a local LAN client has access to the router's web interface, I followed the setup guide. |
Updated the source and destination addresses for LAN communication in the Mikrotik WireGuard setup instructions.
PR type
What kind of change does this PR introduce?
PR checklist
Please check if your PR fulfills the following requirements:
What is the current behavior?
Issue number: N/A
What is the new behavior?
The configuration starts working. Using 10.x network addr everywhere is misleading and causes errors later in NAT section
Does this PR introduce a breaking change?
Other information