Community discussions

  • 1
  • 4
  • 5
  • 6
  • 7
  • 8
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1406
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.39rc [release candidate] is released

Fri Mar 10, 2017 3:22 pm

Version 6.39rc51 has been released.

Changes since previous version:
!) tile - fixed IPsec hardware acceleration out-of-order packet problem, significantly improved performance;
*) tr069-client - fixed write for "Device.ManagementServer.URL";

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
 
onnoossendrijver
Member
Member
Posts: 418
Joined: Mon Jul 14, 2008 11:10 am
Location: The Netherlands

Re: v6.39rc [release candidate] is released

Fri Mar 10, 2017 6:26 pm

Version 6.39rc51 has been released.
!) tile - fixed IPsec hardware acceleration out-of-order packet problem, significantly improved performance;
Can you tell more about this?
Does this also improve IPsec on other multicore platforms like RB750GR3?
Linux/network engineer: ITIL, LPI1, CCNA R+S, CCNP R+S, JNCIA, JNCIS-SEC
 
alexjhart
Member Candidate
Member Candidate
Posts: 191
Joined: Thu Jan 20, 2011 8:03 pm

Re: v6.39rc [release candidate] is released

Fri Mar 10, 2017 6:31 pm

Version 6.39rc51 has been released.
!) tile - fixed IPsec hardware acceleration out-of-order packet problem, significantly improved performance;
Can you tell more about this?
Does this also improve IPsec on other multicore platforms like RB750GR3?
This is specifically for the CCR series (both problem and solution). More information here: viewtopic.php?f=1&t=112545
-----
Alex Hart

The Brothers WISP
 
strn
just joined
Posts: 10
Joined: Tue Jan 17, 2017 11:19 pm

Re: v6.39rc [release candidate] is released

Fri Mar 10, 2017 8:40 pm

Version 6.39rc51 has been released.

Changes since previous version:
!) tile - fixed IPsec hardware acceleration out-of-order packet problem, significantly improved performance;
*) tr069-client - fixed write for "Device.ManagementServer.URL";

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
Did anyone else experienced the issue that the complete NAT configuration was gone after rebooting into rc51?

I had to manually rebuild the whole NAT cfg :/


Gesendet von iPad mit Tapatalk
 
msatter
Forum Guru
Forum Guru
Posts: 1177
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v6.39rc [release candidate] is released

Sat Mar 11, 2017 12:11 am

Version 6.39rc51 has been released.

Changes since previous version:
!) tile - fixed IPsec hardware acceleration out-of-order packet problem, significantly improved performance;
*) tr069-client - fixed write for "Device.ManagementServer.URL";

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
Did anyone else experienced the issue that the complete NAT configuration was gone after rebooting into rc51?

I had to manually rebuild the whole NAT cfg :/
No problem over here with the NAT or any other rules.
Two RB760iGS (hEX S) in series. One does PPPoE and both do IKEv2.
Running:
RouterOS 6.46Beta / Winbox 3.19 / MikroTik APP 1.3.1
Having an Android device, use https://github.com/M66B/NetGuard/releases (no root required)
 
Beone
Member Candidate
Member Candidate
Posts: 243
Joined: Fri Feb 11, 2011 1:11 pm

Re: v6.39rc [release candidate] is released

Sun Mar 12, 2017 11:46 am

CAPSMAN controller: CCR1009
Wifi CAPS: WAP AC + HAP AC

v6.36.4:
working fine, reference speed wireless: 250-260Mbit/s

v6.38.x :
- massive wireless issues with capsman (continous disconnects, slow speeds)
- RSTP causing forwarding issues (traffic not forwarding, DHCP not getting through)

v6.39rcXX-51:
- Wireless speed issue: speed only half (~ 140Mbit/s; half speed compared to v6.36.4; downgrading back to 6.36.4 results in higher speed)
 
Zorro
Long time Member
Long time Member
Posts: 676
Joined: Wed Apr 16, 2014 2:43 pm

Re: v6.39rc [release candidate] is released

Mon Mar 13, 2017 11:15 am

is any chance for fix for recent linux breach ?
eg this one:
https://security-tracker.debian.org/tra ... -2017-2636
 
User avatar
macgaiver
Forum Guru
Forum Guru
Posts: 1717
Joined: Wed May 18, 2005 5:57 pm
Location: Sol III, Sol system, Sector 001, Alpha Quadrant

Re: v6.39rc [release candidate] is released

Mon Mar 13, 2017 11:22 am

is any chance for fix for recent linux breach ?
eg this one:
https://security-tracker.debian.org/tra ... -2017-2636
... in the Linux kernel through 4.10.1... 
RouterOS v6 uses v3.3.6 and don't have hdlc ...you are safe.
With great knowledge comes great responsibility, because of ability to recognize id... incompetent people much faster.
 
biatche
Member Candidate
Member Candidate
Posts: 128
Joined: Tue Oct 13, 2015 6:50 am

Re: v6.39rc [release candidate] is released

Mon Mar 13, 2017 1:05 pm

6.38.x severe issues.

setup: gw = rb750gr3 <-> sw = crs125 <-> LAN & ap = wap ac / hap ac

