If your CHR does detect only single interface although it should detect more, then increase RAM assigned for this CHR, reboot and see if problem is resolved. The CHR has 128 MB of RAM, which is the requirement specified at https://wiki.mikrotik.com/wiki/Manual:CHR Do you mean to suggest that it's n...
RouterOS version 6.43rc23 just have been released. It involves CHR related fixes that might resolve problems mentioned within this topic. We applied 6.43rc23 to a couple of hAPs and a handful of Hyper-V CHRs in response to advice issued by Mikrotik Support. In all instances, the CHRs ended up even ...
We're experiencing a similar issue on Hyper-V, albeit without the DHCP component. We're using CHR routers to front customer cloud environments, to route public and private traffic. Periodically these routers are deciding that the private interfaces aren't working; The symptom being that the next-hop...
It is my experience as well! The cause appears to be down in the Linux kernel, as other devices running Linux tend to do the same thing. The most common problem is occuring at the end of a TCP session. When the TCP session is closed (FIN/FIN ACK) the NAT connection tracking entry is immediately del...
We have a Router OS 6.40.4 [CHR] router that appears to be masquerading the vast majority of outbound packets, but then missing some now and then for reasons unclear. We detected this because the router in question connects to our AS edge router, which has Firewall rules to ensure all packets headin...