Community discussions

MikroTik App
 
hapi
Member Candidate
Member Candidate
Posts: 232
Joined: Fri Mar 11, 2011 11:21 am
Location: Czech Republic

Re: v6.42rc [release candidate] is released!

Tue Jan 30, 2018 3:47 pm

Add flow control status to ethernet status in winbox. thx
 
metricmoose
newbie
Posts: 48
Joined: Sat Nov 21, 2015 2:03 am

Re: v6.42rc [release candidate] is released!

Tue Jan 30, 2018 7:47 pm

Version 6.42rc15 has been released.

*) fetch - added "output" option for all modes in order to return result to file, variable or ignore it;
I have been trying to test the ability to store downloaded data in a variable, though I haven't had any luck yet.
[admin@Mikrotik] > /tool fetch https://api.ipify.org/ output=user 
      status: finished
  downloaded: 0KiBC-z pause]
       total: 0KiB
    duration: 0s
        data: [My IP Address was here] 
I can see the data showing up, which is great. Though I can't seem to store that in a variable, I'm used to using "get" in other cases with Mikrotik scripting, but that doesn't seem to be available here. I'm fairly new to Mikrotik scripting, so I hope I'm not missing anything obvious.
 
User avatar
null31
Member Candidate
Member Candidate
Posts: 183
Joined: Fri Dec 23, 2016 6:07 pm
Location: Brazil

Re: v6.42rc [release candidate] is released!

Wed Jan 31, 2018 3:02 am

Hi.
I noted that PVID field has the value 65 as default when add a port to a bridge under the Winbox.
Under terminal is ok, set the value 1 to that field.

Unit RB951Ui-2HnD
ROS 6.42rc15
Winbox 3.11 under wine 3.0 on Arch Linux


Image
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v6.42rc [release candidate] is released!

Wed Jan 31, 2018 7:37 pm

Hi.
I noted that PVID field has the value 65 as default when add a port to a bridge under the Winbox.
Under terminal is ok, set the value 1 to that field.
Confirmed, I see the same thing on rc12
 
JimmyNyholm
Member Candidate
Member Candidate
Posts: 248
Joined: Mon Apr 25, 2016 2:16 am
Location: Sweden

Re: v6.42rc [release candidate] is released!

Thu Feb 01, 2018 12:22 pm

that pvid could be seen in 41rc's aswell if you set something it goes away though
 
gumbi2400
just joined
Posts: 3
Joined: Thu Feb 01, 2018 4:28 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 01, 2018 5:00 pm

I think I found an odd bug.

I recently set up an L2TP/IPSEC VPN connection to an external provider (ipvanish). I noticed that the connection when connecting directly from my local computer I get about 98% of my max internet speed (330Mbps). Setting up this same connection on my rb750gr3 and connecting through there I get no more than 1.5Mbps.

I initially assumed I set up something wrong and went through everything I could think of. Eventually I turned on the packet sniffer to see if I could see anything odd. I ran the speed test again, and I got 98Mbps, not as good as a full blown computer but not bad! When disabling the packet sniffer speed drops back down to 1.5.

In Summary: When using L2TP/IPSEC VPN enabling the packet sniffer increases speed dramatically.

Please let me know if additional information is needed.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 01, 2018 5:05 pm

You need to turn off fastpath and fasttrack in that case.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7049
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.42rc [release candidate] is released!

Thu Feb 01, 2018 5:06 pm

Make sure that packets are not catched by fasttrack. If packet is fasttracked it will not be seen by ipsec policy and you get packet loss/slow tunnels.
 
gumbi2400
just joined
Posts: 3
Joined: Thu Feb 01, 2018 4:28 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 01, 2018 5:29 pm

Ah not a bug after all. My apologies! I feel a bit silly as I thought I already disabled that. Thanks!
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 01, 2018 6:02 pm

Please please please do some work on IPv6!
E.g. following priorities from this posting: viewtopic.php?f=2&t=123302

Things I really need, the sooner the better:
- route marking and multi route tables using marks as in IPv4
(via ipv6 firewall mangle and/or ipv6 route rule)
- configurable IPv6 nameservers in DHCPv6 and RA, or at least the option to publish the router's own
address as nameserver instead of the configured external DNS servers
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Fri Feb 02, 2018 11:03 am

Version 6.42rc18 has been released.

Changes since previous release:

*) bridge - show "hw" flags only on Ethernet interfaces and interface lists;
*) crs3xx - added switch port "storm-rate" limiting options;
*) kidcontrol - added initial support for "/ip kid-control" feature;
*) lte - fixed AT communication with modem (introduced in v6.42rc12);
*) switch - hide "ingress-rate" and "egress-rate" for non-crs3xx switches;
*) tile - improved stability in high throughput HW accelerated IPsec setups ("/system routerboard upgrade" required);
*) upgrade - improved RouterOS upgrade process and restrict upgrade from RouterOS older than v5.16;
*) webfig - fixed backup loading from Webfig on RouterBOARD running default configuration;
*) winbox - allow to comment new object without committing it;
*) wireless - fixed incompatibility with macOS clients;
*) wireless - fixed wireless protocol mode restrictions if lock package is installed and has limits for it;

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 expected or after crash.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 02, 2018 12:13 pm

*) winbox - allow to comment new object without committing it;
Great!
Another potential improvement in this area: allow to set comment on an object without causing any reconfiguration or state-change on it.
(in some cases the configured object goes down-up when you change the comment!)
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.42rc [release candidate] is released!

Fri Feb 02, 2018 12:19 pm

(in some cases the configured object goes down-up when you change the comment!)
Please report exact cases. They fix it :)
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Fri Feb 02, 2018 12:20 pm

pe1chl - Seems that you misunderstood the fix. Assume that you add firewall rule, specify different parameters and do not press "Ok" button yet. Now you press "Comment" button and specify comment. When you press "Ok" on comment form, then in the past whole rule was added to firewall. Now "Ok" button on comment accepts only comment - it does not create a new rule right away.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 02, 2018 2:06 pm

(in some cases the configured object goes down-up when you change the comment!)
Please report exact cases. They fix it :)
I think it is easier for them to find all cases where this is handled incorrectly than for me trying to hunt them down and potentially miss some.
It looks like it really happens *everywhere*, however not in all cases there is an observable impact on operations.
(like a connection being dropped and re-established, or similar)
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 02, 2018 2:09 pm

pe1chl - Seems that you misunderstood the fix. Assume that you add firewall rule, specify different parameters and do not press "Ok" button yet. Now you press "Comment" button and specify comment. When you press "Ok" on comment form, then in the past whole rule was added to firewall. Now "Ok" button on comment accepts only comment - it does not create a new rule right away.
I understand that and I think it is great, because in the past I have sometimes gone wrong with that, e.g. because it stored something that was not configured correctly yet after doing a COPY, and I wanted to reset the comment as one of the first steps. In fact, it would be better when the comment is just a separate TAB on the object, like in Webfig.

However, what I mean is when using the yellow icon to only change the comment on an existing object, it should just change the comment and not do anything else with the object.
 
drbunsen
newbie
Posts: 40
Joined: Fri Apr 29, 2016 7:24 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 02, 2018 2:28 pm

I've updated a crs317 from rc6 to rc18 and now the fan is kicking in regularly. It seems it's trying to keep the cpu temperature below 40C as this is the point when it stops again.
There's nothing in the changelog about it and before that I've even seen cpu temperatures of almost 50C without the fan starting. Has this been changed?

At living room temperatures and idling the fan now iterates between running 30 seconds and being 1-2 minutes off. A little bit annoying and I guess also not the best running conditions for the fans on log term. Especially as it was totally quiet before and not remarkably hotter with like around 44C.
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Fri Feb 02, 2018 2:47 pm

Version 6.42rc20 has been released.

Changes since previous release:

*) upgrade - improved RouterOS upgrade process and restrict upgrade from RouterOS older than v5.16;

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 expected or after crash.
 
drbunsen
newbie
Posts: 40
Joined: Fri Apr 29, 2016 7:24 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 02, 2018 4:10 pm

I've updated a crs317 from rc6 to rc18 and now the fan is kicking in regularly. It seems it's trying to keep the cpu temperature below 40C as this is the point when it stops again.
There's nothing in the changelog about it and before that I've even seen cpu temperatures of almost 50C without the fan starting. Has this been changed?

At living room temperatures and idling the fan now iterates between running 30 seconds and being 1-2 minutes off. A little bit annoying and I guess also not the best running conditions for the fans on log term. Especially as it was totally quiet before and not remarkably hotter with like around 44C.
OK, that was too annoying and I've installed 6.41.1 stable now. Fan stays off with cpu at 42C.
Mikrotik you might want to look into this. Oviously there was some sort of change and as it's not in the changelog I assume it's not intended?
 
User avatar
armandfumal
Member Candidate
Member Candidate
Posts: 159
Joined: Wed Apr 25, 2012 5:50 pm
Location: Weiswampach,LUX
Contact:

Re: v6.42rc [release candidate] is released!

Fri Feb 02, 2018 9:16 pm

*) chr - added "open-vm-tools" on VMware installations;

tested. at least !!!

thanks

Just missing BGP routing in multicore cpu....need this please !!!!
 
User avatar
nz_monkey
Forum Guru
Forum Guru
Posts: 2099
Joined: Mon Jan 14, 2008 1:53 pm
Location: Over the Rainbow
Contact:

Re: v6.42rc [release candidate] is released!

Fri Feb 02, 2018 11:27 pm

Just missing BGP routing in multicore cpu....need this please !!!!
Please see viewtopic.php?f=3&t=129649#p638204
 
jmi2
just joined
Posts: 10
Joined: Mon Feb 05, 2018 11:41 am

Re: v6.42rc [release candidate] is released!

Mon Feb 05, 2018 12:19 pm

short version: With this routerOS version, if there is single client with older card like CM9, then all other clients got no change to communicate without issues.
Simply if such client is connected to AP, then mobile and notebook have horrible connectivity and LG TV and hama radio got disconnected always after few seconds.

long version: Starting with 6.37 (actually already before, if previous FWs like 6.36.4 were switched to use wireless-rep) in combination with old HW like CM9, R52 on client side, wireless channel becomes useless for all (other clients of same AP and also clients of other APs on same channel). Same issue is still there with 6.42rc20.

details:
Starting with 6.37 (and already in previous release, if wireless-rep was enabled), also with 6.40.5 and 6.42rc20 i observed below described issue, when old hardware like CM0, r52 and few others were used. I did test always with boards RB433, but i guess it's wireless issue, as it depends on wireless package used. There is no issue if HW r5nH or r52nM is used.
Issue exists in both G-only and A-only mode.

My setup was indoor:
- mikrotik AP bridge
- mikrotik client1
- mikrotik client2
Tested with fixed data rate and fixed power.

1) Each client works fine, if it's alone on AP.
2) In moment, when 2nd client with CM9 and FW 6.37(.3) or newer (or with wireless-rep package) connects, then for others: CCQ is going down, latencies up (even to hundreds on empty links), loss occurs, or client gets disconnected after few seconds (e.g. LG TV, hama radio, mikrotik with r52nM. But e.g. CM9 client survices with loss (Actually both clients have loss, if both a on version 6.37+). Note: 2nd client is not doing any traffic on AP (expect for neighbours discovery and similar, simply only few packets per second).
3) I also tried to setup 2 APs on same channel and connect 1 CM9 client per AP. If clients were on 6.36.4, it all worked fine, even throughput like 10-15mbit on each AP while sharing channel was possible. However, once i updated one client to affected version (tried with 6.40.5 or 6.42rc20), in moment CM9 connected to one AP, problem occured with client on another AP.
4) I wasn't able to reproduce the issue if using only R5nH / R52nM cards in my test setup. Tested with 6.40.5 and all worked fine.

First i spent one night trying to figure out what went wrong with AP or TV ... then i realized it's enough to turn off mikrotik client with CM9, which was updated to latest version, to get my TV, radio and laptop working fine (e.g. with CM9 client turned on speedtest to internet was 0.5mbit, without CM9 client it was 25mbit)
Then I did tests only between 3-4 mikrotik devices (As described) with client on versions 3.30, 4.17, 5.26, 6.0, 6.29.1, 6.33.3, 6.35.4, 6.36.4, where all was fine
and with 6.36.4 with wireless-rep, 6.37.3, 6.38.5, 6.38.7, 6.39.3, 6.40.5, 6.42rc20 where it was causing described problems.

I also did tests for AP side, so far my outcome is, that AP side has not this issue, e.g. works well if AP is with CM9 and 6.40.5. That means, all clients (cm9, r52nM, r5nH) of this AP are working fine (unless that CM9 client is on affected version of routeros).

For configuration: routerOs was fresh after reset, only IP and wifi configured. For wifi i tried with wpa2 aes and also without security. Also tried to disable roaming (if routerOS allowed it).

For me it looks like that with affected versions CM9 / r52 are constantly sending something to the air, which prevents others to communicate.
 
raffav
Member
Member
Posts: 345
Joined: Wed Oct 24, 2012 4:40 am

Re: v6.42rc [release candidate] is released!

Mon Feb 05, 2018 4:55 pm

Hello
can someone give me a example how to use TLS-host i tryed to use facebook youtube, allot of site no one worked
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.42rc [release candidate] is released!

Tue Feb 06, 2018 7:23 am

can someone give me a example how to use TLS-host i tryed to use facebook youtube, allot of site no one worked
/ip firewall filter
add action=passthrough chain=forward dst-port=443 protocol=tcp tls-host=*.facebook.com
At least I put that rule before Fasttrack rule - and it caught my connection to facebook :)
 
anuser
Long time Member
Long time Member
Posts: 601
Joined: Sat Nov 29, 2014 7:27 pm

Re: v6.42rc [release candidate] is released!

Tue Feb 06, 2018 7:58 am

*) wireless - fixed incompatibility with macOS clients;
What problems exist with macOS clients? Which OS X versions are affected? ( I'm running 6.41 on all CAPs and have no issues being reported by OS X clients...)
 
uldis
MikroTik Support
MikroTik Support
Posts: 3446
Joined: Mon May 31, 2004 2:55 pm

Re: v6.42rc [release candidate] is released!

Tue Feb 06, 2018 10:44 am

*) wireless - fixed incompatibility with macOS clients;
What problems exist with macOS clients? Which OS X versions are affected? ( I'm running 6.41 on all CAPs and have no issues being reported by OS X clients...)
If you were setting priorities for the WMM then sometimes the macOS clients didn't accept packets with some priorities.
 
User avatar
frank333
Member
Member
Posts: 330
Joined: Mon Dec 18, 2017 12:17 pm
Location: S.Marino Router model: RB3011UiAS-RM+RBM11G

Re: v6.42rc [release candidate] is released!

Tue Feb 06, 2018 12:59 pm

in Bandwidth_Test you might have a box to save the ip of test servers without recompile it all the time?
 
hawk
just joined
Posts: 2
Joined: Mon Jan 29, 2018 9:46 am

Re: v6.42rc [release candidate] is released!

Tue Feb 06, 2018 2:53 pm

I have the problem with MSTP. I configured everything but the machine not see the root path cost and designated bridge. Not calculate costs in MSTP.(CRS317)
 
User avatar
frank333
Member
Member
Posts: 330
Joined: Mon Dec 18, 2017 12:17 pm
Location: S.Marino Router model: RB3011UiAS-RM+RBM11G

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 1:11 am

Tip for developers, so that you do not enter the possibility of a percentage value instead of max-limits in the queue tree?
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 3:00 am

Percentage of what?
 
User avatar
frank333
Member
Member
Posts: 330
Joined: Mon Dec 18, 2017 12:17 pm
Location: S.Marino Router model: RB3011UiAS-RM+RBM11G

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 11:36 am

Percentage of what?
I meant to say that, instead of entering the max limit value you could assume a fixed value in percentage or at choice.
Of course, ROS should read the bandwidth instantly or after a set time.
(e. g. 10% bandwidth istantly / 1.10=max-limit)
Last edited by frank333 on Thu Feb 08, 2018 11:44 am, edited 1 time in total.
 
sindy
Forum Guru
Forum Guru
Posts: 10206
Joined: Mon Dec 04, 2017 9:19 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 11:43 am

Percentage of what?
I meant to say that, instead of entering the max limit value you could assume a fixed value in percentage (e. g. 10%) or at choice.
Of course, ROS should read the bandwidth instantly or after a set time.
Again, percentage of what? Interface speed? Some queues are not related to any particular interface.
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 12:02 pm

Version 6.42rc23 has been released.

Changes since previous release:

*) console - fixed "idpr-cmtp" protocol by changing its value from 39 to 38 (CLI only);
*) crs3xx - added initial hw-offload support for 802.3ad and balance-xor bonding
*) disk - fixed disk related processes becoming unresponsive after unplugging used disk;
*) kidcontrol - added initial support for "/ip kid-control" feature;
*) ppp - do not lose "/ppp profile" script configuration after other profile parameters are edited;
*) routerboard - properly report warnings under "/system routerboard" menu;
*) sniffer - fixed situation when "/tool sniffer packet" returned packets in incorrect order;
*) snmp - added w60g support;
*) upgrade - improved RouterOS upgrade process and restrict upgrade from RouterOS older than v5.16;
*) w60g - fixed "/interface w60g reset-configuration";
*) winbox - changed default bridge port PVID value to 1;
*) wireless - added initial support for "nstreme-plus";
*) wireless - improved compatibility with specific wireless AC standard clients;

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 expected or after crash.
 
User avatar
kometchtech
Member Candidate
Member Candidate
Posts: 194
Joined: Sat Jun 15, 2013 4:25 am
Location: Japan
Contact:

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 12:24 pm

Version 6.42rc23 has been released.

Changes since previous release:

*) console - fixed "idpr-cmtp" protocol by changing its value from 39 to 38 (CLI only);
*) crs3xx - added initial hw-offload support for 802.3ad and balance-xor bonding
*) disk - fixed disk related processes becoming unresponsive after unplugging used disk;
*) kidcontrol - added initial support for "/ip kid-control" feature;
*) ppp - do not lose "/ppp profile" script configuration after other profile parameters are edited;
*) routerboard - properly report warnings under "/system routerboard" menu;
*) sniffer - fixed situation when "/tool sniffer packet" returned packets in incorrect order;
*) snmp - added w60g support;
*) upgrade - improved RouterOS upgrade process and restrict upgrade from RouterOS older than v5.16;
*) w60g - fixed "/interface w60g reset-configuration";
*) winbox - changed default bridge port PVID value to 1;
*) wireless - added initial support for "nstreme-plus";
*) wireless - improved compatibility with specific wireless AC standard clients;

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 expected or after crash.
Hi all,

When rc23 was applied, Interface was no longer recognized by OS on the following Routerboard.

- CCR1009-8G-1S-1S+

This was a segmentation fault.

- RB850Gx2

I think that it is better to stop being applied if possible.

Best regards.
Last edited by kometchtech on Thu Feb 08, 2018 12:41 pm, edited 1 time in total.
 
User avatar
frank333
Member
Member
Posts: 330
Joined: Mon Dec 18, 2017 12:17 pm
Location: S.Marino Router model: RB3011UiAS-RM+RBM11G

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 12:33 pm

Percentage of what?
I meant to say that, instead of entering the max limit value you could assume a fixed value in percentage (e. g. 10%) or at choice.
Of course, ROS should read the bandwidth instantly or after a set time.
Again, percentage of what? Interface speed? Some queues are not related to any particular interface.
Image
I thought that in the queue-tree they were divided only into main and parents. I am a beginner.
 
carnivean
just joined
Posts: 7
Joined: Thu Jan 28, 2016 4:41 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 12:37 pm

nstreme-plus ? What is it ? ;)
 
chrryd
just joined
Posts: 8
Joined: Sat Jul 15, 2017 3:03 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 12:44 pm

Version 6.42rc23 has been released.

Changes since previous release:

*) crs3xx - added initial hw-offload support for 802.3ad and balance-xor bonding
Oh! Do we finally get 802.3ad link aggregation in HW on routeros - I've been waiting for that for a long time :-) Any documentation on how to set that up?
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1071
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 12:50 pm

This broke my CHR installation, though I am not sure if 6.42rc23 is involved at all. The system was running 6.42rc20. I booted it and tried to update, the system told me there is not enough free space. After reboot it hangs at "Loading system with initrd".
 
mistry7
Forum Guru
Forum Guru
Posts: 1480
Joined: Tue Oct 13, 2009 11:57 am
Location: Germany

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 1:00 pm

nstreme-plus ? What is it ? ;)
thats my question too
 
morf
Member Candidate
Member Candidate
Posts: 182
Joined: Tue Jun 21, 2011 5:31 pm
Location: Saint-Petersburg

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 1:10 pm

nstreme-plus ? What is it ? ;)
thats my question too
+
 
User avatar
pietroscherer
Trainer
Trainer
Posts: 170
Joined: Thu Mar 05, 2015 3:05 pm
Location: RS, Brazil
Contact:

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 1:48 pm

nstreme-plus ? What is it ? ;)
+ 32984920 :lol:
 
UMarcus
Frequent Visitor
Frequent Visitor
Posts: 95
Joined: Wed Jan 21, 2015 10:11 am
Location: Europe

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 2:01 pm

