We seem to be missing the Dude Server package for 6.49.6 for all architectures that support Dude. Is this a known issue or is the Dude NPK for 6.49.6 coming later? The V7 stable release channel has an updated Dude package. We're slowly transitioning production systems to V7 but still have a lot of devices following the V6 stable channel running Dude.

Will be Dude Server package avable? I still not migrated everything to V7 and absent of Dude is a big complication.
Thanks for help.

Will be Dude Server package avable? I still not migrated everything to V7 and absent of Dude is a big complication.
Thanks for help.

Have it got "forgotten" or do we need to wait for 6.49.7?

We seem to be missing the Dude Server package for 6.49.6 for all architectures that support Dude. Is this a known issue or is the Dude NPK for 6.49.6 coming later? The V7 stable release channel has an updated Dude package. We're slowly transitioning production systems to V7 but still have a lot of devices following the V6 stable channel running Dude.

Wait, where can I download the dude server v7? Is it available fro ARM?

As Normis say some time ago, Thehe Dude is not in active development, but yo can still include the package for RouterOS v6?

Dude package is missing pls advise MikroTik

Will be Dude Server package avable? I still not migrated everything to V7 and absent of Dude is a big complication.
Thanks for help.

Are the bug fixes, mentioned in change log of this release (versus 6.49.5) such that you absolutely have to upgrade from 6.49.5 to 6.49.6 ... the dude package was available for 6.49.5.

Are the bug fixes, mentioned in change log of this release (versus 6.49.5) such that you absolutely have to upgrade from 6.49.5 to 6.49.6 ... the dude package was available for 6.49.5.

Probably not, but the omission of the Dude (without any notices of such in the changelog) seems notably obscure, which is why it's rightly being stressed in this release thread by several users.

So your response seems a bit misplaced... rather than question users whether upgrading is worth the new features they'll get at the expense of the dude and that they can stick to v6.49.5 if they want the dude, maybe you should join us in seeking a formal explanation from MikroTik for such an anomaly, as this question will likely come up again repeatedly and is normal/to be expected until such time as MikroTik comes out and acknowledges the cause for it and what we should expect going forward (was it intentionally removed, or was this a mistake/error on their part?)

So your response seems a bit misplaced...

You're right, it might seem to be a bit counter users' wishes. I fully agree that package set should be the same for all release versions inside same major.minor version series, in particular if some packages were available in 6.49, then they really should be there antill the last release in series. After all, if some device is set to certain channel, it should be possible to upgrade it when upgrade is available.

