PtP setup between two independet LAN - help needed

RouterOS Beginner Basics
1

Hi,
i am completely new to Mikrotik and need a bit of guidance on how to setup a PtP between two independent LAN using Mikrotik Metal2 SHPn.
To minimize traffic over air, i think the best solution is to setup both ends of the PtP as router so only traffic that goes from one to the other LAN passes?
However i am not sure what type i have to configure for the AP and client, where to put in the LAN and WLAN IP addresses and the static routes.
I would appreciate if anybody could give me a quick step-by-step guide please.

What i got is:
-) LAN1: 192.168.1.0/24
-) LAN2: 192.168.2.0/24
What i try to do is:
-) LAN1: 192.168.1.0/24
-) Mikrotik Metal2 SHPn as router and AP
-) PtP Network IP e.g. 192.168.3.0/30
-) Mikrotik Metal2 SHPn as router and Client
-) LAN2: 192.168.2.0/24

2

My configuration so far is:

-) First Mikrotik in “WISP AP” + router mode
-) Second Mikrotik in “PtP bridge” mode

The WISP AP side with router mode works ok so the LAN and the wireless link are “isolated”.
However the other side (PtP bridge mode) has no router functionality and thus no isolation between the LAN and the wireless link.

Can anybody tell me how to correctly configure that side (with router functionality)?

Thanks

3

So you’re not having a WAN uplink on site2?

On site 1, configure wlan1 as AP, on site 2 as station.
Do not bridge anything.
Assign 192.168.3.1/30 to wlan1 on site 1.
Assign 192.168.3.2/30 to wlan1 on site 2.

On site1, add the route for site2:

/ip route
add distance=10 gateway=192.168.3.2 dst-address=192.168.2.0/24

On site2, simply add a default route

/ip route
add distance=1 gateway=192.168.3.1

Apply all the settings you like for having site2 a seperate LAN (like DHCP-server, local address (bound to ether1), etc.)
Do not use NAT rules on site2 - you want your intra-LAN traffic routed. Let site1 do the NAT for connections going out through WAN.
In case you want Queues, better implement the queues for site2 on their router, not on site1.
Off you go.

-Chris

4

hi cdiedrich.

thank you very much for your detailled help!
i got two questions:

1.) is there a special reason why you use a “/30” network mask for the intra-lan segment? is there a performance benefit or just because there are only 2 addresses needed?
2.) if i use an extra router with a WAN port at site 2, would i then setup the mikrotik device on site 2 as PtP bridge?

thanks
ubimikro

5

Good morning ubimikro,

for your question1:
Transport networks are normally designed to have the smallest possible address space - no performance gain, but more space within the same range to add more transport networks.
And I just copied it from your initial post - where you already mentioned a /30 network :wink:

For question2:
No, still no bridge.
In this case, you’ll add a route in the new router:


/ip route
add distance=10 dst-address=192.168.1.0/24 gateway=192.168.2.<local IP of your PtP client>

And on your PtP client:

/ip route
add distance=1 gateway=192.168.2.1 #if this should be your WAN router
add distance=10 dst=address=192.168.1.0/24 gateway=192.168.3.1

-Chris

6

Thanks again Chris for your help!
I think i’ll stay with this solution if there are no dawbacks using CLE bridge mode:

LAN1: 192.168.1.0/24

PtP WLAN link: Mikrotik WISP AP mode (ap-bridge) 192.168.3.1/29
PtP WLAN link: Mikrotik CLE mode (station bridge) 192.168.3.2/29

@LAN2: WLAN router with WAN-port set to 192.168.3.3/29

LAN2: 192.168.2.0/24