Things have been operational in 6.37.1 750g3,crs125 and 1x wap ac. I have 3 vlans, 1 for management, 2 for lan. I bought another few wap ac and hap ac to add to the network.

First, I upgraded from 6.37.1 to 6.38.5. (some weird stuff happened upgrading CRS125.. more on this in another thread post later that led me to believe that the CRS had become faulty). Anwyay, found that the CRS lost connectivity to the hex although I wasn't yet aware it was a version issue. Hex couldn't mac ping CRS. It was intermittent, after several configuration resets on the CRS, I could get the hex to ping/mac ping the CRS. Thought I had stablized it after that. After solving that, I went on to plug in and out devices. Plugged in the HAP AC to the CRS resulted in the CRS losing connectivity to the hex. SPENT 8 HOURS straight thinking its my configuration issue since its a production environment. Finally, for some reason, I realized it could be a version issue and so I went on to downgrade all the mikrotik devices to the old working version -- 6.37.1. Voila, things seem to be stable again. Also, related or not, while i was on 6.38.5, HAP AC had difficult time (intermittent) picking up a dhcp client ip from the hex.. whether or not its due to the CRS being in between. After downgrading, it picked up the dhcp client ip pretty much immediately. WAP AC was fine though, had always picked up a dhcp address without any issues. So of course it also misled me from thinking theres a version issue.

Alright, I'm very furious. So much wasted time and no profit. What's going on here? is 6.37.x = stable ; 6.38 = beta while 6.39 = alpha? Does Mikrotik warrant their users for such trouble? ALSO Lost a lot of credibility by my client here. I still look forward to IKEv2 so staying on 6.37 is really no solution.

Edit: Do move this post to the 6.38.5 thread, my mistake for posting here.
Last edited by biatche on Mon Mar 13, 2017 1:53 pm, edited 4 times in total.
 
biatche
Member Candidate
Member Candidate
Posts: 128
Joined: Tue Oct 13, 2015 6:50 am

Re: v6.39rc [release candidate] is released

Mon Mar 13, 2017 1:11 pm

CAPSMAN controller: CCR1009
Wifi CAPS: WAP AC + HAP AC

v6.36.4:
working fine, reference speed wireless: 250-260Mbit/s

v6.38.x :
- massive wireless issues with capsman (continous disconnects, slow speeds)
- RSTP causing forwarding issues (traffic not forwarding, DHCP not getting through)

v6.39rcXX-51:
- Wireless speed issue: speed only half (~ 140Mbit/s; half speed compared to v6.36.4; downgrading back to 6.36.4 results in higher speed)
I think the issues you mentioned may be related to what I mentioned in #260. Infuriating.
 
pe1chl
Forum Guru
Forum Guru
Posts: 5566
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.39rc [release candidate] is released

Mon Mar 13, 2017 2:28 pm

Are you sure this is not the issue related to (changes in) spanning tree?
 
Zorro
Long time Member
Long time Member
Posts: 676
Joined: Wed Apr 16, 2014 2:43 pm

Re: v6.39rc [release candidate] is released

Mon Mar 13, 2017 3:43 pm

is any chance for fix for recent linux breach ?
eg this one:
https://security-tracker.debian.org/tra ... -2017-2636
... in the Linux kernel through 4.10.1... 
RouterOS v6 uses v3.3.6 and don't have hdlc ...you are safe.
well, since "3.2 and above(up to 4.11?)" listed as "vulnerable" unless "particular security fix" delivered - it IS VULNERABLE, i guess.

how do you Know(!) that ROS lack "drivers/tty/n_hdlc" in it ?
do you had ROS source-code access ?
 
User avatar
macgaiver
Forum Guru
Forum Guru
Posts: 1717
Joined: Wed May 18, 2005 5:57 pm
Location: Sol III, Sol system, Sector 001, Alpha Quadrant

Re: v6.39rc [release candidate] is released

Mon Mar 13, 2017 3:57 pm

well, since "3.2 and above(up to 4.11?)" listed as "vulnerable" unless "particular security fix" delivered - it IS VULNERABLE, i guess.

how do you Know(!) that ROS lack "drivers/tty/n_hdlc" in it ?
do you had ROS source-code access ?
have you seen HDLC protocol frames anywhere in RouterOS? I haven't...

Just lets take random piece of code from linux and then just assume that it is used in RouterOS and assume that it has the same vulnerability...
This is ridiculous.
With great knowledge comes great responsibility, because of ability to recognize id... incompetent people much faster.
 
JanezFord
Member Candidate
Member Candidate
Posts: 262
Joined: Wed May 23, 2012 10:58 am

Re: v6.39rc [release candidate] is released

Mon Mar 13, 2017 5:40 pm

6.38.x severe issues.

Alright, I'm very furious. So much wasted time and no profit. What's going on here? is 6.37.x = stable ; 6.38 = beta while 6.39 = alpha? Does Mikrotik warrant their users for such trouble? ALSO Lost a lot of credibility by my client here. I still look forward to IKEv2 so staying on 6.37 is really no solution.
I have had issues like you on several of the networks I manage and learned the hard way to disable rstp on every mikrotik bridge in the network if using 6.38.x or later version ... guess something is severely broken in bridge rstp. It just doesn't work as expected and makes other devices disappear from network. You will find many posts regarding this issue on the forum. It is not a solution, because rstp is there for a reason but only a workaround if you really need IKEv2.