*) wireless - improved compatibility with specific wireless AC standard clients;
What does 'improve compatibility' mean ? Also speed related ?
 
th0massin0
Member Candidate
Member Candidate
Posts: 156
Joined: Sun May 11, 2014 4:16 am
Location: Poland

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 2:25 pm

May I ask about boot from VirtIO-SCSI (in CHR) in this release?
 
User avatar
null31
Member Candidate
Member Candidate
Posts: 183
Joined: Fri Dec 23, 2016 6:07 pm
Location: Brazil

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 2:39 pm

This broke my CHR installation, though I am not sure if 6.42rc23 is involved at all. The system was running 6.42rc20. I booted it and tried to update, the system told me there is not enough free space. After reboot it hangs at "Loading system with initrd".
Same here, except by the message about free space.
Upgrade from 6.42rc20 to 6.42rc23, after reboot, CHR is broken.
Detects one interface only and with mac-address filled with zero.

Linux live and scp to get the supout.rif.

Image from CHR cli: https://i.imgur.com/kfKnjjF.png

I sent a ticket to MikroTik support. [Ticket#2018020822005224]
Last edited by null31 on Thu Feb 08, 2018 3:05 pm, edited 1 time in total.
 
zryny4
just joined
Posts: 9
Joined: Sun Apr 17, 2016 12:29 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 2:45 pm

After upgrade from rc20 to rc23, I cannot login to router via http: "ERROR: Not Found", ssh -- ok, login not default admin.
 
doush
Long time Member
Long time Member
Posts: 665
Joined: Thu Jun 04, 2009 3:11 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 2:47 pm

what is nstreme-plus ?
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 3:00 pm

Main part of upgrade process happens on old version.

For example, rc21 -> rc23. If upgrade fails, then it is caused by rc21 version. As you can see in changelog we are still working on upgrade improvements. At the moment latest fixes are included in rc23. You can test upgrade improvements only when upgrade from rc23 to, for example, rc24 will be available.

In future, if you experience problems with upgrade, then remember to mention from which precise RouterOS version and to which you made an upgrade.
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1071
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 3:04 pm

Main part of upgrade process happens on old version.

For example, rc21 -> rc23. If upgrade fails, then it is caused by rc21 version. As you can see in changelog we are still working on upgrade improvements. At the moment latest fixes are included in rc23. You can test upgrade improvements only when upgrade from rc23 to, for example, rc24 will be available.
Sure. But with "not enough free space available" the system should cancel upgrade and stay with old version, no?
Are you interested in the broken image?
 
User avatar
null31
Member Candidate
Member Candidate
Posts: 183
Joined: Fri Dec 23, 2016 6:07 pm
Location: Brazil

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 3:43 pm

For example, rc21 -> rc23. If upgrade fails, then it is caused by rc21 version. As you can see in changelog we are still working on upgrade improvements. At the moment latest fixes are included in rc23. You can test upgrade improvements only when upgrade from rc23 to, for example, rc24 will be available.
Well...
I tried boot-up a VDI, VMDK and Ova (imported to vbox) from CHR 6.42rc23, all of them show the same message.
Message: https://i.imgur.com/3rs5CPZ.png

Now, I booted-up a VDI from CHR 6.41.1 with IP address, one DNS and one default route. I upgrade to 6.42rc23, no problems after upgrade, but was over a minimal config to access internet and nothing more.

Edit after rc24: Even the VDI of CHR 6.42rc24 show the above message about Missing OS...
Print from CHR 6.42rc24: https://i.imgur.com/Dlg9NSm.png

I feel this release (rc23/24) like a lulz from development team. :lol:
Last edited by null31 on Thu Feb 08, 2018 4:12 pm, edited 5 times in total.
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 4:01 pm

Version 6.42rc24 has been released.

Changes since previous release:

*) crs3xx - added initial hw-offload support for 802.3ad and balance-xor bonding
*) export - fixed "/system routerboard mode-button" compact export;
*) firewall - fixed "tls-host" firewall feature (introduced v6.41);

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 expected or after crash.t
 
blingblouw
Member
Member
Posts: 345
Joined: Wed Aug 25, 2010 9:43 am

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 4:02 pm

Nstreme-plus?
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 878
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 5:28 pm

this AM I Installed [upgraded] 6.42rc24 on my CCR1009 and now no connectivity --- Winbox cannot discover the Router

How do I recover from this please?

[EDIT] following is what I did to recover:
1. connect my serial cable
2. connect my Ethernet cable to ether7
3. run netinstall
4. reboot the CCR1009 ... use the reset button and hold reset in then power up the router, observer the netinstall screen until it recognizes the router THEN release the reset
5.via netinstall install RouterOS v6.41
6. reconfigure the CCR1009 then upgrade to 6.42rc24 .... so far everything is OK

Thanks to Dan from https://www.balticnetworks.com/ for the excellent help.
Last edited by mozerd on Mon Feb 12, 2018 2:43 pm, edited 3 times in total.
 
User avatar
null31
Member Candidate
Member Candidate
Posts: 183
Joined: Fri Dec 23, 2016 6:07 pm
Location: Brazil

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 5:35 pm

this AM I Installed 6.42rc24 on my CCR1009 and now no connectivity --- Winbox cannot discover the Router

How do I recover from this please?
Access the router over physical console, or netinstall it!
-----------
CHR v6.42rc24 persist the problem about Missing OS.
I asked to a friend to configure and boot VHDX image on Hyper-V over windows 10.
The result? Fail.
Print from him: https://i.imgur.com/7jVC4oe.png
 
105547111
Member Candidate
Member Candidate
Posts: 135
Joined: Fri Jun 22, 2012 9:46 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 6:06 pm

Version 6.42rc24 has been released.

Changes since previous release:

*) crs3xx - added initial hw-offload support for 802.3ad and balance-xor bonding
*) export - fixed "/system routerboard mode-button" compact export;
*) firewall - fixed "tls-host" firewall feature (introduced v6.41);

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 expected or after crash.t
Strods,

Doesn't this also have the kernel crash fix for CCR introduced in 6.41.1?
 
raffav
Member
Member
Posts: 345
Joined: Wed Oct 24, 2012 4:40 am

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 6:28 pm

@Strods

Since this new crs Poe series is out, so this version belongs to the same of crs1xx having the same features or it have new features available on crs3xx series?


Enviado do meu iPad usando Tapatalk
 
User avatar
honzam
Forum Guru
Forum Guru
Posts: 2394
Joined: Wed Feb 27, 2008 10:27 pm
Location: Czech Republic

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 6:53 pm

Nstreme-plus?
I upgrade old rb711-5Hnd to 6.42rc24. There is no possibility set nstreme-plus
 
Airell
just joined
Posts: 9
Joined: Fri Mar 25, 2016 3:40 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 7:03 pm

I bricked my RB850Gx2 when updating to 6.42rc23...
It did not came up and WinBox did not find any mac-address neighbours any of the interfaces.
Clearing config (using hardware reset button) did not work either, I had to use netinstall to get it back to life. :(

Cheers, Airell.
 
raffav
Member
Member
Posts: 345
Joined: Wed Oct 24, 2012 4:40 am

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 8:59 pm

MT support
i can confirme that has a bug on this RC 24 version the dhcp-client is buggy, i cant make it work it has a Invalid on terminal
i will set ip manual and sent a suport file to MT email

edit
unfortunately I cant set up manually because i get interface as invalid , so i cant send you a support file
 
LIV2
newbie
Posts: 30
Joined: Sat Jan 23, 2016 7:42 am

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 9:48 pm

@Strods

Since this new crs Poe series is out, so this version belongs to the same of crs1xx having the same features or it have new features available on crs3xx series?


Enviado do meu iPad usando Tapatalk
It would be nice to finally get LACP on the CRS125. the fact that we haven't got it by now and the changelog only mentions the CRS3XX series doesn't fill me with much hope though.
 
raffav
Member
Member
Posts: 345
Joined: Wed Oct 24, 2012 4:40 am

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 11:22 pm

Where is the dude client for RC24?
 
CapFloor
just joined
Posts: 10
Joined: Sat Feb 06, 2016 1:38 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 08, 2018 11:44 pm

Hi, rc24 didn't only kill one crs1009, it does the same with an rb1100ah4, both out-of-the-box with default configuration. Netinstall brought them back to life.
 
birchman
just joined
Posts: 1
Joined: Fri Feb 09, 2018 5:04 am

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 5:24 am

I bricked my CCR1009 when updating to 6.42rc23 :(
What to do?
The Netinstall cant install on a Flash Card or USB
Net boot don't work...
 
alexjhart
Member Candidate
Member Candidate
Posts: 197
Joined: Thu Jan 20, 2011 8:03 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 6:49 am



*) crs3xx - added initial hw-offload support for 802.3ad and balance-xor bonding
What does "initial" mean here?
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 6:50 am

Main part of upgrade process happens on old version.

For example, rc21 -> rc23. If upgrade fails, then it is caused by rc21 version. As you can see in changelog we are still working on upgrade improvements. At the moment latest fixes are included in rc23. You can test upgrade improvements when upgrading from rc23 to, for example, rc24.

At the moment we are not aware about any problems with upgrade starting from 6.42rc23 version.

In future, if you experience problems with upgrade, then remember to mention from which precise RouterOS version and to which you made an upgrade.
 
CapFloor
just joined
Posts: 10
Joined: Sat Feb 06, 2016 1:38 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 11:03 am

Hi,
I did the upgrade to rc24 on both the ccr1009 and the rb1100ahx4 from rc20. Both were bricked then.
BR
 
PatrickKan
just joined
Posts: 7
Joined: Thu Oct 25, 2012 7:10 pm

v6.42rc [release candidate] is released!

Fri Feb 09, 2018 11:36 am

I bricked my CCR1036-8G-2S+ too after flashing rc24 - it got stuck at "Starting services" - tried resetting configurations but nothing works. I managed to force etherboot via serial console but bootp kept trying to connect PC to the router (port 8 ) without success so netinstall failed too. What else can I do?
 
User avatar
null31
Member Candidate
Member Candidate
Posts: 183
Joined: Fri Dec 23, 2016 6:07 pm
Location: Brazil

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 12:59 pm

At the moment we are not aware about any problems with upgrade starting from 6.42rc23 version.
Are you serious about this?
Did you saw my previous posts?
> viewtopic.php?f=21&t=129034&start=150#p641249
> viewtopic.php?f=21&t=129034&start=150#p641262
> viewtopic.php?f=21&t=129034&p=641436#p641289

When has a clean config, upgrade occours normally, but when have various settings, the CHR fail to start or no detect correctly the interfaces.
I reported the problems with CHR and when I download a image from MT's website, I can't use a new image because the ROS doesn't boot and show that message "Missing OS"... this isn't a simple problem from "upgarde", the image available is a problem itself.
To me, this isn't a upgrade problem and yes a "Oops!" in the commit of code with problems to the rc branch.
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 1:48 pm

We did explain upgrade process few posts ago. Upgrade happens on old version not on the one which you want to install:
viewtopic.php?f=21&t=129034&p=641456#p641392

Upgrade from 6.42rc20 (not from rc23):
viewtopic.php?f=21&t=129034&start=150#p641249
If I did understand post correctly, then this is about fresh installation, not an upgrade:
viewtopic.php?f=21&t=129034&start=150#p641262
Version from which upgrade was made is not mentioned:
viewtopic.php?f=21&t=129034&p=641436#p641289

I would also like to remind that rc versions are beta versions for RouterOS enthusiasts who are willing to test new features and can Netinstall/re-install RouterOS if necessary.
 
User avatar
null31
Member Candidate
Member Candidate
Posts: 183
Joined: Fri Dec 23, 2016 6:07 pm
Location: Brazil

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 2:22 pm

Upgrade from 6.42rc20 (not from rc23):
viewtopic.php?f=21&t=129034&start=150#p641249
If I did understand post correctly, then this is about fresh installation, not an upgrade:
viewtopic.php?f=21&t=129034&start=150#p641262
Version from which upgrade was made is not mentioned:
viewtopic.php?f=21&t=129034&p=641436#p641289
On the first link, the rc24 hadn't out yet.
On the second link, is about fresh install (rc23 and rc24) where I showed that images don't work, no boot. Also I showed a upgrade over a fresh install (6.41.1 > rc24), worked with no problems.
On the third link, is about a fresh install (rc24) over another platform of virtualizer, to show that problem not occur only on VirtualBox.

On the two last links, I tried to say that rc23 and rc24 doesn't work from a fresh install, they are bricked in the source, the MT's webiste.

The SHA256 of VDI image is ok, then isn't corrupted by download. But if I try to boot them, I receive that message that doesn't have a OS.
[kaze@hueragem3 Downloads]$ sha256sum -c chr-6.42rc24.vdi.sha256
chr-6.42rc24.vdi: OK
If a fresh install don't work, is complicate to use a CHR above of rc20... I'm trying to help about problems, I saw them, are serious and were reported.
I tried to help.
I hope that now is more clear than before.

Remind that CHR don't have Netinstall mode.
I know how the version works on MikroTik and how to be not 7uck3d, and that is why the CHR is my guinea pig, so isn't a problem if they die on upgarde process.

Thanks strods for reply.
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 2:30 pm

Thank you for explanation. We will fix this "fresh" installation issue of CHR instances as soon as possible.
 
PtDragon
Frequent Visitor
Frequent Visitor
Posts: 80
Joined: Sun Apr 26, 2009 8:52 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 3:58 pm

update from .20 to .24 build made my ccr1036 hang totally on boot, it did not even respond to reset button.
Netinstall was the only thing that saved the day.
Be careful please with this update!
 
User avatar
null31
Member Candidate
Member Candidate
Posts: 183
Joined: Fri Dec 23, 2016 6:07 pm
Location: Brazil

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 4:13 pm

Did someone tried to do a downgrade to rc18 or more old and then upgrade to rc24?
I saw that 6.42rc20 is a bomb as origin of upgrade to rc23/rc24.

Edit:
Well, I did upgrade on two RB: hap ac lite (rc14) and RB951Ui-2HnD (rc20).
Both to rc24, and no problems with upgrade.
Maybe isn't be a bomb, but...
Last edited by null31 on Fri Feb 09, 2018 5:34 pm, edited 1 time in total.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7049
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 4:18 pm

Be careful with downgrade from rc. It may brick the router.
 
JimmyNyholm
Member Candidate
Member Candidate
Posts: 248
Joined: Mon Apr 25, 2016 2:16 am
Location: Sweden

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 4:27 pm

*) crs3xx - added initial hw-offload support for 802.3ad and balance-xor bonding
Jiiiha!.... Will test prompty. Offcourse 4 tuble ip hash srcip srcport dstip dstport will come later right!?
 
User avatar
null31
Member Candidate
Member Candidate
Posts: 183
Joined: Fri Dec 23, 2016 6:07 pm
Location: Brazil

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 4:52 pm

Did someone tried to do a downgrade to rc18 or more old and then upgrade to rc24?
I saw that 6.42rc20 is a bomb as origin of upgrade to rc23/rc24.
Well, I made some tests with CHR only.
CHR images that not have the "Missing OS" is rc15 and below.
I took a rc15 image and did upgrade to rc20 using routeros-x86 npk package, then I rebooted and then made a upgrade from rc20 to rc24, mac-address filled with zero as result.
Before upgrade to rc24, I made a clone from rc20.
I did downgrade from rc20 to rc18 and then, upgrade from rc18 to rc24, Vbox closes the VM due crash to start CHR. :lol:
Upgrade from rc15 to rc24 have no problems.

Simplifying, downgrade from rc18 and above isn't a option, the better is wait in rc15 for newer versions.
If you are in rc18 and rc20, well, prepare your netinstall. :)
 
JimmyNyholm
Member Candidate
Member Candidate
Posts: 248
Joined: Mon Apr 25, 2016 2:16 am
Location: Sweden

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 5:08 pm

*) crs3xx - added initial hw-offload support for 802.3ad and balance-xor bonding
Jiiiha!.... Will test prompty. Offcourse 4 tuble ip hash srcip srcport dstip dstport will come later right!?
Ok So I tested on a CRS326-24G-2S+ but neither winbox nor cli shows anything anywhere. Initial maybe initial not ready for test yet or do I need to do something other then define bond and add the bond to the bridge?
 
User avatar
rtacheny
Frequent Visitor
Frequent Visitor
Posts: 57
Joined: Sat Sep 14, 2013 7:13 pm
Location: Braham, MN USA
Contact:

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 5:08 pm

Are we going to get any kind of response onto what nstreme-plus is? Please?
 
User avatar
indnti
Frequent Visitor
Frequent Visitor
Posts: 86
Joined: Thu Nov 09, 2006 11:53 am

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 6:06 pm

FYI. Upgrade from 6.42rc15 to rc24 on CRS125-24G-1S works fine
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 09, 2018 8:34 pm

When I update my CHR (under ESXi) from 6.42rc20 to 6.42rc24 there is a problem with the interfaces. Looking on the console I see that there
is only ether1 and the references to ether2 are replaced by *2 but both interfaces fail to work. "direct route" is no longer present (default route is)

I understand the real cause is in rc20 and I will need to do a fresh install as I don't have a snapshot backup with older version anymore...
(restoring to rc20 made it working again but update will of course kill it)
 
bbs2web
Member Candidate
Member Candidate
Posts: 232
Joined: Sun Apr 22, 2012 6:25 pm
Location: Johannesburg, South Africa
Contact:

Re: v6.42rc [release candidate] is released!

Sat Feb 10, 2018 11:44 am

Could MikroTik please fix BGP peer exports not containing 'remote-as=64512'. We note this behavior on both a 6.41 CHR and CCR1036:
/routing bgp peer
  add default-originate=if-installed in-filter=X-in name=Y out-filter=X-out remote-address=1.1.1.2 tcp-md5-key=secret123 ttl=default remote-as=64512

Then review resulting export:
[admin@router] > /routing bgp peer export
  /routing bgp peer
    add default-originate=if-installed in-filter=X-in name=Y out-filter=X-out remote-address=1.1.1.2 tcp-md5-key=secret123 ttl=default
 
mistry7
Forum Guru
Forum Guru
Posts: 1480
Joined: Tue Oct 13, 2009 11:57 am
Location: Germany

Re: v6.42rc [release candidate] is released!

Sat Feb 10, 2018 2:24 pm

Are we going to get any kind of response onto what nstreme-plus is? Please?

too secret to tell everyone!
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3296
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v6.42rc [release candidate] is released!

Sat Feb 10, 2018 3:34 pm

Are we going to get any kind of response onto what nstreme-plus is? Please?

too secret to tell everyone!

If this is correct:
nstream is a wireless protocol mikrotik proprietary.
(found using google)
Then I guess that nstreme-plus is the same as nstreme with some more funtion.
 
User avatar
rtacheny
Frequent Visitor
Frequent Visitor
Posts: 57
Joined: Sat Sep 14, 2013 7:13 pm
Location: Braham, MN USA
Contact:

Re: v6.42rc [release candidate] is released!

Sat Feb 10, 2018 5:06 pm

Are we going to get any kind of response onto what nstreme-plus is? Please?

too secret to tell everyone!

If this is correct:
nstream is a wireless protocol mikrotik proprietary.
(found using google)
Then I guess that nstreme-plus is the same as nstreme with some more funtion.
Googling nstreme is not the answer, protocols can vary vastly. nstreme and NV2 (nstreme version 2) are entirely different. I want details on what is actually different in nstreme plus and would like to know if it was developed specifically for any type of hardware (there have been many complaints with nstreme and nv2 on AC). We have abandoned mikrotik for wireless on 2.4 and 5ghz but still rely on them for some remaining 900mhz customers. I want to know if this will be applicable for us.
 
nkourtzis
Member Candidate
Member Candidate
Posts: 219
Joined: Tue Dec 11, 2012 12:56 am
Location: Greece

Re: v6.42rc [release candidate] is released!

Sat Feb 10, 2018 9:23 pm

Dear Mikrotik,

Thank you for including the option for automatic upgrade of the bootloader. Since the new version numbering scheme for routerboot was introduced, this option was the only sensible thing to include. Can you also though make it automatically perform the second -required- reboot? From the moment it is checked, it means that the user desires routerboot to be automatically upgraded when routeros is upgraded. Not performing the reboot essentially leaves the bootloader upgrade process half-finished. It makes sense to complete it by automatically rebooting the unit a second time. It go one step further, I would suggest to have both steps of the upgrade (upgrade and reboot) take place if possible before starting any other services or before the double beep. Possibly you could even introduce a special beep pattern during boot to signal that the bootloder is taking place, maybe a long then short one.

Thank you.
 
0ldman
Forum Guru
Forum Guru
Posts: 1465
Joined: Thu Jul 27, 2006 5:01 am

Re: v6.42rc [release candidate] is released!

Sat Feb 10, 2018 11:16 pm

Nstreme plus, any hints?

I'm about to update a couple of test units...
 
ste
Forum Guru
Forum Guru
Posts: 1924
Joined: Sun Feb 13, 2005 11:21 pm

Re: v6.42rc [release candidate] is released!

Sun Feb 11, 2018 9:26 am

