# v7.17beta \[testing\] is released!

**URL:** <https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003>\
**Category:** Announcements\
**Created:** [September 27, 2024, 1:24pm UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003 "2024-09-27T13:24:17Z")\
**Posts on this page:** 20\
**Page:** 9

<div class="post-metadata">

**Author:** ![pe1chl](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/pe1chl/32/55588_2.png) [@pe1chl](https://forum.mikrotik.com/u/pe1chl)\
**Post date:** [October 2, 2024, 10:13am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/161 "2024-10-02T10:13:43Z")

</div>

Well, that whole “it will reboot to change the setting” makes the whole thing even worse than it already is.  
Not only is it required to physically go to each router, and to connect to the CLI and issue the command and press the button, but also it will cause an interruption in the network at that time.  
It is usually even more difficult to get physical access in a maintenance service window than it already is in the first place.  
Even when a reboot is required to activate the new settings, it could be noted and the reboot could be done later.  
(just as when you upgrade routerboot, for example)  
And we cannot even prepare the new device-settings ahead of time, because 7.16 does not allow to set the new properties yet.  
The fact that it is a “cold reboot” is also bad, e.g. we have “add ARP for dhcp leases” and “arp mode reply-only” on all the networks, and a cold reboot leaves some clients in a confused state because new leases have not yet been written to storage and after boot will have no ARP entry. At least do a warm reboot!

---

<div class="post-metadata">

**Author:** ![dksoft](https://forum.mikrotik.com/letter_avatar/dksoft/32/6_449c533f586939b6e5f246632a46421f.png) [@dksoft](https://forum.mikrotik.com/u/dksoft)\
**Post date:** [October 2, 2024, 10:35am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/162 "2024-10-02T10:35:14Z")

</div>

> [@](#):
>
> Documentation of device-mode has been updated with more info. If anyone has any doubts or questions, please post them here and we will answer them in the documentation

I want to prepare a site of which I don’t have physical access to in the next months.

What is the best command to be ready and have all features enabled?

---

<div class="post-metadata">

**Author:** ![Joe1vm](https://forum.mikrotik.com/letter_avatar/joe1vm/32/6_449c533f586939b6e5f246632a46421f.png) [@Joe1vm](https://forum.mikrotik.com/u/Joe1vm)\
**Post date:** [October 2, 2024, 10:37am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/163 "2024-10-02T10:37:53Z")

</div>

Please, what will happen to the running containers after the update to 7.17?

---

<div class="post-metadata">

**Author:** ![gigabyte091](https://forum.mikrotik.com/letter_avatar/gigabyte091/32/6_449c533f586939b6e5f246632a46421f.png) [@gigabyte091](https://forum.mikrotik.com/u/gigabyte091)\
**Post date:** [October 2, 2024, 10:44am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/164 "2024-10-02T10:44:43Z")

</div>

Nothing should happen, on my ax3 everything is working. Do you have an issue ?

---

<div class="post-metadata">

**Author:** ![Coughy](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/coughy/32/3335_2.png) [@Coughy](https://forum.mikrotik.com/u/Coughy)\
**Post date:** [October 2, 2024, 10:57am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/165 "2024-10-02T10:57:58Z")

</div>

nothing it works fine nothing to do with containers unless you have different partitions for them but most run on usb??

> [@](#):
>
> Please, what will happen to the running containers after the update to 7.17?

---

<div class="post-metadata">

**Author:** ![Coughy](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/coughy/32/3335_2.png) [@Coughy](https://forum.mikrotik.com/u/Coughy)\
**Post date:** [October 2, 2024, 10:59am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/166 "2024-10-02T10:59:58Z")

</div>

in your log do you get HapAx3\_5Ghz detect LAN if you have that active??  
seem to show up every 3 hrs or so only the HapAx3\_5Ghz detect LAN no other interface does it

> [@](#):
>
> Nothing should happen, on my ax3 everything is working. Do you have an issue ?

---

<div class="post-metadata">

**Author:** ![FezzFest](https://forum.mikrotik.com/letter_avatar/fezzfest/32/6_449c533f586939b6e5f246632a46421f.png) [@FezzFest](https://forum.mikrotik.com/u/FezzFest)\
**Post date:** [October 2, 2024, 11:10am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/167 "2024-10-02T11:10:41Z")

</div>

> [@](#):
>
> We have added to the manual some more info about device mode, including that it will reboot in any case.  
> The console message will also be amended in future betas.

But it’s still not clear what I need to do to make sure I can still use all features (including traffic-gen, container, partitions, bootloader and downgrade) on our 2000+ devices in the field without having to physically visit each one of them and do a powercycle.

Also, the documentation is still confusing. It first mentions (under ‘Available device-mode modes’) that traffic-gen, container, partitions, bootloader, downgrade are disabled for ‘advanced mode’. But then under ‘List of available properties’ it says “Default: yes, for advanced mode” describing properties that also include traffic-gen, container, partitions, bootloader and downgrade?  
 ![WTH.PNG](https://data-discourse.cdn.mikrotik.com/original/3X/6/c/6c1996c96dcc48dad7601369fb3158346f989fce.png)

---

<div class="post-metadata">

**Author:** ![normis](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/normis/32/8_2.png) [@normis](https://forum.mikrotik.com/u/normis)\
**Post date:** [October 2, 2024, 11:16am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/168 "2024-10-02T11:16:36Z")

</div>

No, we do not plan to implement annual licensing or any other licensing changes.

Device mode, as clarified in the manual, is meant to protect home users who have their routers taken over by attackers and are using them for botnet purposes.

EVEN THOUGH we have no known security issues in RouterOS AND we have added default passwords out of the box, improved security will ensure the devices stay secure for a long time. Home user does not need traffic generator.

---

<div class="post-metadata">

**Author:** ![holvoetn](https://forum.mikrotik.com/letter_avatar/holvoetn/32/6_449c533f586939b6e5f246632a46421f.png) [@holvoetn](https://forum.mikrotik.com/u/holvoetn)\
**Post date:** [October 2, 2024, 11:17am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/169 "2024-10-02T11:17:45Z")

</div>

> [@](#):
>
> Nothing should happen, on my ax3 everything is working. Do you have an issue ?

It’s not ok on my RB5009.  
None of my containers start (iperf, openspeedtest, pi-hole) and yesterday I noticed a couple of drops during Teams calls (never saw that happening before).  
Will troubleshoot later this evening.

---

<div class="post-metadata">

**Author:** ![normis](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/normis/32/8_2.png) [@normis](https://forum.mikrotik.com/u/normis)\
**Post date:** [October 2, 2024, 11:18am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/170 "2024-10-02T11:18:32Z")

</div>

> [@](#):
>
> > [@](#):
> >
> > We have added to the manual some more info about device mode, including that it will reboot in any case.  
> > The console message will also be amended in future betas.
> 
> But it’s still not clear what I need to do to make sure I can still use all features (including traffic-gen, container, partitions, bootloader and downgrade) on our 2000+ devices in the field without having to physically visit each one of them and do a powercycle.
> 
> Also, the documentation is still confusing. It first mentions (under ‘Available device-mode modes’) that traffic-gen, container, partitions, bootloader, downgrade are disabled for ‘advanced mode’. But then under ‘List of available properties’ it says “Default: yes, for advanced mode” describing properties that also include traffic-gen, container, partitions, bootloader and downgrade?

Home and Advanced mode are like presets, that allow certain list of features. Groups of features, that are listed next to them in the manual.  
BUT there is no mode that allows ALL features, if you have Advanced and also need some additional features, you have to enable them one by one. I suggest reading the entire documentation page, it clarifies this further in the text.

---

<div class="post-metadata">

**Author:** ![normis](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/normis/32/8_2.png) [@normis](https://forum.mikrotik.com/u/normis)\
**Post date:** [October 2, 2024, 11:26am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/171 "2024-10-02T11:26:19Z")

</div>

Containers ALWAYS had device-mode requirement, since day one. Maybe you forgot you set it. So nothing changes if you had a running container.

---

<div class="post-metadata">

**Author:** ![Joe1vm](https://forum.mikrotik.com/letter_avatar/joe1vm/32/6_449c533f586939b6e5f246632a46421f.png) [@Joe1vm](https://forum.mikrotik.com/u/Joe1vm)\
**Post date:** [October 2, 2024, 11:38am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/172 "2024-10-02T11:38:21Z")

</div>

Thank’s to all for the confirmation regarding containers…

---

<div class="post-metadata">

**Author:** ![normis](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/normis/32/8_2.png) [@normis](https://forum.mikrotik.com/u/normis)\
**Post date:** [October 2, 2024, 11:46am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/173 "2024-10-02T11:46:27Z")

</div>

I have posted further updates to the manual, so all your Device mode questions should be answered in there .

---

<div class="post-metadata">

**Author:** ![normis](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/normis/32/8_2.png) [@normis](https://forum.mikrotik.com/u/normis)\
**Post date:** [October 2, 2024, 11:47am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/174 "2024-10-02T11:47:17Z")

</div>

If your containers stopped working after upgrade to 7.17, it might not be related to device mode at all.

---

<div class="post-metadata">

**Author:** ![nmt1900](https://forum.mikrotik.com/letter_avatar/nmt1900/32/6_449c533f586939b6e5f246632a46421f.png) [@nmt1900](https://forum.mikrotik.com/u/nmt1900)\
**Post date:** [October 2, 2024, 11:49am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/175 "2024-10-02T11:49:17Z")

</div>

This still looke like a mess…

_There are several EOL products which do not “confirm” mode changes with a reset button press. These routers can confirm mode change only with a power cycle._

Which devices? Will there be a list?

Second question which I still find hard time to get answer to - will all device-mode related changes from changelog get initiated to all devices which have features (to be disabled as per changelog) already in use i.e. if non-default settings are already applied to device-mode settings? If yes then it is an obvious departure from “not-to-mess-with-applied-configuration” philosophy.  
What settings should be next to be expected to be steamrolled over?

P. S. We now have 3 Device-mode presets and no clear defiition of which devices default to which one.

This “one-liner” is not enough → _Advanced (previously called enterprise) mode is assigned to CCR and 1100 series devices, home mode is assigned to home routers and basic mode to any other type of device_

---

<div class="post-metadata">

**Author:** ![infabo](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/infabo/32/55692_2.png) [@infabo](https://forum.mikrotik.com/u/infabo)\
**Post date:** [October 2, 2024, 11:54am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/176 "2024-10-02T11:54:58Z")

</div>

~~[quote=holvoetn post\_id=1100939 time=1727869432 user\_id=185526]~~  
Were do I need to look then ?  
[/quote]

Any hints in log?

---

<div class="post-metadata">

**Author:** ![holvoetn](https://forum.mikrotik.com/letter_avatar/holvoetn/32/6_449c533f586939b6e5f246632a46421f.png) [@holvoetn](https://forum.mikrotik.com/u/holvoetn)\
**Post date:** [October 2, 2024, 11:59am UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/177 "2024-10-02T11:59:34Z")

</div>

> [@](#):
>
> If your containers stopped working after upgrade to 7.17, it might not be related to device mode at all.

I never said it was related to device mode.  
However it is related to ROS 7.17beta… and that’s what this thread is about, no ?

I will troubleshoot this evening.

---

<div class="post-metadata">

**Author:** ![normis](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/normis/32/8_2.png) [@normis](https://forum.mikrotik.com/u/normis)\
**Post date:** [October 2, 2024, 12:03pm UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/178 "2024-10-02T12:03:57Z")

</div>

Sorry about that, my mistake, this whole thread has turned into “questions about device mode”

---

<div class="post-metadata">

**Author:** ![holvoetn](https://forum.mikrotik.com/letter_avatar/holvoetn/32/6_449c533f586939b6e5f246632a46421f.png) [@holvoetn](https://forum.mikrotik.com/u/holvoetn)\
**Post date:** [October 2, 2024, 12:05pm UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/179 "2024-10-02T12:05:02Z")

</div>

~~[quote=infabo post\_id=1100947 time=1727870098 user\_id=177714]~~  
~~[quote=holvoetn post\_id=1100939 time=1727869432 user\_id=185526]~~  
Were do I need to look then ?  
[/quote]

Any hints in log?  
[/quote]

Missing exec. Only thing which shows in log after start and then immediately stop.  
  
At first sight (quickly logged in via wireguard during lunch break) disk is mounted correctly (it did cause problems in the past with some USB3 drives on Rb5009 but it seems it gets recognized ok now each time after reboot), folders are still there from what I can see. Mounts are present as expected.  
  
On itself not a real issue since those containers are pretty easy to setup again from scratch but I am simply wondering why it broke all of a sudden.

---

<div class="post-metadata">

**Author:** ![OlofL](https://forum.mikrotik.com/letter_avatar/olofl/32/6_449c533f586939b6e5f246632a46421f.png) [@OlofL](https://forum.mikrotik.com/u/OlofL)\
**Post date:** [October 2, 2024, 12:39pm UTC](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003/180 "2024-10-02T12:39:36Z")

</div>

\*) dns - added option to create named DNS servers that can be used as forward-to servers

Does this mean forwarder-to can try to forward to multiple servers?  
Does it mean if first server doesnt respond (because its down), it will retry next forwarder before giving answer back to client?  
Like this guy is talking about: [http://forum.mikrotik.com/t/dns-forwarding-multiple-dns-servers/163556/4](http://forum.mikrotik.com/t/dns-forwarding-multiple-dns-servers/163556/4)

Or does this change simply mean that the named forwarder you define will automatically resolve behind the scenes, so that you dont have add one or multiple static A records for the forwarders?

[Previous page](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003.md?page=8)

[Next page](https://forum.mikrotik.com/t/v7-17beta-testing-is-released/179003.md?page=10)