JF.
 
biatche
Member Candidate
Member Candidate
Posts: 128
Joined: Tue Oct 13, 2015 6:50 am

Re: v6.39rc [release candidate] is released

Mon Mar 13, 2017 6:03 pm

6.38.x severe issues.

Alright, I'm very furious. So much wasted time and no profit. What's going on here? is 6.37.x = stable ; 6.38 = beta while 6.39 = alpha? Does Mikrotik warrant their users for such trouble? ALSO Lost a lot of credibility by my client here. I still look forward to IKEv2 so staying on 6.37 is really no solution.
I have had issues like you on several of the networks I manage and learned the hard way to disable rstp on every mikrotik bridge in the network if using 6.38.x or later version ... guess something is severely broken in bridge rstp. It just doesn't work as expected and makes other devices disappear from network. You will find many posts regarding this issue on the forum. It is not a solution, because rstp is there for a reason but only a workaround if you really need IKEv2.

JF.
I do not follow how this can be let to happen in a "current" version. My setup is fairly simple and I'm no veteran. I had always had the impression that Mikrotik devices are utilized in corporate environments, schools, banks, etc. and this issue caused major outages. Worst of all I was oblivious to it, not realizing it could be a version issue due to a certain sequence of events. If it had been a simple "I upgraded, and issue started appearing" then I would have suspected its a version issue.

Anyway, as mentioned in post #260, I would like to share what made me think the CRS went faulty.

Initially, the setup was 1x Hex, 1x CRS, 1x WAP AC. Everything was working. I had decided to upgrade to the latest version before deploying more WAP AC and HAP AC. I had upgraded the Hex & WAP AC and they worked. From winbox on the HEx router, I used mac telnet to access the CRS. I tried to initiate the upgrade on the CRS by doing /system package update download which I did on WAP AC and it says "downloading now or something".. but this time it complained being unable to connect and then /system package update install which also complained the same thing. It was only then I realized I had forgotten to set the DNS on the switch. Here's the thing, RIGHT AFTER doing a /ip dns set address=8.8.8.8, i lost connectivity to the switch. WAP AC and clients connected to the switch were still pingable however. It was only a bit later I realized by "neighbors" that the version had been upgraded to 6.38.5. HEre's where I thought I did a bad flash. After resetting the device configuration several times, the device was pingable which also led me to believe that it had a borked flash. The point is: Why the heck did the upgrade happen when it complained that it can't locate the download server which is understoodable because there was no DNS set. Why did upgrade happen on its own after setting DNS? I even thought that bad flash happened because I keyed in the command twice (in similarity)
 
hedele
Member
Member
Posts: 338
Joined: Tue Feb 24, 2009 11:23 pm

Re: v6.39rc [release candidate] is released

Mon Mar 13, 2017 10:05 pm

I do not follow how this can be let to happen in a "current" version. My setup is fairly simple and I'm no veteran. I had always had the impression that Mikrotik devices are utilized in corporate environments, schools, banks, etc. and this issue caused major outages.
Well here's the thing. I'm guessing 90% of those corporate, school, bank, whatever networks are definitely _not_ running "current" or "rc" code. In fact, I believe most of them aren't even running "bugfix" code, but even more well-proven, older releases (even if Mikrotiks standard response to literally every single problem report ever is "try current version to see if it is fixed"). I know of several decently-sized ISP networks even that still run on ROS 5.x for that reason.

Once you learn that indeed "bugfix" is the absolute border of what you will want to run in any more-than-lab-sized production network without previous testing, it's really not too bad. I am running 6.37.5 without any trouble at all on a bunch of different (CHR, x86, mmips, mipsbe, tile) devices and generally never had trouble sticking to the "bugfix" tree. If you really really need a new feature or fix in a current or rc version, give that one a thorough lab test followed by a limited production rollout and another testing period before actually rolling it out everywhere. If you don't want or can't follow that procedure, you're better off waiting for the particular fix or feature to soak down into "bugfix" releases.

It's not an issue that's isolated to Mikrotik either. I dare you to go grab the most recent ED IOS versions that Cisco gives away for their kit and carelessly throw it onto your devices. I'm pretty sure _something_ will probably go wrong, somewhere - which is why you'd want to choose a MD branch that's had a couple rebuilds already. Which is what "bugfix" is, more or less.
Last edited by hedele on Mon Mar 13, 2017 11:03 pm, edited 1 time in total.
 
patrick7
Member Candidate
Member Candidate
Posts: 298
Joined: Sat Jul 20, 2013 2:40 pm

Re: v6.39rc [release candidate] is released

Mon Mar 13, 2017 10:46 pm

I hope banks etc run Cisco, Juniper, or something like this.
 
mducharme
Trainer
Trainer
Posts: 791
Joined: Tue Jul 19, 2016 6:45 pm

