Transmit loop detected

RouterOS Beginner Basics
1

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

2

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

Sorry for my English
MyLan.jpeg

3

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?

4

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.

5

i have this problem in ver 6.22 and 6.28rc20.

6

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.

7

up! please, what’s happening
the problem is still not resolved

8

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.

9

Verify in the bridge settings in STP TAB is set to NONE, default is RSTP

10

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.

11

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.

12

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.

13

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.

14

same problem here on random Routerboard, please fix

15

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

16

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. :wink:

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

Regards Florian

17

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)

18

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

19

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);

20

No solution yet?