Nstreme plus, any hints?

I'm about to update a couple of test units...
+1

We have some remaining sites with MT wireless. Forced to replace them by customer demands. Would love to do a SW upgrade to keep them running.

@MT could you please describe what nstreme plus will do better ?
 
sup5
Member
Member
Posts: 359
Joined: Sat Jul 10, 2010 12:37 am

Re: v6.42rc [release candidate] is released!

Sun Feb 11, 2018 12:23 pm

The Dude Client is broken after updating to 6.42rc24:
Please wait while updating:
"Bad http response from cloud"


Where is the download for the windows-client?

Edit:
It seems like the Dude-Client tries to fetch this URL:
https://upgrade.mikrotik.com/routeros/6 ... 42rc24.tgz
But it just throws this error message:
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>C8CAC51C5479E518</RequestId>
<HostId>
3aRnHLgJqfV4AKF81siOXhSgng8kYK1qYiDci7AL7PPOYkAmt0jMpV6AGcyVhvyLNrws/PYiJqQ=
</HostId>
</Error>
I tried a few version numbers. It seems that 6.42rc20 is the newest Dude-Client downloadable.

Mikrotik: fix this please.
Last edited by sup5 on Sun Feb 11, 2018 1:08 pm, edited 2 times in total.
 
server8
Long time Member
Long time Member
Posts: 592
Joined: Fri Apr 22, 2011 1:27 pm

Re: v6.42rc [release candidate] is released!

Sun Feb 11, 2018 12:32 pm

+1 nstreme plus info update
 
0ldman
Forum Guru
Forum Guru
Posts: 1465
Joined: Thu Jul 27, 2006 5:01 am

Re: v6.42rc [release candidate] is released!

Sun Feb 11, 2018 9:51 pm

Updated two test units, eager to tinker.

There are no new nstreme options, nothing for nv2, nada.

Where/how do we access this and what do they do?
 
Florian
Member Candidate
Member Candidate
Posts: 117
Joined: Sun Mar 13, 2016 9:45 am
Location: France

Re: v6.42rc [release candidate] is released!

Mon Feb 12, 2018 8:21 am

So, if we are under r20 and don't want to "clean flash", we're screwed and can't upgrade, right ?
 
User avatar
Smoerrebroed
Frequent Visitor
Frequent Visitor
Posts: 75
Joined: Mon Feb 12, 2018 10:21 am

Re: v6.42rc [release candidate] is released!

Mon Feb 12, 2018 10:24 am

Is it normal that installing 6.42rc24 does not correctly create a bootable system disk when used on x86 hardware? Comes up with "no OS found" or such. 6.42rc15 was just fine in that respect.

Cheers

Smoerrebroed
 
telcouk
newbie
Posts: 31
Joined: Mon Jan 08, 2018 3:50 pm

Re: v6.42rc [release candidate] is released!

Mon Feb 12, 2018 10:49 am

!) tile - improved overall system performance and stability ("/system routerboard upgrade" required);

Anyone have any details as to what this means?
 
server8
Long time Member
Long time Member
Posts: 592
Joined: Fri Apr 22, 2011 1:27 pm

Re: v6.42rc [release candidate] is released!

Mon Feb 12, 2018 12:39 pm

We have started a massive and very expensive migration to other vendor due to low wireless performance with NV2, is it possible to know something about nstreme plus?

I know it's hard for mikortik reveal own strategy but we are working not joking and if we can save money it 'll be very appreciated.

Normis please

Thank you in advance Giuseppe
 
uldis
MikroTik Support
MikroTik Support
Posts: 3446
Joined: Mon May 31, 2004 2:55 pm

Re: v6.42rc [release candidate] is released!

Mon Feb 12, 2018 1:04 pm

Nstreme-plus is almost the same Nstreme protocol but with some additional tweaks to get better compatibility with latest ARM based wireless chipset hardware that we started to release recently.
 
mistry7
Forum Guru
Forum Guru
Posts: 1480
Joined: Tue Oct 13, 2009 11:57 am
Location: Germany

Re: v6.42rc [release candidate] is released!

Mon Feb 12, 2018 7:34 pm

Nstreme-plus is almost the same Nstreme protocol but with some additional tweaks to get better compatibility with latest ARM based wireless chipset hardware that we started to release recently.
That's exactly what we feared
again only patchwork and no innovation
 
User avatar
rtacheny
Frequent Visitor
Frequent Visitor
Posts: 57
Joined: Sat Sep 14, 2013 7:13 pm
Location: Braham, MN USA
Contact:

Re: v6.42rc [release candidate] is released!

Mon Feb 12, 2018 9:27 pm

Nstreme-plus is almost the same Nstreme protocol but with some additional tweaks to get better compatibility with latest ARM based wireless chipset hardware that we started to release recently.
So no sync options or anything like that?
 
jmi2
just joined
Posts: 10
Joined: Mon Feb 05, 2018 11:41 am

Re: v6.42rc [release candidate] is released!

Mon Feb 12, 2018 9:41 pm

was this thread correct place to report viewtopic.php?f=21&t=129034&p=640649#p640649 ? (as i see neither hint nor confirmation of issue)? Should i post it elsewhere? Thank you.
 
nkourtzis
Member Candidate
Member Candidate
Posts: 219
Joined: Tue Dec 11, 2012 12:56 am
Location: Greece

Re: v6.42rc [release candidate] is released!

Mon Feb 12, 2018 9:58 pm

Nstreme-plus is almost the same Nstreme protocol but with some additional tweaks to get better compatibility with latest ARM based wireless chipset hardware that we started to release recently.
That's exactly what we feared
again only patchwork and no innovation

Mate, Mikrotik is mainly routing. Wireless is a peripheral offering, not core business for them. They do not have the horsepower to pursue both of them equally. If you want wireless, go to one of the guys that do that as their main business and then combine the best of both worlds.
 
LeoCombes
Frequent Visitor
Frequent Visitor
Posts: 78
Joined: Mon May 28, 2007 3:56 pm

Re: v6.42rc [release candidate] is released!

Tue Feb 13, 2018 6:58 pm

*) radius - increase allowed RADIUS server timeout to 60s;

To add an important reason to the too short limit problem of timeout in radius:
Successful authentications are answered immediately (in order of milliseconds if possible), but to protect the server from brute-force attacks and DOS-type attacks, radius is usually configured in order that in case of failed authentication, the response is delayed for a longer time (usually 4 or 5 seconds). In that way the attack slows down and is not effective.

For that it is important to be able to configure a "large" timeout time.
 
mistry7
Forum Guru
Forum Guru
Posts: 1480
Joined: Tue Oct 13, 2009 11:57 am
Location: Germany

Re: v6.42rc [release candidate] is released!

Tue Feb 13, 2018 7:26 pm

Nstreme-plus is almost the same Nstreme protocol but with some additional tweaks to get better compatibility with latest ARM based wireless chipset hardware that we started to release recently.
nstreme Connection with this RC ist not working on LHG ac
 
sindy
Forum Guru
Forum Guru
Posts: 10206
Joined: Mon Dec 04, 2017 9:19 pm

Re: v6.42rc [release candidate] is released!

Tue Feb 13, 2018 9:09 pm

Mate, Mikrotik is mainly routing. Wireless is a peripheral offering, not core business for them. They do not have the horsepower to pursue both of them equally. If you want wireless, go to one of the guys that do that as their main business and then combine the best of both worlds.
Hm, this is probably the reason why the wireless product line contains much more items than the wireless-less ;-) one.
 
jkarras
Member Candidate
Member Candidate
Posts: 226
Joined: Fri Sep 06, 2013 3:07 am
Location: Utah, USA

Re: v6.42rc [release candidate] is released!

Tue Feb 13, 2018 9:45 pm

*) radius - increase allowed RADIUS server timeout to 60s;

To add an important reason to the too short limit problem of timeout in radius:
Successful authentications are answered immediately (in order of milliseconds if possible), but to protect the server from brute-force attacks and DOS-type attacks, radius is usually configured in order that in case of failed authentication, the response is delayed for a longer time (usually 4 or 5 seconds). In that way the attack slows down and is not effective.

For that it is important to be able to configure a "large" timeout time.

This isn't actually true as the radius server will return either an accept or deny (if bad password) immediately. This timeout only affects no response from the radius server before it tries to send the exact same packet again. Its still very helpful when your radius server is at a remote site across a high latency link.
 
User avatar
andersonmarin
Trainer
Trainer
Posts: 22
Joined: Fri Mar 01, 2013 3:21 pm
Location: Brasil
Contact:

Re: v6.42rc [release candidate] is released!

Wed Feb 14, 2018 9:39 am

nstreme-plus ? What is it ? ;)
+ 32984920 :lol:
Nstreme-plus is almost the same Nstreme protocol but with some additional tweaks to get better compatibility with latest ARM based wireless chipset hardware started to release recently.
 
JimmyNyholm
Member Candidate
Member Candidate
Posts: 248
Joined: Mon Apr 25, 2016 2:16 am
Location: Sweden

Re: v6.42rc [release candidate] is released!

Wed Feb 14, 2018 10:25 am

*) radius - increase allowed RADIUS server timeout to 60s;

To add an important reason to the too short limit problem of timeout in radius:
Successful authentications are answered immediately (in order of milliseconds if possible), but to protect the server from brute-force attacks and DOS-type attacks, radius is usually configured in order that in case of failed authentication, the response is delayed for a longer time (usually 4 or 5 seconds). In that way the attack slows down and is not effective.

For that it is important to be able to configure a "large" timeout time.

This isn't actually true as the radius server will return either an accept or deny (if bad password) immediately. This timeout only affects no response from the radius server before it tries to send the exact same packet again. Its still very helpful when your radius server is at a remote site across a high latency link.
And you all miss upon proxied multifactor stuff where upstream servers is waiting on user action on other device. The timeout need to be high so that user have time to respond and router not destroying auth process by resending same request again and being denied due to replay attack.
Auth can be a complicated beast if you dwell down the rabbit hole.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7049
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.42rc [release candidate] is released!

Wed Feb 14, 2018 11:54 am

60s RADIUS timeout was added exactly for two factor authentication cases.
 
LeoCombes
Frequent Visitor
Frequent Visitor
Posts: 78
Joined: Mon May 28, 2007 3:56 pm

Re: v6.42rc [release candidate] is released!

Wed Feb 14, 2018 4:14 pm

*) radius - increase allowed RADIUS server timeout to 60s;

To add an important reason to the too short limit problem of timeout in radius:
Successful authentications are answered immediately (in order of milliseconds if possible), but to protect the server from brute-force attacks and DOS-type attacks, radius is usually configured in order that in case of failed authentication, the response is delayed for a longer time (usually 4 or 5 seconds). In that way the attack slows down and is not effective.

For that it is important to be able to configure a "large" timeout time.
This isn't actually true as the radius server will return either an accept or deny (if bad password) immediately. This timeout only affects no response from the radius server before it tries to send the exact same packet again. Its still very helpful when your radius server is at a remote site across a high latency link.
http://networkradius.com/doc/3.0.10/raddb/security.html

reject_delay parameter is used to delay responses, so, server will not return reject immediately if is set to 5 seconds, as I have configured and work as expected.
Accept response is in 120ms roundtrip and reject responses is in 5120ms approximately.
 
alexjhart
Member Candidate
Member Candidate
Posts: 197
Joined: Thu Jan 20, 2011 8:03 pm

Re: v6.42rc [release candidate] is released!

Wed Feb 14, 2018 4:45 pm



*) crs3xx - added initial hw-offload support for 802.3ad and balance-xor bonding
What does "initial" mean here?
Strods?
 
105547111
Member Candidate
Member Candidate
Posts: 135
Joined: Fri Jun 22, 2012 9:46 pm

Re: v6.42rc [release candidate] is released!

Wed Feb 14, 2018 10:39 pm

Is IGMP snooping fixed in rc24 or in 6.41.2?

Got yelled at last time so I've left it off for now :-)
 
NetflashTechnical
just joined
Posts: 15
Joined: Fri May 10, 2013 3:43 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 12:54 am

Is IGMP snooping fixed in rc24 or in 6.41.2?

Got yelled at last time so I've left it off for now :-)
Response to my ticket to support@ is that they plan on addressing it in 6.42 eventually, but it doesn't look like it's been touched yet
 
w0lt
Long time Member
Long time Member
Posts: 537
Joined: Wed Apr 02, 2008 2:12 pm
Location: Minnesota USA

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 1:11 am

Doesn't work correctly for me yet using a CRS-125.
 
anuser
Long time Member
Long time Member
Posts: 601
Joined: Sat Nov 29, 2014 7:27 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 10:25 am

Throughput test with laptop (Intel AC3168) + WAP AC + 6.42rc24 and internal test server:
- low download
- good upload

Image
Last edited by anuser on Thu Feb 15, 2018 1:26 pm, edited 1 time in total.
 
ste
Forum Guru
Forum Guru
Posts: 1924
Joined: Sun Feb 13, 2005 11:21 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 12:41 pm

This is a S+RJ10 plugged into CRS317 connected with 1GE to a foreign switch which is not capable of doing 10GE.
Status shows rate=10Gbps which is wrong. Connection works.

Unplugging Ethernetcable makes the port flapping. Show connected/disconnected.



[admin@G10S01] > interface ethernet monitor sfp-sfpplus1 once
;;; TRUNK ins RZ
name: sfp-sfpplus1
status: link-ok
auto-negotiation: done
rate: 10Gbps
full-duplex: yes
tx-flow-control: no
rx-flow-control: no
advertising:
link-partner-advertising:
sfp-module-present: yes
sfp-rx-loss: no
sfp-tx-fault: no
sfp-type: SFP-or-SFP+
sfp-connector-type: RJ45
sfp-link-length-copper: 1m
sfp-vendor-name: MikroTik
sfp-vendor-part-number: S+RJ10
sfp-vendor-revision: 1.0
sfp-vendor-serial: 815D03C24FA5
sfp-manufacturing-date: 17-08-28
sfp-wavelength: 1280nm
eeprom-checksum: good
eeprom: 0000: 03 04 22 00 00 00 00 00 08 00 00 00 64 00 00 00 .."..... ....d...
0010: 00 00 01 00 4d 69 6b 72 6f 54 69 6b 20 20 20 20 ....Mikr oTik
0020: 20 20 20 20 00 00 02 00 53 2b 52 4a 31 30 20 20 .... S+RJ10
0030: 20 20 20 20 20 20 20 20 31 2e 30 20 05 00 00 31 1.0 ...1
0040: 00 02 00 00 38 31 35 44 30 33 43 32 34 46 41 35 ....815D 03C24FA5
0050: 20 20 20 20 31 37 30 38 32 38 20 20 00 00 00 a6 1708 28 ....
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
 
edinorog
newbie
Posts: 25
Joined: Wed Aug 20, 2014 3:23 pm
Location: Россия

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 4:07 pm

Image

6.42rc24 :evil: ....................................... 6.42rc27 :evil: how long will this last?
 
huntermic
Member Candidate
Member Candidate
Posts: 111
Joined: Wed Oct 26, 2016 3:42 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 4:25 pm

Damn, i will be pissed if i get the same netinstall party going again.
Had the same issue when updating from 6.42rc18 -> 6.42.rc24 and it cost me a lot of time. that was on a RB3011UiAS-RM



6.42rc24 :evil: ....................................... 6.42rc27 :evil: how long will this last?
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7049
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 4:54 pm

As it was mentioned several times before in this topic. Upgrade happens on old version
6.42rc17 - 6.42rc24 are bad versions, so if you want to upgrade from these versions, use netinstall from the beginning.
 
huntermic
Member Candidate
Member Candidate
Posts: 111
Joined: Wed Oct 26, 2016 3:42 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 4:59 pm

I read somewhere that 6.42rc24 would not be a version with known issues, so that has changed now?

-------------
Main part of upgrade process happens on old version.

For example, rc21 -> rc23. If upgrade fails, then it is caused by rc21 version. As you can see in changelog we are still working on upgrade improvements. At the moment latest fixes are included in rc23. You can test upgrade improvements when upgrading from rc23 to, for example, rc24.

At the moment we are not aware about any problems with upgrade starting from 6.42rc23 version.

In future, if you experience problems with upgrade, then remember to mention from which precise RouterOS version and to which you made an upgrade.
-------------

As it was mentioned several times before in this topic. Upgrade happens on old version
6.42rc17 - 6.42rc24 are bad versions, so if you want to upgrade from these versions, use netinstall from the beginning.
 
edinorog
newbie
Posts: 25
Joined: Wed Aug 20, 2014 3:23 pm
Location: Россия

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 5:08 pm

As it was mentioned several times before in this topic. Upgrade happens on old version
6.42rc17 - 6.42rc24 are bad versions, so if you want to upgrade from these versions, use netinstall from the beginning.

I'm wildly sorry! It's now constantly necessary so to install RC via netinstall?
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7049
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 5:09 pm

No, only if older version was 6.42rc17 - 6.42rc24
 
edinorog
newbie
Posts: 25
Joined: Wed Aug 20, 2014 3:23 pm
Location: Россия

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 5:14 pm

No, only if older version was 6.42rc17 - 6.42rc24
Then why when upgrading from version 6.42rc20 to version 6.42rc27 the router again ceased to give signs of life?
 
huntermic
Member Candidate
Member Candidate
Posts: 111
Joined: Wed Oct 26, 2016 3:42 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 5:16 pm

And we should just believe you when you say it all works perfectly again starting from the untested ( by users ) 6.42.rc27 version?
No, only if older version was 6.42rc17 - 6.42rc24
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7049
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 5:18 pm

Because you are upgrading from bad version. upgrade from any of my previously mentioned rc versions most likely will fail.
 
huntermic
Member Candidate
Member Candidate
Posts: 111
Joined: Wed Oct 26, 2016 3:42 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 5:18 pm

6.42rc20 falls within the range of faulty firmwares ( 6.42rc17 - 6.42rc24 )
No, only if older version was 6.42rc17 - 6.42rc24
Then why when upgrading from version 6.42rc20 to version 6.42rc27 the router again ceased to give signs of life?
 
edinorog
newbie
Posts: 25
Joined: Wed Aug 20, 2014 3:23 pm
Location: Россия

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 5:24 pm

Because you are upgrading from bad version. upgrade from any of my previously mentioned rc versions most likely will fail.

If I understood you correctly .... then even when the release will be released ... will it be updated to it from the "bad" version it does not work out? I understand the way out 2?
1. Rolls back to the RC version earlier than 17 and is already updated to 27
2. Update the version via netinstall
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7049
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 5:35 pm

And we should just believe you when you say it all works perfectly again starting from the untested ( by users ) 6.42.rc27 version?
You don't have to believe me,but upgrade from rc26 to rc27 works, so there is very big chance that upgrade from rc27 will also work :D It is still an RC version anyway so anything can happen.
I do not see the reason for complains, RC was always test version for those who are willing to test it on routers in test environment where netinstalling router is not a problem.
If you put test version on production router or only remotely reachable routers then that is on you.

@edinorog Yes, if you upgrade from bad version upgrade may fail even if you upgrade to final 6.42.
 
User avatar
null31
Member Candidate
Member Candidate
Posts: 183
Joined: Fri Dec 23, 2016 6:07 pm
Location: Brazil

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 5:58 pm

Successful upgrade on hAP ac lite and RB951Ui-2HnD, from rc24 to rc27. And hEX r2 from rc15 to rc27.
Finally is available the band 5Ghz n/ac. :)

CHR's VDI image is working now from fresh install.

Can be added the channel width 40/80mhz?
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7049
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 6:23 pm

What's new in 6.42rc27 (2018-Feb-14 11:53):

*) bridge - fixed false MAC address learning on hAP ac2, cAP ac;
*) bridge - fixed incorrect "fast-forward" enabling when ports were switched;
*) bridge - hide options for disabled bridge features in CLI;
*) capsman - added "allow-signal-out-off-range" option for Access List entries (CLI only);
*) capsman - added support for "interface-list" in Access List entries (CLI only);
*) capsman - added support for "interface-list" in datapath (CLI only);
*) capsman - log "signal-strength" when successfully connected to AP;
*) chr - fixed fresh installations (including ISO images) (introduced in v6.42rc24);
*) kidcontrol - initial work on "/ip kid-control" feature;
*) lte - added initial support for SIM7600 LTE modem interface;
*) smb - improved NetBIOS name handling and stability;
*) snmp - added "/interface w60g print oid";
*) tile - fixed occasional reporting of bogus voltage;
*) upgrade - improved RouterOS upgrade process and restrict upgrade from RouterOS older than v5.16;
*) wireless - added "realm-raw" setting for "/interface wireless interworking-profiles" (CLI only);
*) wireless - added initial support for "nstreme-plus";
*) wireless - added support for "band=5ghz-n/ac" (CLI only);
*) wireless - added support for "interface-list" in Access List entries (CLI only);
*) wireless - fixed long "scan-list" entries not working for ARM based wireless interfaces;
 
0ldman
Forum Guru
Forum Guru
Posts: 1465
Joined: Thu Jul 27, 2006 5:01 am

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 6:36 pm

Throughput test with laptop (Intel AC3168) + WAP AC + 6.42rc24 and internal test server:
- low download
- good upload

