# v6.44beta \[testing\] is released!

**URL:** <https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205>\
**Category:** Announcements\
**Created:** [September 11, 2018, 10:47am UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205 "2018-09-11T10:47:19Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![emils](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/emils/32/1457_2.png) [@emils](https://forum.mikrotik.com/u/emils)\
**Post date:** [September 11, 2018, 10:47am UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/1 "2018-09-11T10:47:19Z")

</div>

**Version 6.44beta6 has been released.**

Before an upgrade:

1. Remember to make backup/export files before an upgrade and save them on another storage device;
2. Make sure the device will not lose power during upgrade process;
3. Device has enough free storage space for all RouterOS packages to be downloaded.

**What’s new in 6.44beta6 (2018-Sep-11 08:52):**

Changes in this release:

!) upgrade - release channels renamed - “bugfix” to “long-term”, “current” to “stable” and “release candidate” to “testing”;  
!) upgrade - “testing” release channel now can contain “beta” together with “release-candidate” versions;  
\*) chr - assign interface names based on underlying PCI device order on KVM;  
\*) crs317 - fixed packet forwarding on bonded interfaces without hardware offloading;  
\*) crs3xx - improved data transmission between 10G and 1G ports;  
\*) dhcpv4-server - fixed service becoming unresponsive after interface leaves and enters the same bridge;  
\*) dhcpv6-client - log only failed pool additions;  
\*) ethernet - fixed IPv6 packet forwarding on IPQ4018 devices;  
\*) hotspot - properly update dynamic “walled-garden” entries when changing “dst-host”;  
\*) ike2 - added option to specify certificate chain;  
\*) ike2 - fixed local address lookup when initiating new connection;  
\*) ike2 - fixed rare authentication and encryption key mismatches after rekey with PFS enabled;  
\*) lte - fixed DHCP relay packet forwarding when in passthrough mode;  
\*) lte - fixed Jaton/SQN modems preventing router from booting properly;  
\*) rb3011 - added IPsec hardware acceleration support;  
\*) routerboard - fixed memory tester reporting false errors on IPQ4018 devices (“/system routerboard upgrade” required);  
\*) sniffer - made “connection”, “host”, “packet” and “protocol” sections read-only;  
\*) switch - fixed ACL rules on IPQ4018 devices;  
\*) upnp - improved UPnP service stability when handling HTTP requests;  
\*) w60g - added “frequency-list” setting;  
\*) w60g - fixed interface LED status update on connection;  
\*) winbox - allow setting “network-mode” to “auto” under LTE interface settings;  
\*) wireless - removed “czech republic 5.8” regulatory domain information as it overlaps with “ETSI 5.7-5.8”;

If you experience version related issues, then please send supout file from your router to [support@mikrotik.com](mailto:support@mikrotik.com). File must be generated while router is not working as expected or after crash.

---

<div class="post-metadata">

