Community discussions

MikroTik App
 
n1kt0
just joined
Topic Author
Posts: 12
Joined: Sun Dec 07, 2014 9:44 pm

Transmit loop detected

Sun Dec 07, 2014 10:13 pm

hello all
I have RB951G-2HnD and 750GL
I wont PPTP+ EoIP
Add in 750GL PPTP Server and configure it add in 951G-2HnD PPTP Client
But when I configure EoIP
/interface eoip add name=eoip-vpn local-address=88.77.66.1 remote-address=88.77.66.100 tunnel-id=0 disabled=no
/interface bridge add name=bridge-vpn disabled=no
/interface bridge port add bridge=bridge-vpn interface=ether1
/interface bridge port add bridge=bridge-vpn interface= eoip-vpn
In log
Message: eoip-vpn transmit loop detected, downing interface for 60 seconds

Sorry for my English
 
n1kt0
just joined
Topic Author
Posts: 12
Joined: Sun Dec 07, 2014 9:44 pm

Re: Transmit loop detected

Tue Dec 09, 2014 7:31 pm

I want to explain as a the network is arranged.
Perhaps a problem in this.

Sorry for my English
You do not have the required permissions to view the files attached to this post.
 
n1kt0
just joined
Topic Author
Posts: 12
Joined: Sun Dec 07, 2014 9:44 pm

Re: Transmit loop detected

Wed Dec 10, 2014 1:27 pm

hello all

I found information that some have the same situation.
At 6.19 everything works at 6.22 gives out a mistake.

Some bug 6.22 can do it?
 
n1kt0
just joined
Topic Author
Posts: 12
Joined: Sun Dec 07, 2014 9:44 pm

Re: Transmit loop detected

Fri Dec 19, 2014 5:49 pm

At least tell why there is a loop.
I understand that because of that that one interface how to get out of this situation?

Somebody do this scheme?

Please help.
 
User avatar
smarag
newbie
Posts: 27
Joined: Fri Jun 04, 2004 9:06 am
Location: Piraeus - Athens - Greece
Contact:

Re: Transmit loop detected

Sun Apr 19, 2015 2:30 pm

i have this problem in ver 6.22 and 6.28rc20.
 
tambu
just joined
Posts: 9
Joined: Tue Nov 26, 2013 5:06 pm

Re: Transmit loop detected

Wed May 27, 2015 10:46 am

i have vlans over eoip (in bridge all interfaces and eoip too) and when i upgraded routeros from 6.19 to 6.26, 6.27, 6.28 I got a problem: "interface,warning eoip-tunnel1 transmit loop detected, downing interface for 60 seconds"
the problem occurs when the client (wifi) connected to mikrotik. Client wds added to bridge.

what is the problem? how to solve? on 6.19 all works.
 
tambu
just joined
Posts: 9
Joined: Tue Nov 26, 2013 5:06 pm

Re: Transmit loop detected

Tue Dec 22, 2015 9:15 am

up! please, what's happening
the problem is still not resolved
 
Zorro
Long time Member
Long time Member
Posts: 675
Joined: Wed Apr 16, 2014 2:43 pm

Re: Transmit loop detected

Tue Dec 22, 2015 10:50 am

thats why for Legacy MIPS-BE chips/SoC 6.5 remain my Favorite version of ROS, among other things.
bottom line: its nice when newer features added without breaking Older ones. which may had sometimes More use than fancy new.
 
telnetpr
newbie
Posts: 29
Joined: Fri Dec 18, 2015 9:02 pm

Re: Transmit loop detected

Tue Dec 22, 2015 2:53 pm

Verify in the bridge settings in STP TAB is set to NONE, default is RSTP
 
tambu
just joined
Posts: 9
Joined: Tue Nov 26, 2013 5:06 pm

Re: Transmit loop detected

Wed Dec 23, 2015 10:30 am