Image
Just a heads up, Mikrotik usually has some issue with Intel cards, they generally get them fixed, but Intel's drivers are garbage.

If you can swap from Intel wireless you'll be happier for it. I've done side by side testing with more than just MT APs, every OS from 98 to 10, several versions of Linux. Intel's hardware is sound. Their drivers controlling that hardware are garbage. The only time I really was happy with my Intel cards was when they released the source and someone else made a 2200bg driver for Linux. I don't know if the driver's source is available any more.
 
huntermic
Member Candidate
Member Candidate
Posts: 111
Joined: Wed Oct 26, 2016 3:42 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 7:12 pm

Why isn't there a test that you can run as developers to see wether you can use a version to upgrade to a version with a higher number? Should be a basic test that prevents us from heaving these issues.
And we should just believe you when you say it all works perfectly again starting from the untested ( by users ) 6.42.rc27 version?
You don't have to believe me,but upgrade from rc26 to rc27 works, so there is very big chance that upgrade from rc27 will also work :D It is still an RC version anyway so anything can happen.
I do not see the reason for complains, RC was always test version for those who are willing to test it on routers in test environment where netinstalling router is not a problem.
If you put test version on production router or only remotely reachable routers then that is on you.

@edinorog Yes, if you upgrade from bad version upgrade may fail even if you upgrade to final 6.42.
 
User avatar
null31
Member Candidate
Member Candidate
Posts: 183
Joined: Fri Dec 23, 2016 6:07 pm
Location: Brazil

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 7:38 pm

Why isn't there a test that you can run as developers to see wether you can use a version to upgrade to a version with a higher number? Should be a basic test that prevents us from heaving these issues.
Developer doing a debug? Well, they know how to don't the wrong things passively.
The users are the best debuggers, they can do something that developers doesn't think.
 
biatche
Member Candidate
Member Candidate
Posts: 128
Joined: Tue Oct 13, 2015 6:50 am

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 8:41 pm

*) capsman - added "allow-signal-out-off-range" option for Access List entries (CLI only);
thanks for adding that... but i hope the spelling within winbox is allow-signal-out-of-range
 
sid5632
Long time Member
Long time Member
Posts: 554
Joined: Fri Feb 17, 2017 6:05 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 8:57 pm

What's new in 6.42rc27 (2018-Feb-14 11:53):
Where is the Dude client? Again?
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 9:17 pm

Please remember what we have been telling from the first public rc release - rc versions are provided for MikroTik enthusiasts who are ready to Netinstall router if necessary. Versions are tested on few routers and released right away. If you are experiencing issues with an upgrade and do not want to Netinstall devices any more, then you should wait for a final 6.42 release.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 9:34 pm

Is it safe to make a backup of a CHR running 6.42rc20 then install 6.42rc27 using OVA and then restore the backup?
Or will that re-introduce the problem?
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 9:55 pm

Issue is not with the device or configuration, it is the upgrade process itself. We recommend that you make export file, try to upgrade (if you had problematic rc installed), if fail, then Netinstall device or make a new installation (CHR, VM) and import configuration back.

Unfortunately sometimes you have to make sacrifices in order to get a better results. This time sacrifice is a batch of few bad rc versions in order to make upgrade process much more reliable.

Thank you for those who are testing rc versions and reporting results back to support. We really appreciate that and other RouterOS users also have much less problems when full releases come out.
 
User avatar
TomjNorthIdaho
Forum Guru
Forum Guru
Posts: 1493
Joined: Mon Oct 04, 2010 11:25 pm
Location: North Idaho
Contact:

Re: v6.42rc [release candidate] is released!

Thu Feb 15, 2018 11:18 pm

Re: What's new in 6.42rc27 (2018-Feb-14 11:53):

hmmm , would somebody shed some light/information on the following:
*) chr - fixed fresh installations (including ISO images) (introduced in v6.42rc24);
*) wireless - added "realm-raw" setting for "/interface wireless interworking-profiles" (CLI only);
*) wireless - added initial support for "nstreme-plus";
*) wireless - fixed long "scan-list" entries not working for ARM based wireless interfaces;

North Idaho Tom Jones
 
105547111
Member Candidate
Member Candidate
Posts: 135
Joined: Fri Jun 22, 2012 9:46 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 16, 2018 12:56 am

Please remember what we have been telling from the first public rc release - rc versions are provided for MikroTik enthusiasts who are ready to Netinstall router if necessary. Versions are tested on few routers and released right away. If you are experiencing issues with an upgrade and do not want to Netinstall devices any more, then you should wait for a final 6.42 release.
Okay this is indeed perfectly true, but why do support insist on a 6.41.1 and 6.41.2 tickets running RC on production routers or else the fix will have to wait until 6.42 final?
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Fri Feb 16, 2018 6:40 am

105547111 - Sometimes we can make potential fix for the problem based on supout files. After that fix must be tested (if we can not reproduce the same problem locally). We are not forcing anyone to test rc versions. These fixes are introduced with an option - if you do not mind testing the fix, then try out rc version. Fixes are not included in 6.x.y versions (without confirmation that fix has actually helped) so you would have as much reliable release as possible.
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Fri Feb 16, 2018 3:23 pm

What's new in 6.42rc28 (2018-Feb-16 07:02):

*) chr - added "virtio-scsi" driver on KVM installations;
*) chr - added support for Hyper-V ballooning;
*) chr - added support for Hyper-V guest quiescing;
*) chr - added support for Hyper-V host-guest file transfer;
*) chr - added support for Hyper-V integration services;
*) chr - added support for Hyper-V static IP injection;
*) chr - added support for NIC hot-plug on VMware and Xen installations;
*) chr - fixed additional disk detaching on Xen installations;
*) ipsec - properly detect interface for "mode-config" client IP address assignment;
*) gps - improved NMEA sentence handling;
*) r11e-lte - improved LTE connection initialization process;

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 expected or after crash.
 
User avatar
indnti
Frequent Visitor
Frequent Visitor
Posts: 86
Joined: Thu Nov 09, 2006 11:53 am

Re: v6.42rc [release candidate] is released!

Fri Feb 16, 2018 3:47 pm

As it was mentioned several times before in this topic. Upgrade happens on old version
6.42rc17 - 6.42rc24 are bad versions, so if you want to upgrade from these versions, use netinstall from the beginning.

Will there be no fix that is ist possible to upgrade from one of this versions?
Or what a bout a downgrade e.g. from 6.42.rc20 to 6.41.2 ?
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26351
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Fri Feb 16, 2018 3:51 pm

As it was mentioned several times before in this topic. Upgrade happens on old version
6.42rc17 - 6.42rc24 are bad versions, so if you want to upgrade from these versions, use netinstall from the beginning.

Will there be no fix that is ist possible to upgrade from one of this versions?
Or what a bout a downgrade e.g. from 6.42.rc20 to 6.41.2 ?
Answered many times before! The old version is the one that performs upgrade. We can't fix a released and installed version.
 
User avatar
ziegenberg
Frequent Visitor
Frequent Visitor
Posts: 53
Joined: Thu Mar 07, 2013 11:14 am
Location: Vienna
Contact:

Re: v6.42rc [release candidate] is released!

Fri Feb 16, 2018 4:45 pm

Well!
What's new in 6.42rc28 (2018-Feb-16 07:02):

*) chr - added "virtio-scsi" driver on KVM installations;
*) chr - added support for Hyper-V ballooning;
*) chr - added support for Hyper-V guest quiescing;
*) chr - added support for Hyper-V host-guest file transfer;
*) chr - added support for Hyper-V integration services;
*) chr - added support for Hyper-V static IP injection;
*) chr - added support for NIC hot-plug on VMware and Xen installations;
Thank you very, very much!!
 
sindy
Forum Guru
Forum Guru
Posts: 10206
Joined: Mon Dec 04, 2017 9:19 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 16, 2018 4:46 pm

As it was mentioned several times before in this topic. Upgrade happens on old version

Will there be no fix that it is possible to upgrade from one of this versions?
We can't fix a released and installed version.
Well, you definitely cannot, but I assume it would be technically possible to provide a dedicated application (as an npk file) which would both perform the configuration upgrade and then install the software upgrade instead of the running version. I understand that this would be way too much effort to spend on every single RC version just to save the adrenaline addicts who use RC for machines they cannot easily reach for netinstall, but I had a case of losing conifguration when upgrading from 6.41 stable to 6.42rc9. Netinstall wasn't necessary in this case, but I would have been very disappointed if that would have happened to me when upgrading the 6.41 to 6.41.2 1500 km crow line away on the same model (which luckily didn't happen).

And don't be surprised that it is hard for people to get the concept - the upgrade process of every other vendor I've met works on the principle that the new software knows how the configuration structure looked like in the previous versions and converts it into its own format if necessary. In your case, with just a little bit of exaggeration, each version must be a future-teller and expect what any of the future versions will require. A much more interesting challenge to deal with, I guess. (I actually assume that the truth is somewhere in between and that the leaving version has to export its configuration into some generic format which the coming version then converts into whatever it needs, and that this export process is where the bugs are, but the more it should be possible to create a "postfix" application which would export the running configuration into that generic format instead of the leaving version itself, maybe into another file which the coming version would prefer over the one created by the leaving application if it would find it).
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7049
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.42rc [release candidate] is released!

Fri Feb 16, 2018 5:17 pm

I think you are mixing two different things. Upgrade failure had nothing to do with configuration. Software installation process was redesigned, which led to "bricked" (unable to boot) routers in those RC versions.
 
sindy
Forum Guru
Forum Guru
Posts: 10206
Joined: Mon Dec 04, 2017 9:19 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 16, 2018 5:39 pm

I think you are mixing two different things. Upgrade failure had nothing to do with configuration. Software installation process was redesigned, which led to "bricked" (unable to boot) routers in those RC versions.
Apologies, this is probably because my imagination was not wild enough to admit that the task of downloading a binary and applying it could go so much wrong :-) So I've assumed that the configuration conversion must be the culprit.

Do I read you right that a reboot with just a single new .npk module (like hotspot) would brick the machine as well if it runs a "bad" RC version?

Regardless the above, when the machine is far/high/deep enough to be physically connected to, it is not a big difference whether you need to netinstall it or "only" restore the default configuration and then modify or replace it.
 
owsugde
newbie
Posts: 39
Joined: Thu Oct 06, 2016 5:01 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 16, 2018 7:10 pm

6.42rc28 wrecked my CHR on libvirtd / Qemu KVM setup. Virtio network interfaces (or any interfaces at all) aren't recognized anymore.

Do not install 6.42rc28 on KVM CHR!

Still trying to salvage this thing, will write more later...

Add: Just managed to get 6.41.2 installed. Had to get the stable package file to the guest first somehow, which if you don't have any way of officially interacting with the guest on the host (interfaces are all down) is quite the ordeal:
  • mount raw image with manually calculated offset
  • put file in right place in Linux file system underlying RouterOS
  • run guest, qemu console to it, login, do /system package downgrade
I can only repeat: Don't install rc28 on QEMU/KVM!!
Last edited by owsugde on Fri Feb 16, 2018 9:12 pm, edited 3 times in total.
 
drbunsen
newbie
Posts: 40
Joined: Fri Apr 29, 2016 7:24 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 16, 2018 8:40 pm

CHR on rc28:
- disabled package dude
- disabled package wireless
- disabled package hotspot
- enabled package ipv6

After reload, packages show correctly to be disabled/enabled, but in WebFig CapsMan, Wireless and Dude menus are still there and IPv6 one is missing. On the terminal IPv6 is there and the others are gone.

Edit: Not sure what happened, but after configuring some more stuff WebFig now shows IPv6 and the disabled ones are gone. Maybe it was a browser issue as I also closed the Tab completely in between?
Last edited by drbunsen on Fri Feb 16, 2018 10:23 pm, edited 1 time in total.
 
105547111
Member Candidate
Member Candidate
Posts: 135
Joined: Fri Jun 22, 2012 9:46 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 16, 2018 9:14 pm

6.42rc28 wrecked my CHR on libvirtd / Qemu KVM setup. Virtio network interfaces aren't recognized anymore.

Do not install 6.42rc28 on KVM CHR!

Still trying to salvage this thing, will write more later...
:-( Oh no... I also had a CHR running same RC in qemu/kvm and bang wouldn't even boot. Quickest fix was I had backup image of the CHR and always download current backups. Copied over current image and then uploaded the backup and restored, since its the same CHR.

Now anytime I take a VM down I backup the image :-)
 
UpRunTech
Member Candidate
Member Candidate
Posts: 212
Joined: Fri Jul 27, 2012 12:11 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 16, 2018 10:12 pm

*) wireless - fixed incompatibility with macOS clients


What was fixed or improved here? Will this also improve IOS clients? I have some sites with a lot of Macbook Airs and iPads so am keen to know,
 
Pea
Member Candidate
Member Candidate
Posts: 233
Joined: Fri Jul 17, 2015 11:07 pm
Location: Czech

Re: v6.42rc [release candidate] is released!

Fri Feb 16, 2018 10:50 pm

Already answered in this topic:
viewtopic.php?f=21&t=129034&start=150#p640819
 
UpRunTech
Member Candidate
Member Candidate
Posts: 212
Joined: Fri Jul 27, 2012 12:11 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 16, 2018 11:33 pm

Derp, well that's good. I am definitely mangling packets with prio. from high 3 DSCP bits to make sure Airplay works as well as possible with WMM. Still I wonder, will this help IOS units too or do they not have this problem? When did the bug get introduced or was it always there?
 
anuser
Long time Member
Long time Member
Posts: 601
Joined: Sat Nov 29, 2014 7:27 pm

Re: v6.42rc [release candidate] is released!

Sat Feb 17, 2018 1:45 am

What's new in 6.42rc27 (2018-Feb-14 11:53):
*) wireless - added support for "band=5ghz-n/ac" (CLI only);
1. setting this one within CAPSMAN would be nice to have.
2. What will be the difference between "band=5ghz-a/n/ac" and "5ghz-n/ac"? Some kind of old compatible mode on the first one that will be disabled on the second and therefore results in higher performance?
 
User avatar
null31
Member Candidate
Member Candidate
Posts: 183
Joined: Fri Dec 23, 2016 6:07 pm
Location: Brazil

Re: v6.42rc [release candidate] is released!

Sat Feb 17, 2018 1:51 am

2. What will be the difference between "band=5ghz-a/n/ac" and "5ghz-n/ac"? Some kind of old compatible mode on the first one that will be disabled on the second and therefore results in higher performance?
It's like the 2ghz-g/n, where is disabled the 802.11b.
 
ckleea
Frequent Visitor
Frequent Visitor
Posts: 62
Joined: Sun Apr 21, 2013 12:19 pm

Re: v6.42rc [release candidate] is released!

Sat Feb 17, 2018 2:28 am

Is it ok to upgrade from 6.42rc3 to 6.42rc28?

I tried to upgrade from v21 to v24 and it caused by x86 routerOS fail to have connection. I have used sometimes to restore the older working version. The one I got at home was rc3.
 
biatche
Member Candidate
Member Candidate
Posts: 128
Joined: Tue Oct 13, 2015 6:50 am

Re: v6.42rc [release candidate] is released!

Sat Feb 17, 2018 6:24 am

*) wireless - fixed incompatibility with macOS clients
can mikortik tell us if this is (presumably) implied for capsman as well?
 
biatche
Member Candidate
Member Candidate
Posts: 128
Joined: Tue Oct 13, 2015 6:50 am

Re: v6.42rc [release candidate] is released!

Sat Feb 17, 2018 6:26 am

What's new in 6.42rc27 (2018-Feb-14 11:53):
*) wireless - added support for "band=5ghz-n/ac" (CLI only);
1. setting this one within CAPSMAN would be nice to have.
2. What will be the difference between "band=5ghz-a/n/ac" and "5ghz-n/ac"? Some kind of old compatible mode on the first one that will be disabled on the second and therefore results in higher performance?
yes mikrotik, please tell us if disabling an old band mode results in an improvement. dont make me create a new email ticket for every question
 
User avatar
Alessio Garavano
Member
Member
Posts: 306
Joined: Sat May 29, 2004 12:49 am
Location: Corrientes, Argentina
Contact:

Re: v6.42rc [release candidate] is released!

Sat Feb 17, 2018 6:52 am

Hi guys, it would be great if you allow to select, within each update channel, 5 or 6 previous versions, in order to update the RC versions correctly and correlatively.
Or make a downgrade directly to the previous version that we liked or better worked for us.

Thanks and regards,
 
WireDick
just joined
Posts: 5
Joined: Sun Dec 10, 2017 3:26 pm

Re: v6.42rc [release candidate] is released!

Sat Feb 17, 2018 2:27 pm

Bricked RB3011UiAS-RM by updating from rc20 To rc27.

LCD shows always "starting services"...

Netinstall wont work anymore... LCD shows ether Boot but Router will not apear in netinstall GUI. Troubleshoot this with other mikrotik products they imedatly apear on the GUI at the same win7 machine with same settings and cable/port...

don't update from any RC!!! it will brick the device.
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v6.42rc [release candidate] is released!

Sat Feb 17, 2018 2:36 pm

