Since you posted no configuration export.., my only guess would be that you didn't exclude ipsec traffic from fasttrack.

Thanks a lot. Fasttrack it was.

It's just don't explain why it worked before electricity loss...

No one have faced with situation when IPSec becomes unusable slow? What could cause it and how to fix it?

Hello, Before electricity lose everything was working without problems. After loss of electricity in data center traffic through RB3011UiAS become unusable. We have 2 LANs connected through IPSec site-to-site, on both sides Mikrotik routers. Connection status is established, but after that there is ...

a bit late, but check Your DNS settings in router.

use 1 masquerade without out-interface. This solve the problem

Code: Select all

chain=srcnat action=masquerade 

This will also change source IP of sender in SMTP logs.

But thanks any way, adding src-address resolves issue with SMTP

Thank's a lot.

In Firewall rules I configured port forward, but didn't figured out to do the same in mangle

I have similar problem. When I'm connecting from some external addresses connections comes in from interface WAN1, but outgoing traffic is going to WAN2. Changing order in mangle nor adding no-mark didn't helped. /ip address add address=89.xxx.xxx.xxx/26 broadcast=89.xxx.xxx.63 comment="" ...

Maybe I'm something missing but it seems, that

Simple rule : /ip firewall filter add chain=forward p2p=bit-torrent action=drop

don't block all torrent connections.

I'm using MikroTik RouterOS 4.12

routing table flush every 10min also I had some problems with NAT: I configured ECMP load balancing with masquerade, but when I'm switching from route 2 to route 3, I can't connect to RDC through WAN1, but WAN2 works. When I'm switching back to route 2 WAN1 work's without problems. 2 A S ;;; 1 GW 0....

Are there any fix or news about ECMP problem?