Re: v6.39rc [release candidate] is released

Tue Mar 14, 2017 2:39 am

6.38.x severe issues.

Alright, I'm very furious. So much wasted time and no profit. What's going on here? is 6.37.x = stable ; 6.38 = beta while 6.39 = alpha? Does Mikrotik warrant their users for such trouble? ALSO Lost a lot of credibility by my client here. I still look forward to IKEv2 so staying on 6.37 is really no solution.
I have had issues like you on several of the networks I manage and learned the hard way to disable rstp on every mikrotik bridge in the network if using 6.38.x or later version ... guess something is severely broken in bridge rstp. It just doesn't work as expected and makes other devices disappear from network. You will find many posts regarding this issue on the forum. It is not a solution, because rstp is there for a reason but only a workaround if you really need IKEv2.

JF.
I do not follow how this can be let to happen in a "current" version. My setup is fairly simple and I'm no veteran. I had always had the impression that Mikrotik devices are utilized in corporate environments, schools, banks, etc. and this issue caused major outages. Worst of all I was oblivious to it, not realizing it could be a version issue due to a certain sequence of events. If it had been a simple "I upgraded, and issue started appearing" then I would have suspected its a version issue.

Anyway, as mentioned in post #260, I would like to share what made me think the CRS went faulty.

Initially, the setup was 1x Hex, 1x CRS, 1x WAP AC. Everything was working. I had decided to upgrade to the latest version before deploying more WAP AC and HAP AC. I had upgraded the Hex & WAP AC and they worked. From winbox on the HEx router, I used mac telnet to access the CRS. I tried to initiate the upgrade on the CRS by doing /system package update download which I did on WAP AC and it says "downloading now or something".. but this time it complained being unable to connect and then /system package update install which also complained the same thing. It was only then I realized I had forgotten to set the DNS on the switch. Here's the thing, RIGHT AFTER doing a /ip dns set address=8.8.8.8, i lost connectivity to the switch. WAP AC and clients connected to the switch were still pingable however. It was only a bit later I realized by "neighbors" that the version had been upgraded to 6.38.5. HEre's where I thought I did a bad flash. After resetting the device configuration several times, the device was pingable which also led me to believe that it had a borked flash. The point is: Why the heck did the upgrade happen when it complained that it can't locate the download server which is understoodable because there was no DNS set. Why did upgrade happen on its own after setting DNS? I even thought that bad flash happened because I keyed in the command twice (in similarity)
Did you read the changelog before upgrading? The big warning they have? The issues you are having really sound like they are related to that change:
What's new in 6.38 (2016-Dec-30 11:33):

Important note!!!
RouterOS v6.38 contains STP/RSTP changes which makes bridges compatible with IEEE 802.1Q-2014 by sending and processing BPDU packets without VLAN tag.
To avoid STP/RSTP compatibility issues with older RouterOS versions, upgrade RouterOS to v6.38 on all routers in Layer2 networks with VLAN and STP/RSTP configurations.
The recommended procedure is to start by upgrading the remotest routers and gradually do it to the Root Bridge device.
If after upgrade you experience loss of connectivity, then disabling STP/RSTP on RouterOS bridge interface will restore connectivity so you can complete upgrade process on your network.
In other words, you needed to upgrade the spoke device first (probably the WAP), followed by the CRS and then the Hex, or disable STP first.
 
biatche
Member Candidate
Member Candidate
Posts: 128
Joined: Tue Oct 13, 2015 6:50 am

Re: v6.39rc [release candidate] is released

Tue Mar 14, 2017 2:59 am

6.38.x severe issues.

Alright, I'm very furious. So much wasted time and no profit. What's going on here? is 6.37.x = stable ; 6.38 = beta while 6.39 = alpha? Does Mikrotik warrant their users for such trouble? ALSO Lost a lot of credibility by my client here. I still look forward to IKEv2 so staying on 6.37 is really no solution.
I have had issues like you on several of the networks I manage and learned the hard way to disable rstp on every mikrotik bridge in the network if using 6.38.x or later version ... guess something is severely broken in bridge rstp. It just doesn't work as expected and makes other devices disappear from network. You will find many posts regarding this issue on the forum. It is not a solution, because rstp is there for a reason but only a workaround if you really need IKEv2.

JF.
I do not follow how this can be let to happen in a "current" version. My setup is fairly simple and I'm no veteran. I had always had the impression that Mikrotik devices are utilized in corporate environments, schools, banks, etc. and this issue caused major outages. Worst of all I was oblivious to it, not realizing it could be a version issue due to a certain sequence of events. If it had been a simple "I upgraded, and issue started appearing" then I would have suspected its a version issue.

Anyway, as mentioned in post #260, I would like to share what made me think the CRS went faulty.