CPU hog issue is still not fixed in rc28
(Ticket#2018010522007579)

Image
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Sun Feb 18, 2018 12:25 am

I had a CHR that was originally installed on VMware ESXi some versions ago when only the bare disk image was available.
(using the trick of converting the image to SCSI)
It initially had ether1 connected to a LAN network (which has access to internet via another router), later ether2 was added
directly connected to internet, and configured in RouterOS. It had Dude installed but not enabled at this time.

As it was effectively stuck at 6.42rc20 because of the update bug, I exported the config and the dude database and created a
new VM from the 6.42rc28 OVA file. I connected ether1 to the LAN and added a second network interface to the VM, again
connected to internet as before.

However, whatever I try, RouterOS sees the LAN interface as ether2 and the internet interface as ether1. So what is called
network interface 1 in ESXi is ether2 in RouterOS.
Even when I deleted the second network interface and reset the configuration, seeing that LAN is ether1 and everything is correct,
as soon as I added the extra interface the names were swapped again.

I gave in and edited my exported config to match the swapped ether1 and ether2 and everything now works as before,
but what is going on here? it is confusing and inconvenient.
 
User avatar
null31
Member Candidate
Member Candidate
Posts: 183
Joined: Fri Dec 23, 2016 6:07 pm
Location: Brazil

Re: v6.42rc [release candidate] is released!

Sun Feb 18, 2018 4:11 am

However, whatever I try, RouterOS sees the LAN interface as ether2 and the internet interface as ether1. So what is called
network interface 1 in ESXi is ether2 in RouterOS.
Even when I deleted the second network interface and reset the configuration, seeing that LAN is ether1 and everything is correct,
as soon as I added the extra interface the names were swapped again.
The same occurs in VirtualBox since rc23 (I saw this after the upgrade from rc20 to rc23).

I configured a fresh CHR in rc27, on first try, swapped the interfaces. On second try, was disabled the NIC #2 and I did a MAC reinitialize in both interfaces. Booted with one interface and I added a new IP to ether1 and then was shutdown. Was enabled NIC #2 and booted, then the problem stopped.
I upgraded to rc28 and no problem with swapped interfaces.

The interfaces that I use in VBox are "Intel PRO/1000 MT Desktop", NIC #1 as bridged and NIC #2 as NAT Network.
 
User avatar
indnti
Frequent Visitor
Frequent Visitor
Posts: 86
Joined: Thu Nov 09, 2006 11:53 am

Re: v6.42rc [release candidate] is released!

Sun Feb 18, 2018 11:17 pm

Answered many times before! The old version is the one that performs upgrade. We can't fix a released and installed version.

If you bring out a version that *bricks* hardware you must consider that it will not happen. maybe a special intermediate version to repair version rc20-24. It can not be true that one be forced to use rc20 till the end of lifetime of that hardware!
 
User avatar
ziegenberg
Frequent Visitor
Frequent Visitor
Posts: 53
Joined: Thu Mar 07, 2013 11:14 am
Location: Vienna
Contact:

Re: v6.42rc [release candidate] is released!

Mon Feb 19, 2018 2:06 am

Hello!
If you bring out a version that *bricks* hardware you must consider that it will not happen. maybe a special intermediate version to repair version rc20-24. It can not be true that one be forced to use rc20 till the end of lifetime of that hardware!
Well, RC Versions are not meant to be production ready versions. So expect them to break stuff. And because of that, only use them in a lab or test environment, where you are happy to do netinstall if things break.

PS: I still advocate that MikroTik changes the name of the "release candidate" version to "beta", "development" or "unstable" version. Just to be crystal clear about it's purpose and for the sake of customer happiness.
 
kasparskr
MikroTik Support
MikroTik Support
Posts: 139
Joined: Mon Jul 27, 2015 11:46 am

Re: v6.42rc [release candidate] is released!

Mon Feb 19, 2018 10:17 am

Could you please send the supout file to support, we would like to take a look at it.

Which ESXi version are you using?
I had a CHR that was originally installed on VMware ESXi some versions ago when only the bare disk image was available.
(using the trick of converting the image to SCSI)
It initially had ether1 connected to a LAN network (which has access to internet via another router), later ether2 was added
directly connected to internet, and configured in RouterOS. It had Dude installed but not enabled at this time.

As it was effectively stuck at 6.42rc20 because of the update bug, I exported the config and the dude database and created a
new VM from the 6.42rc28 OVA file. I connected ether1 to the LAN and added a second network interface to the VM, again
connected to internet as before.

However, whatever I try, RouterOS sees the LAN interface as ether2 and the internet interface as ether1. So what is called
network interface 1 in ESXi is ether2 in RouterOS.
Even when I deleted the second network interface and reset the configuration, seeing that LAN is ether1 and everything is correct,
as soon as I added the extra interface the names were swapped again.

I gave in and edited my exported config to match the swapped ether1 and ether2 and everything now works as before,
but what is going on here? it is confusing and inconvenient.
 
kasparskr
MikroTik Support
MikroTik Support
Posts: 139
Joined: Mon Jul 27, 2015 11:46 am

Re: v6.42rc [release candidate] is released!

Mon Feb 19, 2018 10:21 am

Could you please send us to support the supout file, we would like to take a look.

Also, please explain in more detail what exactly did you do: did you upgrade from an earlier rc? Or from current version? From which?

Thanks.
6.42rc28 wrecked my CHR on libvirtd / Qemu KVM setup. Virtio network interfaces (or any interfaces at all) aren't recognized anymore.

Do not install 6.42rc28 on KVM CHR!

Still trying to salvage this thing, will write more later...

Add: Just managed to get 6.41.2 installed. Had to get the stable package file to the guest first somehow, which if you don't have any way of officially interacting with the guest on the host (interfaces are all down) is quite the ordeal:
  • mount raw image with manually calculated offset
  • put file in right place in Linux file system underlying RouterOS
  • run guest, qemu console to it, login, do /system package downgrade
I can only repeat: Don't install rc28 on QEMU/KVM!!
 
ste
Forum Guru
Forum Guru
Posts: 1924
Joined: Sun Feb 13, 2005 11:21 pm

Re: v6.42rc [release candidate] is released!

Mon Feb 19, 2018 10:50 am

Hello!
If you bring out a version that *bricks* hardware you must consider that it will not happen. maybe a special intermediate version to repair version rc20-24. It can not be true that one be forced to use rc20 till the end of lifetime of that hardware!
Well, RC Versions are not meant to be production ready versions. So expect them to break stuff. And because of that, only use them in a lab or test environment, where you are happy to do netinstall if things break.

PS: I still advocate that MikroTik changes the name of the "release candidate" version to "beta", "development" or "unstable" version. Just to be crystal clear about it's purpose and for the sake of customer happiness.
Yes. "Release Candidate" normaly is something that is expected to be near production quality:
https://en.wikipedia.org/wiki/Software_ ... _candidate
And at least CRS317-1G-16S+RM needs the rc to work. And there is no hint CRS317-1G-16S+RM is a beta product.

So please MT increase your SW Development Quality control to protect your customers from bad experience.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Mon Feb 19, 2018 11:29 am

I encountered another problem in my "fresh 6.42rc28 install then import old config" that I forgot to mention above:
I am using the serial port on this CHR (configured to map to the hardware serial port in the VMware ESXi config) to
connect to the serial port of a CCR router at the same site. This is an emergency access in case there is some
error in the CCR config. (the CHR is on a bridge in the CCR so it will not always be useful, but one can always try)

Well, for that config in the previous version there was this:
/port
set 0 baud-rate=115200
On the new version this config is refused with "cannot set speed because port is in use".
(and the import stops there! that is another issue that should be fixed: when such an error is encountered when
importing a config, the import should just go on with the next step. this kind of problem makes it impossible to
do a /system reset-configuration no-defaults=yes run-after-reset=scriptname because almost always there is some
minor hiccup like this and you are left with an unconfigured router)

When examining the situation I found it is now required to go to /system console and disable the console on the
serial port. After doing that, it is again possible to set the serial port speed.

However, when looking in the /export after that, this command:
/system console
set [ find ] disabled=yes
appears way down in the /export and the /port (same as above) still appears near the top.
So importing this config on a freshly reset router will still fail!
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7049
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.42rc [release candidate] is released!

Mon Feb 19, 2018 12:19 pm

It can not be true that one be forced to use rc20 till the end of lifetime of that hardware!
You are not forced to use rc20. Use netinstall to install version.
 
User avatar
indnti
Frequent Visitor
Frequent Visitor
Posts: 86
Joined: Thu Nov 09, 2006 11:53 am

Re: v6.42rc [release candidate] is released!

Mon Feb 19, 2018 6:06 pm

It can not be true that one be forced to use rc20 till the end of lifetime of that hardware!
You are not forced to use rc20. Use netinstall to install version.
What about that experience:
Bricked RB3011UiAS-RM by updating from rc20 To rc27.
LCD shows always "starting services"...
Netinstall wont work anymore... LCD shows ether Boot but Router will not apear in netinstall GUI. Troubleshoot this with other mikrotik products they imedatly apear on the GUI at the same win7 machine with same settings and cable/port...
don't update from any RC!!! it will brick the device.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7049
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.42rc [release candidate] is released!

Mon Feb 19, 2018 6:12 pm

If you use netinstall to install newer version then there will be no problems. It was already mentioned before several times.
 
timoid
newbie
Posts: 39
Joined: Tue Jan 01, 2008 8:20 am

Re: v6.42rc [release candidate] is released!

Tue Feb 20, 2018 2:10 am

rc28 broken for chr+esxi?

using vmxnet3 drivers, two interfaces becomes one and the one interface that's there has a mac of all zeros.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Tue Feb 20, 2018 11:12 am

rc28 broken for chr+esxi?

using vmxnet3 drivers, two interfaces becomes one and the one interface that's there has a mac of all zeros.
I have it working on ESXi but see above for an issue I have (the sequence of the ESXi interfaces is not the same as the ether#)

Maybe you have upgraded from a version around 6.42rc20? Then, this is indeed the problem that you will have.
You will need to re-install from the OVA or image!
 
tigro11
Frequent Visitor
Frequent Visitor
Posts: 87
Joined: Tue Feb 20, 2018 12:31 am

Re: v6.42rc [release candidate] is released!

Tue Feb 20, 2018 3:28 pm

hi guys, on my rb750Gr3 with firmware 6.42rc28 I wanted to mount a hotspot for a job. I can not install the user-manager package.
Are there any solutions?
thank you all

Valerio
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Tue Feb 20, 2018 3:31 pm

hi guys, on my rb750Gr3 with firmware 6.42rc28 I wanted to mount a hotspot for a job. I can not install the user-manager package.
Are there any solutions?
No. There is no usermanager for this router, also not for stable version.
It is unclear why this is, e.g. there is a dude (network monitoring) package for this router, so the smallish (low-end) type should not be the reason.
Anyway, you need another router type or use an external RADIUS server e.g. a Raspberry Pi with freeradius.
(which provides a lot more functionality than usermanager anyway, and you could use it to host a local webpage too)
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7049
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.42rc [release candidate] is released!

Tue Feb 20, 2018 3:36 pm

Yes, there is 6.42rc changelog:
*) userman - added support for ARM and MMIPS platform;

Download MMIPS extra packages, there will be userman package in archive.
 
tigro11
Frequent Visitor
Frequent Visitor
Posts: 87
Joined: Tue Feb 20, 2018 12:31 am

Re: v6.42rc [release candidate] is released!

Tue Feb 20, 2018 4:07 pm

in the zip file is not present in the package, or have changed package name.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7049
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.42rc [release candidate] is released!

Tue Feb 20, 2018 4:25 pm

um-snap.png
You do not have the required permissions to view the files attached to this post.
 
tigro11
Frequent Visitor
Frequent Visitor
Posts: 87
Joined: Tue Feb 20, 2018 12:31 am

Re: v6.42rc [release candidate] is released!

Tue Feb 20, 2018 4:29 pm

it is only present on the beta version.
I tried to install it, but it does not install.
I have also installed the beta firmware but do not install lost
 
tigro11
Frequent Visitor
Frequent Visitor
Posts: 87
Joined: Tue Feb 20, 2018 12:31 am

Re: v6.42rc [release candidate] is released!

Tue Feb 20, 2018 7:17 pm

I see that the previous posts have been deleted.
Returning to the question, it turns out to you that the package is not installed?
is this a problem already reported?
thank you
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.42rc [release candidate] is released!

Tue Feb 20, 2018 9:30 pm

Why it doesn't install? What's in Log after reboot? We're not telepathists...
 
kez
newbie
Posts: 40
Joined: Tue Jul 05, 2005 4:13 am

Re: v6.42rc [release candidate] is released!

Tue Feb 20, 2018 9:53 pm

[removed]
Last edited by kez on Fri Feb 23, 2018 8:40 am, edited 1 time in total.
 
tigro11
Frequent Visitor
Frequent Visitor
Posts: 87
Joined: Tue Feb 20, 2018 12:31 am

Re: v6.42rc [release candidate] is released!

Tue Feb 20, 2018 10:42 pm

Why it doesn't install? What's in Log after reboot? We're not telepathists...
then, after doing a reset and installing version 6.41.2 I tried to reinstall the package user-manager-6.42rc20-mmips.npk but nothing to do. after reboot the package is not installed

now he is continuously restarting by making a beep
Last edited by tigro11 on Tue Feb 20, 2018 10:53 pm, edited 1 time in total.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Tue Feb 20, 2018 10:46 pm

then, after doing a reset and installing version 6.41.2 I tried to reinstall the package user-manager-6.42rc20-mmips.npk but nothing to do. after reboot the package is not installed
That is normal! You can ONLY install the same version!
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Tue Feb 20, 2018 10:47 pm

I see that the previous posts have been deleted.
That is a pity indeed. It looks like the forum database has crashed and a backup has been loaded.
 
tigro11
Frequent Visitor
Frequent Visitor
Posts: 87
Joined: Tue Feb 20, 2018 12:31 am

Re: v6.42rc [release candidate] is released!

Tue Feb 20, 2018 11:12 pm

I tried to reset it, but it keeps rebooting with a beep at every reboot. How can I rewrite the firmware?
thank you
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Wed Feb 21, 2018 7:47 am

What's new in 6.42rc30 (2018-Feb-20 10:44):

*) console - improved console stability after it has not been used for a long time;
*) filesystem - implemented additional system storage maintenance checks on ARM CPU based devices;
*) filesystem - improved error correcting process on RB1100AHx4 storage;
*) gps - added GPS port support for Quectel EC25-E modem when used in LTE mode;
*) ipsec - properly detect interface for "mode-config" client IP address assignment;
*) kidcontrol - initial work on "/ip kid-control" feature;
*) lte - fixed rare situation when r11-LTE interface is missing after reboot;
*) lte - improved IP configuration request process for r11e-LTE-US card;
*) netwatch - limit to read, write, test and reboot policies for Netwatch script execution;
*) tr069-client - correctly return TransferComplete after vendor configuration file transfer;
*) usb - improved packet processing over USB modems;
*) wireless - improved wireless stability on hAP ac2 devices while USB is being used;

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 expected or after crash.

Note that release candidate versions are published strictly for testing purposes and should not be used on production routers.
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1071
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.42rc [release candidate] is released!

Wed Feb 21, 2018 9:23 am

*) ipsec - properly detect interface for "mode-config" client IP address assignment;
This is broken again. Sent my info to [Ticket#2018012322003459].
 
tigro11
Frequent Visitor
Frequent Visitor
Posts: 87
Joined: Tue Feb 20, 2018 12:31 am

Re: v6.42rc [release candidate] is released!

Wed Feb 21, 2018 9:25 am

I have the rb 750gr3 in continuous loop, after 5 seconds reboots and makes a beep, can you restore the firmware maybe via micro sd or with the usb port?
With netinstall it does not see the cpu.
 
User avatar
null31
Member Candidate
Member Candidate
Posts: 183
Joined: Fri Dec 23, 2016 6:07 pm
Location: Brazil

Re: v6.42rc [release candidate] is released!

Wed Feb 21, 2018 1:58 pm

I have the rb 750gr3 in continuous loop, after 5 seconds reboots and makes a beep, can you restore the firmware maybe via micro sd or with the usb port?
With netinstall it does not see the cpu.
Try the ether1 on hEX (750Gr3) and connect it directly to PC.
Tips: viewtopic.php?f=13&t=131072#p643620
 
owsugde
newbie
Posts: 39
Joined: Thu Oct 06, 2016 5:01 pm

Re: v6.42rc [release candidate] is released!

Wed Feb 21, 2018 3:17 pm

Installing 6.42rc30 from rc20 makes the RB3011 unbootable! See other descriptions of update bug.

Updated from rc20 to rc30, didn't boot back up. Resetting didn't do anything, so I had to netinstall back the stable. And that even only worked after three tries. :shock:
Last edited by owsugde on Wed Feb 21, 2018 6:27 pm, edited 1 time in total.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Wed Feb 21, 2018 3:20 pm

6.42rc30 makes the RB3011 unbootable! Don't install!

Updated from rc20 to rc30, didn't boot back up. Resetting didn't do anything, so I had to netinstall back the stable. And that even only worked after three tries. :shock:
This is wellknown, no need to report it, read above. The problem is that rc20 won't update to anything. Not a problem with rc30 as you suspect.
 
tigro11
Frequent Visitor
Frequent Visitor
Posts: 87
Joined: Tue Feb 20, 2018 12:31 am

Re: v6.42rc [release candidate] is released!

Wed Feb 21, 2018 3:26 pm

I have the rb 750gr3 in continuous loop, after 5 seconds reboots and makes a beep, can you restore the firmware maybe via micro sd or with the usb port?
With netinstall it does not see the cpu.
Try the ether1 on hEX (750Gr3) and connect it directly to PC.
Tips: viewtopic.php?f=13&t=131072#p643620
Hi guys, I solved with windows xp, with win10 I could not see the rb750g
 
owsugde
newbie
Posts: 39
Joined: Thu Oct 06, 2016 5:01 pm

Re: v6.42rc [release candidate] is released!

Wed Feb 21, 2018 3:27 pm

Oh OK, I was under the impression that the problem was with updating from rc20 to rc24. Didn't know it was even worse than that.
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Wed Feb 21, 2018 4:49 pm

Once more - if you upgrade/downgrade from 6.42rc versions below rc25 - you might (not will) experience issues. Does not matter which version you install. If you experience such problems, then Netinstall will be required. This is know problem which is already resolved. At the moment (after rc25) we have not experienced or received complaints about issues with upgrade/downgrade.
 
amokkatmt
newbie
Posts: 33
Joined: Mon Oct 24, 2011 3:31 pm

Re: v6.42rc [release candidate] is released!

Thu Feb 22, 2018 2:23 pm

Hello. So now we can not use global variables in scripts called by or put as is in netwatch??? Is this by design now?? My scripts using global vars, now netwatch can not get/set values.
Yes, checked manuals, Mikrotik removed "policy" policy for netwatch scripts and global variables now can not be accessed. Seems like all global vars are "created by another users", so can't be accessed. Not the best upgrade IMHO...
 
Insider
Member Candidate
Member Candidate
Posts: 201
Joined: Mon Jun 27, 2005 4:51 pm
Location: Czech
Contact:

Re: v6.42rc [release candidate] is released!

Fri Feb 23, 2018 1:13 pm

There is a bug in last versions, you cant usually add interface to bridge port via winbox.. Via CLI no problem
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Fri Feb 23, 2018 1:57 pm

There is a bug in last versions, you cant usually add interface to bridge port via winbox..
Did you update winbox too?
 
Insider
Member Candidate
Member Candidate
Posts: 201
Joined: Mon Jun 27, 2005 4:51 pm
Location: Czech
Contact:

Re: v6.42rc [release candidate] is released!

Fri Feb 23, 2018 2:45 pm

There is a bug in last versions, you cant usually add interface to bridge port via winbox..
Did you update winbox too?
3.12
 
buzzdee
newbie
Posts: 35
Joined: Mon Apr 22, 2013 1:22 pm

Re: v6.42rc [release candidate] is released!

Sat Feb 24, 2018 10:17 pm

@jmi2
short version: With this routerOS version, if there is single client with older card like CM9, then all other clients got no change to communicate without issues.
Simply if such client is connected to AP, then mobile and notebook have horrible connectivity and LG TV and hama radio got disconnected always after few seconds.

long version: Starting with 6.37 (actually already before, if previous FWs like 6.36.4 were switched to use wireless-rep) in combination with old HW like CM9, R52 on client side, wireless channel becomes useless for all (other clients of same AP and also clients of other APs on same channel). Same issue is still there with 6.42rc20.
...
original post here

Did you check different frequencies? I had two 912UAG-5HPnD and one 411U with R52 connected to another 411U with R52 at 5200MHz with one 912 constantly dropping connection. Can't completely rule out, that nothing else was using the spectrum at that frequency but scanning for wlans at 20MHz bandwidth didn't show anything. But changing to 5220MHz stabilized the connection
 
JimmyNyholm
Member Candidate
Member Candidate
Posts: 248
Joined: Mon Apr 25, 2016 2:16 am
Location: Sweden

Re: v6.42rc [release candidate] is released!

Sun Feb 25, 2018 12:10 pm

Ok So I did see the wiki was updated to state the fact of HW offload on crs3xx series. So I did a new test and:
23 I H ether24                      bridge1                   yes   64     0x80         10                 10       none
24   H Core                         bridge1                   yes   64     0x80         10                 10       none
[admin@labb-mgmt-1] /interface bridge port> 
Shurely it states that the Bond in my case named Core show hardware offload....
But!:

Setting admit only taged vlan, making it part of the vlans as taged member. Adding IP and accessing stuff works for most part from bridge to other but other to bridge sort of comes and goes.
I see one odd thing in the export:
/interface ethernet
set [ find default-name=sfp-sfpplus2 ] mac-address=6C:3B:6B:ED:F8:46
/interface bridge
add igmp-snooping=yes name=bridge1 protocol-mode=none pvid=64 vlan-filtering=yes
/interface bonding
add lacp-rate=1sec min-links=1 mode=802.3ad name=Core slaves=sfp-sfpplus1,sfp-sfpplus2 transmit-hash-policy=\
    layer-3-and-4
Why do the system change the mac'adddres one of the lacp member ports? the Unit should advertise its chassiID in its LACP BDPU's but then the individual links is surly individual links. There is, as far as I can se, in winbox or cli not any way to see the lacp state is this by design or misstake or is it not ready yet.

Could you please expose lacp states to cli and winbox!.

Edit: If I activate one port 1-24 on the bridge then the switch is reachable from bonding (sfp-sfppluss1,sfp-sfpluss2) but if I remove the cable from port 1-24 the switch does not answer from bridge bonding interface anymore. Is this a bug due to new hardware offload that bridge doesn't think of the bundle as to enable the bridge ip's.
@Mikrotik do you need me to create support case or is this relevant information to do you tests?
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Mon Feb 26, 2018 2:57 pm

What's new in 6.42rc35 (2018-Feb-26 10:46):

*) bridge - added host aging timer for crs3xx and Atheros hw-bridges;
*) bridge - added per-port learning options (CLI only);
*) bridge - added static host support (CLI only);
*) bridge - added per-port forwarding options for broadcasts, unknown-multicasts and unknown-unicasts (CLI only);
*) bridge - fixed MAC learning for VRRP interfaces on bridge;
*) crs212 - fixed Ethernet boot through CRS326 devices;
*) crs3xx - added initial “hw-offload†support for 802.3ad and “balance-xor†bonding;
*) crs3xx - added switch port "storm-rate" limiting options;
*) dhcp - improved DHCP service reliability when it is configured on bridge interface;
*) fetch - added "http-content-type" option to allow setting MIME type of the data in free text form;
*) flashfig - properly apply configuration provided by Flashfig;
*) health - log warning when switching between redundant power supplies;
*) hotspot - improved HTTPS matching in Walled Garden rules;
*) ike1 - fixed wildcard policy lookup on responder;
*) ipsec - properly detect interface for "mode-config" client IP address assignment;
*) kidcontrol - initial work on "/ip kid-control" feature;
*) lte - added support for the user and password authentication for wAP-LTE-kit-US (R11e-LTE-US);
*) poe - hide PoE related properties on interfaces which does not provide power output;
*) ssh - remove imported public SSH keys when their owner user is removed;
*) wireless - fixed RTS/CTS option for the ARM based wireless devices;
*) tr069-client - fixed TR069 service becoming unavailable when related service package is not available;
*) tr069-client - fixed "/tool fetch" commands executed with ".alter" script;

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 expected or after crash.

Note that release candidate versions are published strictly for testing purposes and should not be used on production routers.
 
JimmyNyholm
Member Candidate
Member Candidate
Posts: 248
Joined: Mon Apr 25, 2016 2:16 am
Location: Sweden

Re: v6.42rc [release candidate] is released!

Mon Feb 26, 2018 4:31 pm

Tested This New RC. My Bridge LACP bridge problem still exists. Not reachable through lacp bond if no other local port on bridge is active.

ip dhcp-client connected to bridge1 does eternal searching after reboot disable and enable fixes the problem
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.42rc [release candidate] is released!

