What about this?
Updated almost the entire routerboard line (2000+) to 6.46.4. Everything works fine. Except The Dude. After updating, the devices are permanently reconnected on the maps. Torn on the charts. In addition, і can’t connect through the WinBox only through SSH…
P.S. At 6.46.3 The Dude worked fine…
And with that?
http://forum.mikrotik.com/t/update-wireless-devices-via-the-dude/134412/1
Today, 4 hours I was updating my equipment by manually packing.
new branding packet required
This is one of the most wanted feature! Where we can get this gem?
I upgraded my PPPoE router and other routers, and connections has been dropping, and when they try to reconnect I only see logs as trying to connect and the connection never happens, I tried to roll back, but the issue is still there. I can’t find whats the problem.
What to say. The dude is getting worse and worse. And what was once a very strong side of MikroTik is now its weakest side. It is a pity … I do not understand this position of the company. Honestly, I really love MikroTik and I’m worried about it. You guys fix the little bugs in the dude. Understand it as an integral part of the system.
CHR updated to 6.46.4 (onlys used for dude).
now i can see in the terminal : 12:59:16 echo: system,error,critical login failure for user admin from 127.0.0.1 via winbox
by the way, no logs showed anymore in /logs.
Dear All,
After upgraded to V6.46.4, my RB450G not working, the blue and green LED lite up.
The power supply is 24V.
When I changed the power supply from 24V to 12V, the router working again.
I put it back to 24V, it stopped again.
Now it working well on 12V.
I’m having some issues when connecting to The Dude.
Sometimes I need to disconnect and connect. Same LAN.
Sometimes it gives me timeout.
Sometimes it shows getting stuff but it gets nothing.
I need to disconnect and connect… and keep this going til it gets data.
And I can see login and logout logs..
[quote=clippingpathgraphic post_id=778183 time=1583299124 user_id=158357]
Facing a problem, The system auto-upgrade broken since 6.46.1
[/quote]
I third the branding questions.
There is no information about “branding” in the manual, wiki/Manual:Branding doesn’t exist, and wiki/Branding was deleted in 2011 (even though it is still linked to).
Where can we get information about branding?
Is it something we have to buy?
Or is it only for manufacturers?
[quote=macsrwe post_id=778309 time=1583383002 user_id=11740]
[quote=clippingpathgraphic post_id=778183 time=1583299124 user_id=158357]
Facing a problem, The system auto-upgrade broken since 6.46.1
[/quote]
The new problem in Dude is 6.46.4. Users from the Dude group cannot connect to it. The group is configured according to the wiki: https://wiki.mikrotik.com/wiki/Manual:The_Dude_v6/Admins
And up to 6.46.4 everything worked. Now writes that the username is incorrect. If the user is transferred to a full group, it is connected. In addition, I can’t connect to the server through the winbox until I stop the dude’s server. Just a window with an entrance hangs and the connection does not occur… You have to connect via SSH to stop Dude, and then for example upload the necessary files through Winbox…
P.S.
Can a representative of Mikrotik give at least one comment?
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:
There are connection problems without agents…
Unfortunately at this point your most likely looking at a minimum of a week or two till next stable release and a chance for a fix. However, it would be inviting more problems to simply deploy the next “stable” release in your production network without an additional week or two of in-house testing once its made available. Your best option at this point is to downgrade to 6.44.6 “long term” and watch for people to report an improvement with the dude in the forum comments upon subsequent releases. I would also recommend assessing your current policy’s and procedures especially in regards to how long you test new software releases before deploying them as you appeared to push this out rather quickly after it was released. I assume with having been a forum member since 2015 that you are familiar with the “stable” tree functioning more as community test and review release then one intended for production.
Best regards,
Brian
@mikrotikedoff
Like, I wrote above, I love MikroTik and I really like what they do. I have enough experience to know when to upgrade equipment. More over, I have to say that version 6.46.4 is great, it is very nice and stable on my 2500+ boards. And my claims are just to work on Dude, he has many bugs and they last for years. For example, http://forum.mikrotik.com/t/update-wireless-devices-via-the-dude/134412/1 (problem updating APs on some separate packages) and more. The latest version added even more critical issues. What I find, I describe, and the representatives of MikroTik are silent. I just want to hear their answer, clarify the problem and all. But in response, silence … And for me, Dude is a critical program in which thousands of equipment…
Let them already make the dude paid and develop it properly. There was already an attempt to monetize when they abandoned the PC version. Well, unsuccessfully, just make the paid version really unrealistic? I would like to see how they run thousands of routers without Dude…
P.S. MikroTik has only one problem of ignoring perennial pleas to fix a small number of critical bugs…
+1
Had problems with a BGP Router with very high cpu usage at BGP routes coming in (tcp). Normaly one cpu is at 100% this time all cpus where at >90% (ospf fails and winbox disconnects). Could this be related?
Same issues here…
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. Also, the pipe is constantly connected to the equipment … See screenshots…
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.