Initially, the setup was 1x Hex, 1x CRS, 1x WAP AC. Everything was working. I had decided to upgrade to the latest version before deploying more WAP AC and HAP AC. I had upgraded the Hex & WAP AC and they worked. From winbox on the HEx router, I used mac telnet to access the CRS. I tried to initiate the upgrade on the CRS by doing /system package update download which I did on WAP AC and it says "downloading now or something".. but this time it complained being unable to connect and then /system package update install which also complained the same thing. It was only then I realized I had forgotten to set the DNS on the switch. Here's the thing, RIGHT AFTER doing a /ip dns set address=8.8.8.8, i lost connectivity to the switch. WAP AC and clients connected to the switch were still pingable however. It was only a bit later I realized by "neighbors" that the version had been upgraded to 6.38.5. HEre's where I thought I did a bad flash. After resetting the device configuration several times, the device was pingable which also led me to believe that it had a borked flash. The point is: Why the heck did the upgrade happen when it complained that it can't locate the download server which is understoodable because there was no DNS set. Why did upgrade happen on its own after setting DNS? I even thought that bad flash happened because I keyed in the command twice (in similarity)
Did you read the changelog before upgrading? The big warning they have? The issues you are having really sound like they are related to that change:
What's new in 6.38 (2016-Dec-30 11:33):

Important note!!!
RouterOS v6.38 contains STP/RSTP changes which makes bridges compatible with IEEE 802.1Q-2014 by sending and processing BPDU packets without VLAN tag.
To avoid STP/RSTP compatibility issues with older RouterOS versions, upgrade RouterOS to v6.38 on all routers in Layer2 networks with VLAN and STP/RSTP configurations.
The recommended procedure is to start by upgrading the remotest routers and gradually do it to the Root Bridge device.
If after upgrade you experience loss of connectivity, then disabling STP/RSTP on RouterOS bridge interface will restore connectivity so you can complete upgrade process on your network.
In other words, you needed to upgrade the spoke device first (probably the WAP), followed by the CRS and then the Hex, or disable STP first.
Actually I've been looking/waiting for you on IRC for two days.
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 24077
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v6.39rc [release candidate] is released

Tue Mar 14, 2017 8:28 am

is any chance for fix for recent linux breach ?
eg this one:
https://security-tracker.debian.org/tra ... -2017-2636
... in the Linux kernel through 4.10.1... 
RouterOS v6 uses v3.3.6 and don't have hdlc ...you are safe.
well, since "3.2 and above(up to 4.11?)" listed as "vulnerable" unless "particular security fix" delivered - it IS VULNERABLE, i guess.

how do you Know(!) that ROS lack "drivers/tty/n_hdlc" in it ?
do you had ROS source-code access ?
1) RouterOS is not affected
2) Even if it would be, RouterOS users have no ability to run their own programs. It couldn't be applicable anyway.
No answer to your question? How to write posts
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1406
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.39rc [release candidate] is released

Wed Mar 15, 2017 4:37 pm

6.39rc54 has been released.

Changes since previous version;
*) ike1 - fixed ph2 ID logging;
*) ipsec - allow mixing aead algorithms in proposal;
*) ipsec - show hardware accelerated authenticated SAs;
*) lte - added initialization for Cinterion;
*) netinstall - fixed typos;
*) ppp-client - added support for Datacard 750UL, DWR-730 and K4607-Zr;
*) snmp - added optical table;
*) snmp - added fan-speed OIDs in "/system health print oid";
*) snmp - fixed rare crash;
*) snmp - improved getall filter;
*) tr069-client - added "Device.WiFi.NeighboringWiFiDiagnostic." support;
*) tr069-client - added Upload RPC "2 Vendor Log File" support;
*) tr069-client - fixed "Device.ManagementServer." value update;
*) tr069-client - fixed crash on =acs-url change special case;
*) userman - allow "name-for-user" to be empty and not unique;
*) wireless - fixed false positive DFS radar detection caused by iPhone 6s devices;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
 
alexjhart
Member Candidate
Member Candidate
Posts: 191
Joined: Thu Jan 20, 2011 8:03 pm

Re: v6.39rc [release candidate] is released

Wed Mar 15, 2017 10:43 pm

6.39rc54 has been released.
*) ipsec - show hardware accelerated authenticated SAs;
Where can this be found?
-----
Alex Hart

The Brothers WISP
 
Sob
Forum Guru
Forum Guru
Posts: 4411
Joined: Mon Apr 20, 2009 9:11 pm

Re: v6.39rc [release candidate] is released

Wed Mar 15, 2017 11:38 pm

I don't see anything in WinBox, but CLI has new flag "H - hw-authenc" in "/ip ipsec installed-sa print".
People who quote full posts should be spanked with ethernet cable. Some exceptions for multi-topic threads may apply.
 
alexjhart
Member Candidate
Member Candidate
Posts: 191
Joined: Thu Jan 20, 2011 8:03 pm

Re: v6.39rc [release candidate] is released

Thu Mar 16, 2017 12:04 am

I don't see anything in WinBox, but CLI has new flag "H - hw-authenc" in "/ip ipsec installed-sa print".
Thanks. Not sure how I missed that when printing before. Guess I was looking for a yes/no value, not flag. Makes sense.
-----
Alex Hart

The Brothers WISP
 
IntrusDave
Forum Guru
Forum Guru
Posts: 1282
Joined: Fri May 09, 2014 4:36 am
Location: Rancho Cucamonga, CA