My question was in the line of necessity of this particular version upgrade. Specially so as previous poster was mentioning v7 and I assume he wants to get some new functionality (staibility of v7 certainly doesn't warrant upgrade from any of v6 versions). Since there's no change in functionality mentined in change log for this release, this couldn't be a driver for OP to install this release. (the list of my rants is much longer, but I'll stop here - again, I'm not rying to imply that MT does not have to provide dude package).

Looks like Dude is now available on the downloads page for this release. Did anyone ever see an official explanation anywhere? There was also a complete outage of the download page shortly after this release. Those 2 things happening so closely together is very strange indeed.

Dude is NOT available, do not post bullshit

You guys misunderstanding each other.. xD ... Dude Client is present, yes. But Dude .npk file is absent from the extra package zip files and download/update server.

Was this meant to be the new long term release?
Why would you run the cube lite 60 and the wireless wire nray on anything but long term?

Unless there's a specific fix/feature you need in the stable train for a specific reason on a specific device.....why would you run anything but on long-term?

ANY UPDATE FOR DUDE SERVER???

If none of the fixes are needed, revert. And stop shouting. It is rude.

Can someone explain to me why one would run 7.2.1 instead of 6.49.6, aside from the cake support in the newer kernels ?
Because honestly, thus far, after enormous amounts of experimenting and testing time, I have not found an advantage in using cake or fq_codel over the old 6.4* defaults, not for mikrotik devices anyway. WiFi has become unstable since 7, or rather, the network connectivity for wireless devices. I suspect mikrotik hardware drivers are not compatible with the cue additions or something.

Can someone explain to me why one would run 7.2.1 instead of 6.49.6, aside from the cake support in the newer kernels ?
Because honestly, thus far, after enormous amounts of experimenting and testing time, I have not found an advantage in using cake or fq_codel over the old 6.4* defaults, not for mikrotik devices anyway. WiFi has become unstable since 7, or rather, the network connectivity for wireless devices. I suspect mikrotik hardware drivers are not compatible with the cue additions or something.

Sure: you have bought a piece of HW with a factory installed S/W >7.x in this case you can´t go back to 6.x.
There are a few nice new features though: OpenVPN UDP, Zerotier, Containers (will be...)

7.x is only required for newer hardware that does not support 6.x.
If you don't need 7.x stay on 6.x for your production environments

ANY UPDATE FOR DUDE SERVER???

.
Did you download and look in the all_packages-xxx-6.49.6.zip file?
I found it in the all_packages-arm-6.49.6.zip archive.

Ok, misunderstand the reply.

The Dude SERVER package now is inside the ZIP with all packages:
download.mikrotik.com/routeros/6.49.6/all_packages-<PLATFORM>-6.49.6.zip
only on already supported <PLATFORM>

So just to clarify, what if I update TILE CCR1036 from 6.49.5 (with installed DUDE server) to 6.49.6? Is it safe to do it normally from WinBox OR do I have to manually add Dude package after, OR?

Press only "Download" instead of "Download&Install", put manually the dude file inside from all_packages-<PLATFORM>-6.49.6.zip (not all package, obviously),
and just now reboot.

Free Hint: open with 7-zip or similar the routeros-<PLATFORM>-6.49.6.npk and extract the file etc/<FIRMWARE TYPE>-6.49.6.fwf
put that file inside root of RouterBOARD and do a System / RouterBOARD / Upgrade for upgrade the BIOS / Firmware before reboot,
on this way you reboot the device only one time for both RouterBOOT and RouterOS (and after update remember to update also the LTE firmware, if any)

Thanks! Just think about this "process", is it intention from developers OR some mistake?

Probably the 2nd

Then probably will wait for 6.49.7 ...

Then probably will wait for 6.49.7 ...

I wonder what for?

7.x is only required for newer hardware that does not support 6.x.
If you don't need 7.x stay on 6.x for your production environments

So, if my hardware came with a 6.* version, I should not upgrade to 7.* if I don't need extra features?
If so, why is this not mentioned anywhere near the upgrade options, because as it stands, all my 6.* devices have upgraded to 7 over time, and not because I chose to, but because it was the next version when looking for updates.
Are you saying I should do a netinstall for all those devices to downgrade to 6.49.6 ? And can I then re-load config using the latest config backups saved from a 7.* version ?

If you experience no problems on those devices using 7, there is no need to downgrade.
Ultimately ROS6 will be phased out and replaced by ROS7. But that will still take quite some time.

Ultimately ROS6 will be phased out and replaced by ROS7. But that will still take quite some time.

On all devices? As I understand it, the hardware determines if 7.* is a good idea or not.

As far as I know ROS7 runs on all current devices. Depending on the features you need to use, it might still have problems but they are working on that to solve those issues.
And those devices being at the lower limit of the specifications (e.g. 16mb flash), will probably be phased out as well sooner or later. That's a logical evolution.

So, if my hardware came with a 6.* version, I should not upgrade to 7.* if I don't need extra features?
If so, why is this not mentioned anywhere near the upgrade options, because as it stands, all my 6.* devices have upgraded to 7 over time, and not because I chose to, but because it was the next version when looking for updates.
Are you saying I should do a netinstall for all those devices to downgrade to 6.49.6 ? And can I then re-load config using the latest config backups saved from a 7.* version ?

Yes, one should only do the jump if REALLY needed. RoS 7 is really promising, but it is NOT feature complete.

I can't speak for EVERY version of RoS out there, but AFAIK, one would need to change the train from "stable" to "upgrade", in order to go from 6.x to 7.x

Now, I can see why someone not familiar with Mikrotik would think that "upgrade" is the same as "we updated our firmware, and this is what is new". It isn't.

When You open the "check for updates", on the "packages" area, the router shows You the latest version of the train in use by it at the moment.

So. If You are using 6.x, the (say) "stable" option would show You the latest stable release. As of now, version "6.49.6".
If You choose the "upgrade" train, as of now, the version presented would be "7.2.1"

Yes, I know: it is weird. But it would be hard to find another way to do this. RoS isn't beta. Isn't RC either. At the same time, RoS 7.x doesn't have the same features as RoS 6.x. So, Mikrotik got pressed between a rock and a hard place.

Eventually RoS 7 will have the same features as RoS 6.x. When this time come, one SHOULD upgrade to it. But not before - unless You NEED something RoS 7 have, and RoS 6.x doesn't.

So just to clarify, what if I update TILE CCR1036 from 6.49.5 (with installed DUDE server) to 6.49.6? Is it safe to do it normally from WinBox OR do I have to manually add Dude package after, OR?

You should upload routeros-tile-6.49.6.npk and dude-tile-6.49.6.npk to the router and reboot. If you have another packages from extras, then these should be uploaded as well prior reboot. If some of these are missing, then update would not happen and corresponding message would be found in system log.

After this /system routerboard upgrade and /system reboot in a usual way.

So, If we want to have the updated stable version, we can't run Dude.
Dude will work for 3 months and after will be dead for 3 months .

Unless you read the posts above to find out where the dude package is and upgrade it you wont be able to run it...

Any idea how long Router OS v6 will be maintened and updated ?
Any good reason to stay on V6 when your device can be upgraded to V7 ?
Sorry if it's a dumb question, i'm new to mikrotik...

No.
I think the consensus is to stay on v6 when your device supports it unless you really need something from v7 right now. This is due to bugs in v7.

On the other hand, I applaud every brave soul who helps to discover those bugs in v7, so that other's don't have to. :)

My guess - few years. Because of this.

PPP Radius Accounting to include IPv6 PD............................. Pleaseeeeee Consider Mikrotik Team

Any idea how long Router OS v6 will be maintened and updated ?
Any good reason to stay on V6 when your device can be upgraded to V7 ?
Sorry if it's a dumb question, i'm new to mikrotik...

No.
I think the consensus is to stay on v6 when your device supports it unless you really need something from v7 right now. This is due to bugs in v7.

I don't want IPV6 running on our network. We use custom DNS servers for web filtering. The IPV4 DHCP server tells the clients the DNS server addresses to use. Then, our policies can be applied. With V6, I can just disable the IPV6 package and web filtering works as it should. With V7, IPV6 is included into the main package. I have not found a way to disable it. If your ISP uses SLAAC, your clients use whatever DNS servers are pushed to them through router advertisements. The web filter would no longer work because sites that would be blocked on the IPV4 stack would be resolved on the IPv6 stack.

@mroccella simply on v7 set ipv6-disabled=yes on ipv6 settings...
And about DNS: with TLS 1.3 or just one click on browser, and use DoH, and you can not more filter anything. (v6 or v7, is equal)