Verify in the bridge settings in STP TAB is set to NONE, default is RSTP
in bridge settings in STP tab i set NONE, yes. But it not resolved the problem.
I understand that the loop can not be in my network, in this case
tunnel go down only when connected to an access point wi-fi customers.
 
telnetpr
newbie
Posts: 29
Joined: Fri Dec 18, 2015 9:02 pm

Re: Transmit loop detected

Wed Dec 23, 2015 4:35 pm

Verify in the bridge settings in STP TAB is set to NONE, default is RSTP
in bridge settings in STP tab i set NONE, yes. But it not resolved the problem.
I understand that the loop can not be in my network, in this case
tunnel go down only when connected to an access point wi-fi customers.
Run a debug to see what happen.

Some years ago, i was having this problem or close to yours. My problem was because of a duplicate IP address with my tunnel and other device.
 
stonet
just joined
Posts: 2
Joined: Sat Sep 06, 2014 3:15 pm

Re: Transmit loop detected

Wed Mar 09, 2016 9:49 pm

I too have this problem,

I have an eoip tunnel riding inside a L2TP tunnel. The EOIP Tunnel is bridged to an ethernet port and all is well. If I add a DHCP client to the bridge that bridges the eoip tunnel and the ethernet port the tunnel immediately drops and the error message eoip tunnel transmit loop detected appears in the log. If I then remove the DHCP client the tunnel comes back up.

I am doing this on a RB493 with 6.33.3 without problems but it is happening on a 750UP with 6.33.3, I upgraded the 750UP to 6.34.2 and it still happens.
 
chpoqxie
just joined
Posts: 1
Joined: Sat May 21, 2016 3:46 pm

Re: Transmit loop detected

Sat May 21, 2016 3:59 pm

the version 6.22 has changes:
*) eoip/eoipv6/gre/gre6/ipip/ipipv6/6to4 tunnels have new features:
tunnels go down when no route to destination;
tunnels go down for 1 minute when transmit loop detected, warning gets logged;
new keepalive-retries setting;
keepalives enabled by default for new tunnels (10sec interval, 10 retries);
so... i have bug with "transmit loop detected" too on versions 6.30, 6.32, 6.34. on misc mikrotik models.
i am sure that my many small networks have no loops.
i am fix it by killing "bugged" eoip tunnel and make another with the same settings. and it works perfectly for weeks and months.

but WHY? why the interface not UP after "downing interface for 60 seconds" even if there was a loop?? i think it was a bad bugged changes (or "bug'o'features") in 6.22 version.

please fix this bug, mikrotik developers.
 
IHRMax
just joined
Posts: 5
Joined: Thu Feb 27, 2014 6:35 pm

Re: Transmit loop detected

Sun May 22, 2016 9:33 pm

same problem here on random Routerboard, please fix
 
ffrauter
just joined
Posts: 23
Joined: Mon May 16, 2011 12:43 pm

Re: Transmit loop detected

Sat Aug 06, 2016 9:12 pm

Same problem here with 6.30.4
EoIP Tunnels go down and stay down until rebooting the router. "transmit loop detected, downing interface for 60 seconds"

Are there any infos how to fix that problem?

Thanks Florian
 
ffrauter
just joined
Posts: 23
Joined: Mon May 16, 2011 12:43 pm

Re: Transmit loop detected

Fri Aug 12, 2016 10:26 am

For all those who have the same problem with "Transmit loop detected".

There is a BUG in RouterOS 6.30 when the UPTIME is more than 248 days. EOIP Tunnels go down until TIK is rebooted. You find in log the "Transmit loop detected, downing interface ...."
This bug should be solved in 6.34, which I was told by Mikrotik support. I will update and try it, but I have to wait. ;-)

Addition info: In 6.29.1 I have one Router online which do NOT have this problem.

Regards Florian
 
tambu
just joined
Posts: 9
Joined: Tue Nov 26, 2013 5:06 pm

Re: Transmit loop detected

Fri Jan 27, 2017 4:54 pm