Re: v6.39rc [release candidate] is released

Thu Mar 16, 2017 12:46 am

*) ipsec - show hardware accelerated authenticated SAs;
Is there any possibility that WinBox could highlight the algorithms that are hardware accelerated on each platform?
David Joyce
Network & Security Engineer
Intrus Technologies, LLC.
Rancho Cucamonga, CA, USA
 
alexjhart
Member Candidate
Member Candidate
Posts: 191
Joined: Thu Jan 20, 2011 8:03 pm

Re: v6.39rc [release candidate] is released

Thu Mar 16, 2017 1:10 am

*) ipsec - show hardware accelerated authenticated SAs;
Is there any possibility that WinBox could highlight the algorithms that are hardware accelerated on each platform?
You mean putting this information into winbox? https://wiki.mikrotik.com/wiki/Manual:I ... encryption. Couldn't hurt. I could see it being useful to make that information more readily available in the data sheets/brochures on routerboard.com too.
-----
Alex Hart

The Brothers WISP
 
IntrusDave
Forum Guru
Forum Guru
Posts: 1282
Joined: Fri May 09, 2014 4:36 am
Location: Rancho Cucamonga, CA

Re: v6.39rc [release candidate] is released

Thu Mar 16, 2017 1:13 am

*) ipsec - show hardware accelerated authenticated SAs;
Is there any possibility that WinBox could highlight the algorithms that are hardware accelerated on each platform?
You mean putting this information into winbox? https://wiki.mikrotik.com/wiki/Manual:I ... encryption. Couldn't hurt. I could see it being useful to make that information more readily available in the data sheets/brochures on routerboard.com too.
Yes, exactly.
David Joyce
Network & Security Engineer
Intrus Technologies, LLC.
Rancho Cucamonga, CA, USA
 
Beone
Member Candidate
Member Candidate
Posts: 243
Joined: Fri Feb 11, 2011 1:11 pm

Re: v6.39rc [release candidate] is released

Thu Mar 16, 2017 1:47 am

- Wireless + CAPSMAN: what about airtime fairness and bandsteering?
 
alexjhart
Member Candidate
Member Candidate
Posts: 191
Joined: Thu Jan 20, 2011 8:03 pm

Re: v6.39rc [release candidate] is released

Thu Mar 16, 2017 1:50 am

- Wireless + CAPSMAN: what about airtime fairness and bandsteering?
Probably best requested as new reply in viewtopic.php?f=1&t=45934 or topic in viewforum.php?f=1 (might already exist too)
-----
Alex Hart

The Brothers WISP
 
User avatar
nz_monkey
Forum Guru
Forum Guru
Posts: 1810
Joined: Mon Jan 14, 2008 1:53 pm
Location: Straya
Contact:

Re: v6.39rc [release candidate] is released

Thu Mar 16, 2017 9:28 am

*) ipsec - show hardware accelerated authenticated SAs;
Is there any possibility that WinBox could highlight the algorithms that are hardware accelerated on each platform?
I have requested this a few times, and each time I get pointed at the Wiki..

I really wish they would do this, even if it was under "/system resources" and showed which algorithms are accelerated in hardware.. It's all there in dmesg so the dev's can easily obtain the information.
http://thebrotherswisp.com/ | Mikrotik MTCNA, MTCRE, MTCINE | Fortinet FTCNA, FCNSP, FCT | Extreme Networks ENA
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1406
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.39rc [release candidate] is released

Thu Mar 16, 2017 1:12 pm

Version 6.39rc55 has been released.
Changes since previous version:
!) bridge - fixed BPDU rx/tx when protocol-mode=none;
*) api - fixed double dynamic flags for "/ip firewall address-list print";
*) console - fixed DHCP/PPP add-default-route distance minimal value to 1;
*) console - fixed "/ip neighbor discovery" export;
*) console - fixed crash;
*) console - fixed incorrect ":put [/lcd get enabled]" value;
*) userman - automatically select all newly created users to generate vouchers;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
 
biatche
Member Candidate
Member Candidate
Posts: 128
Joined: Tue Oct 13, 2015 6:50 am

Re: v6.39rc [release candidate] is released

Thu Mar 16, 2017 8:01 pm

before you release final version, which i do feel is drawing near..... please test vlans on CRS bridge + HAP AC.. all on the latest version.
 
User avatar
bajodel
Long time Member
Long time Member
Posts: 545
Joined: Sun Nov 24, 2013 8:30 am
Location: Italy

Re: v6.39rc [release candidate] is released

Thu Mar 16, 2017 8:06 pm

!) bridge - fixed BPDU rx/tx when protocol-mode=none

can we have more information on this? thanks
 
athurdent
just joined
Posts: 24
Joined: Fri Sep 09, 2016 7:02 pm

Re: v6.39rc [release candidate] is released

Fri Mar 17, 2017 9:13 am

6.39rc54 has been released.
*) wireless - fixed false positive DFS radar detection caused by iPhone 6s devices;
This is not fixed, the problem still persists.
 
User avatar
vmiro
Frequent Visitor
Frequent Visitor
Posts: 71
Joined: Sun Jan 29, 2006 6:53 pm

