i have updated (packagees, dude & routerboard) the dude Server and all clients but the dude Server can't connect.dude - updated The Dude to use new style authentication method;
Have you updated the Dude client on your computer? 6.46.4 has to be installed manually, as older versions cannot connect to RouterOS 6.46.4 to do autoupdate as it has usually been.i have updated (packagees, dude & routerboard) the dude Server and all clients but the dude Server can't connect.dude - updated The Dude to use new style authentication method;
RouterOS Status: std failure_ not allowed (9)
bevore upgrade it works...
everything works fine except RouterOS login and also link statistics based on RouterOS
How do we take advantage of this? Looking in ROS and haven't been able to find anything and I've also looked at the branding manager and couldn't see anything.*) branding - allow forcing configuration script as default configuration (new branding packet required);
Hello MT guys!*) system - improved system stability when receiving/sending TCP traffic on multicore devices;
This happens to me on HAP ac2, RB951Ui-2HnD, HAP Lite, even with a user that has full permission. I don't see this problem on CHR, CCR, HeX.I stand corrected (somehow)!
It looks like Dude server cannot make RouterOS connections to other devices and ends up with STD failure, when RouterOS connection is made in context of limited user account. Previously it was possible with only "read" + "dude" permissions.
Now it has to be at least "read" + "dude" + "winbox". After I added "winbox" permission and clicked "Reconnect", connection state changed to OK and all RouterOS data became visible again.
RB4011, updated without problems.After updating in arm an RB4011 has stopped working, there is no response in any ethernet. Nor can I recover it with netinstall since the ethernet ports are not activated when pressing reset.
Hello, did you upgrade your dude?Hi!
I also have an error std failure: not allowed (9).
Installed v6.46.4 [stable], the user has full rights
Is there a solution?
I too am having this issue.Hi!
I also have an error std failure: not allowed (9) but only on Dude agents!
Direct connection Dude server to clients are fine.
Please help!
Please more infoHello MT guys!*) system - improved system stability when receiving/sending TCP traffic on multicore devices;
Could you give more details about this?
I would like to know if there is an improviment for CCR and x86 devices as well.
Cheers
Hello everyone,- The Dude server must be updated to monitor 6.46.4 and v6.47beta30+ RouterOS type devices.
- The Dude client must be manually upgraded after upgrading The Dude server.
- To get RouterOS data from the devices, The Dude now requires RouterOS to be 6.46.4 or v6.47beta30+.
It's not really a fix though, because you aren't distributing the check to the dude agent.Updated: Fixed my issue by selecing Server as agent , Hope this helps
Did you get an autosupout file? I already created a ticket for this issue.SNMP stoped workin...
NoDid you get an autosupout file? I already created a ticket for this issue.SNMP stoped workin...
ssh-keygen -l -f .ssh/id_rsa.pub
2048 SHA256:nh4ojMnBnq3umMdoAu/fb4rhzUstO+Y9VdY/3dP07mA flo@Florians-MacBook-Pro.local (RSA)
Does this applies also for R11e-LTE6?
*) lte - use APN from network when blank APN used on R11e-4G;
What about this?We are looking into the communication issues with The Dude connecting through Agent. Other issues related with The Dude "std failure" message must be caused by old version on either The Dude server or RouterOS client.
theprojectgroup, please enable SSH debug logs (/system logging add topics=ssh) and generate a supout.rif file after a fresh connection attempt. Send this file to us at support@mikrotik.com for inspection.
Facing a problem, The system auto-upgrade broken since 6.46.1
Tech support said the dude is frozen again. And when there will be at least some kind of fixes they can not say...Facing a problem, The system auto-upgrade broken since 6.46.1
Yup, and no announcement that a fix is in the works. And since then, they broke the Dude.
I am absolutely not upgrading anything anywhere until these two regressions are fixed. Hope you have someone working on these high priority, MT.
We are looking into the communication issues with The Dude connecting through Agent.
We are looking into the communication issues with The Dude connecting through Agent.
+1Hello MT guys!*) system - improved system stability when receiving/sending TCP traffic on multicore devices;
Could you give more details about this?
I would like to know if there is an improviment for CCR and x86 devices as well.
Cheers
Same issues here....All Mikrotik devices and Dude: 6.46.4
Example:
Router1 with RouterOS(6.46.4) Dude connection OK.
Router2 with RouterOS(6.46.4) no direct connection to Dude Server, uses Router1 as Agent:
Error: std failure: not alowed (9), ...
Router1 SSH log:
Router2 SSH log:
New problems with 6.46.4. All information that is removed through the ROS is distorted. For example, on graphs of loading of interfaces of jumping 2-3 times bigger than real.
CPU load max 25-30%. Where the load 10% of the graphics are the same. In version 6.46.3 the graphs were displayed normally. There are currently no problems with schedules if they are built by SNMP.New problems with 6.46.4. All information that is removed through the ROS is distorted. For example, on graphs of loading of interfaces of jumping 2-3 times bigger than real.
What is the % CPU usage on your DynaDish? This graph looks symptomatic of the metering process periodically missing interval deadlines and then making up for the missed data in the next interval.
There are currently no problems with schedules if they are built by SNMP.
About Dude "std" error:
To get RouterOS data from the devices, Dude now requires RouterOS to be 6.46.4 or newer. The other stats and of course Ping will still work. This is due to security measures being strengthened.
Specially after your question I translated the schedule from ROS to SNMP. As you can see, the same graph is displayed.There are currently no problems with schedules if they are built by SNMP.
Ah, so you are saying that data collection is unimpaired, but data display by /tool graph (only) is faulty...?
Hey @Emils,We are looking into the communication issues with The Dude connecting through Agent. Other issues related with The Dude "std failure" message must be caused by old version on either The Dude server or RouterOS client.
theprojectgroup, please enable SSH debug logs (/system logging add topics=ssh) and generate a supout.rif file after a fresh connection attempt. Send this file to us at support@mikrotik.com for inspection.
...
12:03:25 ssh,debug agreed on: diffie-hellman-group-exchange-sha256 rsa-sha2-256 aes128-ctr aes128-ctr hmac-sha2-256 hmac-sha2-256 none none
...
12:03:26 ssh,debug pki algorithm: ssh-rsa
12:03:26 ssh,info publickey accepted for user: admin
12:03:26 system,info,account user admin logged in from 10.1.1.20 via ssh
...
You didn't straightforwardly answer the question. I see no giant spikes in the SNMP graph, so can I assume you agree that only /tool graph display is at fault?Specially after your question I translated the schedule from ROS to SNMP. As you can see, the same graph is displayed.Ah, so you are saying that data collection is unimpaired, but data display by /tool graph (only) is faulty...?There are currently no problems with schedules if they are built by SNMP.
only the Dude server has to be upgraded
Try upgrading them from 6.44.6 to 6.46.4 and they will not be able to communicate normallyI have Dude 6.46.4 and many RBs 6.44.6, and they all are talking with Dude.
I was using Dude on my HexS with no issues until this 6.46.4 update. After several hours it is not possible to access via winbox or accept incoming connections as if the cpu were at 100%. The only way to reestablish the Dude service is to access it through telnet and restart it.
The exact same problem. Through agents does not work.I was using Dude on my HexS with no issues until this 6.46.4 update. After several hours it is not possible to access via winbox or accept incoming connections as if the cpu were at 100%. The only way to reestablish the Dude service is to access it through telnet and restart it.
Same problem. Yes, it used to be, but it was less frequent. For example, if I was missing a link with the server while working in dude. After the break, the client was no longer connected. And because of the WinBox it was impossible to connect to the server. To remedy the situation, you need to connect via telent or SSH and stop the dude or restart the server... Now the situation is even worse access through WinBox disappears when ever you like...
And what was the reason? It's in Log.I had tried several times but the firmware was not get updated, it always stuck on v4.64.3.
Do not know what the reason is. After system reboot all logs were gone, no way to trace what happen. I had tried Winbox 3.21 and through script, the result was the same, the firmaware still v4.64.3 (not v.4.64.4)And what was the reason? It's in Log.I had tried several times but the firmware was not get updated, it always stuck on v4.64.3.
Do not know what the reason is. After system reboot all logs were gone, no way to trace what happen. I had tried Winbox 3.21 and through script, the result was the same, the firmaware still v4.64.3 (not v.4.64.4)And what was the reason? It's in Log.I had tried several times but the firmware was not get updated, it always stuck on v4.64.3.
The same problem with x86 PPPoE NAS. This problem has been around for about six months now. The solution is to go to: C:\Users\...\AppData\Roaming\Mikrotik\Winboxmy x86 pppoe concetrator works almost ok, but after upgrading Winbox not always is able to load the data from router, freezing at start.
then some time it works, was not able to understand why it happens,
mac-telnet works all the times
Thanks for help and suggestion. I managed to update to firmware 4.64.4 using browser metod (connect to the device through browser) and performed the update. This was my last easy out try before I went into heavy weigh debug flow./system logging add topics=error,critical action=diskDo not know what the reason is. After system reboot all logs were gone, no way to trace what happen. I had tried Winbox 3.21 and through script, the result was the same, the firmaware still v4.64.3 (not v.4.64.4)And what was the reason? It's in Log.I had tried several times but the firmware was not get updated, it always stuck on v4.64.3.
/system package update install
If there's something wrong, it will be in the logs after reboot
I did some testing :We are looking into the communication issues with The Dude connecting through Agent. Other issues related with The Dude "std failure" message must be caused by old version on either The Dude server or RouterOS client.
/interface ethernet switch port
set ether2 vlan-header=add-if-missing vlan-mode=secure
up, still brokenSystem - auto-upgrade broken since 6.46.1 please fix it.
thx
Agreed. 6.44.6 - best for SXT devices for now...There is bug in this version RouterOS. I have two SXT SA5 configured as bridge (WISP AP and CPE, no other wireless devices). Distance between devices is about 600meters. Before upgrade, both devices were working on routerOS 6.44.6 and was fairly ok (stable link with CCQ circa 97% and 54Mbps). After upgrade (both devices, I've upgraded ROS as well as firmware) SXT device constantly connects and disconnects every several seconds. During connection CCQ constantly falls down from 100% to 38% and then device configured as CP disconnects. After few seconds the link is restored and CCQ again fall down until disconnects and again. There were problems with restoring previous version of firmware, because CPE is in place which is very hard to reach. The best protocol for sending npk files through broken unstable link is FTP (I've tested FTP, SCP and WinBox protocols)
+smb on a security device is just crazy. It should be entirely removed from RouterOS. That's what nas devices are made for, firewalled behind the router.
I cannot agree more !smb on a security device is just crazy. It should be entirely removed from RouterOS. That's what nas devices are made for, firewalled behind the router.
Probably something in (firewall?) configuration which was harmless before but has hit now. Open a dedicated topic in General and follow my automatic signature just below. Then, edit your previous post with a link to that new topic.hi there,
after i upgrade to 46.4 im experience my ip cannot reply ping from internet, but it can from inside network. anyone notice or just me ?