i have vlans over eoip (in bridge all interfaces and eoip too) and when i upgraded routeros from 6.19 to 6.26, 6.27, 6.28 I got a problem: "interface,warning eoip-tunnel1 transmit loop detected, downing interface for 60 seconds"
the problem occurs when the client (wifi) connected to mikrotik. Client wds added to bridge.

what is the problem? how to solve? on 6.19 all works.
today i have routeros 6.37.3 and problem not solved.
why the developers did not fix this bug? remove the tunnel disconnection mechanism (loop detected)
 
qwerty00
just joined
Posts: 18
Joined: Thu Feb 16, 2017 11:38 am

Re: Transmit loop detected

Tue Mar 14, 2017 11:59 am

Hi,
are there updates about this issue?
I have this problem for a long time now and i use differente routerOS versions.
Sometimes there is the log "eoip-tunnel1 transmit loop detected, downing interface for 60 seconds" but the interface does not return up.
Is there a way to resolve this problem with keep-alive timeout or similar?

Thanks
 
qwerty00
just joined
Posts: 18
Joined: Thu Feb 16, 2017 11:38 am

Re: Transmit loop detected

Fri Aug 04, 2017 4:11 pm

Hello,

are there any news, on RouterOS higher than 6.37, about this problem?

This is part of the changelog for version 6.39.
Should this have impact on the issue?
What's new in 6.39 (2017-Apr-27 10:06):
*) tunnels - fixed reboot loop on configurations with IPIP and EoIP tunnels (introduced in 6.39rc68);
 
minelli
newbie
Posts: 44
Joined: Tue Feb 26, 2008 2:36 am

Re: Transmit loop detected

Thu Jan 04, 2018 4:18 pm

No solution yet?
 
skisawa
just joined
Posts: 2
Joined: Fri Feb 23, 2018 12:01 am

Re: Transmit loop detected

Fri Feb 23, 2018 12:14 am

For all those who have the same problem with "Transmit loop detected".

There is a BUG in RouterOS 6.30 when the UPTIME is more than 248 days. EOIP Tunnels go down until TIK is rebooted. You find in log the "Transmit loop detected, downing interface ...."
This bug should be solved in 6.34, which I was told by Mikrotik support. I will update and try it, but I have to wait. ;-)

Addition info: In 6.29.1 I have one Router online which do NOT have this problem.

Regards Florian
i found in version 6.29.1 , i with upgrade to version 6.33.6
 
skisawa
just joined
Posts: 2
Joined: Fri Feb 23, 2018 12:01 am

Re: Transmit loop detected

Fri Feb 23, 2018 12:15 am

For all those who have the same problem with "Transmit loop detected".

There is a BUG in RouterOS 6.30 when the UPTIME is more than 248 days. EOIP Tunnels go down until TIK is rebooted. You find in log the "Transmit loop detected, downing interface ...."
This bug should be solved in 6.34, which I was told by Mikrotik support. I will update and try it, but I have to wait. ;-)

Addition info: In 6.29.1 I have one Router online which do NOT have this problem.

Regards Florian
i found in version 6.29.1 , i with upgrade to version 6.33.6
 
User avatar
Chaosphere64
Frequent Visitor
Frequent Visitor
Posts: 94
Joined: Wed Aug 10, 2016 10:19 pm

Re: Transmit loop detected

Wed Sep 19, 2018 11:00 am

Still facing the error, and I am totally sure that there is no loop in my network.

RouterOS version is 6.43.1. Maybe the MT devs take another look at this problem.

Will try to remove and recreate the EoIP tunnel (interface) like chpoqxie suggested.
 
User avatar
Chaosphere64
Frequent Visitor
Frequent Visitor
Posts: 94
Joined: Wed Aug 10, 2016 10:19 pm

Re: Transmit loop detected

Tue Nov 06, 2018 9:27 pm

Still facing the error, and I am totally sure that there is no loop in my network.

RouterOS version is 6.43.1. Maybe the MT devs take another look at this problem.