Mon Feb 26, 2018 4:50 pm

Tested This New RC. My Bridge LACP bridge problem still exists. Not reachable through lacp bond if no other local port on bridge is active.

ip dhcp-client connected to bridge1 does eternal searching after reboot disable and enable fixes the problem
Have you set admin-mac on the bridge?
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1071
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.42rc [release candidate] is released!

Mon Feb 26, 2018 4:56 pm

*) ipsec - properly detect interface for "mode-config" client IP address assignment;
This is broken again. Sent my info to [Ticket#2018012322003459].
Fixed in 6.42rc35. Thanks!
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1071
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.42rc [release candidate] is released!

Mon Feb 26, 2018 5:17 pm

Upgrade fails on CHR:
/system package update install 
          channel: release-candidate
  current-version: 6.42rc30
   latest-version: 6.42rc35
           status: ERROR: not enough disk space, 19.4MiB is required and only 18.1MiB is free
/system resource print                                          
                   uptime: 2m44s
                  version: 6.42rc30 (testing)
               build-time: Feb/20/2018 10:44:28
              free-memory: 203.1MiB
             total-memory: 221.7MiB
                      cpu: Intel(R)
                cpu-count: 2
            cpu-frequency: 2594MHz
                 cpu-load: 0%
           free-hdd-space: 18.2MiB
          total-hdd-space: 63.5MiB
  write-sect-since-reboot: 416
         write-sect-total: 417
        architecture-name: x86_64
               board-name: CHR
                 platform: MikroTik
Upgrade path was 6.41.2 -> 6.42rc30 -> 6.42rc35. The system does not list any files except directories "skins" and "pub".
 
JimmyNyholm
Member Candidate
Member Candidate
Posts: 248
Joined: Mon Apr 25, 2016 2:16 am
Location: Sweden

Re: v6.42rc [release candidate] is released!

Mon Feb 26, 2018 11:00 pm

Have you set admin-mac on the bridge?
I have only created the bridge1 interface.
/interface bridge export 
# mar/12/1970 15:13:17 by RouterOS 6.42rc35
# software id = M8A7-BVIJ
#
# model = CRS326-24G-2S+
/interface bridge
add igmp-snooping=yes name=bridge1 protocol-mode=none pvid=64 vlan-filtering=yes
/interface bridge port
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether1 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether2 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether3 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether4 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether5 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether6 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether7 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether8 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether9 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether10 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether11 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether12 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether13 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether14 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether15 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether16 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether17 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether18 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether19 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether20 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether21 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether22 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether23 pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether24 pvid=64
add bridge=bridge1 frame-types=admit-only-vlan-tagged ingress-filtering=yes interface=Core pvid=64
/interface bridge vlan
add bridge=bridge1 tagged=Core untagged="bridge1,ether1,ether2,ether3,ether4,ether5,ether6,ether7,ether8,ether9,ether10
    ,ether11,ether12,ether13,ether14,ether15,ether16,ether17,ether18,ether19,ether20,ether21,ether22,ether23,ether24" \
    vlan-ids=64
This works as expected with all interfaces that are not hardware offloaded lacp bonding the interface named Core is a bonding interface.

Bridge Running:
/interface bridge print detail 
Flags: X - disabled, R - running 
 0 R name="bridge1" mtu=auto actual-mtu=1500 l2mtu=1592 arp=enabled arp-timeout=auto mac-address=6C:3B:6B:ED:F8:2E 
     protocol-mode=none fast-forward=yes igmp-snooping=yes auto-mac=yes ageing-time=5m vlan-filtering=yes pvid=64 
It does have a mac in running and that mac is what is being seen on arp lookups on other machines aswell.
/interface bonding export 
# mar/12/1970 15:15:33 by RouterOS 6.42rc35
# software id = M8A7-BVIJ
#
# model = CRS326-24G-2S+
/interface bonding
add lacp-rate=1sec min-links=1 mode=802.3ad name=Core slaves=sfp-sfpplus1,sfp-sfpplus2 transmit-hash-policy=\
    layer-3-and-4
what do you make of that?
 
jmi2
just joined
Posts: 10
Joined: Mon Feb 05, 2018 11:41 am

Re: v6.42rc [release candidate] is released!

Mon Feb 26, 2018 11:25 pm

@jmi2
short version: With this routerOS version, if there is single client with older card like CM9, then all other clients got no change to communicate without issues.
Simply if such client is connected to AP, then mobile and notebook have horrible connectivity and LG TV and hama radio got disconnected always after few seconds.

long version: Starting with 6.37 (actually already before, if previous FWs like 6.36.4 were switched to use wireless-rep) in combination with old HW like CM9, R52 on client side, wireless channel becomes useless for all (other clients of same AP and also clients of other APs on same channel). Same issue is still there with 6.42rc20.
...
original post here

Did you check different frequencies? I had two 912UAG-5HPnD and one 411U with R52 connected to another 411U with R52 at 5200MHz with one 912 constantly dropping connection. Can't completely rule out, that nothing else was using the spectrum at that frequency but scanning for wlans at 20MHz bandwidth didn't show anything. But changing to 5220MHz stabilized the connection
Sure, i tried multiple channels, also two bands, i tried to change nearly each wireless setting.
And once i figured out, that it's old card mikrotik with new firmware causing problems, i also did that one test, which confirmed, that routeros in this combination must be "flooding" air as with no very little useful traffic, it's capable to turn spectrum to totally unusable to other ap on same frequency. With older firmware all tests worked like a charm. See my full post.
 
wolph
just joined
Posts: 1
Joined: Tue Feb 20, 2018 2:25 am

Re: v6.42rc [release candidate] is released!

Tue Feb 27, 2018 1:20 am

It seems that since the new firmware (6.42rc35) my capsman managed ap's can't get a dhcp lease anymore. All other devices in the network have no problems, but the mikrotik devices are unable to obtain a lease.

My logs are filled with:
feb/27 00:18:22 dhcp,warning dhcp1 offering lease x.x.x.x for C0:FF:EE:00:BA:BE w
ithout success 
feb/27 00:18:22 dhcp,warning dhcp1 offering lease x.x.x.x for C0:FF:EE:00:BA:BE w
ithout success 
[edit]
Reprovisioning through capsman solves the issue temporarily. After a few minutes it goes back to the "without success" state.
The bridges have an admin-mac set and rebooting and resetting the devices makes no difference

Reverting back to stable and doing the same capsman reset immediately resolves the issue
[/edit]
Last edited by wolph on Tue Feb 27, 2018 12:26 pm, edited 1 time in total.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.42rc [release candidate] is released!

Tue Feb 27, 2018 8:06 am

Have you set admin-mac on the bridge?
I have only created the bridge1 interface.
<...>
what do you make of that?
/interface bridge
set bridge1 auto-mac=no admin-mac=6C:3B:6B:ED:F8:2E
And then recheck.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.42rc [release candidate] is released!

Tue Feb 27, 2018 10:08 am

Checking 6.42rc35, my L2TP/IPSec setup doesn't work anymore, connection stops at
10:50:58 ipsec Adjusting my encmode UDP-Tunnel->Tunnel
10:50:58 ipsec Adjusting peer's encmode UDP-Transport(4)->Transport(2)
10:50:58 ipsec encmode mismatched: my:Tunnel peer:Transport
Back to 6.41 - and it's fine again:
10:55:18 ipsec Adjusting my encmode UDP-Transport->Transport
10:55:18 ipsec Adjusting peer's encmode UDP-Transport(4)->Transport(2)
Settings are quite straightforward:
/ip ipsec proposal
set [ find default=yes ] auth-algorithms=sha256,sha1
/interface l2tp-server server
set authentication=mschap2 enabled=yes ipsec-secret=wonttellyou use-ipsec=yes
Can anybody check this?
 
User avatar
emils
Forum Veteran
Forum Veteran
Posts: 906
Joined: Thu Dec 11, 2014 8:53 am

Re: v6.42rc [release candidate] is released!

Tue Feb 27, 2018 10:50 am

Thanks, Chupaka. We will fix this in next versions.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Tue Feb 27, 2018 11:31 am

Please also fix the automatic addition of a DHCP client. It should only do this on first boot, when applying default config.
When there already is config (address, route) it should not create a DHCP client!
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Tue Feb 27, 2018 12:33 pm

pe1chl - I assume that you are referring to CHR. This problem is not related to this concrete RouterOS version, however, we will fix it in upcoming RouterOS releases.
 
wise0tamas
just joined
Posts: 14
Joined: Sun Oct 03, 2010 1:12 am

Re: v6.42rc [release candidate] is released!

Tue Feb 27, 2018 1:44 pm

Upgrade fails on CHR:
/system package update install 
          channel: release-candidate
  current-version: 6.42rc30
   latest-version: 6.42rc35
           status: ERROR: not enough disk space, 19.4MiB is required and only 18.1MiB is free
/system resource print                                          
                   uptime: 2m44s
                  version: 6.42rc30 (testing)
               build-time: Feb/20/2018 10:44:28
              free-memory: 203.1MiB
             total-memory: 221.7MiB
                      cpu: Intel(R)
                cpu-count: 2
            cpu-frequency: 2594MHz
                 cpu-load: 0%
           free-hdd-space: 18.2MiB
          total-hdd-space: 63.5MiB
  write-sect-since-reboot: 416
         write-sect-total: 417
        architecture-name: x86_64
               board-name: CHR
                 platform: MikroTik
Upgrade path was 6.41.2 -> 6.42rc30 -> 6.42rc35. The system does not list any files except directories "skins" and "pub".
I suppose, you might have shrinked the disk, as normally (AFAIK) 128MB is the starting disk size of CHR in every type.
Or you started using CHR from the beginning, then 64MB was the starting size of the disk (as far as I can remember).
I can see 95+MiB total-hdd-space in every CHR I use, and 60+MiB free-hdd-space, so upgrade is always successful for me.

Probably, you should try resizing the disk of the CHR, then it might use the extra space, but probably, only the installation phase can resize the inner filesystem of CHR.

You should start from scratch, as stated in the System Requirements wiki, there 128MB of RAM and 128MB of disk space is required to operate/install CHR. You only need to copy out the current configuration, probably nothing more is needed.
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1071
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.42rc [release candidate] is released!

Tue Feb 27, 2018 2:46 pm

Upgrade fails on CHR:
/system package update install 
          channel: release-candidate
  current-version: 6.42rc30
   latest-version: 6.42rc35
           status: ERROR: not enough disk space, 19.4MiB is required and only 18.1MiB is free
/system resource print                                          
                   uptime: 2m44s
                  version: 6.42rc30 (testing)
               build-time: Feb/20/2018 10:44:28
              free-memory: 203.1MiB
             total-memory: 221.7MiB
                      cpu: Intel(R)
                cpu-count: 2
            cpu-frequency: 2594MHz
                 cpu-load: 0%
           free-hdd-space: 18.2MiB
          total-hdd-space: 63.5MiB
  write-sect-since-reboot: 416
         write-sect-total: 417
        architecture-name: x86_64
               board-name: CHR
                 platform: MikroTik
Upgrade path was 6.41.2 -> 6.42rc30 -> 6.42rc35. The system does not list any files except directories "skins" and "pub".
I suppose, you might have shrinked the disk, as normally (AFAIK) 128MB is the starting disk size of CHR in every type.
Or you started using CHR from the beginning, then 64MB was the starting size of the disk (as far as I can remember).
I can see 95+MiB total-hdd-space in every CHR I use, and 60+MiB free-hdd-space, so upgrade is always successful for me.

Probably, you should try resizing the disk of the CHR, then it might use the extra space, but probably, only the installation phase can resize the inner filesystem of CHR.

You should start from scratch, as stated in the System Requirements wiki, there 128MB of RAM and 128MB of disk space is required to operate/install CHR. You only need to copy out the current configuration, probably nothing more is needed.
Yes, this is an installation from the really early days of CHR. 8)
This is just a test installation, I will try to resize or reinstall.
 
TestCRS
just joined
Posts: 13
Joined: Mon Jan 22, 2018 4:49 pm

Re: v6.42rc [release candidate] is released!

Tue Feb 27, 2018 3:53 pm

Please answer a few questions about crs317.
1) will the switch be able to do vlan-remapping and outbound filtering(acl) ?
if the answer is positive, then when to expect it.

2) whether the switch forwards the qinq packets at wire-speed ?
if the answer is positive, how it is configured.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.42rc [release candidate] is released!

Tue Feb 27, 2018 3:59 pm

Thanks, Chupaka. We will fix this in next versions.
Thanks for the quick response. Is there any workaround? I'm trying to setup it in Google Cloud so I cannot downgrade to 6.41.
 
gudava
just joined
Posts: 1
Joined: Sun Feb 18, 2018 8:16 pm

Re: v6.42rc [release candidate] is released!

Tue Feb 27, 2018 5:23 pm

Tested This New RC. My Bridge LACP bridge problem still exists. Not reachable through lacp bond if no other local port on bridge is active.

ip dhcp-client connected to bridge1 does eternal searching after reboot disable and enable fixes the problem
Have you set admin-mac on the bridge?
I have same problem and yes I have admin-mac on brigde.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7049
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.42rc [release candidate] is released!

Tue Feb 27, 2018 5:32 pm

We are aware of this DHCP client problem, will try to fix in one of the next RC versions.
 
JimmyNyholm
Member Candidate
Member Candidate
Posts: 248
Joined: Mon Apr 25, 2016 2:16 am
Location: Sweden

Re: v6.42rc [release candidate] is released!

Tue Feb 27, 2018 5:36 pm

We are aware of this DHCP client problem, will try to fix in one of the next RC versions.
Thanks mrz....
Are you aware and have reproduced the LACP problem aswell?
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Tue Feb 27, 2018 5:40 pm

pe1chl - I assume that you are referring to CHR. This problem is not related to this concrete RouterOS version, however, we will fix it in upcoming RouterOS releases.
That is right, it is for CHR. Well, it appears to be a on-off problem, I did not see it in 6.42rc30 and it returned in 6.42rc35 but maybe that is pure coincidence.
It is a bit of a problem that the router suddenly obtains a new address and route that is not the configured one.
 
w0lt
Long time Member
Long time Member
Posts: 537
Joined: Wed Apr 02, 2008 2:12 pm
Location: Minnesota USA

Re: v6.42rc [release candidate] is released!

Wed Feb 28, 2018 3:20 am

Well, Well, Well... With this latest release (6.42 rc35), IGMP-Snooping seems to be working correctly on a CRS-125 !!
Wow, what went right. :o
Seemed to make a difference (at least observed), after upgrading the firmware to rc35 as well.
It's been working correctly (for me), for over 4 hours... Never did that before.. 8)

Kudos Tik ROS Team... :)
 
User avatar
emils
Forum Veteran
Forum Veteran
Posts: 906
Joined: Thu Dec 11, 2014 8:53 am

Re: v6.42rc [release candidate] is released!

Wed Feb 28, 2018 8:11 am

Thanks for the quick response. Is there any workaround? I'm trying to setup it in Google Cloud so I cannot downgrade to 6.41.
You can downgrade to previous release candidate version or configure IPsec with static policies instead of using policy template to generate them.
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1071
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.42rc [release candidate] is released!

Wed Feb 28, 2018 9:11 am

Looks like up-script from netwatch is no longer run with 6.42rc35. Are there any changes not mentioned in changelog?
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.42rc [release candidate] is released!

Wed Feb 28, 2018 9:16 am

Looks like up-script from netwatch is no longer run with 6.42rc35. Are there any changes not mentioned in changelog?
Doesn't run in rc35 compared to what? Can't it be
What's new in 6.42rc30 (2018-Feb-20 10:44):
*) netwatch - limit to read, write, test and reboot policies for Netwatch script execution;
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1071
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.42rc [release candidate] is released!

Wed Feb 28, 2018 9:47 am

Looks like up-script from netwatch is no longer run with 6.42rc35. Are there any changes not mentioned in changelog?
Doesn't run in rc35 compared to what? Can't it be
What's new in 6.42rc30 (2018-Feb-20 10:44):
*) netwatch - limit to read, write, test and reboot policies for Netwatch script execution;
Ups, I skipped 6.42rc30 due to issues with ipsec and missed that change. Thanks for the hint!
Looks like I have to figure what exactly breaks my scripts.
 
User avatar
artz
MikroTik Support
MikroTik Support
Posts: 88
Joined: Tue Oct 17, 2017 5:51 pm
Location: Riga
Contact:

Re: v6.42rc [release candidate] is released!

Wed Feb 28, 2018 10:36 am

Are you aware and have reproduced the LACP problem aswell?
There is something specific to your setup that is causing access to the CPU being lost. Please write to support@mikrotik.com, attach the supout.rif file and a small, simplified network diagram (preferably with device's model name on the other end).

You can also try disabling IGMP Snooping to check if that isn't causing the issue.
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1071
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.42rc [release candidate] is released!

Wed Feb 28, 2018 12:15 pm

Looks like up-script from netwatch is no longer run with 6.42rc35. Are there any changes not mentioned in changelog?
Doesn't run in rc35 compared to what? Can't it be
What's new in 6.42rc30 (2018-Feb-20 10:44):
*) netwatch - limit to read, write, test and reboot policies for Netwatch script execution;
Ups, I skipped 6.42rc30 due to issues with ipsec and missed that change. Thanks for the hint!
Looks like I have to figure what exactly breaks my scripts.
My scripts requires "sensitive"... So back to scheduler with a high interval.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.42rc [release candidate] is released!

Wed Feb 28, 2018 12:18 pm

My scripts requires "sensitive"... So back to scheduler with a high interval.
Sounds wrong :)

Can't you just create script in System -> Scripts and run it from on-up event of Netwatch?
You can downgrade to previous release candidate version or configure IPsec with static policies instead of using policy template to generate them.
It works, thanks :)
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1071
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.42rc [release candidate] is released!

Wed Feb 28, 2018 12:34 pm

My scripts requires "sensitive"... So back to scheduler with a high interval.
Sounds wrong :)
The script reads and writes private-pre-shared-key from "/ interface wireless access-list" and sends e-mails. Both actions require "sensitive".
Can't you just create script in System -> Scripts and run it from on-up event of Netwatch?
That's what I did. But it does no longer work.
 
bbs2web
Member Candidate
Member Candidate
Posts: 232
Joined: Sun Apr 22, 2012 6:25 pm
Location: Johannesburg, South Africa
Contact:

Re: v6.42rc [release candidate] is released!

Thu Mar 01, 2018 12:37 am

Is it intended that 'on down' script is called each time a PPPoE client unsuccessfully tries to connect?

I have a simple script that clears VoIP connection tracking entries, to essentially force them to reroute and only want it to run 'on up' if the connection was previously down and only 'on down' when it was previously connected.
/ip firewall connection remove [find dst-address ~ ":3478"];
/ip firewall connection remove [find dst-address ~ ":3479"];
/ip firewall connection remove [find dst-address ~ ":4569"];
/ip firewall connection remove [find dst-address ~ ":5060"];
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Thu Mar 01, 2018 2:31 pm

What's new in 6.42rc37 (2018-Mar-01 09:29):

*) bridge - fixed bridge port interface parameter under "/interface bridge host print detail";
*) console - do not allow variables that start with digit to be referenced without $ sign;
*) romon - make secret field sensitive in console;
*) wireless - improved wireless scan functionality for devices with multiple wireless interfaces;

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 expected or after crash.

Note that release candidate versions are published strictly for testing purposes and should not be used on production routers.
 
dksoft
Member Candidate
Member Candidate
Posts: 148
Joined: Thu Dec 06, 2012 8:56 am
Location: Germany

Re: v6.42rc [release candidate] is released!

Thu Mar 01, 2018 3:36 pm

What's new in 6.42rc37 (2018-Mar-01 09:29):
Since rc35 CAPs do no longer get an DHCP IP-address if the DHCP client runs on a bridge.
Disabling and enabling the bridge brings DHCP back into live. But after reboot DHCP client keep trying as before.
The DHCP server does see a DHCP request and replies but the CAP does accept the reply.
Tested with WAP AC and CAP AC.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7049
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v6.42rc [release candidate] is released!

Thu Mar 01, 2018 3:40 pm

We are aware of dhcp client problem on bridge interface, we will fix it in future RC versions. Disable/enable bridge or dhcp client and it will get an address.
 
dksoft
Member Candidate
Member Candidate
Posts: 148
Joined: Thu Dec 06, 2012 8:56 am
Location: Germany

Re: v6.42rc [release candidate] is released!

Thu Mar 01, 2018 4:01 pm

We are aware of dhcp client problem on bridge interface, we will fix it in future RC versions. Disable/enable bridge or dhcp client and it will get an address.
Thanks, I added this to make my CAPs work again:
/system scheduler
add name=DHCP-restart on-event=DHCP-restart policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon \
    start-time=startup
/system script
add name=DHCP-restart owner=admin policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon source=\
    ":delay 15\r\
    \n/interface bridge disable bridgeLocal\
    \n:delay 2\
    \n/interface bridge enable bridgeLocal\
    \n"
 
tigro11
Frequent Visitor
Frequent Visitor
Posts: 87
Joined: Tue Feb 20, 2018 12:31 am

