those in DC not. the ones dying yes, they had hotspot queues on them dynamically added. (default-small) and maaybe some PCQ as parents not sure. Well 7.19b6 should fix it, well at least according to MikroTIk. We will see. I moved the hotspot from a 2216 to the 2116 and now the 2216 does not have th...

those in DC not.

the ones dying yes, they had hotspot queues on them dynamically added. (default-small) and maaybe some PCQ as parents not sure.

Hey, having these issues with 2116 since its realease. port flapping -> HW replacement and new box dies within a month. have other 2x 2116s in DC running on 7.5 with 2 years uptime. One box had one of the LACP ports flapping for a month and uptime timer reset after 1 year uptime but all good otherwi...

We have about 30 1009s still left. Just a FYI.

Thanks, but I guess its not worth to ship them into EU

I tried disabling the bonding port and it didn't seem to make a difference. So I downgraded the CCR2116 back to 7.6 and so far no reboots for a few days. On version 7.7, it was rebooting 2-3 times daily and sometimes chain-rebooting (2-3 times in a row). So 7.7 made rebooting MUCH worse. If 7.6 is ...

....
Now that we have containers, it may be time to leave some things in the dust (like SMB server, proxy, hotspot, and apparently also DNS resolver) and focus on routing again.

We have 1k+ CCRs 1009/1036 in production just for hotspot.

Hello, Just a small update. It was confirmed today by support that it ignores CNAME TTL and rather takes A entry TTL. In the meantime I have done script which checks active peer count and also estabilished PH2 count. if there is no active peer or active ph2 amount is lower than 2 ( we use 4) then di...

Hello There,
I wonder if opening ticket makes sense.

I am 100% sure at this point that when peer is specified as FQDN and it dies nothing happens, IP lookup happens only when peer is disabled and enabled.

David

RouterOS also allows to specify multiple peers for policy, I didn't try it before, but I assume it's meant as failover. When I test it now, it doesn't seem to work at all. Initially there's active phase 1 for both peers, phase 2 for one of them, and tunnel works. When that peer dies, I'd expect tha...

Are you saying that other vendors equipment functions as expected but MTs version of the functionality, is ( and this is my least favourite term for factually describing issues) WONKY??? (ps there is no coincidence that wonkey rhymes with donkey which some would call an ass and Sob is in this threa...

Yes, This is exactly the issue I am having. It seems to me, that resolve is done just first time when peer is connecting. Then it sticks to it no-matter what is going on(with or without DPD) . Only solution is do disable peer and enable again to actually connect to second availabl peer. TTL is set t...

Hello community, I would like to ask for clarification about implementation of IPSEC peer with FQDN. In our envinroment we have few hundreds spokes of multiple brands (majority Cisco ASA, Mikrotiks and Fortigates) and we are using CNAME(2 hubs) as peer FQDN to achieve load-balancing and failover. Cu...

Good afternoon. Sorry to bother again. Someone are expereincing the same issue? Thank you. Regards.

Hello, did you try to use bootfile name and DHCP Option Set in DHCP network rather than in DHCP Server ?

It worked for me.

Hi, is there any chance that you are using masquerade ? If so try using src NAT instead.

David