EoIP tunnel in CHR or x86 VM don´t permit bridge

RouterOS Virtualization
1

Hello,

I need extend my LAN from my office DC (RB2011-iUAS-RM - L4 License << MKT1 >>) to a vDC in a cloud provider in my country, I have a vDC (CHR P1 License <>) with internet connection and vApp network with 3 VMs 2 Windows and 1 Linux.

I create a EoIP and bridge interfaces in MKT1 and including LAN interface and EoIP tunnel, my Office LAN devices don’t lose connection, in MKT2 create EoIP and bridge interfaces, the EoIP attached to the bridge and when I include the LAN port to the bridge, vDC LAN lose connection to router and don’t send packets to another side of EoIP Tunnel.

This configuration on physic RB Mikrotik is OK but when move to CHR or VM with X86 RouterOS installation not.

2

Hi

I have the same problem on Hyper-v and i solved the issue enabling the Mac-Address spoofing on the CHR NIC.

The miktoik support tell me that “though EoIP itself together with bridge change MAC-address.”

Also check this in the CHR manual (http://wiki.mikrotik.com/wiki/Manual:CHR) in the last paragraph

Packets not passing from guests
The problem: after configuring a software interface (VLAN, EoIP, bridge, etc.) on the guest CHR it stops passing data to the outside world beyond the router.

The solution: check your VMS (Virtualization Management System) security settings, if other MAC addresses allowed to pass if packets with VLAN tags allowed to pass through. Adjust the security settings according to your needs like allowing MAC spoofing or certain MAC address range. For VLAN interfaces, it is usually possible to define allowed VLAN tags or VLAN tag range.

3

Do you know if this solution is applicable to AWS cloud? I have exacly the same issue running EoIP+Bridge to AWS…

Thanks

4

[quote=Myaircloud post_id=888582 time=1635735864 user_id=191043]
I have this problem: after the EOIP is connected, the client can obtain the IP address of the VLAN that the headquarters needs to be connected, but it cannot communicate for some reason.
[/quote]

Were you able to figure it out? I am having a similar issue.

5

I think these problems are indeed related to mac address spoofing.
I am using CHR and EoIP with Hyper-V for a long time and everything is working until now.