Re: v6.42rc [release candidate] is released!

Sat Mar 03, 2018 3:20 am

kid-control:
hello guys, I do not know if I'm on the right page, since I have children at home I connect to the internet, I saw the kid-control utility, apart from the times and the mac address, you can also set custom dns that block adult sites?

thank you
valerio
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Sat Mar 03, 2018 10:59 am

You can always configure OpenDNS as your DNS server, either as the DNS for the router itself and then advertise the router address as DNS server in DHCP
or by advertising the OpenDNS servers in DHCP, and then configure an OpenDNS account on your internet address with the settings you like.
You do not require kid-control for that.
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3296
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v6.42rc [release candidate] is released!

Sat Mar 03, 2018 11:32 am

You can always configure OpenDNS as your DNS server
This helps just for smaller kids. Larger kids understand what is going on, and set an other DNS server.
So you should also block other DNS server than the OpenDNS.
Even then they can use VPN and bypass OpenDNS DNS.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.42rc [release candidate] is released!

Sat Mar 03, 2018 11:47 am

Even then they can use VPN and bypass OpenDNS DNS.
That's why you should block any traffic in chain=forward and force using web proxy :)
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Sat Mar 03, 2018 11:48 am

There is nothing you can do to really block things, it is only possible to do some shielding.
When you close your entire router they can use their 3G/4G connection.
 
tigro11
Frequent Visitor
Frequent Visitor
Posts: 87
Joined: Tue Feb 20, 2018 12:31 am

Re: v6.42rc [release candidate] is released!

Sat Mar 03, 2018 4:07 pm

You can always configure OpenDNS as your DNS server, either as the DNS for the router itself and then advertise the router address as DNS server in DHCP
or by advertising the OpenDNS servers in DHCP, and then configure an OpenDNS account on your internet address with the settings you like.
You do not require kid-control for that.
it's okay as you say if I want to screen all the traffic, even the adults.
I want to isolate children from filtered dns like norton, but adult traffic is open to everything. If it would be possible to insert custom dns on mac address kid it would be much easier.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Sat Mar 03, 2018 4:17 pm

It should be possible to do that! It should be possible have 2 DHCP server configs on your network, one with only static entries for the kid's devices
and one with the pool for all other devices, and then you can configure these servers with a different DNS address.
I did not try that, so you may encounter some hurdles.

You could also isolate the kid's network entirely (make a separate virtual WiFi AP with different SSID and password) and put a separate IP
range on it with different DNS server setup. I have a config like that running, not for kids but for guests. I have a separate guest WiFi SSID
that only routes to internet (while my own SSID is bridged to my LAN), and it has a separate DHCP server which advertises 8.8.8.8 as the DNS,
while my own network uses the MikroTik DNS resolver. This works without issue.
 
tigro11
Frequent Visitor
Frequent Visitor
Posts: 87
Joined: Tue Feb 20, 2018 12:31 am

Re: v6.42rc [release candidate] is released!

Sat Mar 03, 2018 4:37 pm

my idea was to use existing wifi and filter everything through mac address. Would you give me a hint on how I could do?
thank you
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3296
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v6.42rc [release candidate] is released!

Sat Mar 03, 2018 4:55 pm

When you close your entire router they can use their 3G/4G connection.
That is what I see too, so then you have lost the battle :)
Better to give good education.
 
csi
newbie
Posts: 31
Joined: Wed Mar 02, 2016 10:05 am

Re: v6.42rc [release candidate] is released!

Sat Mar 03, 2018 11:30 pm

Hello,

I've tried to configure bonding interfaces on the CRS326 based on the wiki entry:
https://wiki.mikrotik.com/wiki/Manual:C ... es#Bonding

When I try to add the ether interfaces to the bridge, I get the following error message:
failure: ether2 is already slave
The bonding interface is also not workling. I have tried to connect a NAS, where the bonding interface works fine with other devices, like a RB3011.
I'm using RouterOS Version 6.42rc37 in CRS326. Is this a bug?


Many thanks in advanced.
csi
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Sun Mar 04, 2018 12:13 am

When I try to add the ether interfaces to the bridge, I get the following error message:
failure: ether2 is already slave
You should add the bonding interface, not the ethernet interface!
 
csi
newbie
Posts: 31
Joined: Wed Mar 02, 2016 10:05 am

Re: v6.42rc [release candidate] is released!

Sun Mar 04, 2018 12:57 am

You should add the bonding interface, not the ethernet interface!
The documentation says add both.
 
skuykend
Member Candidate
Member Candidate
Posts: 274
Joined: Tue Oct 06, 2015 7:28 am

Re: v6.42rc [release candidate] is released!

Sun Mar 04, 2018 5:19 am

The documentation says add both.
It's showing ether3 and ether4 also in the bridge as non-bonded ports as an example, but the bonded interface consisting of ether1 and ether2 is added to the bridge just as bond1.
 
ivanfm
newbie
Posts: 48
Joined: Sun May 20, 2012 5:07 pm

Re: v6.42rc [release candidate] is released!

Sun Mar 04, 2018 2:21 pm

You can always configure OpenDNS as your DNS server, either as the DNS for the router itself and then advertise the router address as DNS server in DHCP
or by advertising the OpenDNS servers in DHCP, and then configure an OpenDNS account on your internet address with the settings you like.
You do not require kid-control for that.
it's okay as you say if I want to screen all the traffic, even the adults.
I want to isolate children from filtered dns like norton, but adult traffic is open to everything. If it would be possible to insert custom dns on mac address kid it would be much easier.
With dhcp options and option sets you can define different DNS servers for specific users by mac address.
 
csi
newbie
Posts: 31
Joined: Wed Mar 02, 2016 10:05 am

Re: v6.42rc [release candidate] is released!

Sun Mar 04, 2018 9:15 pm

The documentation says add both.
It's showing ether3 and ether4 also in the bridge as non-bonded ports as an example, but the bonded interface consisting of ether1 and ether2 is added to the bridge just as bond1.
You are right, my mistake. But I don't get the "H" flag on the bonding device and it still not work. Also today I get the following messages on serial console, when I tried to reconfigure the bonding device:
MikroTik 6.42rc37 (testing)
MikroTik Login: 

Rebooting...
Stopping services...
Internal error: Oops: 17 [#1] SMP
CPU: 0    Not tainted  (3.3.5 #11)
PC is at bond_netdev_event+0x5c/0x158 [bonding@0x7f244000]              
LR is at notifier_call   
Then I have tried to add an 802.3ad connection between CRS326 and RB3011. Interfaces coming up, so that I configured an IP address on each endpoint. It doesn't matter, ping does not work in each direction.

Additional it's not possible to configure MTU size on CRS326 on bonding interfaces. On RB3011 it works fine.
[admin@MikroTik] /interface bonding> set bond2 mtu=8148
failure: could not set mtu
[admin@MikroTik] /interface bonding> 

Many thanks
csi
 
temposuender
just joined
Posts: 1
Joined: Sun Mar 04, 2018 10:05 pm

Re: v6.42rc [release candidate] is released!

Sun Mar 04, 2018 10:26 pm

Upgrade fails on CHR:
/system package update install 
          channel: release-candidate
  current-version: 6.42rc30
   latest-version: 6.42rc35
           status: ERROR: not enough disk space, 19.4MiB is required and only 18.1MiB is free
/system resource print                                          
                   uptime: 2m44s
                  version: 6.42rc30 (testing)
               build-time: Feb/20/2018 10:44:28
              free-memory: 203.1MiB
             total-memory: 221.7MiB
                      cpu: Intel(R)
                cpu-count: 2
            cpu-frequency: 2594MHz
                 cpu-load: 0%
           free-hdd-space: 18.2MiB
          total-hdd-space: 63.5MiB
  write-sect-since-reboot: 416
         write-sect-total: 417
        architecture-name: x86_64
               board-name: CHR
                 platform: MikroTik
Upgrade path was 6.41.2 -> 6.42rc30 -> 6.42rc35. The system does not list any files except directories "skins" and "pub".
I suppose, you might have shrinked the disk, as normally (AFAIK) 128MB is the starting disk size of CHR in every type.
Or you started using CHR from the beginning, then 64MB was the starting size of the disk (as far as I can remember).
I can see 95+MiB total-hdd-space in every CHR I use, and 60+MiB free-hdd-space, so upgrade is always successful for me.

Probably, you should try resizing the disk of the CHR, then it might use the extra space, but probably, only the installation phase can resize the inner filesystem of CHR.

You should start from scratch, as stated in the System Requirements wiki, there 128MB of RAM and 128MB of disk space is required to operate/install CHR. You only need to copy out the current configuration, probably nothing more is needed.
Got a similar issue but I have a 128MB partition
[admin@MikroTik] /log> /system package update install
          channel: release-candidate
  current-version: 6.42rc28
   latest-version: 6.42rc37
           status: ERROR: not enough disk space, 10.0MiB is required and only 3.7MiB is free
[admin@MikroTik] /log> /system resource print
                   uptime: 41m13s
                  version: 6.42rc28 (testing)
               build-time: Feb/16/2018 07:02:32
              free-memory: 90.7MiB
             total-memory: 128.0MiB
                      cpu: MIPS 74Kc V4.12
                cpu-count: 1
            cpu-frequency: 600MHz
                 cpu-load: 11%
           free-hdd-space: 3872.0KiB
          total-hdd-space: 128.0MiB
  write-sect-since-reboot: 5375
         write-sect-total: 31175782
               bad-blocks: 0%
        architecture-name: mipsbe
               board-name: RB951Ui-2HnD
                 platform: MikroTik
 
I cant find anything that I can cleanup.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Mon Mar 05, 2018 10:01 am

You should make a backup, download that, then netinstall the device with "keep configuration" option, and when it
does not resolve the situation use "default configuration" and restore your backup.
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Wed Mar 07, 2018 12:53 pm

What's new in 6.42rc39 (2018-Mar-07 07:01):

*) bridge - added per-port forwarding options for broadcasts, unknown-multicasts and unknown-unicasts;
*) bridge - added per-port learning options;
*) bridge - added support for static hosts;
*) bridge - fixed reliability on software bridges when used on devices without switch chip;
*) capsman - added "allow-signal-out-of-range" option for Access List entries;
*) capsman - added support for "interface-list" in Access List and Datapath entries;
*) console - fixed "idpr-cmtp" protocol by changing its value from 39 to 38;
*) crs3xx - added initial "hw-offload" support for 802.3ad and "balance-xor" bonding;
*) crs3xx - added switch port "storm-rate" limiting options;
*) dhcp - improved DHCP service reliability when it is configured on bridge interface;
*) email - set maximum number of sessions to 100;
*) fetch - increased maximum number of sessions to 100;
*) ike1 - fixed wildcard policy lookup on responder;
*) quickset - fixed NAT if PPPoE client is used for Internet access;
*) winbox - made UDP local and remote TX size parameter optional in Bandwidth Test tool;
*) winbox - moved "ageing-time" setting from STP to General tab;
*) winbox - added "antenna" setting under GPS settings for MIPS platform devices;
*) winbox - added 160 MHz "channel-width" to wireless settings;
*) winbox - added broadcast and flood settings to bridge ports;
*) winbox - added missing protocol numbers to IPv4 and IPv6 firewall;
*) winbox - removed "VLAN" section from "Switch" menu for CRS3xx devices;
*) winbox - fixed maximal ID for Traffic Generator stream;
*) winbox - fixed name for "out-bridge-list" parameter under bridge firewall rules;
*) winbox - removed Enable and Disable buttons from IPsec "mode-config" list;
*) winbox - show "D" flag under "/ip dhcp-client" menu;
*) winbox - show CQI in LTE info;
*) winbox - show only master CAP interfaces under CAPsMAN wireless scan tool;
*) wireless - added support for "band=5ghz-n/ac";
*) wireless - added support for "interface-list" for Access List entries;
*) wireless - added support for legacy AR9485 chipset;
*) wireless - improved wireless scan functionality;

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 expected or after crash.

Note that release candidate versions are published strictly for testing purposes and should not be used on production routers.
 
dksoft
Member Candidate
Member Candidate
Posts: 148
Joined: Thu Dec 06, 2012 8:56 am
Location: Germany

Re: v6.42rc [release candidate] is released!

Wed Mar 07, 2018 2:36 pm

There now is support for "band=5ghz-n/ac" in the GUI but none in the capsman GUI.
 
biatche
Member Candidate
Member Candidate
Posts: 128
Joined: Tue Oct 13, 2015 6:50 am

Re: v6.42rc [release candidate] is released!

Wed Mar 07, 2018 3:18 pm

There now is support for "band=5ghz-n/ac" in the GUI but none in the capsman GUI.
My exact thoughts. Why?
 
User avatar
juliokato
Member Candidate
Member Candidate
Posts: 228
Joined: Mon Oct 26, 2015 4:27 pm
Location: Brazil

Re: v6.42rc [release candidate] is released!

Wed Mar 07, 2018 5:09 pm

I It is incredible that we have no improvement for IPv6.
Please please please do some work on IPv6!
E.g. following priorities from this posting: viewtopic.php?f=2&t=123302

Things I really need, the sooner the better:
- route marking and multi route tables using marks as in IPv4
(via ipv6 firewall mangle and/or ipv6 route rule)
- configurable IPv6 nameservers in DHCPv6 and RA, or at least the option to publish the router's own
address as nameserver instead of the configured external DNS servers
 
User avatar
honzam
Forum Guru
Forum Guru
Posts: 2394
Joined: Wed Feb 27, 2008 10:27 pm
Location: Czech Republic

Re: v6.42rc [release candidate] is released!

Wed Mar 07, 2018 6:45 pm


*) winbox - added 160 MHz "channel-width" to wireless settings
Which products support 160Mhz? Thanks
 
User avatar
mozerd
Forum Veteran
Forum Veteran
Posts: 878
Joined: Thu Oct 05, 2017 3:39 pm
Location: Canada
Contact:

Re: v6.42rc [release candidate] is released!

Wed Mar 07, 2018 11:14 pm

What's new in 6.42rc39 (2018-Mar-07 07:01):

*) winbox - show "D" flag under "/ip dhcp-client" menu;
Is this supposed to show under Terminal or via Winbox DHCP-Client Window row dispaly ? If its under window mine does not show the "D: flag as described for the release. If its under Terminal it does show up as in the Flags: row
My question:: when should the "D" flag appear under DHCP-Client? before the ip address has been assignend or after the ip addrsss has been assigned by the server?
 
105547111
Member Candidate
Member Candidate
Posts: 135
Joined: Fri Jun 22, 2012 9:46 pm

Re: v6.42rc [release candidate] is released!

Thu Mar 08, 2018 12:25 am

I It is incredible that we have no improvement for IPv6.
Please please please do some work on IPv6!
E.g. following priorities from this posting: viewtopic.php?f=2&t=123302

Things I really need, the sooner the better:
- route marking and multi route tables using marks as in IPv4
(via ipv6 firewall mangle and/or ipv6 route rule)
- configurable IPv6 nameservers in DHCPv6 and RA, or at least the option to publish the router's own
address as nameserver instead of the configured external DNS servers
Yes can't agree more. Have got 6to4 backup as well as other tunnels but no can't route it properly, or heaven's forbid the ability to route specific ipv6 traffic over better suited tunnels :-(
 
User avatar
BartoszP
Forum Guru
Forum Guru
Posts: 2870
Joined: Mon Jun 16, 2014 1:13 pm
Location: Poland

Re: v6.42rc [release candidate] is released!

Thu Mar 08, 2018 1:45 am

What's new in 6.42rc39 (2018-Mar-07 07:01):
.....
*) wireless - added support for "interface-list" for Access List entries;
.....
Could we expect MAC-addresses list implemented?
 
kunago
newbie
Posts: 26
Joined: Sun Mar 09, 2014 1:58 pm

Re: v6.42rc [release candidate] is released!

Thu Mar 08, 2018 3:25 pm

Is CAPsMAN's VLAN implementation going to be fixed to work with the new bridge implementation? Now PVID seems to be used over VLAN and therefore makes CAPsMAN a little unusable.
 
sindy
Forum Guru
Forum Guru
Posts: 10206
Joined: Mon Dec 04, 2017 9:19 pm

Re: v6.42rc [release candidate] is released!

Thu Mar 08, 2018 4:00 pm

Is CAPsMAN's VLAN implementation going to be fixed to work with the new bridge implementation? Now PVID seems to be used over VLAN and therefore makes CAPsMAN a little unusable.
To me CAPsMAN along with VLANs works in 6.41+, so can you open a separate topic for that and describe what you want to achieve? Maybe a workaround can be found.
 
JimmyNyholm
Member Candidate
Member Candidate
Posts: 248
Joined: Mon Apr 25, 2016 2:16 am
Location: Sweden

Re: v6.42rc [release candidate] is released!

Thu Mar 08, 2018 4:20 pm

*) bridge - added per-port forwarding options for broadcasts, unknown-multicasts and unknown-unicasts;
*) bridge - added per-port learning options;
*) bridge - added support for static hosts;
Thanks. This will make it possible to configure stuff that I was waiting for.
Is there any plans for more learning modes. now there are Auto, On, Off.
[admin@MikroTik] > interface bridge port set learn=
auto  no  yes


No I do understand do not learn, static only check...
Yes I do understand learn end of discussion check...
But Auto? No but Yes? For Auto to make sence it would be accompanied with max-learn-hosts=[nr] being integer number from 1 to n and the option on-max-replace-mode=[none, fifo, lifo] and on-max-replace-timeout=[nr] sec.
With the learn being Auto and:
No timeout set honor only on-max-replace-mode
timeout set honor on-max-replace-mode and check that the timeout is reached before.


Am I right to be waiting for this aswell?
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Thu Mar 08, 2018 4:46 pm

dksoft, biatche - This is still an rc version. The first step is to add such mode in regular wireless settings;
mozerd - As changelog entry states "winbox - show "D" flag..." it is a Winbox fix. Applies to, for example, DHCP client created by "detect-internet" feature;
kunago - Have you contacted support regarding this matter? If not, then write to support, explain the issue that you have and if it an actual software issue, then we will try to resolve it;
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v6.42rc [release candidate] is released!

Fri Mar 09, 2018 2:42 am

Getting very poor performance with FastTrack, hap ac, 150Mbps download speed slows down to 15Mbps. Fasttrack disabled and I can get full speed. This only started recently, so I imagine it is from one of the RC's.
 
alexjhart
Member Candidate
Member Candidate
Posts: 197
Joined: Thu Jan 20, 2011 8:03 pm

Re: v6.42rc [release candidate] is released!

Fri Mar 09, 2018 2:44 am



*) crs3xx - added initial hw-offload support for 802.3ad and balance-xor bonding
What does "initial" mean here?
Strods?
For those still wondering, I found this https://wiki.mikrotik.com/wiki/Manual:C ... es#Bonding
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Fri Mar 09, 2018 10:31 am

Getting very poor performance with FastTrack, hap ac, 150Mbps download speed slows down to 15Mbps. Fasttrack disabled and I can get full speed. This only started recently, so I imagine it is from one of the RC's.
Such reports are probably meaningless without included export of your configuration, at least the firewall, queueing and routing part.
Maybe you should mail a supout.rif to support.
 
csi
newbie
Posts: 31
Joined: Wed Mar 02, 2016 10:05 am

Re: v6.42rc [release candidate] is released!

Fri Mar 09, 2018 12:25 pm

*) crs3xx - added initial "hw-offload" support for 802.3ad and "balance-xor" bonding;
Well done!
I can confirm it's working on a CRS326 now. Still open is the issue to change MTU size.
[admin@MikroTik] /interface bonding> set bond2 mtu=8148
failure: could not set mtu
[admin@MikroTik] /interface bonding>
 
JimmyNyholm
Member Candidate
Member Candidate
Posts: 248
Joined: Mon Apr 25, 2016 2:16 am
Location: Sweden

Re: v6.42rc [release candidate] is released!

Fri Mar 09, 2018 12:58 pm

*) crs3xx - added initial "hw-offload" support for 802.3ad and "balance-xor" bonding;
Well done!
I can confirm it's working on a CRS326 now. Still open is the issue to change MTU size.
[admin@MikroTik] /interface bonding> set bond2 mtu=8148
failure: could not set mtu
[admin@MikroTik] /interface bonding>
Can allso Confirm that my LACP probelm still exists: accessing the ip owned by bridge over hw offloaded tag'ed only vlan lacp is not possible. Arp on upstream client gets mac for bridge/ip but no luck pinging or connecting.
 
User avatar
artz
MikroTik Support
MikroTik Support
Posts: 88
Joined: Tue Oct 17, 2017 5:51 pm
Location: Riga
Contact:

Re: v6.42rc [release candidate] is released!

Fri Mar 09, 2018 4:54 pm

Well done!
I can confirm it's working on a CRS326 now. Still open is the issue to change MTU size.
[admin@MikroTik] /interface bonding> set bond2 mtu=8148
failure: could not set mtu
[admin@MikroTik] /interface bonding>
You must set L2MTU on slave interfaces first.
 
NetflashTechnical
just joined
Posts: 15
Joined: Fri May 10, 2013 3:43 pm

