Current issue aside I just wish that they would start using more respectable domains names for this dynamic DNS service. kissthenet.net and mynetname.net sound more like highly suspicious chinese spam operation than reliable DNS service. Maybe something with their main brand domain like: ns1.dyn.mik...

Still down

• 159.148.147.201 ns1.kissthenet.net:
  DNS daemon responds (very infrequently) but does not reach records database for serial # <-> IP mappings
• 159.148.172.251 ns2.kissthenet.net:
  DNS daemon (udp/53, tcp/53) seems to be completely offline

We depend on this service for critical operations, so having a reliable alternative or knowing when it will be restored would be greatly appreciated. Universal solution would be for Mikrotik to implement DNS RFC2136 support allowing dynamic record updates to *any* standards compliant DNS server/ser...

mynetname.net DNS server daemon responds sometimes (ns1/ns2.kissthenet.net). Maybe backend database for dynamic device serial <-> IP mappings is down? Good Morning, Riga. Time to wake up. # dig @ns1.kissthenet.net <redacted serial>.sn.mynetname.net in cname ; <<>> DiG 9.18.28-0ubuntu0.24.04.1-Ubuntu...

IMHO It would be much more professional if MikroTik would use their own main DNS servers (mimas.mt.lv and moon.mt.lv) for resolving the mynetname.net domain. Currently mynetname.net domain DNS is forwarded by some cheap reseller web hosting (resell.biz) + kissthenet.net as intermediary. This seems t...

For some reason SwOS 2.16 is offered also for CSS610-1Gi-7R-2S+ which should be using SwOS Lite 2.17?

Is this an error or is CSS610 really supported on full SwOS 2.16?

Just tested with latest RouterOS 7.8 and RB1200. Not looking good. Same results: Ports 1-8 connect but no traffic is flowing through Ports 9 and 10 work ok -- [admin@MikroTik] /interface/ethernet/switch> print Columns: NAME, TYPE # NAME TYPE 0 switch1 Atheros-8316 [admin@MikroTik] /interface/etherne...

That sounds promising!

RouterBoard very close to RB1200, the RB1100AHx2 also uses PPC CPU and AR8327 switch chips:

https://wiki.mikrotik.com/images/e/ed/R ... treams.png

It is fully working with ROS v7 releases.

BTW, I've got a few RB951Gs running v7 without such problems. RB951G also uses AR8327 switch chip, so support for AR8327 in v7 seems to be just fine. Also wAP R ac (RBwAPGR-5HacD2HnD) uses Atheros 8327 and works wonderfully with v7.4.1 and v7.5rc1. I agree that the issue is must not be with support...

I received following response from MikroTik support to my RB1200 ticket:

Hello,
Thank you for contacting MikroTik Support.

Thanks for the reports, we will see what can be done here, meanwhile please use ROS 6.48.6.

RB1200 installs and boots 7.4.1 and 7.5rc1 just fine, but ethernet ports 1-8 do not have any IP connectivity. Link negotiation works ok for each port, but traffic does not flow through. What's your support ticket number? People need to reference it in theirs. In addition to ticket SUP-90869 , I've ...

RouterBOARD 1200 (RB1200) is able to install and upgrade to ROS 7.x, but loses connectivity on ethernet ports 1-8 , while ports 9 and 10 remain accessible. To summarize: RouterOS v7.x installs ok Ports 1-8 negotiate links, leds work as expected, but no L2 or IP traffic flows. Ports 9 and 10 work ok ...

What's your support ticket number? People need to reference it in theirs.

My ticket number for reporting RB1200 port 1-8 issues with ROS 7.x is SUP-90869

*) interface - fixed default interface naming on RB1100x2; As you seem to be working on PowerPC platform devices, could you please show some ROS 7 -love to trusty old RB1200 (RouterBOARD 1200)? RB1200 installs and boots 7.4.1 and 7.5rc1 just fine, but ethernet ports 1-8 do not have any IP connectiv...

FYI I've tested a debug/development firmware for mmips devices that fixes SSH service issues. Mikrotik Support has informed me, that their proposed fix will be included in the upcoming releases: Great, glad to hear that. We will finish up the fix and will include it in the upcoming RouterOS releases...

I just created support ticket (/w supout.rif, screenshots) from our testing unit.

Waiting for MikroTik support to respond.

I can confirm that this issue exists also with RBLtAP-2HnD (LtAP LTE6 kit) (mmips) and RouterOS 7.3.1

I'm having this issue with latest 7.1.3 release. IPSec site-to-site tunnels seems to work between ROS 6.x <-> ROS 7.x, but two ROS 7.x routers are unable to keep traffic flowing after tunnel has been established. IPSec tunnel negotiates phase 1 and phase 2 successfully (policy state: established) bu...

Does v7.1.3 give us working IPSec site-to-site tunneling between two ROS 7 devices? Previous v7 releases stop routing traffic between two ROS7 devices after 10-15 seconds of establishing site-to-site tunnel. Tunnels work if either end is v6.x device though. Can anyone confirm improvement in v7.1.3 I...

There is one major L2TP/IPSec regression in 6.48.x that has not yet been fixed in 6.48.5 (or anything newer): Using ROS 6.48.x, 6.49.x, 7.x and configuring IPSec peers with DNS name as remote address (not using fixed remote IP) the L2TP/IPSec connectivity stops working because any DNS addressed IPSe...

could not upgrade from 48 to 48.1 kernel failure in previous boot rb3011 Did you do any reboots with 6.48 before this upgrade? The reboot failures with various models (RB3011 and CRS9x) is issue related to the first 6.48 release. I have not yet tested if fresh install of 6.48.1 reboot bricks these ...

Installed 6.48.1 to test device and first thing I noticed is that this Web UI bug introduced in 6.48 is still present in 6.48.1: - By default /webfig/ URL (default after fresh login) always forwards to "QuickSet / Port Mapping" configuration options. This happens even if Quick Set has been...

So MikroTik, please say .. something!

In case you missed it, in post #303 above Mikrotik did say something.

Yes, I missed it.

Glad they did. It gives us hope.

Unusually long period of silence from MikroTik. No development releases, no emergency fixes to the 6.48, no communication about the situation whatsoever. And the buggy version is still being distributed to customers as stable. I admit however, that on most - not all - device models the 6.48 runs ok ...

I'm new to Mikrotik and I've changed many devices in my network quite (too) fast. Now I'm quite shocked what's called stable here. I'm even not seeing a warning or similar that this release .. well ... sucks basically. Which 'normal user' looks in this forum before he upgrades to this version?! Not...

It is unbelievable that this release has not been pulled already or fixed version released for a full month. 6.48 breaks so many features on so many different MikroTik device models that it must have a dramatic effect on new customers and new devices being installed. Most of the posts in this forum ...

Issues I encountered with various MikroTik models after upgrading to 6.48 [stable]: All devices : webfig always forwards after login to the new "Port Mapping" quickset page. Does not prevent config/usage, but very annoying. All devices : IPSec connectivity issues (Phase 1, Phase 2, PFS - v...