v7.12beta [testing] is released!

Hello, how can I help move forward support of specific transceivers? I have SUP-110942 open for many months for supporting UACC-CM-RJ45-MG, but no reply after initial interaction. And none of the beta/rc final versions since then helped on CRS309/310.

I think I have found some potential cause why this doesn’t work in RouterOS, or only on some platforms. The module doesn’t support the RX_LOS from the SFF-8472 standard (page A0h, byte 65, bit 1 is set to zero - actually both options bytes are zero, which means that neither TX_FAULT nor TX_DISABLE are supported), but on the CRS309/310 the module is listed as always “RX Loss”.

Could it be that the hardware driver for these models always polls/checks the RX loss hardware line, even if the transceiver doesn’t support it, so thus it never detects link up? This should be a half an hour investigation on the driver side (the fix will take of course more, but at least would move investigation forward), so could you please please forward it to whomever is responsible for this hardware?

Happy to provide more info either via RouterOS debugging or via Linux ethtool. Many thanks in advance!

Try covering rx_los pin with nail polish. Not the most elegant solution, but floating this pin on module may get it online

ROS do not reply SOA DNS record by default, even if the SOA record has been obtained from the upstream DNS server and has been displayed in the ROS DNS cache.

For example: Cloudflare tunnel cannot be started because the returned (argotunnel.com) domain record does not contain an SOA record.

This issue exists in both 7.11.2 and 7.12beta9

I have seen some discussion on the 7.7rc post.
http://forum.mikrotik.com/t/v7-7rc-is-released/162872/230

Interesting that you found an actual problem resulting from that behavior. But did you really confirm it to be the reason?
As you mentioned I encountered a problem with the DNS resolver in 7.7rc and went to great lengths debugging it, found the same thing you mention above, but in the end it was a “red herring”, it was not the reason why I had problems. That was caused by other misbehavior in the DNS resolver that was fixed.

Version 7.12rc1 has been released.
http://forum.mikrotik.com/t/v7-12rc-is-released/170147/1