Working before in dude and stopped graphing since update 6.35:
Function: ros_command(“/caps-man registration-table print count-only”)
Other probes/data sources are all timeout too
Ok, thanks for your answer… Sorry for my mistake!
I have 6.32.3 RB2011UAS and I try to update via winbox System - Packages - Download&Install, MT reboots but it isn’t updated. Same when I press only “Download” and then reboot. Nothing changes.
CoA is good, but why not allow changes to dynamic queues the old way as well? I have used this to remove all speed limits at night on the PPPoE server - disable/enable queues from scheduled scripts.
I see - thanks. Using wireless-cm2 for now, will give more time for the new stuff to mature (hoping to see more nv2/802.11ac improvements).
Hello,
I installed v6.35 onto a RB1100AHx2 - Working like a charm.
Thank you
RB433UAH (power 24V 2A) RouterOS 6.35 …freeze/crash (uptime 5days) no winbox, no ssh, no http, no webpage internet..ping/dns work board/internet, statistic all graf no log graf
routerboard power off/on works
In cap clients recursive dupeliclate virtual wlan interface after reconnect capsman server
example:
2 X ;;; managed by CAPsMAN
;;; channel: 2412/20-Ce/gn(20dBm), SSID: XXXXX1, CAPsMAN forwarding
wlan1 wlan 1500 1600 2290 4C:5E:0C:06:3F:FC
3 DX ;;; managed by CAPsMAN
;;; SSID: XXXXX2, CAPsMAN forwarding
wlan2 wlan 1500 1600 4E:5E:0C:06:3F:FC
4 DX ;;; managed by CAPsMAN
;;; SSID: XXXXX3, CAPsMAN forwarding
wlan3 wlan 1500 1600 4E:5E:0C:06:3F:FD
5 X wlan4 wlan 1600 2290 4E:5E:0C:06:3F:FC ← here
6 X wlan5 wlan 1600 2290 4E:5E:0C:06:3F:FD ← here
…
12 X wlan11 wlan 1600 2290 4E:5E:0C:06:3F:FD ← here
probelm in CM2 also in REP wireless module
tested on:
Server CCR1009-8G-1S
Client: RBmAP2n, RB952Ui-5ac2nD, RB962UiGS-5HacT2HnT, RB751G-2HnD,
Hi, i have a problem with my CCR i update to the new version,
The problem is i am using Radius Manager and the api doesn’t work here and all user speed stay like it’s except if i disconnect them by myself when you will repair this problem
105547111 - MTU and L2MTU issues are already fixed in 6.36rc
Beone - We will look into this
CyberTod,andriys - Just noticed and reported to developers that g/n is missing from Winbox drop list. You can set it through CLI and it will work
eworm,pe1chl - Export for switch configuration is fixed in 6.36rc
folkert - Do you have MRRU on PPPoE. Try to reduce it so it would be lower than L2MTU on ethernet
freemannnn - Bucket is well explained here - http://wiki.mikrotik.com/wiki/Manual:HTBv6
hatred,napismizpravu - Please report to support@mikrotik.com with detailed explanation of problem, if you experience it again. If router has serial port, then we would want to see what you see there during these reboots
hohwin3a - If installation still reboots your x86 constantly, then please report to support@mikrotik.com. If you see some error output, then make picture or video with it and attach to message to support
lgkahn - Yes, it is mentioned in changelog that latest Winbox is required. If it says that RoMON is disabled, then if you are admin, then connect to router through Winbox, enable RoMON policy and then connect through RoMON
marekm - Wireless-rep needs to be installed manually. You can still use -cm2
McTedson - When you think that NAT is working have you tried to clear connections list and check again?
nuru, dialsc,rommo911,mitzone,qbek - Please report to support@mikrotik.com with detailed explanation and supout files from problematic version
PtDragon,tgrand,RomanHujer - Please try 6.36rc version
Sergey371 - Do router work and Winbox is only problem?
TecnoNet - If API changes dynamic queue speed limit then it is and will not be possible. You have to use static queues or CoA
VirusDr - this issue is already reported to developers. We will try to fix it as soon as possible
WirelessRudy - Yes, normally upgrade works like that, but these specific version had a bug which required router to be rebooted first (6.35rc29-rc49)
and so on. I hope to be released version 6.35.1 with bugfixes?
Hi,
Just to save someone’s time,
it took me one and a half day to (finaly) read this thread, and to understand that 6.35 stable is unable to connect to any Cap.
Upgraded to 6.36rc and it just worked (even without any further configuration).
My eyes hurt.
Have a nice day, keep up the good work. 
I get huge discrepancy in Ping latency using the Dude on a CHR 6.35. Pings from Winbox are good. Pings from Dude client are bad.
http://forum.mikrotik.com/t/dudev6-pings-are-bad-from-client-but-not-from-router/97427/1
I’ve been seeing the same thing since they resumed x86 support with the separate package, FWIW.
I also encountered some odd behavior when I upgraded an RB433AH. In my case the upgraded unit was an older hardware version, and it uses the “IC Plus 175C” switch chip instead of the “175D” version. It appeared that the upgrade did not handle this older chip correctly, and my Ethernet interfaces were either unavailable, or the bridge that I had configured was not working with the selected Ethernet bridge ports. This, in turn, caused some of my firewall filter rules to become invalid. Furthermore, I observed that some of my filter rules were lost after the upgrade.
I worked around these problems using the serial console by first inserting a permissive rule that allowed me to gain access via one of the Ethernet interfaces. At this point I could use Winbox (or Webfig) to take a closer look at what had changed. In my case, I needed to re-implement my Bridge configurations, and I eventually decided to just restore all of my filter rules from a backup (I’ve learned it’s always a good idea to capture an export to a file before playing around with firmware upgrades).
I’m sharing this experience in case it is helpful to others. So far, after resolving these glitches, the RB433AH is working fine with 6.35, including the wireless AR922X card. I’ll be conducting further testing.
This issue is now fixed in 6.36rc version:
Known issue: some huawei lte modems might not get IP address after the reboot of the router - disable/enable of the modems fixes that
routing is not working or packet mark is not working
packet comes in on interface and is logged by prerouting after which it disappears
supout sent to support
reproduce: create Route Rule that sends packet to some other router that routes it back to this one on another interface
receive same packet on another interface, where mange rule adds packet mark in Prerouting
packet is not detected by mangle rule in forward with that packet mark
extreme fail
CCR1072
P.S. ontop of this when this packet is eventually routed, it is not source NAT-ed
Try to disable/enable routing rules.
After some clicking I sniffed and saw that packet indeed goes out. Its just not catched by mangle rule.
Now current problem is that MASQ rule does not change the source IP of the packet as it goes out.
You need to clear connection tracking. Probably connection was established before that mangle rule was functional.