**Author:** ![macgaiver](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/macgaiver/32/104_2.png) [@macgaiver](https://forum.mikrotik.com/u/macgaiver)\
**Post date:** [September 11, 2018, 10:51am UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/2 "2018-09-11T10:51:40Z")

</div>

O\_o “beta”!!! The hell just froze over!! what happened there?

---

<div class="post-metadata">

**Author:** ![honzam](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/honzam/32/451_2.png) [@honzam](https://forum.mikrotik.com/u/honzam)\
**Post date:** [September 11, 2018, 10:54am UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/3 "2018-09-11T10:54:55Z")

</div>

Now Beta. And Alpha? Alpha V7? 🙂

---

<div class="post-metadata">

**Author:** ![bennyh](https://forum.mikrotik.com/letter_avatar/bennyh/32/6_449c533f586939b6e5f246632a46421f.png) [@bennyh](https://forum.mikrotik.com/u/bennyh)\
**Post date:** [September 11, 2018, 11:14am UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/4 "2018-09-11T11:14:53Z")

</div>

> [@](#):
>
> Now Beta. And Alpha? Alpha V7? 🙂

Guys! If there will be ROS 7 stable release, we should celebrate it with a big worldwide party 😃

ontopic:Did someone test the v6.44 on rb3011?

---

<div class="post-metadata">

**Author:** ![upower3](https://forum.mikrotik.com/letter_avatar/upower3/32/6_449c533f586939b6e5f246632a46421f.png) [@upower3](https://forum.mikrotik.com/u/upower3)\
**Post date:** [September 11, 2018, 12:34pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/5 "2018-09-11T12:34:29Z")

</div>

> !) upgrade - release channels renamed - “bugfix” to “long-term”, “current” to “stable” and “release candidate” to “testing”;

Tell me the truth, who decided that **current** is **stable**? It is bugfix that can be considered stable, while current is some bleeding-edge and sometimes even “never to use in prod” version.

Will the naming be backward aware, like cli to accept **both bugfix and long-term**?

And what to do with old releases (6.29) which are not aware of branches at all and consider itself as **stable**?

---

<div class="post-metadata">

**Author:** ![schadom](https://forum.mikrotik.com/letter_avatar/schadom/32/6_449c533f586939b6e5f246632a46421f.png) [@schadom](https://forum.mikrotik.com/u/schadom)\
**Post date:** [September 11, 2018, 2:40pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/6 "2018-09-11T14:40:01Z")

</div>

Would be very nice to see some routing (especially BGP, BGP4 SNMP MIBs, etc.) improvements for 6.44!  
Also currently peering session re-connects when it’s comment is changed in Winbox. This is annoying and could be changed.

---

<div class="post-metadata">

**Author:** ![Bobstonom](https://forum.mikrotik.com/letter_avatar/bobstonom/32/6_449c533f586939b6e5f246632a46421f.png) [@Bobstonom](https://forum.mikrotik.com/u/Bobstonom)\
**Post date:** [September 11, 2018, 3:20pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/7 "2018-09-11T15:20:07Z")

</div>

Just saw this. Will definitely check it out. 🙂

By the way, newbie here. Aside from being a MikroTik novice, I’m also a critter lover. I’m usually found at home, treating my Pomeranian, Jules, to his [nylabones](http://www.petstreetmall.com/DogBones.aspx) and watching TV with my wife. Such a simple, yet, happy life. Cheers, fellas!

---

<div class="post-metadata">

**Author:** ![z1022](https://forum.mikrotik.com/letter_avatar/z1022/32/6_449c533f586939b6e5f246632a46421f.png) [@z1022](https://forum.mikrotik.com/u/z1022)\
**Post date:** [September 11, 2018, 3:25pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/8 "2018-09-11T15:25:38Z")

</div>

> [@](#):
>
> Now Beta. And Alpha? Alpha V7? 🙂

Alpha V7 will be launched after v6.99 or v6.999 released 😆😆😆

---

<div class="post-metadata">

**Author:** ![upower3](https://forum.mikrotik.com/letter_avatar/upower3/32/6_449c533f586939b6e5f246632a46421f.png) [@upower3](https://forum.mikrotik.com/u/upower3)\
**Post date:** [September 11, 2018, 3:55pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/9 "2018-09-11T15:55:54Z")

</div>

> [@](#):
>
> currently peering session re-connects when it’s comment is changed in Winbox.

So to say, MT used to **down and up** again PPP-interfaces when you change comment on it! It was this way some time ago, not sure for now, but this was some “bright” idea these days (and maybe today).

---

<div class="post-metadata">

**Author:** ![honzam](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/honzam/32/451_2.png) [@honzam](https://forum.mikrotik.com/u/honzam)\
**Post date:** [September 11, 2018, 3:57pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/10 "2018-09-11T15:57:48Z")

</div>

Would be very nice to see some wireless (especially NV2, AC) improvements for 6.44!  
The bandwidth per 20Mhz channel is very small. Compared to competition…

---

<div class="post-metadata">

**Author:** ![upower3](https://forum.mikrotik.com/letter_avatar/upower3/32/6_449c533f586939b6e5f246632a46421f.png) [@upower3](https://forum.mikrotik.com/u/upower3)\
**Post date:** [September 11, 2018, 3:58pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/11 "2018-09-11T15:58:47Z")

</div>

> [@](#):
>
> > [@](#):
> >
> > Now Beta. And Alpha? Alpha V7? 🙂
> 
> Alpha V7 will be launched after v6.99 or v6.999 released :lol: :lol: :lol:

I suspect they will release some absolutely new change in the system somewhere between 6.49 and 6.49.7, so noone will ever be able to predict that. Look at new bridge implementation introduction, some serious change that is there in current (sorry, _so called_ stable) release but not in the bugfix, and you get the idea.

---

<div class="post-metadata">

**Author:** ![djdrastic](https://forum.mikrotik.com/letter_avatar/djdrastic/32/6_449c533f586939b6e5f246632a46421f.png) [@djdrastic](https://forum.mikrotik.com/u/djdrastic)\
**Post date:** [September 11, 2018, 4:06pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/12 "2018-09-11T16:06:05Z")

</div>

> [@emils](#):
>
> !) upgrade - release channels renamed - “bugfix” to “long-term”, “current” to “stable” and “release candidate” to “testing”;

Hi Mikrotik will this release channel naming be pushed down into other releases at a later time ?  
All my ansible scripts at present that upgrade 100’s of rb’s point to “bugfix” , “current” and “release candidate”

Gonna have to do a bit of retooling if so.

---

<div class="post-metadata">

**Author:** ![notToNew](https://forum.mikrotik.com/letter_avatar/nottonew/32/6_449c533f586939b6e5f246632a46421f.png) [@notToNew](https://forum.mikrotik.com/u/notToNew)\
**Post date:** [September 11, 2018, 6:13pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/13 "2018-09-11T18:13:11Z")

</div>

> [@](#):
>
> !) upgrade - release channels renamed - “bugfix” to “long-term”, “current” to “stable” and “release candidate” to “testing”;

That’s good, but we need another channel named oldstable, where 6.42 should go and stay for at least several weeks.

At least do make downgrading more seamless when necessary.

---

<div class="post-metadata">

**Author:** ![mkx](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/mkx/32/1611_2.png) [@mkx](https://forum.mikrotik.com/u/mkx)\
**Post date:** [September 11, 2018, 6:35pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/14 "2018-09-11T18:35:35Z")

</div>

> [@](#):
>
> That’s good, but we need another channel named oldstable, where 6.42 should go and stay for at least several weeks.
> 
> At least do make downgrading more seamless when necessary.

If MT is not going to release new versions in 6.42.x series, then this series does not need its own channel. If you want to downgrade your RB to some particular older version of ROS you can always download it (manually construct download URL if every other option to get DL link fails) and install.  
Channels are only useful for semi-automated upgrades and for users that trust in MT decission about which version belongs to which category of stability. If you’re not one of us, then you can completely ignore channel naming and install whatever version of ROS you believe is best for yor RBs.

---

<div class="post-metadata">

**Author:** ![boldsuck](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/boldsuck/32/1248_2.png) [@boldsuck](https://forum.mikrotik.com/u/boldsuck)\
**Post date:** [September 11, 2018, 6:40pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/15 "2018-09-11T18:40:32Z")

</div>

> [@](#):
>
> > [@](#):
> >
> > !) upgrade - release channels renamed - “bugfix” to “long-term”, “current” to “stable” and “release candidate” to “testing”;
> 
> That’s good, but we need another channel named oldstable, where 6.42 should go and stay for at least several weeks.
> 
> At least do make downgrading more seamless when necessary.

Upload ‘old Firmware’ to Router and reboot…  
…downgrade ready. 😉

---

<div class="post-metadata">

**Author:** ![Chupaka](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/chupaka/32/215_2.png) [@Chupaka](https://forum.mikrotik.com/u/Chupaka)\
**Post date:** [September 13, 2018, 12:00pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/16 "2018-09-13T12:00:15Z")

</div>

You’ll need to press Downgrade button, not just reboot 🙂 But yes, that’s that simple.

---

<div class="post-metadata">

**Author:** ![bennyh](https://forum.mikrotik.com/letter_avatar/bennyh/32/6_449c533f586939b6e5f246632a46421f.png) [@bennyh](https://forum.mikrotik.com/u/bennyh)\
**Post date:** [September 13, 2018, 1:08pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/17 "2018-09-13T13:08:37Z")

</div>

IPSec results appeared on the RB3011 product page as the Mikrotik guys promised, but theese values are lower than IPSec results on the 750Gr3 page. The HW crypt core is weaker in the RB3011 or there will be optimalizations in further ROS releases?

---

<div class="post-metadata">

**Author:** ![blingblouw](https://forum.mikrotik.com/letter_avatar/blingblouw/32/6_449c533f586939b6e5f246632a46421f.png) [@blingblouw](https://forum.mikrotik.com/u/blingblouw)\
**Post date:** [September 13, 2018, 1:54pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/18 "2018-09-13T13:54:00Z")

</div>

seems this release gave us a wireless channel 66000 on w60g interface. Nice!

---

<div class="post-metadata">

**Author:** ![jarda](https://forum.mikrotik.com/letter_avatar/jarda/32/6_449c533f586939b6e5f246632a46421f.png) [@jarda](https://forum.mikrotik.com/u/jarda)\
**Post date:** [September 13, 2018, 1:54pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/19 "2018-09-13T13:54:24Z")

</div>

Mikrotik, please explain why you needed to rename the release channels. Also please explain what real change does this mean. Without that the renaming of current to stable is very confusing for those who came recently or do not know that the only well tested bugfix could be considered as stable in reality.

---

<div class="post-metadata">

**Author:** ![bennyh](https://forum.mikrotik.com/letter_avatar/bennyh/32/6_449c533f586939b6e5f246632a46421f.png) [@bennyh](https://forum.mikrotik.com/u/bennyh)\
**Post date:** [September 13, 2018, 2:35pm UTC](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205/20 "2018-09-13T14:35:48Z")

</div>

> [@](#):
>
> Mikrotik, please explain why you needed to rename the release channels. Also please explain what real change does this mean. Without that the renaming of current to stable is very confusing for those who came recently or do not know that the only well tested bugfix could be considered as stable in reality.

Maybe they think the new Bridge module is mature enough, to mark as stable. This naming method was earlier too, so they only returned to that.

[Next page](https://forum.mikrotik.com/t/v6-44beta-testing-is-released/123205.md?page=2)