Re: v6.42rc [release candidate] is released!

Fri Mar 09, 2018 5:27 pm

What's new in 6.42rc39 (2018-Mar-07 07:01):

*) bridge - added per-port forwarding options for broadcasts, unknown-multicasts and unknown-unicasts;
*) bridge - added per-port learning options;
*) bridge - added support for static hosts;
*) bridge - fixed reliability on software bridges when used on devices without switch chip;
Q: How do you set the "default" option for "Unknown Unicast Flood", "Unknown Multicast Flood" and "Broadcast Flood" overall for an interface. It seems like dynamic interfaces (say an l2tp interface on the bridge) default to all flooding ON can you can't modify the options. I wonder if you can add a "Default Unknown Unicast Flood", "Default Unknown Multicast Flood", and "Default Broadcast Flood" option to the bridge, OR allow the ppp profile to set the bridge options similar to how you can set horizon.
 
bbs2web
Member Candidate
Member Candidate
Posts: 232
Joined: Sun Apr 22, 2012 6:25 pm
Location: Johannesburg, South Africa
Contact:

Re: v6.42rc [release candidate] is released!

Fri Mar 09, 2018 8:28 pm

Please would MikroTik consider allowing us to set granular pps (packets per second) filtering on ports, instead of percentage. 1% of 10 Gbps is still 100 Mbps, this would rapidly exhaust MAC address tables and take the network offline.

D-Link DGS and Netgear M4300 switches support setting most ports to selectively drop excess or shutdown port when exceeding eg 500 pps for customer facing ports, whilst having different values on internal ports.

Are there plans to provide dot1q-tunnel equivalent features and switch port rules to manipulate two VLAN tags? (eg pop outer and inner tags and replace them with others)
 
csi
newbie
Posts: 31
Joined: Wed Mar 02, 2016 10:05 am

Re: v6.42rc [release candidate] is released!

Fri Mar 09, 2018 8:38 pm

Well done!
I can confirm it's working on a CRS326 now. Still open is the issue to change MTU size.
[admin@MikroTik] /interface bonding> set bond2 mtu=8148
failure: could not set mtu
[admin@MikroTik] /interface bonding>
You must set L2MTU on slave interfaces first.
Many thanks for the hint. It's working now.
 
User avatar
nz_monkey
Forum Guru
Forum Guru
Posts: 2099
Joined: Mon Jan 14, 2008 1:53 pm
Location: Over the Rainbow
Contact:

Re: v6.42rc [release candidate] is released!

Fri Mar 09, 2018 11:48 pm

Please would MikroTik consider allowing us to set granular pps (packets per second) filtering on ports, instead of percentage. 1% of 10 Gbps is still 100 Mbps, this would rapidly exhaust MAC address tables and take the network offline.
+1

Please do this!! On our Extreme and Juniper switches we set PPS differently depending on the role of the port, e.g. ENNI's get very low limits, Trunks get very high limits, Servers get high limits, Edge devices get very low limits.
 
idlemind
Forum Guru
Forum Guru
Posts: 1146
Joined: Fri Mar 24, 2017 11:15 pm
Location: USA

Re: v6.42rc [release candidate] is released!

Sat Mar 10, 2018 1:41 am

Are there plans to provide dot1q-tunnel equivalent features and switch port rules to manipulate two VLAN tags? (eg pop outer and inner tags and replace them with others)
I've been using QinQ trunking in software bridges on a hex for sometime now. Nothing really special to report about it. I imagine it's software switched but for me that's not a problem.
 
JimmyNyholm
Member Candidate
Member Candidate
Posts: 248
Joined: Mon Apr 25, 2016 2:16 am
Location: Sweden

Re: v6.42rc [release candidate] is released!

Sat Mar 10, 2018 7:31 pm

# jan/13/1970 03:06:17 by RouterOS 6.42rc39
# software id = JLRA-QA36
#
# model = CRS326-24G-2S+
# serial number = 763C06E78477
/interface ethernet
set [ find default-name=sfp-sfpplus2 ] mac-address=6C:3B:6B:ED:F9:E6
/interface bridge
add admin-mac=6C:3B:6B:ED:F9:E6 auto-mac=no fast-forward=no name=bridge1 protocol-mode=none pvid=64 vlan-filtering=yes
/interface bonding
add lacp-rate=1sec min-links=1 mode=802.3ad name=Core slaves=sfp-sfpplus1,sfp-sfpplus2 transmit-hash-policy=layer-3-and-4
/interface bridge port
add bridge=bridge1 frame-types=admit-only-vlan-tagged interface=Core pvid=64
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged interface=ether1 pvid=64 unknown-multicast-flood=no unknown-unicast-flood=no
/interface bridge vlan
add bridge=bridge1 tagged=Core untagged=bridge1,ether1 vlan-ids=64
/ip dhcp-client
add dhcp-options=hostname,clientid disabled=no interface=bridge1
/system identity
set name=dc-jkb-dsa-4
/system package update
set channel=release-candidate
/system routerboard settings
set boot-os=router-os silent-boot=no
You have model and version i initial comment rows my LACP problem connect only Core interface (LACP sfpsfpplus1,sfpsfplus2) to upstream network nothing else. Now the switch on vlan64 will get ip and can access everything it should. But nothing from the upstream device can access the bride not by mac nor IP.
If i then check the connection by connecting a laptop to ether1 this laptop gets ip from upstream dhcp and all works AND the bridge itself is accessable from upstream on other device(winbox l2 or l3).

The minute I disconnect the laptop (ether1) so that the only active port in bridge is Core (lacp hw bond/trunk) then the same upstream system can't access the bride no more through any l2 or l3 means in winbox. It is seen still but can't login.

Please try to replicate and Confirm that you are aware of this an working on fixing it.

[Ticket#2018031222001218] RE: LACP HW problem reac [...]
Last edited by JimmyNyholm on Mon Mar 12, 2018 10:07 am, edited 1 time in total.
 
bbs2web
Member Candidate
Member Candidate
Posts: 232
Joined: Sun Apr 22, 2012 6:25 pm
Location: Johannesburg, South Africa
Contact:

Re: v6.42rc [release candidate] is released!

Sun Mar 11, 2018 12:15 am

Exactly... The CPUs in CRS class devices are weak, extremely weak. I assisted someone recently that couldn't do 10Mbps routing on a CRS125, as this was software based.

I would like to see more high end merchant silicon implementations. Broadcom Dune, for example, was released in 2015 and provides 800 Gbps forwarding capacity per device, VXLAN, NVGRE, Geneve, MPLS, VPLS, hierarchical traffic manager with support for thousands of flows and external DDR4 or GDDR5 packet buffering support.

People are excited about CRS326 when a 4 year old D-Link DGS (8x1Gbps UTP, 24x1Gbps SFP, 2x10Gbps, dual power) switch does everything wirespeed and supports (R|M)STP, QinQ, dot1q-tunnel?

Mikrotik should work on their RouterOS 7 unicorn, these functions are missing and sorely needed:
- IPv6 blackholing
- Per interface rp-filter settings (no reverse path filtering in IPv6 at all currently)
- MPLS for static or BGP routes
- BGP multi-protocol support (IPv4 BGP sessions that exchange IPv6 routes and then switch traffic using MPLS labels)
- IPv6 MPLS
- VirtIO NIC multi-queue support
- Integrate the high-availability work that community members have done. Most people would probably purchase pairs of CCR devices if they could simply connect a heartbeat cable and enable a feature.
- Proper VRF isolation and working trace routes
- IPv4 and IPv6 feature parity (NAT (even just 6to6 or prefix translation), connection tracking, etc)

I've been using QinQ trunking in software bridges on a hex for sometime now. Nothing really special to report about it. I imagine it's software switched but for me that's not a problem.
Are there plans to provide dot1q-tunnel equivalent features and switch port rules to manipulate two VLAN tags? (eg pop outer and inner tags and replace them with others)
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Sun Mar 11, 2018 10:00 am

Exactly... The CPUs in CRS class devices are weak, extremely weak. I assisted someone recently that couldn't do 10Mbps routing on a CRS125, as this was software based.
Well the CPU is weak, but not THAT weak. To have that problem you would have to do IPsec or extremely lot of (and badly ordered) filters.

However, a CRS is NOT a replacement for an L3-routing switch as available from A-brand manufacturers (HP Procurve / Aruba Networks, Cisco etc).
Those switches do wirespeed routing just like they do wirespeed switching, and a CRS simply cannot do that.

My position remains, when you require a professional switch with wirespeed L3 routing and other facilities available in that range (DHCP and ARP snooping/filtering etc)
then do not buy from MikroTik. MicroTik has some nice low-end switches that can do some routing but it is only intended for management and/or some special use
case, not to route the main traffic of the switch. And it does not offer many of the facilities available on those professional switches.

Maybe it will change in the future, but hey, maybe in the future we'll also get RouterOS v7. However, that does not seem to be the near future.
So for now, buy CRS only when you need mainly plain switching and no advanced features.
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Mon Mar 12, 2018 10:46 am

Version 6.41.3 has been released with fixes from 6.42rc backported to 6.41.x release tree:
viewtopic.php?f=21&t=131810
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Mon Mar 12, 2018 10:47 am

What's new in 6.42rc41 (2018-Mar-09 08:01):

*) ipsec - improved single tunnel hardware acceleration performance on MMIPS platform devices;
*) snmp - provide "board-name" information;

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 expected or after crash.

Note that release candidate versions are published strictly for testing purposes and should not be used on production routers.
 
biatche
Member Candidate
Member Candidate
Posts: 128
Joined: Tue Oct 13, 2015 6:50 am

Re: v6.42rc [release candidate] is released!

Mon Mar 12, 2018 1:40 pm

small changelog, final version soon? :)
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Mon Mar 12, 2018 1:46 pm

small changelog, final version soon? :)
No, everyone is now working on the big IPv6 update!
(I am dreaming...)
 
User avatar
juliokato
Member Candidate
Member Candidate
Posts: 228
Joined: Mon Oct 26, 2015 4:27 pm
Location: Brazil

Re: v6.42rc [release candidate] is released!

Mon Mar 12, 2018 2:33 pm

Me too.....
:lol:
No, everyone is now working on the big IPv6 update!
(I am dreaming...)
 
benbennett
just joined
Posts: 4
Joined: Thu May 05, 2016 6:53 am

Re: v6.42rc [release candidate] is released!

Tue Mar 13, 2018 9:52 am

Went from 6.42rc24 to 6.42rc41 and it broke my dual WAN configuration, its similar to this configuration except I am just using 2 WANS with a 3:1 ratio, ie one WAN gets more traffic. https://aacable.wordpress.com/tag/mikro ... wan-links/


Cannot roll back either or force a downgrade for some reason.

Would resetting the configuration and downgrading work? I don't know why the downgrade just fails. It just reboots and I am stuck on 6.42rc41

( I have the script that saves backup every reboot, so I was just going to reset, downgrade,upgrade ,restore)
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.42rc [release candidate] is released!

Tue Mar 13, 2018 10:00 am

It just reboots and I am stuck on 6.42rc41
And nothing in Log?
 
User avatar
doneware
Trainer
Trainer
Posts: 647
Joined: Mon Oct 08, 2012 8:39 pm
Location: Hungary

Re: v6.42rc [release candidate] is released!

Tue Mar 13, 2018 1:20 pm

*) capsman - improved CAPsMAN responsiveness on systems with large amount of CAP interfaces;
can anyone please describe in numeric format, what "large amount" means?
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v6.42rc [release candidate] is released!

Tue Mar 13, 2018 2:19 pm

Hundreds
 
benbennett
just joined
Posts: 4
Joined: Thu May 05, 2016 6:53 am

Re: v6.42rc [release candidate] is released!

Tue Mar 13, 2018 10:02 pm

Here is the log where it started going wrong
omitting package system-6.41.3: older package is already provided
can not install ppp-6.41.3: system-6.41.3 is not installed, but is required
 
benbennett
just joined
Posts: 4
Joined: Thu May 05, 2016 6:53 am

Re: v6.42rc [release candidate] is released!

Tue Mar 13, 2018 10:14 pm

Got it to downgrade. There were packages in the root directory on the router that I was using to sync files to a dude server. That was causing a conflict.

Sorry my problem.
 
User avatar
strods
MikroTik Support
MikroTik Support
Topic Author
Posts: 1623
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v6.42rc [release candidate] is released!

Thu Mar 15, 2018 3:33 pm

What's new in 6.42rc43 (2018-Mar-14 10:45):

!) tile - improved overall system performance and stability ("/system routerboard upgrade" required);
*) crs326 - fixed known multicast flooding to the CPU;
*) dhcp - improved DHCP service reliability when it is configured on bridge interface;
*) ssh - generate SSH keys only on the first connect attempt instead of the first boot;
*) ups - improved disconnect message handling between RouterOS and UPS;
*) wireless - enable all chains by default on devices without external antennas after configuration reset;

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 expected or after crash.

Note that release candidate versions are published strictly for testing purposes and should not be used on production routers.
 
User avatar
tomaskir
Trainer
Trainer
Posts: 1162
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: v6.42rc [release candidate] is released!

Thu Mar 15, 2018 8:20 pm

*) ssh - generate SSH keys only on the first connect attempt instead of the first boot;
Could you please comment on why this change was made?

Is it not better to generate these at startup than to make an user wait the first time he connects?
Specifically on older boards (with single-core 400MHz CPUs), this generation can take a long time.

Lets say I power-on a new router , or a router that has been reset to empty config.
It's way more comfortable for me for that router to generate its SSH keys while I might be clicking doing other things, rather than make me wait when I want to connect.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10208
Joined: Mon Jun 08, 2015 12:09 pm

Re: v6.42rc [release candidate] is released!

Thu Mar 15, 2018 8:39 pm

Specifically on older boards (with single-core 400MHz CPUs), this generation can take a long time.

Lets say I power-on a new router , or a router that has been reset to empty config.
It's way more comfortable for me for that router to generate its SSH keys while I might be clicking doing other things, rather than make me wait when I want to connect.
My guess would be that routers are powered off-on during initialization when it takes so long, and configuration gets inconsistent resulting in complaints or returns.
 
upower3
Member
Member
Posts: 425
Joined: Thu May 07, 2015 11:46 am

Re: v6.42rc [release candidate] is released!

Fri Mar 16, 2018 12:01 am

Tried 6.42rc43 and found nice visual bug:

Image

Under System -> Routerboard I can see factory ROS version, while under System -> Resources it is blank field.

Any SIM slot control button still there even that RB951G-2HnD have no such slot. Funny to see this suddenly appeared "feature".
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1071
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v6.42rc [release candidate] is released!

Fri Mar 16, 2018 12:09 am

Under System -> Routerboard I can see factory ROS version, while under System -> Resources it is blank field.
One is RouterOS version, the other is boot firmware version.
Looks like older devices do not have a record about factory RouterOS version.
 
105547111
Member Candidate
Member Candidate
Posts: 135
Joined: Fri Jun 22, 2012 9:46 pm

Re: v6.42rc [release candidate] is released!

Fri Mar 16, 2018 1:00 am

*) ssh - generate SSH keys only on the first connect attempt instead of the first boot;
Could you please comment on why this change was made?

Is it not better to generate these at startup than to make an user wait the first time he connects?
Specifically on older boards (with single-core 400MHz CPUs), this generation can take a long time.

Lets say I power-on a new router , or a router that has been reset to empty config.
It's way more comfortable for me for that router to generate its SSH keys while I might be clicking doing other things, rather than make me wait when I want to connect.
+1
 
Keyko
newbie
Posts: 27
Joined: Sat Dec 23, 2017 6:27 pm

6.42rc43 +hAP AC^2 = boot loop

Fri Mar 16, 2018 1:07 am

Good afternoon.

Such a problem - 6.42rc43 +hAP AC^2 = boot loop. If you roll 6.42rc43 and do not update the firmware, everything seems to be fine, but it's worth updating the firmware and the router stupidly goes to the boot loops. At the same time, I tried to download a stable version via nethinstall, but there is still a loop.

If the router reboots from the button (pull out the button, hold down the button, insert the PS and wait for 20 seconds, the router allows you to go through the winbox, but if you just reboot or turn it off / on, it's a loop again.

I was able to roll back to stable firmware in this way - installed 6.41.3, then rebooted from the button to the factory, connected to winbox and rolled firmware by pressing "update firmware" several times and then rebooted the device.


So it goes.


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

Re: v6.42rc [release candidate] is released!

Fri Mar 16, 2018 7:14 am

tomaskir, pe1chl, 105547111 - Waiting time is not too long. This kind of implementation will satisfy the biggest part of the users so we decided to re-make this generate process.
upower3, eworm - This is not a bug. If router was installed in factory before we introduced this feature "show min RouterOS version", then this value is not specified. These are two different variables - RouterBOOT and RouterOS minimal supported versions.
Keyko - We will look into this problem and fix it as soon as possible if we managed to reproduce it. I recommend that you still contact support@mikrotik.com regarding this problem so you can get more feedback from our side and reach solution much faster.
 
User avatar
tomaskir
Trainer
Trainer
Posts: 1162
Joined: Sat Sep 24, 2011 2:32 pm
Location: Slovakia

Re: v6.42rc [release candidate] is released!

Fri Mar 16, 2018 11:46 am

Waiting time is not too long. This kind of implementation will satisfy the biggest part of the users so we decided to re-make this generate process.
But what is the benefit - what was the original need to change this?

Because from what I can see, this has only disadvantages.
Making users wait when they want to connect is NOT a good UX.
 
morf
Member Candidate
Member Candidate
Posts: 182
Joined: Tue Jun 21, 2011 5:31 pm
Location: Saint-Petersburg

Re: v6.42rc [release candidate] is released!

Fri Mar 16, 2018 12:07 pm

The big problem on CCR1072 with 6.42rc43 (Release candidate)
After the upgrade, all 10g interfaces were lost! Only 1 gb copper is still visible. Reset did not help.
I had to roll back to a stable 6.41.3
 
atlanticd
newbie
Posts: 30
Joined: Thu Jun 11, 2015 6:42 pm

Re: 6.42rc43 +hAP AC^2 = boot loop

Sat Mar 17, 2018 3:14 pm

Hi strods, Keyko,

I experienced the same on my hAP ac^2. I upgraded from factory 6.40.5 to 6.42rc43 using netinstall (netinstall version was also 6.42rc43). After successful update, I triggered firmware upgrade in Winbox by clicking on Upgrade button on System/Routerboard menu. After upgrading the firmware to 6.42rc43, the boot loop started. I tried to install with netinstall and RouterBOOT "15 seconds" method 6.41.3, again 6.42rc43, and lastly 6.40.6, and although install was always successful, the boot loop still remained. In the end I recognized that even without pressing reset button while plugging in the power, it always went to RouterBOOT (I saw it in netinstall Ready state always). Finally, I reverted by RouterBOOT "5 seconds" factory reset method to boot, that booted properly RouterOS 6.40.6 (the last I tried with netinstall), and I saw that current firmware was 6.42rc43, and Upgrade firmware was 3.43. Here is a screenshot:
Image

Once I clicked on Upgrade, and after reboot, I could properly boot again. And upgrade again to 6.42rc43 (and of course this time I skipped firmware upgrade, so it is running now with ROS=6.42rc43 and RouterBOOT 3.43)

So steps to reproduce:
1. Upgrade from factory firmware to 6.42rc43
2. Upgrade firmware to 6.42rc43
3. Bootloop start to happen

Revert:
1. Boot the device with "5 seconds method" : Hold this button during boot time until LED light starts flashing, release the button to reset RouterOS configuration (total 5 seconds)
2. Trigger Upgrade (which is actually Downgrade) of RouterBoot firmware


Kindly ask you to investigate this issue. Thank you.

Good afternoon.

Such a problem - 6.42rc43 +hAP AC^2 = boot loop. If you roll 6.42rc43 and do not update the firmware, everything seems to be fine, but it's worth updating the firmware and the router stupidly goes to the boot loops. At the same time, I tried to download a stable version via nethinstall, but there is still a loop.

If the router reboots from the button (pull out the button, hold down the button, insert the PS and wait for 20 seconds, the router allows you to go through the winbox, but if you just reboot or turn it off / on, it's a loop again.

I was able to roll back to stable firmware in this way - installed 6.41.3, then rebooted from the button to the factory, connected to winbox and rolled firmware by pressing "update firmware" several times and then rebooted the device.


So it goes.


Sincerely.
 
psannz
Member Candidate
Member Candidate
Posts: 127
Joined: Mon Nov 09, 2015 3:52 pm
Location: Renningen, Germany

Re: 6.42rc43 +hAP AC^2 = boot loop

Sat Mar 17, 2018 4:21 pm

Good afternoon.

Such a problem - 6.42rc43 +hAP AC^2 = boot loop. If you roll 6.42rc43 and do not update the firmware, everything seems to be fine, but it's worth updating the firmware and the router stupidly goes to the boot loops. At the same time, I tried to download a stable version via nethinstall, but there is still a loop.
Can confirm the issue, 6.42rc43 RouterBoot and hAP AC^2 don't mix well.

Who is online

Users browsing this forum: No registered users and 12 guests