Community discussions

MikroTik App
 
edknoch
just joined
Topic Author
Posts: 1
Joined: Tue Mar 31, 2020 10:31 pm

CHR in AWS

Tue Mar 31, 2020 11:22 pm

I have a VPC in the AWS cloud and I am currently testing the Mikrotik CHR. I am able to spin up the CHR and add it to my VPC group as an instance. I then spun up two instances in the VPC, both of which can reach the CHR - routing is working between the devices in the VPC.

At this point, I added a remote router (hap) using an L2TP connection over Cellular (dynamic) to the CHR device on its public interface.

The handshake works and connection is established between the remote and chr router.

In the CHR router, I can ping all devices in the remote network - without issue.

What I cannot do is tunnel through in the VPC on the Outbound Private IP space to the remote router locations.

Network is defined as such:

ether1 --> 192.168.30.250 CHR Router --> L2TP (192.168.77.200) <--> L2TP client (192.168.77.201) --> 10.10.1.1 (Remote Router) --> Edge device (10.10.1.100)

CHR can ping all devices in remote network (10.10.1.0/24) over the L2TP tunnel

VPC Devices in network
Linux Server (192.168.30.30)
Linux Server (192.168.30.31)

Device in VPC in same security network with route created
10.10.1.0/24 ==> Network interface on CHR Router (192.168.30.250)

At this point, I cannot ping or get traffic into the network (on the CHR) over the L2TP VPN.

Is there anyway to resolve this?

Thank you,

Ed
 
HaPe
Member Candidate
Member Candidate
Posts: 241
Joined: Fri Feb 10, 2012 10:24 pm
Location: Poland

Re: CHR in AWS

Tue May 05, 2020 1:29 am

Hello,

have you added routes in VPC to tell servers in your vpc how to reach 192.168.77.x?
Remember to disable Source/Destination Check on the EC2 instance.
In anticipation on new The Dude release.

Who is online

Users browsing this forum: Baidu [Spider] and 4 guests