Will try to remove and recreate the EoIP tunnel (interface) like chpoqxie suggested.
Mea culpa. This time it IS my fault, I made a mistake while configuring an EoIP tunnel over a WiFi bridge using CAPsMAN. Bridged a CAP interface solely used for the WiFi bridge together with the EoIP tunnel interface because I was just looking for an unwanted radio on the Bridge.

So it was basically a Layer 8 problem ...
 
User avatar
vecernik87
Forum Veteran
Forum Veteran
Posts: 882
Joined: Fri Nov 10, 2017 8:19 am

Re: Transmit loop detected

Sun Dec 09, 2018 3:19 am

It seems that I had bad luck with this issue as well. I can confirm in my case, switching bridge from RSTP to NONE on one of devices helped (does not seem to matter which one). Also it does not seem to matter, if there is additional switch with RSTP enabled. Also it does not matter if the bridge has any other port other than EOIP (which proves there can't be a loop if there is only one port in the bridge)

To summarize it - I believe it is happening only, when EOIP is connected directly to RSTP bridge on both ends.
 
Kraken2k
Frequent Visitor
Frequent Visitor
Posts: 72
Joined: Wed Oct 01, 2014 1:50 pm
Location: Prague

Re: Transmit loop detected

Wed Mar 30, 2022 4:40 pm

I started to experience the same behavior after upgrading from RoS v6.48.1 to 7.1.3 with both IP-IP and EoIP tunnels (until then, they were working with the same configuration without any issue). Now I'm getting "eoip-tunnel-1 transmit loop detected, downing interface for 60 seconds" error all the time.

On both sides, tunnels are added to bridges to provide L2 connectivity between devices and the tunnel usually fails after sending some amount of data through, so I assume this is not connected with any regular mechanism that actually checks for loops.

I tried to disable all loop detection mechanisms on both sides (on the tunnel interfaces and on the bridges) but the message keeps coming and the interface is being disabled. Makes me wonder, which RoS mechanism actually does this.
 
aoakeley
Member Candidate
Member Candidate
Posts: 171
Joined: Mon May 21, 2012 11:45 am

Re: Transmit loop detected

Thu Mar 31, 2022 5:11 am

I started to experience the same behavior after upgrading from RoS v6.48.1 to 7.1.3 with both IP-IP and EoIP tunnels (until then, they were working with the same configuration without any issue). Now I'm getting "eoip-tunnel-1 transmit loop detected, downing interface for 60 seconds" error all the time.

On both sides, tunnels are added to bridges to provide L2 connectivity between devices...........
Same after upgrade to 7.1.5
Tried disabling STP on the bridge at both ends, but the issue persists.
 
gp700
just joined
Posts: 3
Joined: Fri Apr 15, 2022 9:32 am

Re: Transmit loop detected

Fri Apr 15, 2022 9:58 am

The same problem after updating RB4011iGS+ to version 7. Upgrading to 7.2 did not help. At 6.48.6 it worked without errors.
"eoip-tunnel1 transmit loop detected, downing interface for 60 seconds"
Is there a solution to this problem?
 
Kraken2k
Frequent Visitor
Frequent Visitor
Posts: 72
Joined: Wed Oct 01, 2014 1:50 pm
Location: Prague

Re: Transmit loop detected

Thu Jun 02, 2022 5:56 pm

The issue still persists on 7.2.3
 
gp700
just joined
Posts: 3
Joined: Fri Apr 15, 2022 9:32 am

Re: Transmit loop detected

Wed Jun 15, 2022 12:59 pm

In 7.2.3 the problem is fixed. However, a new one has appeared: routing rules have stopped working on the interface with two IPs.
This may not be a related error. I will create a new topic.
/routing rule add action=lookup disabled=no dst-address=172.19.33.200/32 interface=bridge-local src-address=192.168.1.200/32 table=main
/routing rule add action=lookup disabled=no dst-address=192.168.1.200/32 interface=bridge-local src-address=172.19.33.200/32 table=main
 
ethernet
just joined
Posts: 22
Joined: Tue Aug 25, 2009 1:44 am

Re: Transmit loop detected

Mon Jun 20, 2022 12:54 am

No, the problem is NOT fixed in 7.2.3. Has someone tested 7.3.1?
 
gp700
just joined
Posts: 3
Joined: Fri Apr 15, 2022 9:32 am

Re: Transmit loop detected

Mon Jun 20, 2022 11:14 am

In 7.2.3 the problem is fixed. However, a new one has appeared: routing rules have stopped working on the interface with two IPs.
This may not be a related error. I will create a new topic.
/routing rule add action=lookup disabled=no dst-address=172.19.33.200/32 interface=bridge-local src-address=192.168.1.200/32 table=main
/routing rule add action=lookup disabled=no dst-address=192.168.1.200/32 interface=bridge-local src-address=172.19.33.200/32 table=main
Sorry, this applies to version 7.3.1
 
Kraken2k
Frequent Visitor
Frequent Visitor
Posts: 72
Joined: Wed Oct 01, 2014 1:50 pm
Location: Prague

Re: Transmit loop detected

Wed Jun 22, 2022 11:36 am

I can confirm, that this issue is fixed in 7.3.1 - I've updated RoS yesterday and tested intensively since then. EoIP tunnels are stable.

Thanks!
 
MikeKulls
Member Candidate
Member Candidate
Posts: 130
Joined: Thu Dec 22, 2016 4:31 am

Re: Transmit loop detected

Thu Jul 21, 2022 7:25 am

I can confirm, that this issue is fixed in 7.3.1 - I've updated RoS yesterday and tested intensively since then. EoIP tunnels are stable.

Thanks!
I can confirm it's an issue in 7.3.1. I've been trying to bridge 2 Mikrotiks wirelessly for a month. I tried WDS, that got about 100 "unicast key exchange" errors a day, I tried station bridge mode, that got about 8 links down a day. Now I'm trying station mode with EoIP and that is a lot better but I got one "transmit loop detected" error in 24hrs. The fact it only gives this error once in 24 hrs should mean I don't have a loop?? Both boxes are 7.3.1. Cut down config below.
/interface bridge
add admin-mac=4C:5E:0C:EE:CD:48 auto-mac=no name=BRIDGE_MAIN protocol-mode=none

/interface eoip
add allow-fast-path=no local-address=192.168.7.2 mac-address=02:39:3D:0C:60:A5 name=EOIP_MAIN remote-address=192.168.7.1 tunnel-id=12345

/interface wireless security-profiles
add authentication-types=wpa2-psk eap-methods="" mode=dynamic-keys name=PROFILE_MIKE supplicant-identity=""

/interface wireless
set [ find default-name=wlan1 ] band=2ghz-onlyn country=australia disabled=no distance=indoors frequency=2437 installation=indoor name=WLAN_UPLINK radio-name=Tavern security-profile=PROFILE_MIKE ssid=Uplink
add disabled=no keepalive-frames=disabled mac-address=4E:5E:0C:EE:CD:4D master-interface=WLAN_UPLINK multicast-buffering=disabled name=WLAN_TEST security-profile=PROFILE_MIKE ssid=Test

/interface bridge port
add bridge=BRIDGE_MAIN interface=ether4
add bridge=BRIDGE_MAIN interface=EOIP_MAIN
add bridge=BRIDGE_MAIN interface=WLAN_TEST

/ip address
add address=192.168.3.2/24 interface=BRIDGE_MAIN network=192.168.3.0
add address=192.168.7.2/30 interface=WLAN_UPLINK network=192.168.7.0
 
User avatar
sergejs
MikroTik Support
MikroTik Support
Posts: 6695
Joined: Thu Mar 31, 2005 3:33 pm
Location: Riga, Latvia
Contact:

Re: Transmit loop detected

Tue Sep 13, 2022 4:44 pm

I can confirm, that this issue is fixed in 7.3.1 - I've updated RoS yesterday and tested intensively since then. EoIP tunnels are stable.

Thanks!
I can confirm it's an issue in 7.3.1. I've been trying to bridge 2 Mikrotiks wirelessly for a month. I tried WDS, that got about 100 "unicast key exchange" errors a day, I tried station bridge mode, that got about 8 links down a day. Now I'm trying station mode with EoIP and that is a lot better but I got one "transmit loop detected" error in 24hrs. The fact it only gives this error once in 24 hrs should mean I don't have a loop?? Both boxes are 7.3.1. Cut down config below.
/interface bridge
add admin-mac=4C:5E:0C:EE:CD:48 auto-mac=no name=BRIDGE_MAIN protocol-mode=none

/interface eoip
add allow-fast-path=no local-address=192.168.7.2 mac-address=02:39:3D:0C:60:A5 name=EOIP_MAIN remote-address=192.168.7.1 tunnel-id=12345

/interface wireless security-profiles
add authentication-types=wpa2-psk eap-methods="" mode=dynamic-keys name=PROFILE_MIKE supplicant-identity=""

/interface wireless
set [ find default-name=wlan1 ] band=2ghz-onlyn country=australia disabled=no distance=indoors frequency=2437 installation=indoor name=WLAN_UPLINK radio-name=Tavern security-profile=PROFILE_MIKE ssid=Uplink
add disabled=no keepalive-frames=disabled mac-address=4E:5E:0C:EE:CD:4D master-interface=WLAN_UPLINK multicast-buffering=disabled name=WLAN_TEST security-profile=PROFILE_MIKE ssid=Test

/interface bridge port
add bridge=BRIDGE_MAIN interface=ether4
add bridge=BRIDGE_MAIN interface=EOIP_MAIN
add bridge=BRIDGE_MAIN interface=WLAN_TEST

/ip address
add address=192.168.3.2/24 interface=BRIDGE_MAIN network=192.168.3.0
add address=192.168.7.2/30 interface=WLAN_UPLINK network=192.168.7.0
Make sure EOIP remote IP address is not reachable over the bridge, where interface is added.
 
starcomwi
just joined
Posts: 1
Joined: Tue Apr 18, 2023 8:19 pm

Re: Transmit loop detected

Tue Apr 18, 2023 8:21 pm

To correct this issue you need to set up a separate loopback address on each router to connect the EOIP to .
 
pjkundert
just joined
Posts: 7
Joined: Tue Aug 18, 2009 5:48 am

Re: Transmit loop detected

Tue Oct 03, 2023 10:53 pm

To correct this issue you need to set up a separate loopback address on each router to connect the EOIP to .
I would be *very* interested to discuss this further with you -- I've been strugging for weeks to get EoIP links working...
 
pjkundert
just joined
Posts: 7
Joined: Tue Aug 18, 2009 5:48 am

Re: Transmit loop detected

Wed Oct 11, 2023 7:50 pm



I can confirm it's an issue in 7.3.1. I've been trying to bridge 2 Mikrotiks wirelessly for a month. I tried WDS, that got about 100 "unicast key exchange" errors a day, I tried station bridge mode, that got about 8 links down a day. Now I'm trying station mode with EoIP and that is a lot better but I got one "transmit loop detected" error in 24hrs. The fact it only gives this error once in 24 hrs should mean I don't have a loop?? Both boxes are 7.3.1. Cut down config below.
/interface bridge
add admin-mac=4C:5E:0C:EE:CD:48 auto-mac=no name=BRIDGE_MAIN protocol-mode=none

/interface eoip
add allow-fast-path=no local-address=192.168.7.2 mac-address=02:39:3D:0C:60:A5 name=EOIP_MAIN remote-address=192.168.7.1 tunnel-id=12345

/interface wireless security-profiles
add authentication-types=wpa2-psk eap-methods="" mode=dynamic-keys name=PROFILE_MIKE supplicant-identity=""

/interface wireless
set [ find default-name=wlan1 ] band=2ghz-onlyn country=australia disabled=no distance=indoors frequency=2437 installation=indoor name=WLAN_UPLINK radio-name=Tavern security-profile=PROFILE_MIKE ssid=Uplink
add disabled=no keepalive-frames=disabled mac-address=4E:5E:0C:EE:CD:4D master-interface=WLAN_UPLINK multicast-buffering=disabled name=WLAN_TEST security-profile=PROFILE_MIKE ssid=Test

/interface bridge port
add bridge=BRIDGE_MAIN interface=ether4
add bridge=BRIDGE_MAIN interface=EOIP_MAIN
add bridge=BRIDGE_MAIN interface=WLAN_TEST

/ip address
add address=192.168.3.2/24 interface=BRIDGE_MAIN network=192.168.3.0
add address=192.168.7.2/30 interface=WLAN_UPLINK network=192.168.7.0
Make sure EOIP remote IP address is not reachable over the bridge, where interface is added.
I have been struggling for months, now, trying to connect an EoIP link across a wireless link, unsuccessfully. Worst problem: it will fail for hours due to "transmit loop detected, downing interface for 60 seconds" -- and then, start working and continue working reliably! So, there is some bug still in this transmit loop detection code.

But, regardless -- could you post simple example of an L2 connection between two bridges, over a wireless link? I've tried to use all kinds of filtering that I can think of, to prevent "EOIP remote IP address is not reachable over the bridge", without success. I'm sure it'll be obvious, when you post a working example...
 
pjkundert
just joined
Posts: 7
Joined: Tue Aug 18, 2009 5:48 am

Re: Transmit loop detected - SOLVED!

Mon Dec 04, 2023 9:57 pm

Well, I finally solved this "transmit loop detected" issue with EoIP connections.

It is indeed a bug (still exists, as of v7.12.1).

Here is the way to replicate the problem:

Set up a wireless link between 2 Routeros devices: wireless antenna (A) and wireless client (C). This may be via a manually configured 802.11 connection, or one controlled by a CAPsMAN controller. It doesn't matter if you configure the datapath to enable "local routing" or not, or if you use VLAN routing or not -- the "transmit loop detected" defect can be triggered, either way.

(A) <- (... 802.11 ...) -> (C)

WORKING:

Now, to observe that EoIP works, follow the instructions in https://help.mikrotik.com/docs/display/ROS/EoIP. You can observe that you have two bridges (one on each device) that are now connected as a layer-2 broadcast domain. You will not observe any "transmit loop detected" issues.



TO TRIGGER THE "transmit loop detected" DEFECT:

Next, to observe the "transmit loop detected" defect, alter the test bed as follows.

Add a third RouterOS device (M). In my case, the CAPsMAN manager router (M) was managing a second CAP antenna (A), which provided the wireless link to the client routeros device (C):

(M) <-(Ethernet)-> (A) <- (... 802.11 ...) -> (C)

Once the wireless link is working, establish the EoIP connection NOT between the remote client (C) and the router containing the wireless antenna (A) -- but establish it between the client (C) and the third router (M), you just added.

You will observe that, most of the time but not all of the time, that router (M) will complain about a "transmit loop detected".


TO SOLVE THE "transmit loop detected" DEFECT:

So, how do you work around this? Protect the traffic between the client (C) and the other endpoint of the EoIP connection (M) -- you must establish an IPIP (or wireguard, or whatever) tunnel connection between EoIP endpoint devices (M) and (C)! Once the actual route of the EoIP traffic is "hidden" inside this tunnel, the EoIP implementation in (M) sees that traffic arriving locally (not coming in over an Ethernet port), and does not falsely detect a "transmit loop".

@sergejs, would it be possible to escalate this at Mikrotik? Thanks,

Who is online

Users browsing this forum: Bolendox, DMITRYB, LeoNaXe and 37 guests