Re: v6.39rc [release candidate] is released

Mon Mar 20, 2017 2:38 pm

!) bridge - fixed BPDU rx/tx when protocol-mode=none

can we have more information on this? thanks
I had a problem on one of my WAP ac where the wlan interfaces are not added to the bridge. Clients can connect but there is no communication with the router. And the protocol mode was set to none...
WAP ac have enabled cap and is getting the configuration from CAPsMAN. This is how the problem reflects on my configuration ;)

mIRO
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1406
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.39rc [release candidate] is released

Mon Mar 20, 2017 4:08 pm

athurdent - Please write to support@mikrotik.com and send supout file from device with this version and after you have tested this fix
 
athurdent
just joined
Posts: 24
Joined: Fri Sep 09, 2016 7:02 pm

Re: v6.39rc [release candidate] is released

Mon Mar 20, 2017 6:51 pm

strods - I already have a ticket open, Uldis asked me for remote access last Friday. Have not heard back yet, but you should already be able to access my device.
 
JimmyNyholm
Member Candidate
Member Candidate
Posts: 249
Joined: Mon Apr 25, 2016 2:16 am
Location: Sweden

Re: v6.39rc [release candidate] is released

Tue Mar 21, 2017 1:17 pm

!) bridge - fixed BPDU rx/tx when protocol-mode=none

Fixed as in now we do forward all bpdu's transparrently or now we eat all transparrently What is done exactly?
Need to know so we may plan for the changed behaviour.
 
anuser
Member
Member
Posts: 372
Joined: Sat Nov 29, 2014 7:27 pm

Re: v6.39rc [release candidate] is released

Wed Mar 22, 2017 3:09 pm

CAPSMAN controller: CCR1009
Wifi CAPS: WAP AC + HAP AC

v6.36.4:
working fine, reference speed wireless: 250-260Mbit/s

v6.38.x :
- massive wireless issues with capsman (continous disconnects, slow speeds)
- RSTP causing forwarding issues (traffic not forwarding, DHCP not getting through)

v6.39rcXX-51:
- Wireless speed issue: speed only half (~ 140Mbit/s; half speed compared to v6.36.4; downgrading back to 6.36.4 results in higher speed)
I´m in the same situation: throughput is rather low. I have CAPSMAN with WAP AC devices.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8292
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.39rc [release candidate] is released

Wed Mar 22, 2017 3:12 pm

In WebFig, it's possible to move (drag'n'drop) rules even if the list is sorted not by rule number. In WinBox it's not possible :)
Russian-speaking forum: https://forum.mikrotik.by/. Welcome!

For every complex problem, there is a solution that is simple, neat, and wrong.

MikroTik. Your life. Your routing.
 
uldis
MikroTik Support
MikroTik Support
Posts: 3424
Joined: Mon May 31, 2004 2:55 pm

Re: v6.39rc [release candidate] is released

Wed Mar 22, 2017 6:04 pm

v6.39rcXX-51:
- Wireless speed issue: speed only half (~ 140Mbit/s; half speed compared to v6.36.4; downgrading back to 6.36.4 results in higher speed)
We need more info how to reproduce this problem. Step by step so we could try to reproduce this problem.
What wireless packages you used on the 6.36.4 and did you downgrade both CAPsMAN and CAP?
 
palhaland
just joined
Posts: 10
Joined: Mon Aug 15, 2016 9:05 pm

Re: v6.39rc [release candidate] is released

Fri Mar 24, 2017 9:27 am

I think I have found an issue with the RC.

Steps to reproduce:
1. On a RouterOS 6.38.x create a backup of the setup.
2. Upgrade to 6.39rcXX-xx
3. Reset the board.
4. Apply backup
5. After reboot RouterBoard has no configuration.
 
User avatar
BartoszP
Forum Guru
Forum Guru
Posts: 1702
Joined: Mon Jun 16, 2014 1:13 pm
Location: Poland

Re: v6.39rc [release candidate] is released

Fri Mar 24, 2017 11:22 am

Backup should be restored to same version of ROS as i have been made.
You should try /export your configuration if you want to restore it to the newer version of ROS
Real admins use real keyboards.
 
anuser
Member
Member
Posts: 372
Joined: Sat Nov 29, 2014 7:27 pm

Re: v6.39rc [release candidate] is released

Fri Mar 24, 2017 12:45 pm

v6.39rcXX-51:
- Wireless speed issue: speed only half (~ 140Mbit/s; half speed compared to v6.36.4; downgrading back to 6.36.4 results in higher speed)
We need more info how to reproduce this problem. Step by step so we could try to reproduce this problem.
What wireless packages you used on the 6.36.4 and did you downgrade both CAPsMAN and CAP?
So I tested with CAPSMAN => Configuration => Distance set to indoors AND CAPSMAN => Configuration => Rates empty setting.

distance between laptop and accesspoint: ~30cm

