I did off course read that. But it now seems to work and since no more post not working for me too, it would be nice with an update from MT, like:@Jotne
From @normis:We have identified the issue and a fix is coming shortly.
I did search the forum to try to see what you are asking for, but there are no post about SUP-172111Please MikroTik, check SUP-172111 before release 7.17 stable.
SMB is unstable with hAP ac2.
Thanks
Do you have any more information on this?What's new in 7.17beta4 (2024-Oct-18 11:32):
*) log - added hostname support to remote logging action;
And its arm as well, so zerotier etc should work.That I didn't know! Where is it? Great news, finally we are leaving the 16MB behind!Even for the useful RB750Gr3 there is now an announced replacement with 128MB flash!
There has been releases with more changes :)That is a terrifyingly large amount of changes.
train count
6.43 459
6.42 433
6.47 416
6.46 414
6.39 399
7.2 392
6.40 376
6.38 365
6.44 361
6.48 357
6.45 351
7.16 322
6.41 287
7.15 276
7.14 267For me the netwatch script do works fine. It should send a log line each time one device goes up and down.I am having a problem with the Netwatch reporting.
It may have something to do with you config. You can post it here.it will show cache full, an error message saying "DNS cache full" appears, which I hadn't encountered before...
For me it would be that I can use the installer in Ubuntu, likeAppImage and Snap are also mentoned here, but described as bad.
What is the "best way" to distribute linux apps, in your opinion?
{
:local test [/ip cloud get public-address]
:put $test
}
Can you give a list of why its not production-ready?I hope so, v7 is still far away from a production-ready replacement.
And I was waiting for a rewrite of the syslog system to follow rfc 5424 that was released in 2009!!!Was waiting to see the igmp-proxy issue found on SUP-152693 that affects IPTV Movistar Spain fixed in 7.16
Still no fix for logging mess SUP-105353 SUP-144261Still no fix for igmp-proxy issue SUP-152693, so waiting for it at next versions.
I do hope to see the above message regarding logging mess SUP-105353 SUP-144261:What's new in 7.16beta5 (2024-Jul-25 15:47):
*) log - logging now following rfc 5424 standard;
This is a beta version, not a production version.Rolling back the dns is shit
I may have some to do with this:MQTT no longer works after upgrade to 7.15
247 listed. Exactly the same as in 7.14 ;)After Long Wait ROS v7.15 with huge change log is here
Our bug tracker reports, that your issue has been fixed. This means that in the upcoming days, we plan to release a RouterOS update with this fix.
Why?I need to block YouTube as much as possible to minimize access to the platform.
I would think so. If you look at command history, it looks the same if its run from Winbox or from terminal.Does WinBox effectively issue CLI commands to get/set changes?
/system/history/printYou have followed the 2e settings about kid control?Found a bug, there is no data in traffic
Even if MT has reduced size on latest version, your older version are to big to upgrade.Update to 7.15beta8 fails on wAP AC with error: upgrade failed, free 133kB disk space for a(null)upgrade
{
:local ver [:tonum [:pick [/system resource get version] 0 1]]
:put $ver
}Can you resend your contacts to wapek79368@mcuma.comsent by email
RouterOS do support syslog so you can send any logs externally and graph everything. Look at my Mikrotik for Splunk.Feature request: let us save graphs on USB/SD card finally!
Why did you upgrade a remote location, just some hour after a new release?HOW to get it working back on remote location!???
Simple answer yes. RC are not ment for production, do upgrade.I'd like to know, is v7.14rc4 testing and v7.14 stable the same release, except maybe changing the version number and channel? Should I upgrade from v7.14rc4 to this?
Finished??? 7.15 beta is not even released. It may be in alpha.Is it already finished?
These are mention on various version. Are there any change between beta8 or beta9?!) rose-storage - moved SMB service in the RouterOS bundle;
!) smb - removed legacy SMB service (replaced with newer and faster ROSE SMB service);
I have no problem with 7.13.1 on several routers with some complex configurationThat's why I stick with version 7.12, as it's much more stable.
Believe is something you do in a church :)I also believe that the 7.12 should become to long-term.
That is why I think you can just remove it and it will use bc address for local subnet, eks 178.118.85.255 (if its a c net)Can you double check the broadcast-address? It doesn't look like a broadcast address at all.
Why?MT should put out a hotfix for let's Encrypt
Is 7.14aplpha155 newer than 7.14beta? If not the test should be run on 7.14beta.ticket SUP-136050 updated with autosupout generated on crash of 7.14alpha155
/ip/firewall/nat/remove [/ip/firewall/nat find to-ports="1001"]What script?I tried 7.13 on RBM11g but the scripts don't work anymore!
Script is tested and working with all version up to 7.13beta2I am having an issue in ROS 7.11
That makes some sense.The way I understand it:
My thought as well. I am looking forward for a stable long term release 7.12.87.13? not 7.12.1 ???This is actually already fixed in 7.13 which is coming soon. Deprecate message will not be sent if actual prefix is re-used.
Yes, it can be used to control the running state of the script.Are you suggesting I make a global variable? This is probably one of the options, to make some kind of flag (variable). But I still wanted to understand JOBS.
Mayor/Importante changes vs normal/minor changesWhat would be the difference between itens beginning with "!)" and beginning "*)" on the release notes?
Fixed the script. Strange there are not more errorsYou do realize it's "AccountData" ?
Do you have more than one script? Do you run latest ROS?After the update, the above problem has been solved,but "script error: error - contact MikroTik support and send a supout file (10)" This error message still exists
Betamax was better than VHS ;)maybe because is-is performans is a bit better
You have posted this to support@mikrotik.com and got a sup number, if not, nothing will happen.viewtopic.php?t=172400 please fix this.
A protocol from 1992. Why not change to OSPFNo IS-IS, no 6VPE. The wait continues...
There are no reason that it should not com on mipsbe devices, since it uses Wireguard that mipsbe do support today.Do you know if it will be available for the old devices or MIPSBE based
Where did you read that?No, it is listed as "initial support" under version 7.12.
There you are wrong. Wireguard works fine on the RB750g3 Mipsel.Wireguard apparently not supports MIPS architecture. Probably I'm wrong.
Not with a fibre cable.while I agree that cable hanging in the air is riskier in case of thunderstorm I see no reason to bury cable in ground if possible.
What does this convert?What's new in 7.11beta7 (2023-Jul-24 14:45):
*) console - added ":convert" command;
