Some ugly bug while removing EoIP tunnels.

RouterOS General
1

I’ve seen it for some time now. After doing remove on some EoIP interface, MikroTik goes bananas until forced power-cycle reboot (it’s impossible to even reboot it by /system reboot)

Most operations like /interface wireless print, or afore-mentioned /system reboot result in:
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)

To add more fun to this, /system sup-output does the same thing :smiley:
(well, not exactly, it goes to 3 dots, then to 7 - and stays there)

Hope this points you in some direction with removing this bug.

Possible BUG with EoIP
2

If I remember correctly, if you first disable EoIP tunnel and then remove it, it won’t hang. Of course, this is just a workout for the problem, but this is bug.

3

Thanks for the tip, i’ll try it next time :slight_smile:

4

this is part of bash script that had ssh connection to router.

this script removes eiop interface and bridge and bridge port

and no bananas

	
	$sshsession $host1 "/interface bridge port remove [/interface bridge port find interface=$t_int1]"
	$sshsession $host1 "/interface bridge port remove [/interface bridge port find interface=$eoip]"
	$sshsession $host1 "/interface eoip remove $eoip"
	$sshsession $host1 "/interface bridge remove $eoipbridge"
	
	
	$sshsession $host2 "/interface bridge port remove [/interface bridge port find interface=$t_int2]"
	$sshsession $host2 "/interface bridge port remove [/interface bridge port find interface=$eoip]"
	$sshsession $host2 "/interface eoip remove $eoip"
	$sshsession $host2 "/interface bridge remove $eoipbridge"

:unamused:

what i am doing wrong?

5

I think he wants to be able to:

$sshsession $host1 “/interface bridge remove $eoipbridge”

and have all child ports also get deleted first. Something as simple as deleting a bridge (which is very easy to do) shouldn’t cause the router to become instable. A validation on the internal delete command should remove all ports first I think he is saying.

Sam

6

Why am I getting the feeling, that someone tries to make me look stupid, or just genuinely thinks that i’m stupid?

I removed manually bridge ports first, then bridges, and then tried to make my way to removing EoIP tunnels, which failed miserably. This didn’t happen the first time, and it happened to me on many routers before. Disabling EoIP tunnels before-hand helped.

Why you guys started talking about bridges is beyond me - remove eoip-tunnel makes MT go nuts, nothing beyond that. At this point no associated bridge exists in the system anymore (at least according to print command)

7

sorry, didn’t read your first post fully … : )

Sam

8

Apparently janisk also didn’t, but my answer was more directed to him than you. Janisk: less evil answers, more bug fixes :slight_smile: - I’ll manage with disabling EoIP tunnels, now that I know I should do that first, but think about all the others that don’t know! :smiley:

Another thing that may help you guys go in the right direction is - I think this happens on machines that had 2 EoIP tunnels bridged together.

9

WOW this is a HUGE bug! i just happened to me and required a tech visit to a far away router…

i also repeated it in house.

any word on a fix to this MT? or a suggestion as to how to remove this great feature of MT with out fully hanging your router. it just about destrotyed one of mine forcing a sys reset :frowning:

10

sys reset? Rebooting router always fixed mine, and disabling eoip tunnel before removing it seems to be a reliable workaround.