CAPSMAN Controller (x86) version is: 6.39rc55
- So I tested with an HAP AC with serial number: 673706EDxxxx, Windows 10 Pro with Intel 4965AGN
6.36.4(5GHz): ~5MB/s
6.37.5(5GHz): ~7MB/s
6.38.5(5GHz): ~50KB/s to 1,7MB/s . Throughput is going up and down. Mostly at KB/s speed
6.39rc55(5GHz): ~8MB/s.

- New test with an WAP AC with serial number: 69A505A1xxxx, Windows 10 Pro with Intel 4965AGN
6.38.1(5Ghz): ~7,2 MB/s
6.38.5(5GHz): ~7MB/s
6.39rc55(5GHz): ~5MB/s to ~7,5 MB/s

- New test with an WAP AC with serial number 711E06ECxxxx, Windows 10 Pro with Intel 4965AGN
6.35.4(5Ghz): 6,4MB/s
6.36.4(5Ghz): 6,5MB/s
6.38.5(5 GHz): 6,2 MB/s
6.39.rc55(5 Ghz): 4,4MB/s to 6,4MB/s
6.39.rc55(2.4Ghz): 2,4MB/s to 3 MB/s
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1406
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.39rc [release candidate] is released

Fri Mar 24, 2017 12:50 pm

Version 6.39rc58 has been released.

Changes since previous version:

*) certificate - SCEP client now supports FQDN URL and port;
*) ethernet - added "voltage-too-low" status for single port power injector devices;
*) ethernet - fixed unnecessary power cycle of powered device when changing any poe-out related setting on single port power injector devices;
*) ethernet - reversed poe-priority on hEX PoE and OmniTIK 5 PoE to make "poe-priority" consistent to all other RouterOS priorities;
*) fetch - added "http-data" and "http-method" parameters to allow delete, get, post, put methods (content-type=application/x-www-form-urlencoded by default);
*) ike2 - fixed CTR mode;
*) ike2 - remove old SA after rekey;
*) ipsec - fixed SA authentication flag;
*) lte - added log entry for SMS delivery report;
*) ntp - restart NTP client when it is stuck in error state;
*) smb - fixed different memory leaks and crashes;
*) smb - fixed share path on devices with "/flash" directory;
*) userman - fixed rare web interface crash while using Users section;
*) wireless - fixed false positive DFS radar detection caused by iPhone 6s devices;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.
 
pe1chl
Forum Guru
Forum Guru
Posts: 5566
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.39rc [release candidate] is released

Fri Mar 24, 2017 4:58 pm

*) ethernet - reversed poe-priority on hEX PoE and OmniTIK 5 PoE to make "poe-priority" consistent to all other RouterOS priorities;
What does "all other RouterOS priorities" mean?
Note that packet priorities are inconsistent with queue priorities.
(when setting a packet priority e.g. "from DSCP high 3 bits", value 7 is higher priority than value 0, but when setting up a queue tree,
a lower priority value means higher priority for that entry)

And then we do not even consider that in 802.11p, the place where the packet priority is used, the priorities from low to high are like
this: 1 0 2 3 4 5 6 7 because 0 is the default priority leaving no room for a below-normal priority.
 
picacho99
newbie
Posts: 42
Joined: Mon Sep 08, 2014 7:16 pm

Re: v6.39rc [release candidate] is released

Sat Mar 25, 2017 9:15 pm

A RB3011 with a regular configruation when upgraded from v6.38.5 to v6.39.55 or v6.39.58 device becomes unusable: reboots again and again until it is recovered with reset and netinstall.
 
palhaland
just joined
Posts: 10
Joined: Mon Aug 15, 2016 9:05 pm

Re: v6.39rc [release candidate] is released

Sat Mar 25, 2017 10:05 pm

Backup should be restored to same version of ROS as i have been made.
You should try /export your configuration if you want to restore it to the newer version of ROS
Does this apply to upgrading from 6.38 as well? Currently it clears all configuration when upgrading as well
 
IntrusDave
Forum Guru
Forum Guru
Posts: 1282
Joined: Fri May 09, 2014 4:36 am
Location: Rancho Cucamonga, CA

Re: v6.39rc [release candidate] is released

Sun Mar 26, 2017 8:02 pm

A RB3011 with a regular configruation when upgraded from v6.38.5 to v6.39.55 or v6.39.58 device becomes unusable: reboots again and again until it is recovered with reset and netinstall.
I has this same issue. I think it may be from the addition of the partition support.
David Joyce
Network & Security Engineer
Intrus Technologies, LLC.
Rancho Cucamonga, CA, USA
 
zcybercomputing
just joined
Posts: 17
Joined: Tue Feb 14, 2017 4:10 am

Re: v6.39rc [release candidate] is released

Mon Mar 27, 2017 3:18 am

A RB3011 with a regular configruation when upgraded from v6.38.5 to v6.39.55 or v6.39.58 device becomes unusable: reboots again and again until it is recovered with reset and netinstall.
I had this problem going from v6.38.4 to 6.38.5 on the RB3011 also. Unfortunantly the router is one of my main routers, and I didn't have a spare so I couldn't debug. I did have extra packages installed and was running dude.
  • 1
  • 4
  • 5
  • 6
  • 7
  • 8

Who is online

Users browsing this forum: No registered users and 12 guests