v6.41rc [release candidate] is released! New bridge implementation!

Wed Jul 26, 2017 2:36 pm

What's new in 6.41rc3 (2017-Jul-26 09:32):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

!) bridge - implemented software based vlan-aware bridges;
https://wiki.mikrotik.com/wiki/Manual:I ... _Filtering
!) switch - "master-port" conversion into a bridge with hardware offload "hw" option (CLI only);
https://wiki.mikrotik.com/wiki/Manual:S ... Offloading
!) bridge - general development of hw-offload bridge implementation (introduced in v6.40rc36);
*) CRS3xx - switch VLAN configuration integrated within bridge VLAN configuration with hw-offload;
*) arp - fixed invalid static ARP entries after reboot on interfaces without IP address;
*) bonding - improved relialibility on bonding interface removal;
*) bridge - fixed ARP setting (introduced in v6.40rc36);
*) bridge - fixed multicast forwarding (introduced in v6.40rc36);
*) bridge - implemented dynamic entries for active MST port overrides;
*) bridge - implemented software based "igmp-snooping" (CLI only);
*) bridge - implemented software based MSTP (CLI only);
*) bridge - removed "frame-types" and "ingress-filtering" for bridge interfaces (introduced in v6.40rc36);
*) certificate - show "Expired" flag when initial CRL fetch fails;
*) e-mail - do not show errors when sending e-mail from script;
*) firewall - properly remove "address-list" entry after timeout ends;
*) hotspot - improved user statistics collection process;
*) interface - improved interface state change handling when multiple interfaces are affected at the same time;
*) ippool6 - try to assign desired prefix for client if prefix is not being already used;
*) lte - allow to specify the MAC address for passthrough mode;
*) ppp - added client support for Sierra MC7750;
*) rb2011 - fixed possible LCD blinking along with Ethernet LED;
*) rb922 - restored missing wireless interface on some boards;
*) sftp - added functionality which imports ".auto.rsc" file or reboots router on ".auto.npk" upload;
*) trafficgen - fixed "lost-ratio" showing incorrect statistics after multiple sequences;

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

raffav · Wed Jul 26, 2017 2:52 pm

Hello everyone
I'm confused on the crs 125 series what is the best way,
Use the new vlan on bridge or stay using the switch menu?
Thanks.

Enviado de meu XT1580 usando Tapatalk

49er · Wed Jul 26, 2017 3:19 pm

raffav,

I Understand you.
I have the same.
VLAN on Mikrotik is very confussing

raymondr15 · Wed Jul 26, 2017 4:38 pm

Hi,

I am sitting in my office at work and have just update my RB2011UiAS-RM remotely, after rebooting the router am not able to access my router from the WAN side, my internet service provider is a WISP so I logged into my CPE and tried to SSH my router, I am able to login to the router but as soon as I login, the router stops responding for a few minutes and then comes back, same thing keeps happening when trying to SSH to the router. Will have to check the router when I get home.

Folks, don't upgrade your router if it is on a remote location

idlemind · Wed Jul 26, 2017 7:44 pm

New bridge is back!!!!!!! Super excited to test IPv6 pool prefix hinting assignments too. Might not be until next week though.

boldsuck · Thu Jul 27, 2017 1:09 am

RB2011UAS v6.41rc3
Bridge hardware offload is fine.

IPv6 address assignment is broken

State is 'invalid'

/ipv6 address
add address=::1/64 from-pool=netdsl-ipv6 interface=bridge-local advertise=yes

[admin@migo] /ipv6 address> print
Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local 
 #    ADDRESS                                     FROM-POOL INTERFACE                                                                                                    ADVERTISE
 0 IG ::1/64                                      netdsl... bridge-local                                                                                                 yes      
 1 DL fe80::d6ca:6dff:fea0:ff93/64                          bridge-local                                                                                                 no       
 2 DL fe80::d/64                                            pppoe-out1                                                                                                   no       
 3 DL fe80::d6ca:6dff:fea0:ff92/64                          ether1-gateway                                                                                               no

DHCPv6 prefix delegation from ISP is OK.

[admin@migo] /ipv6> dhcp-client print
Flags: D - dynamic, X - disabled, I - invalid 
 #    INTERFACE         STATUS        REQUEST        PREFIX                                                           ADDRESS                                                     
 0    pppoe-out1        bound         prefix         2001:4dd2:8c78::/48, 1d1h47m23s

Supout file was sent.

idlemind · Thu Jul 27, 2017 1:53 am

Hello everyone
I'm confused on the crs 125 series what is the best way,
Use the new vlan on bridge or stay using the switch menu?
Thanks.

Enviado de meu XT1580 usando Tapatalk

My understanding from the 6.40rc36 and 38 releases was that the switch chip menu was to not be used for ports not in a new bridge and ideally all configurations should move to the new VLAN aware hw-offload bridges.

I do recall a conflicting post from a MikroTik poster so clarification from own of the MikroTik folks would be great.

raffav · Thu Jul 27, 2017 2:04 am

Hello everyone
I'm confused on the crs 125 series what is the best way,
Use the new vlan on bridge or stay using the switch menu?
Thanks.

Enviado de meu XT1580 usando Tapatalk
My understanding from the 6.40rc36 and 38 releases was that the switch chip menu was to not be used for ports not in a new bridge and ideally all configurations should move to the new VLAN aware hw-offload bridges.

I do recall a conflicting post from a MikroTik poster so clarification from own of the MikroTik folks would be great.

I asked this because on here on wiki

https://wiki.mikrotik.com/wiki/Manual%3 ... Offloading

If you see the table of crs 1xx/2xx series
It have a - on bridge vlan filter

Enviado de meu XT1580 usando Tapatalk

romihg · Thu Jul 27, 2017 3:43 am

Upgrade from 6.40 last rc to 6.41.3 my 2011UiAS-2HnD all leds on active interfaces are off, Except led on eth10 is on witch is POE Out and is active. Is this normal or something wrong with this.

romihg · Thu Jul 27, 2017 4:05 am

Upgrade from 6.40 last rc to 6.41.3 my 2011UiAS-2HnD all leds on active interfaces are off, Except led on eth10 is on witch is POE Out and is active. Is this normal or something wrong with this.

Leds work on boot. But after router come in working state they switch off.

proximus · Thu Jul 27, 2017 4:43 am

Upgrade from 6.40 last rc to 6.41.3 my 2011UiAS-2HnD all leds on active interfaces are off,

Same here, LED's are dead (RB2011UiAS).

Thu Jul 27, 2017 9:18 am

Hello, we are aware that Ethernet LEDs do not work on RouterBoards with AR8327/QCA8337 switch chips in v6.41rc3 and look forward to fix it soon.

Thu Jul 27, 2017 9:31 am

My understanding from the 6.40rc36 and 38 releases was that the switch chip menu was to not be used for ports not in a new bridge and ideally all configurations should move to the new VLAN aware hw-offload bridges.

Currently, it is implemented only for CRS3xx series switches.

If you see the table of crs 1xx/2xx series
It have a - on bridge vlan filter

On CRS125 VLANs still have to be configured in "/interface ethernet switch" menu to keep hw-offload working. If they are configured in "/interface bridge vlan", the hw-offload will turn off.

idlemind · Thu Jul 27, 2017 12:12 pm

My understanding from the 6.40rc36 and 38 releases was that the switch chip menu was to not be used for ports not in a new bridge and ideally all configurations should move to the new VLAN aware hw-offload bridges.
Currently, it is implemented only for CRS3xx series switches.

If you see the table of crs 1xx/2xx series
It have a - on bridge vlan filter
On CRS125 VLANs still have to be configured in "/interface ethernet switch" menu to keep hw-offload working. If they are configured in "/interface bridge vlan", the hw-offload will turn off.

Becs, thanks for the clarification! While we're chatting. How do we mere mortals edit the wiki?

Thu Jul 27, 2017 1:02 pm

Only staff can edit the wiki

eworm · Fri Jul 28, 2017 12:06 pm

Successfully updated a CRS109-8G-1S-2HnD. Looks great, can't wait for this to be released in current!

!) bridge - implemented software based vlan-aware bridges;
https://wiki.mikrotik.com/wiki/Manual:I ... _Filtering

Before changing my configuration... Does MAC-based-VLAN work with this implementation?

Grickos · Fri Jul 28, 2017 5:52 pm

The VLAN does not work on the Atheros 8327 chip switch.
I create Bridge1 and add Ethernet1 and Ethernet2.
I'm creating VLAN20 on Bridge1 - there's still ok.
But when I add VLAN20 to Bridge2, RB is unavailable on these two ports.

Sorry about my English.

bratislav · Fri Jul 28, 2017 6:53 pm

Shouldn't VLAN be created on Ethernet port, not the bridge ...
Or you are trying Bridge VLAN Filtering and vlan-ids ...

I'm creating VLAN20 on Bridge1 - there's still ok.
But when I add VLAN20 to Bridge2, RB is unavailable on these two ports.

Grickos · Fri Jul 28, 2017 8:54 pm

Shouldn't VLAN be created on Ethernet port, not the bridge ...
Or you are trying Bridge VLAN Filtering and vlan-ids ...
I'm creating VLAN20 on Bridge1 - there's still ok.
But when I add VLAN20 to Bridge2, RB is unavailable on these two ports.

It does not work even if I put my vlan on ether1 or 2.
I want to get the old way tagged vlan20 on ports ether1,2,3 ... n (before master port1 and slave ether2,3, ... n)
Bridge strip Taging. I have DHCP server for vlan20.

It works great on chip switch Atheros 8227.
Simplified Example:

/interface bridge
add name=bridge1
add name=bridge2
add name=bridge3
/interface vlan
add interface=bridge1 name=vlan20 vlan-id=20
add interface=bridge1 name=vlan30 vlan-id=30
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether2
add bridge=bridge2 interface=vlan20
add bridge=bridge3 interface=vlan30

JanezFord · Fri Jul 28, 2017 10:55 pm

If you see the table of crs 1xx/2xx series
It have a - on bridge vlan filter
On CRS125 VLANs still have to be configured in "/interface ethernet switch" menu to keep hw-offload working. If they are configured in "/interface bridge vlan", the hw-offload will turn off.

Will there be shift to new syntax also for CRS125 series? It is a bit confusing to have to use different syntax for each product to get things done ...

JF.

idlemind · Sat Jul 29, 2017 2:55 am

If you see the table of crs 1xx/2xx series
It have a - on bridge vlan filter
On CRS125 VLANs still have to be configured in "/interface ethernet switch" menu to keep hw-offload working. If they are configured in "/interface bridge vlan", the hw-offload will turn off.
Will there be shift to new syntax also for CRS125 series? It is a bit confusing to have to use different syntax for each product to get things done ...

JF.

+1, one would hope it continues to move towards a singular syntax for VLAN configuration and let MikroTik ninja's translate that as needed in middleware into any fidgety model specific configuration options.

raffav · Sat Jul 29, 2017 5:33 am

+1
Agree, need to be more simple, no offense but the Cisco way it very simple
Switch port mode trunk/access
Switch port access vlan x
Switch port trunk allow vlan x,y,z

Enviado do meu iPad usando Tapatalk

Safic · Sat Jul 29, 2017 8:32 am

Shouldn't VLAN be created on Ethernet port, not the bridge ...
Or you are trying Bridge VLAN Filtering and vlan-ids ...
I'm creating VLAN20 on Bridge1 - there's still ok.
But when I add VLAN20 to Bridge2, RB is unavailable on these two ports.
It does not work even if I put my vlan on ether1 or 2.
I want to get the old way tagged vlan20 on ports ether1,2,3 ... n (before master port1 and slave ether2,3, ... n)
Bridge strip Taging. I have DHCP server for vlan20.

Grickos, just put your vlan interfaces at bridge1 and add bridge1 to tagged ports in
/interface bridge vlan

Jotne · Sat Jul 29, 2017 9:43 am

+1
Agree, need to be more simple, no offense but the Cisco way it very simple
Switch port mode trunk/access
Switch port access vlan x
Switch port trunk allow vlan x,y,z

+1

I have worked with HP: very simple vlan setup, Cisco: simple VLAN and others
On Mikrotik I have still not used VLAN, since I have problem to understand how it works.
Its way to complicated.

JimmyNyholm · Sat Jul 29, 2017 1:21 pm

Vlan is Hard to understand IF you used HP as they use the term tag/untagged (Their Ports are all hybrid and can't be trunk or access from the cisco perpspective.)

AccessPort = A port that is only accepting untaged frames on ingress and only output untaged frames on egress. All other frametypes is silently droped
TrunkPort = A port that only accepts tagged frames, all untaged frames is silently droped. it only egress taged frames.

Other have then invented shortcuts of that:

Hybrid = A port that accept both taged and untaged frames on ingress, untaged frames are assumed to belong to a native vlan. the same vlan can even recieve frames taged as beloning to it. Egres a hybrid port outputs as a trunk on all vlans and as an access port on the native vlan.

HP's implementation of only hybrid have stirred quit a few it guys in the field. The cisco way is cleaner and less error prone.

This is a Mikrotik forum and I who claims to understand .1q or qinq or qinqinqinq for one loves the freedom in mikrotik bridge being software layer, switch being hardware layer or at least I assume. Here i'm am currently not sure due to 6.41rc work.... but that will clear when it's done.

boldsuck · Sat Jul 29, 2017 1:32 pm

- ipv6 - fixed IPv6 address request from pool (introduced in 6.41rc1);

RB2011UAS v6.41rc1 - rc20
IPv6 address assignment is broken State is 'invalid'

Just for INFO:
MikroTik have managed to reproduce the problem. The error only occurs with me and a few others. MikroTik are working on it. But I fear this will remain an eternal bug.

I can live with the router not to reboot.

Since 6.41rc13 the DHCPv6 client has no more prefix. The IPv6 address could therefore not be assigned manually. Since 6.41rc20 gets the DHCPv6 client again a prefix which I then manually assigned.

I can not test the feature with the dynamic subprefix.
- Ippool6 - try to assign the requested prefix for client if prefix is not being already used;

Edit:
Damn, I'm stupid! I wanted to answer, do not edit. The forum is unfortunately not in the wayback machine so I can reverse that again. Sorry.

bratislav · Sat Jul 29, 2017 2:13 pm

It does not work even if I put my vlan on ether1 or 2.

It should be like this ... (if your vlans 20 and 30 are on ether2):

/interface bridge
add name=bridge1
add name=bridge2
add name=bridge3
/interface vlan
add interface=ether2 name=vlan20 vlan-id=20
add interface=ether2 name=vlan30 vlan-id=30
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=ether3
add bridge=bridge2 interface=vlan20
add bridge=bridge3 interface=vlan30

Check https://wiki.mikrotik.com/wiki/Manual:Interface/VLAN ...

Eduardo · Sat Jul 29, 2017 5:52 pm

On CRS125 VLANs still have to be configured in "/interface ethernet switch" menu to keep hw-offload working. If they are configured in "/interface bridge vlan", the hw-offload will turn off.

Beginners question: I am not using VLANs on CRS125, but was using masterport. Can I still use this masterport functionality? Or I need to go via VLANs now, to get hardware switching?!

Thanks.

idlemind · Sun Jul 30, 2017 6:05 am

Vlan is Hard to understand IF you used HP as they use the term tag/untagged (Their Ports are all hybrid and can't be trunk or access from the cisco perpspective.)

AccessPort = A port that is only accepting untaged frames on ingress and only output untaged frames on egress. All other frametypes is silently droped
TrunkPort = A port that only accepts tagged frames, all untaged frames is silently droped. it only egress taged frames.

Other have then invented shortcuts of that:

Hybrid = A port that accept both taged and untaged frames on ingress, untaged frames are assumed to belong to a native vlan. the same vlan can even recieve frames taged as beloning to it. Egres a hybrid port outputs as a trunk on all vlans and as an access port on the native vlan.

HP's implementation of only hybrid have stirred quit a few it guys in the field. The cisco way is cleaner and less error prone.

This is a Mikrotik forum and I who claims to understand .1q or qinq or qinqinqinq for one loves the freedom in mikrotik bridge being software layer, switch being hardware layer or at least I assume. Here i'm am currently not sure due to 6.41rc work.... but that will clear when it's done.

JimmyNyholm, a Cisco trunk port will pass both tagged or untagged traffic depending on the allowed VLAN list assigned to the trunk port (by default all VLANs are allowed). This is the "hybrid" behavior you're describing. Leaving the native VLAN routable on trunks is what exposes people to double tagging VLAN hop methods for what it's worth.

idlemind · Sun Jul 30, 2017 6:07 am

The VLAN does not work on the Atheros 8327 chip switch.
I create Bridge1 and add Ethernet1 and Ethernet2.
I'm creating VLAN20 on Bridge1 - there's still ok.
But when I add VLAN20 to Bridge2, RB is unavailable on these two ports.

Sorry about my English.

Grickos, I've not used VLANs in that fashion in any configurations. Looking at the new bridges I have been creating a single bridge and I add the interfaces as bridge ports. I also add all VLANs to this central bridge and adjust ports for tagged or an untagged VLAN as needed. I wouldn't expect two bridges to share information regarding the same VLAN without another bridge to glue them together.

idlemind · Sun Jul 30, 2017 8:22 am

Running the command:

/export

Hardware I tested against:

RouterBOARD 750G r3
RouterBOARD wAP G-5HacT2HnD
RouterBOARD cAP L-2nD

The result I see in the print-out:

#error exporting /system routerboard mode-button

I'm pretty sure it's benign but just thought I'd post it.

JimmyNyholm · Sun Jul 30, 2017 6:58 pm

JimmyNyholm, a Cisco trunk port will pass both tagged or untagged traffic depending on the allowed VLAN list assigned to the trunk port (by default all VLANs are allowed). This is the "hybrid" behavior you're describing. Leaving the native VLAN routable on trunks is what exposes people to double tagging VLAN hop methods for what it's worth.

Idlemind: you are right when talking to later 802.1q adaptations from cisco side. switchport mode trunk will still only accept taged frames on ingress (leaning back from the isl days before 802.q was ratified). You have to tell it to process untagged frames as well and that command is only available after certain version of the ios. We do agree upon that this will make even ciscos implementation leaning to hybrid.
My writing was to open up peoples mind to the idea of what is happening ingress and egress of a switchport, and to set some acronyms. To many techs think vlan is difficult when it's actually not just with the right mindset.

never connect vlan 0 from different vendors, never use spanning tree. Allways know what you are doing.

idlemind · Sun Jul 30, 2017 8:47 pm

JimmyNyholm, a Cisco trunk port will pass both tagged or untagged traffic depending on the allowed VLAN list assigned to the trunk port (by default all VLANs are allowed). This is the "hybrid" behavior you're describing. Leaving the native VLAN routable on trunks is what exposes people to double tagging VLAN hop methods for what it's worth.
Idlemind: you are right when talking to later 802.1q adaptations from cisco side. switchport mode trunk will still only accept taged frames on ingress (leaning back from the isl days before 802.q was ratified). You have to tell it to process untagged frames as well and that command is only available after certain version of the ios. We do agree upon that this will make even ciscos implementation leaning to hybrid.
My writing was to open up peoples mind to the idea of what is happening ingress and egress of a switchport, and to set some acronyms. To many techs think vlan is difficult when it's actually not just with the right mindset.

never connect vlan 0 from different vendors, never use spanning tree. Allways know what you are doing.

Ahh, ISL has been removed in the newer IOS XE based switching lines and you no longer have to express which encapsulation method you want to use.

I would disagree with you. I haven't been bit by the spanning-tree devil and am a firm proponent in it's use. It's definitely a best practice to use spanning-tree in switched networks. It will layer appropriately on top of other redundancy technologies like port-channels as well as protect you from loops.

Like you finished with though, knowing how to use the tool is critical. Spanning-tree with it's many variants and implementations can be difficult to master but it's absolutely essential for any portion of a network that's switched. I'll take slow (fast honestly with RSTP/MSTP) automated failover of my links any day of the week.

vacari · Mon Jul 31, 2017 3:52 am

Hello,
I have a RouterBOARD 3011UiAS
Firmware 3.35 version 6.41rc3
The activity led was disabled.

Thanks a lot.

Mon Jul 31, 2017 9:54 am

What's new in 6.41rc4 (2017-Jul-28 06:48):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

!) bridge - implemented software based vlan-aware bridges;
https://wiki.mikrotik.com/wiki/Manual:I ... _Filtering
!) switch - "master-port" conversion into a bridge with hardware offload "hw" option (CLI only);
https://wiki.mikrotik.com/wiki/Manual:S ... Offloading
!) bridge - general development of hw-offload bridge implementation (introduced in v6.40rc36);
*) bridge - show "admin-mac" only if "auto-mac=no";
*) rb922 - restored missing wireless interface on some boards;

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

idlemind · Mon Jul 31, 2017 7:28 pm

What's new in 6.41rc3 (2017-Jul-26 09:32):
*) ippool6 - try to assign desired prefix for client if prefix is not being already used;

Strods, this is implemented in the IPv6 pool code now but it doesn't seem to be implemented in the address assignment code yet, correct?

[admin@rtr1] > ipv6 address add    
address  advertise  comment  copy-from  disabled  eui-64  from-pool  no-dad  interface

I'm hoping we'll be getting an option to like "pref-prefix" where we can hint what prefix we'd like. Think a prefix of 11 for VLAN11 when getting a /56 assignment from the ISP for that networks /64. Ensuring devices remain some semblance of consistent IPs and keep us administrators sane.

bruins0437 · Tue Aug 01, 2017 6:05 am

Running the command:
Code: Select all
/export
Hardware I tested against:

RouterBOARD 750G r3

RouterBOARD wAP G-5HacT2HnD

RouterBOARD cAP L-2nD
The result I see in the print-out:
Code: Select all
#error exporting /system routerboard mode-button
I'm pretty sure it's benign but just thought I'd post it.

Same issue on RouterBoard 2011. Also "Run After" appears to be broken too,it will not load exported .rsc file. Mikrotik ends up rebooting with no config at all.

-Eric

Tue Aug 01, 2017 3:07 pm

What's new in 6.41rc6 (2017-Aug-01 11:30):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

*) btest - improved reliability on Bandwidth Test when device`s RAM is almost full;
*) dhcpv6-client - do not run DHCPv6 client when IPv6 package is disabled;
*) ipv6 - fixed IPv6 address request from pool (introduced in 6.41rc1);
*) lte - fixed LTE not passing any traffic while in running state;
*) ppp - added support for Sierra MC7750, Verizon USB730L;
*) torch - fixed Torch on PPP tunnels (introduced in 6.40);

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

slimmerwifi · Tue Aug 01, 2017 6:16 pm

We have tested a freshly configured Hap AC with 6.41rc4 and getting large amounts of Radar detect in Regulatory domain.

Accespoint is only usable in super channel mode.

We are in a bank building so no actual radar here

Available for debugging.

boldsuck · Tue Aug 01, 2017 8:08 pm

*) ipv6 - fixed IPv6 address request from pool (introduced in 6.41rc1);

To the half it goes.

[admin@migo] /ipv6 address> add address=::1/64 from-pool=netdsl-ipv6 interface=bridge-local advertise=yes
[admin@migo] /ipv6 address> print
Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local 
 #    ADDRESS                                     FROM-POOL INTERFACE                                                                                                                                                                                                ADVERTISE
 0 DL fe80::d6ca:6dff:fea0:ff93/64                          bridge-local                                                                                                                                                                                             no       
 1 DL fe80::d6ca:6dff:fea0:ff92/64                          ether1-gateway                                                                                                                                                                                           no       
 2 DL fe80::d/64                                            pppoe-out1                                                                                                                                                                                               no       
 3  G 2001:4dd2:a7c1::1/64                        netdsl... bridge-local                                                                                                                                                                                             yes

It works

...but...

[admin@migo] /system> reboot
...
[admin@migo] /ipv6 address> print
Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local 
 #    ADDRESS                                     FROM-POOL INTERFACE                                                                                                                                                                                                ADVERTISE
 0 IG 2001:4dd2:a7c1::1/64                        netdsl... bridge-local                                                                                                                                                                                             yes      
 1 DL fe80::d6ca:6dff:fea0:ff93/64                          bridge-local                                                                                                                                                                                             no       
 2 DL fe80::d/64                                            pppoe-out1                                                                                                                                                                                               no       
 3 DL fe80::d6ca:6dff:fea0:ff92/64                          ether1-gateway                                                                                                                                                                                         no

Damn it! After reboot again invalid.

[admin@migo] /ipv6 address> remove
numbers: 0
[admin@migo] /ipv6 address> add address=::1/64 from-pool=netdsl-ipv6 interface=bridge-local advertise=yes
[admin@migo] /ipv6 address> print
Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local 
 #    ADDRESS                                     FROM-POOL INTERFACE                                                                                                                                                                                                ADVERTISE
 0 DL fe80::d6ca:6dff:fea0:ff93/64                          bridge-local                                                                                                                                                                                             no       
 1 DL fe80::d/64                                            pppoe-out1                                                                                                                                                                                               no       
 2 DL fe80::d6ca:6dff:fea0:ff92/64                          ether1-gateway                                                                                                                                                                                           no       
 3  G 2001:4dd2:a7c8::1/64                        netdsl... bridge-local

It works again.
Workaround. Don't reboot router

Or delete and re-add after each reboot.

Tue Aug 01, 2017 11:47 pm

*) ippool6 - try to assign desired prefix for client if prefix is not being already used;

So how do I use this feature?

Suppose my pool prefix is 2001:db8

:/48 and I wish to assign subprefix 1234::1/64 from this pool onto interface ether1. How do I enter this?
Suppose further that I wish to define this in such a way that if the prefix changes in the future that I don't need to change anything in the router.
I.e. if tomorrow, my dhcpv6-client receives pool 2001:db8:4567::/48, then ether1 should change automatically:
from 2001:db8:abcd

:1/64
to 2001:db8:4567:1234::1/64

Or does this feature only apply to dhcpv6 PD server?

Wed Aug 02, 2017 2:32 pm

What's new in 6.41rc7 (2017-Aug-02 09:51):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

*) export - fixed export for different parameters where numerical range or constant string is expected;
*) ovpn-client - fixed incorrect netmask usage for pushed routes;
*) pppoe-client - fixed incorrectly formed PADT packet;
*) winbox - added "none-dynamic" and "none-static" options for "address-list-timeout" parameter under NAT, Mangle and RAW rules;
*) winbox - do not show duplicate filter parameters "Published" in ARP list;
*) winbox - show warnings under "/system routerboard settings" menu;

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

boldsuck · Wed Aug 02, 2017 8:42 pm

*) ippool6 - try to assign desired prefix for client if prefix is not being already used;
So how do I use this feature?

Suppose my pool prefix is 2001:db8:/48 and I wish to assign subprefix 1234::1/64 from this pool onto interface ether1. How do I enter this?
Suppose further that I wish to define this in such a way that if the prefix changes in the future that I don't need to change anything in the router.

I get a new dynamic IPv6 prefix every time from my ISP after each reconnect or after 26 hours. (with IPv6-DHCP-Client)
Adding ::1/64 to this dynamic IPv6 prefix runs here over 4 years. A subprefix abcd::1/64, I have not yet tested. I will try the days. (If 'IPv6 address request from pool' is fixed in the rc version)

This works, the dynamic prefix is added automatically:
/ipv6 address> add address=::1/64 from-pool=ISP-pool-ipv6 interface=bridge-local advertise=yes

2001:db8

:1/64
2001:db8:0123::1/64
2001:db8:4567::1/64

Thu Aug 03, 2017 10:19 am

Everyone who is experiencing issues with DHCPv6 client - we will have a potential fix for this problem in next 6.41rc version. Please test it when it comes available and report to support@mikrotik.com with results. If fix will help, then we will also include in upcoming current versions.

th0massin0 · Thu Aug 03, 2017 2:17 pm

*) lte - fixed LTE not passing any traffic while in running state;

Problem with reliability of SXT LTE still exists (now: PLMN search in progress) - ROS 6.41rc7.

Thu Aug 03, 2017 4:06 pm

What's new in 6.41rc9 (2017-Aug-03 12:02):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

*) certificate - fixed SCEP "get" request URL encoding;
*) dhcpv6-client - fixed IA evaluation order;
*) l2tp-server - fixed PPP services becoming unresponsive after changes on L2TP server with IPSec configuration;
*) lcd - fixed LCD blinking on RB2011 (introduced in 6.40);
*) lte - added initial passthrough support for wAP LTE;
*) pppoe-client - fixed wrong auto MRU detection over VLAN interfaces;
*) pppoe-server - fixed situation when PPPoE servers become invalid after reboot;
*) sfp - fixed invalid temperature readings when ambient temperature is below 0C;

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

proximus · Thu Aug 03, 2017 5:07 pm

LED's on RB2011 were working again on rc7. With rc9, there are on solid (with link), no activity blinking.

Thu Aug 03, 2017 10:30 pm

LEDs will be fixed again in the next rc release.

juliokato · Thu Aug 03, 2017 11:44 pm

Does the mikrotik development team have no change control? (Cvs)
Bugs always return.....

heaven · Fri Aug 04, 2017 8:04 am

RB2011. pppoe-client from my provider was stop working after upgrade on rc9. Downgrade to stable release.

Fri Aug 04, 2017 10:12 am

heaven - Please send supout file to support@mikrotik.com. Generate it while PPPoE client is not working. We have tested it locally and in general PPPoE client is working as suspected. There must be something very specific.

heaven · Fri Aug 04, 2017 7:38 pm

heaven - Please send supout file to support@mikrotik.com. Generate it while PPPoE client is not working. We have tested it locally and in general PPPoE client is working as suspected. There must be something very specific.

I was already send it! Thank you for your job, guys!

romihg · Sat Aug 05, 2017 10:21 am

Reseting router with /system reset-configuration is the same as /system reset-configuration no-defaults option. So no defaults loaded on boot.

2011UiAS-2HnD with 6.41.9rc

manyyy · Sat Aug 05, 2017 3:52 pm

I have an issue with 6.41.rc9 on RB751G-2HnD.

After upgrade from channel=current 6.40 there is no interface pppoe-client created.
Even if I add this manualy, it wont connect to the DSL BRAS.
Seems that something is wrong with Link Control Protocol.

Log debug below:

14:17:45 pppoe,ppp,debug netia: LCP lowerdown
14:17:45 pppoe,ppp,debug netia: LCP down event in initial state
14:17:45 pppoe,ppp,info netia: disconnected
14:17:55 pppoe,ppp,info netia: initializing...
14:17:55 pppoe,ppp,info netia: connecting...
14:18:05 pppoe,ppp,info netia: terminating... - disconnected

Downgrading to 6.40.1 everything goes back to operational.

idlemind · Mon Aug 07, 2017 9:35 pm

Working on a new RB750Gr3 (hex). I installed 6.41rc9 and I'm unable to get an access port working for a VLAN on the new VLAN aware bridges. A similar configuration is working on a RB750Gr3 running 6,41rc6.

  MMM      MMM       KKK                          TTTTTTTTTTT      KKK
  MMMM    MMMM       KKK                          TTTTTTTTTTT      KKK
  MMM MMMM MMM  III  KKK  KKK  RRRRRR     OOOOOO      TTT     III  KKK  KKK
  MMM  MM  MMM  III  KKKKK     RRR  RRR  OOO  OOO     TTT     III  KKKKK
  MMM      MMM  III  KKK KKK   RRRRRR    OOO  OOO     TTT     III  KKK KKK
  MMM      MMM  III  KKK  KKK  RRR  RRR   OOOOOO      TTT     III  KKK  KKK

  MikroTik RouterOS 6.41rc9 (c) 1999-2017       http://www.mikrotik.com/

[?]             Gives the list of available commands
command [?]     Gives help on the command and list of arguments

[Tab]           Completes the command/word. If the input is ambiguous,
                a second [Tab] gives possible options

/               Move up to base level
..              Move up one level
/command        Use command at the base level

[admin@rtr1] > export
# aug/07/2017 13:27:40 by RouterOS 6.41rc9
# software id = 247N-DPAI
#
# model = RouterBOARD 750G r3
# serial number = xxxxxxxxxxxx
/interface bridge
add admin-mac=6C:3B:6B:bb:xx:yy auto-mac=no fast-forward=no igmp-snooping=no name=br1 vlan-filtering=yes
/interface ethernet
set [ find default-name=ether1 ] name=eth1
set [ find default-name=ether2 ] name=eth2
set [ find default-name=ether3 ] name=eth3
set [ find default-name=ether4 ] name=eth4
set [ find default-name=ether5 ] name=eth5
/ip neighbor discovery
set eth1 discover=no
/interface vlan
add interface=br1 name=br1-vlan11 vlan-id=11
add interface=br1 name=br1-vlan12 vlan-id=12
add interface=br1 name=br1-vlan999 vlan-id=999
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip hotspot profile
set [ find default=yes ] html-directory=flash/hotspot
/ip pool
add name=default-dhcp ranges=192.168.88.10-192.168.88.254
add name=vlan11 ranges=10.214.11.100-10.214.11.199
add name=vlan12 ranges=10.214.11.100-10.214.11.199
add name=vlan13 ranges=10.214.11.100-10.214.11.199
/ip dhcp-server
add address-pool=default-dhcp disabled=no interface=br1 name=defconf
add address-pool=vlan11 disabled=no interface=br1-vlan11 name=vlan11
add address-pool=vlan12 disabled=no interface=br1-vlan12 name=vlan12
/interface bridge port
add bridge=br1 hw=no interface=eth2 pvid=11
add bridge=br1 hw=no interface=eth3
add bridge=br1 hw=no interface=eth4
add bridge=br1 hw=no interface=eth5
/interface bridge vlan
add bridge=br1 untagged=eth2 vlan-ids=11
/ip address
add address=192.168.88.1/24 comment=defconf interface=br1 network=192.168.88.0
add address=10.214.11.254/24 interface=br1-vlan11 network=10.214.11.0
add address=10.214.12.254/24 interface=br1-vlan12 network=10.214.12.0
/ip dhcp-client
add comment=defconf dhcp-options=hostname,clientid disabled=no interface=eth1
/ip dhcp-server network
add address=10.214.11.0/24 dns-server=10.214.0.1 domain=123.local gateway=10.214.11.254
add address=10.214.12.0/24 dns-server=10.214.0.1 domain=123.local gateway=10.214.12.254
add address=192.168.88.0/24 comment=defconf gateway=192.168.88.1
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.88.1 name=router.lan
/ip firewall nat
add action=masquerade chain=srcnat ipsec-policy=out,none out-interface=eth1
/system package update
set channel=release-candidate
#error exporting /system routerboard mode-button
/tool mac-server
set [ find default=yes ] disabled=yes
add interface=br1
add interface=br1-vlan11
/tool mac-server mac-winbox
set [ find default=yes ] disabled=yes
add interface=br1
add interface=br1-vlan11

A packet capture shows STP frames and discovery frames from the relevant VLAN interface, in this case br-vlan11, but does not seem to forward other traffic. I'm unable to mac-telnet into the router despite allowing it on the br1-vlan11 interface. I cannot ping the IP address assigned to br-vlan11 despite seeing it in the CDP message in WireShark (both interface and IP).

Wed Aug 09, 2017 12:37 pm

What's new in 6.41rc11 (2017-Aug-08 09:32):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

*) bridge - added initial support for hardware "igmp-snooping" on CRS1xx/2xx (CLI only);
*) bridge - automatically turn off "fast-forward" feature if both bridge ports have "H" flag;
*) export - fixed interface list export;
*) ike1 - release mismatched PH2 peer IDs;
*) ike2 - check identities on "initial-contact";
*) ike2 - use peer configuration address when available on empty TSi;
*) interface - fixed corrupted "/interface list" configuration after upgrade;
*) ipsec - allow to specify remote peer address as DNS name (CLI only);
*) ipsec - renamed "firewall" argument to "notrack-chain" in peer configuration;
*) led - fixed "modem-signal" LEDs (introduced in 6.40);
*) modem - added initial support for Alcatel IK40 and Olicard 500;
*) rb2011 - fixed possible LCD blinking along with ethernet LED (introduced in 6.40);
*) rb750gr3 - show warning and do not allow to use "protected-bootloader" feature if "factory-firmware" older than 3.34.4 version;
*) ups - fixed duplicate "failed" UPS logs;
*) winbox - added certificate settings;
*) winbox - added support fro certificate CRL list;
*) winbox - do not show duplicate "Template" parameters for filter in IPSec policy list;
*) winbox - fixed bridge port sorting order by interface name;
*) winbox - hide "level" and "tunnel" parameters for IPSec policy templates;
*) winbox - hide FAN speed if it is 0RPM;
*) wireless - added "russia3" country settings;

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

osc86 · Wed Aug 09, 2017 1:47 pm

*) ipsec - allow to specify remote peer address as DNS name (CLI only);

does this mean ipsec tunnels can be established between 2 sites with dynamic ip addresses, so I can get rid of the additional L2TP Tunnel?

mrz · Wed Aug 09, 2017 2:01 pm

In road warrior setups, yes.

heaven · Wed Aug 09, 2017 5:12 pm

PPPoE Client problem that I was wrote earlier is not solved in new RC. The Mikrotik support in mail was promised to me that it was been solved in future new rc((((
P.S. don' t use remote upgrade. pppoe client will not start automatically. After upgrade need to turnoff/turnon pppoe physical interface. Than pppoe client will work.

PeterFreeman · Wed Aug 09, 2017 9:32 pm

Hi all,

The LED issue on the SXT LTE is still not fixed in 6.41.rc11 but it is getting a little closer...
The LED's on the back of the SXT LTE now respond to signal strength but the scale is off. Without moving our bench SXT LTE device, it shows 3-4 LEDs of signal whilst running 6.39.2. Post upgrade to 6.41.rc11 the LEDs only show 2 bars and it does not fluctuate when the signal is either improved or degraded with any significance.
The webfig interface graphs are also still broken. The graph scale is between -40 and -120 dB but eh signal is being metered in 65xxx figures. Chupaka previously noted in the 6.40 release notes that this is probably due to using the wrong DWORD in the code?

Over to you MikroTik

Many thanks

Pete.

idlemind · Thu Aug 10, 2017 1:46 am

New bridge with VLANs still appears broken on my test RB750Gr3 for anything later than 6.41rc6. I can't seem to get NetInstall to work on Windows 10 to try jumping backwards to 6.41rc6 to confirm 100% that is the case. I'm holding off upgrading a production RB750Gr3 past 6.41rc6 where a similar configuration is working without issue.

Packets are received on an interface at the Ethernet level and I can see the counters increment. I do not see it increase the counters on the VLAN interface though.

/interface bridge vlan add bridge=br1 untagged=eth2 vlan-ids=11
/interface vlan add add interface=br1 name=br1-vlan11 vlan-id=11
/interface bridge port add bridge=br1 hw=no interface=eth2 pvid=11
/ip address add interface=br-vlan11 address=10.214.11.254/24

snowflake · Fri Aug 11, 2017 10:37 am

[quote="manyyy"]I have an issue with 6.41.rc9 on RB751G-2HnD.

I have similar problem with PPPoE on RB751G-2HnD with
6.41rc11. Even after reboot the PPPoE link does not activate.
I reconfigured it manually. Still did not work.

I tried unplugging and replugging the Ethernet cable
and the link sprang into life, so it's partially solved.

snowflake · Fri Aug 11, 2017 10:38 am

[quote="manyyy"]I have an issue with 6.41.rc9 on RB751G-2HnD.

I have similar problem with PPPoE on RB751G-2HnD with
6.41rc11. Even after reboot the PPPoE link does not activate.
I reconfigured it manually. Still did not work.

I tried unplugging and replugging the Ethernet cable
and the link sprang into life, so it's partially solved.

erreferre · Fri Aug 11, 2017 10:45 am

*) sftp - added functionality which imports ".auto.rsc" file or reboots router on ".auto.npk" upload;

How can I test this new feature?

Fri Aug 11, 2017 10:57 am

make a new plain text file with contents:

/system identity set name=ITWORKS

Save this file with name test.auto.rsc

Then upload it with SFTP. Check what your identity name is now.

erreferre · Fri Aug 11, 2017 11:35 am

make a new plain text file with contents:
Code: Select all
/system identity set name=ITWORKS
Save this file with name test.auto.rsc

Then upload it with SFTP. Check what your identity name is now.

Yes, with the SFTP client of my computer. But I thought it could be possible to transfer files between MikroTik routers with a native sftp client or with a new fetch mode=sftp.
Thanks,

idlemind · Fri Aug 11, 2017 7:10 pm

make a new plain text file with contents:
Code: Select all
/system identity set name=ITWORKS
Save this file with name test.auto.rsc

Then upload it with SFTP. Check what your identity name is now.

So, if I rename the 6.41rc6 .npk file to 6.41rc6.auto.npk and upload it a RouterBoard it will reboot into 6.41rc6?

raffav · Fri Aug 11, 2017 11:00 pm

Hello

is there any problem on PPPOE-out?

after upgrade they desapear.

snowflake · Sat Aug 12, 2017 2:55 pm

Hello

is there any problem on PPPOE-out?

after upgrade they desapear.

pppoe-client configs disappear after upgrade.
It also invalidates the firewall and NAT configs because the interface has disappeared.

I reinstall the pppoe-client config and try enabling pppoe-client.
I monitor the interface but nothing happens.
I unplug and re-insert the Ethernet lead and the pppoe-out1 interface springs into life.

All this is on RB751G-2HnD

raffav · Sat Aug 12, 2017 4:34 pm

Hello

is there any problem on PPPOE-out?

after upgrade they desapear.
pppoe-client configs disappear after upgrade.
It also invalidates the firewall and NAT configs because the interface has disappeared.

I reinstall the pppoe-client config and try enabling pppoe-client.
I monitor the interface but nothing happens.
I unplug and re-insert the Ethernet lead and the pppoe-out1 interface springs into life.

All this is on RB751G-2HnD

Even ir I recreate ir it don't work
The config is there but invisible lol,
If i go back to current release it show up again and working.

Enviado de meu XT1580 usando Tapatalk

idlemind · Sat Aug 12, 2017 6:58 pm

make a new plain text file with contents:
Code: Select all
/system identity set name=ITWORKS
Save this file with name test.auto.rsc

Then upload it with SFTP. Check what your identity name is now.
So, if I rename the 6.41rc6 .npk file to 6.41rc6.auto.npk and upload it a RouterBoard it will reboot into 6.41rc6?

So, it works for newer versions but not older versions. MikroTik please make it so you can downgrade RouterOS through this mechanic. If necessary make it a boolean value in the /ip service sftp settings to toggle allow/disallow software downgrades.

doneware · Tue Aug 15, 2017 5:50 pm

So, it works for newer versions but not older versions. MikroTik please make it so you can downgrade RouterOS through this mechanic. If necessary make it a boolean value in the /ip service sftp settings to toggle allow/disallow software downgrades.

on the older versions this works just with ftp.
but there's nothing a consecutive sftp and ssh cannot fix, right

scp yourcommandfile.rsc admin@router:
ssh admin@router '/import file-name=yourcommandfile.rsc; /file remove [find where name="yourcommandfile.rsc"]'

the only thing you lose is the output log.

idlemind · Tue Aug 15, 2017 6:13 pm

To be clear I was talking only about uploading a .npk file to the device for the purpose of installing a different version of RouterOS.

It allows you to upgrade (newer code) but not downgrade (older code). As an example you can up to 6.41rc11 by uploading the code file. Once in that version you cannot upload 6.41rc7. You only get a syslog message saying it's an older version.

I'm looking for a way without netinstall to allow that action.

doneware · Tue Aug 15, 2017 6:30 pm

I'm looking for a way without netinstall to allow that action.

sorry.
put your npk files on the /file section, then do a

[bat@hgw2] /ip firewall nat> /sys package downgrade

it will ask for confirmation on reload, and then install whatever version you have on the files, so yes it is the way you downgrade your OS.
i hope i got it right this time.

Wed Aug 16, 2017 1:19 pm

What's new in 6.41rc13 (2017-Aug-15 13:09):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

*) bridge - added initial support for hardware "igmp-snooping" on CRS1xx/2xx (CLI only);
*) bridge - implemented software based "igmp-snooping" (CLI only);
*) bridge - removed "master-port" parameter (CLI only);
*) certificate - fixed import of certificates with empty SKID;
*) dhcp - require DHCP option name to be unique;
*) dhcpv6-client - ignore unknown IA;
*) hotspot - fixed missing "/ip hotspost server profile" if invalid "dns-name" was specified;
*) interface - added option to join and exclude "/interface list" from one and another;
*) lte - improved FastPath support for SXT LTE;
*) lte - added multi APN passthrough support for wAP LTE;
*) lte - do not show USB LTE modem under "/port" menu (introduced in 6.41rc);
*) lte - improved reliability of USB LTE modems;
*) lte - properly recognize USB devices under "/system resource usb" (introduced in 6.41rc12);
*) rb750gr3 - show warning and do not allow to use "protected-bootloader" feature if "factory-firmware" older than 3.34.4 version;

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

eworm · Wed Aug 16, 2017 3:49 pm

I am having issues with CAPsMAN on 6.41rc13... Looks like cap interfaces with CAPsMAN forwarding do not pass any traffic.

horza · Wed Aug 16, 2017 5:42 pm

6.41rc11 -> 6.41rc13 broke my bridge on x86.
The bridge is still there, I can disable and enable it, but it registeres as "not ready" everywhere (firewall, ip...)
In an attempt to fix it, I've deleted the bridge and created a new one with default options and cleared bridge>settings, but the new bridge exhibits same behavior - "not ready" reported by ip, firewall, etc.
I've managed to nicely downgrade back to 6.41rc11 without any config changes, and it works just fine.

I've got a mipsbe test router that's configured almost identically, and that one upgraded nicely and no bridge problems (same bridge configuration as on x86 machine).
No need for help; just reporting an issue for your consideration

idlemind · Wed Aug 16, 2017 9:09 pm

I'm looking for a way without netinstall to allow that action.
sorry.
put your npk files on the /file section, then do a
Code: Select all
[bat@hgw2] /ip firewall nat> /sys package downgrade
it will ask for confirmation on reload, and then install whatever version you have on the files, so yes it is the way you downgrade your OS.
i hope i got it right this time.

Thank you!!!! Nice and convenient way to downgrade. Exactly what I was after.

idlemind · Thu Aug 17, 2017 3:40 am

EDIT: I'm able to replicate the problem the x86 (CHR in my case) problem as well. IP address goes invalid as soon as it's added to a VLAN interface. That said, it works fine on my RB750Gr3 now.

Thu Aug 17, 2017 2:50 pm

idlemind - Which type of interface is the master interface of VLAN?

idlemind · Thu Aug 17, 2017 4:37 pm

idlemind - Which type of interface is the master interface of VLAN?

A bridge. If br1 is the VLAN aware bridge the master interface of the VLAN is br1.

kobuki · Thu Aug 17, 2017 10:46 pm

With the new bridge implementation using HW offload, will it be possible to use multiple bridges using the offload capability, effectively creating multiple "switch groups" that retain wire speed in the group? It's now possible to do something similar using VLANs where each VLAN has a CPU port besides the physical ports. Would the new bridge implementation automatically create VLANs to provide such a setup?

heaven · Fri Aug 18, 2017 7:41 am

PPPoE failed problem was not solved in new RC. My question is - When?

Fri Aug 18, 2017 1:57 pm

What's new in 6.41rc15 (2017-Aug-18 07:33):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

*) capsman - added "vlan-mode=no-tag" option (CLI only);
*) capsman - return complete CA chain when issuing new certificate;
*) export - fixed "/system routerboard" export (introduced in 6.40.1);
*) ike1 - fixed initiator ID comparison to NAT-OA;
*) led - fixed "on" and "off" triggers when multiple LEDs are selected;
*) lte - added passthrough support (CLI only);
*) ospf - fixed OSPF v2 and v3 neighbor election;
*) rb1100ahx4 - fixed HW acceleration fragmented packet decryption when fragment is smaller than 64 bytes;
*) routerboard - added "mode-button" support for RB750Gr3 (CLI only);
*) sfp - fixed SFP interface power monitor when bad SFP DDMI information is received;
*) ssh - do not execute command if it starts with "-" symbol;
*) wireless - added New Zealand regulatory domain information for P2P links;
*) wireless - updated China and New Zealand regulatory domain 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 suspected or after crash.

th0massin0 · Fri Aug 18, 2017 2:12 pm

What's new in 6.41rc15 (2017-Aug-18 07:33):
*) lte - added passthrough support (CLI only);

Is it available for SXT LTE?

Fri Aug 18, 2017 2:59 pm

Unfortunately, currently SXT LTE does not support passthrough mode.

irghost · Fri Aug 18, 2017 4:13 pm

*) lte - added passthrough support (CLI only);

where? i cant find it

Fri Aug 18, 2017 4:29 pm

Please remember that this is rc version - new features appear, are tested, etc. Documentation, GUI support, etc. for new features might not appear right away. Also features are not fully tested yet.

LTE Passthrough is described here:
https://wiki.mikrotik.com/wiki/Manual:I ... assthrough

Soon supported LTE devices also will be listed here:
https://wiki.mikrotik.com/wiki/Supporte ... and_modems

Fri Aug 18, 2017 5:07 pm

What's new in 6.41rc16 (2017-Aug-18 13:44):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

*) ipsec - added DH groups 19, 20 and 21 support for phase1 and phase2 (CLI only);
*) lcd - fixed unresponsive LCD (introduced in 6.41rc15);
*) lte - added passthrough support (CLI only);
*) traffic-flow - fixed reboots when IPv6 address has been set as target address without active IPv6 package;

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

bommi · Fri Aug 18, 2017 5:44 pm

*) ipsec - added DH groups 19, 20 and 21 support for phase1 and phase2 (CLI only);

Is there a chance to get support for brainpool ec curves like DH group 28, 29 and 30?

irghost · Fri Aug 18, 2017 5:57 pm

What's new in 6.41rc16 (2017-Aug-18 13:44):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

*) ipsec - added DH groups 19, 20 and 21 support for phase1 and phase2 (CLI only);
*) lcd - fixed unresponsive LCD (introduced in 6.41rc15);
*) lte - added passthrough support (CLI only);
*) traffic-flow - fixed reboots when IPv6 address has been set as target address without active IPv6 package;

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

passthrough Works With E3372 Hilink Mode RB750Gr3

/interface lte set lte1 apn=apn1/vlan600

heaven · Sat Aug 19, 2017 11:01 am

In RC16 PPPoE failed too. Can Support ask me when it will be solved? I think im not alone who faced with this problm.

b3h3m07h · Sun Aug 20, 2017 8:01 am

still having issues with RB2011UAS-2HnD and optus (aus) Huawei E3372h-607 http://www.optus.com.au/shop/prepaid/mo ... /usb/e3372

under load, p2p , multiple users on netflix or youtube, router reboots.

klaus007 · Sun Aug 20, 2017 9:31 pm

Hallo!
After updating a RB922 with a Huawei ME909s-120 modem to 6.41RC16, the lte-interface doesn't switch in running mode. The status of the interface shows only one information: "Functionality == minimal", nothing else.
Is this a normal behavior in case of lte-passthrough or a bug?

regards

branto · Mon Aug 21, 2017 2:17 am

Working on a new RB750Gr3 (hex). I installed 6.41rc9 and I'm unable to get an access port working for a VLAN on the new VLAN aware bridges. A similar configuration is working on a RB750Gr3 running 6,41rc6.

  MMM      MMM       KKK                          TTTTTTTTTTT      KKK
  MMMM    MMMM       KKK                          TTTTTTTTTTT      KKK
  MMM MMMM MMM  III  KKK  KKK  RRRRRR     OOOOOO      TTT     III  KKK  KKK
  MMM  MM  MMM  III  KKKKK     RRR  RRR  OOO  OOO     TTT     III  KKKKK
  MMM      MMM  III  KKK KKK   RRRRRR    OOO  OOO     TTT     III  KKK KKK
  MMM      MMM  III  KKK  KKK  RRR  RRR   OOOOOO      TTT     III  KKK  KKK

  MikroTik RouterOS 6.41rc9 (c) 1999-2017       http://www.mikrotik.com/

[?]             Gives the list of available commands
command [?]     Gives help on the command and list of arguments

[Tab]           Completes the command/word. If the input is ambiguous,
                a second [Tab] gives possible options

/               Move up to base level
..              Move up one level
/command        Use command at the base level

[admin@rtr1] > export
# aug/07/2017 13:27:40 by RouterOS 6.41rc9
# software id = 247N-DPAI
#
# model = RouterBOARD 750G r3
# serial number = xxxxxxxxxxxx
/interface bridge
add admin-mac=6C:3B:6B:bb:xx:yy auto-mac=no fast-forward=no igmp-snooping=no name=br1 vlan-filtering=yes
/interface ethernet
set [ find default-name=ether1 ] name=eth1
set [ find default-name=ether2 ] name=eth2
set [ find default-name=ether3 ] name=eth3
set [ find default-name=ether4 ] name=eth4
set [ find default-name=ether5 ] name=eth5
/ip neighbor discovery
set eth1 discover=no
/interface vlan
add interface=br1 name=br1-vlan11 vlan-id=11
add interface=br1 name=br1-vlan12 vlan-id=12
add interface=br1 name=br1-vlan999 vlan-id=999
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip hotspot profile
set [ find default=yes ] html-directory=flash/hotspot
/ip pool
add name=default-dhcp ranges=192.168.88.10-192.168.88.254
add name=vlan11 ranges=10.214.11.100-10.214.11.199
add name=vlan12 ranges=10.214.11.100-10.214.11.199
add name=vlan13 ranges=10.214.11.100-10.214.11.199
/ip dhcp-server
add address-pool=default-dhcp disabled=no interface=br1 name=defconf
add address-pool=vlan11 disabled=no interface=br1-vlan11 name=vlan11
add address-pool=vlan12 disabled=no interface=br1-vlan12 name=vlan12
/interface bridge port
add bridge=br1 hw=no interface=eth2 pvid=11
add bridge=br1 hw=no interface=eth3
add bridge=br1 hw=no interface=eth4
add bridge=br1 hw=no interface=eth5
/interface bridge vlan
add bridge=br1 untagged=eth2 vlan-ids=11
/ip address
add address=192.168.88.1/24 comment=defconf interface=br1 network=192.168.88.0
add address=10.214.11.254/24 interface=br1-vlan11 network=10.214.11.0
add address=10.214.12.254/24 interface=br1-vlan12 network=10.214.12.0
/ip dhcp-client
add comment=defconf dhcp-options=hostname,clientid disabled=no interface=eth1
/ip dhcp-server network
add address=10.214.11.0/24 dns-server=10.214.0.1 domain=123.local gateway=10.214.11.254
add address=10.214.12.0/24 dns-server=10.214.0.1 domain=123.local gateway=10.214.12.254
add address=192.168.88.0/24 comment=defconf gateway=192.168.88.1
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.88.1 name=router.lan
/ip firewall nat
add action=masquerade chain=srcnat ipsec-policy=out,none out-interface=eth1
/system package update
set channel=release-candidate
#error exporting /system routerboard mode-button
/tool mac-server
set [ find default=yes ] disabled=yes
add interface=br1
add interface=br1-vlan11
/tool mac-server mac-winbox
set [ find default=yes ] disabled=yes
add interface=br1
add interface=br1-vlan11

A packet capture shows STP frames and discovery frames from the relevant VLAN interface, in this case br-vlan11, but does not seem to forward other traffic. I'm unable to mac-telnet into the router despite allowing it on the br1-vlan11 interface. I cannot ping the IP address assigned to br-vlan11 despite seeing it in the CDP message in WireShark (both interface and IP).

I am seeing something very similar on a CRS210-8G-2S+ switch... CDP/LLDP passes just fine... I even get ARP in the right VLAN(s), but no dice when sending from the neighboring device on the same VLAN.

Mon Aug 21, 2017 8:46 am

Hallo!
After updating a RB922 with a Huawei ME909s-120 modem to 6.41RC16, the lte-interface doesn't switch in running mode. The status of the interface shows only one information: "Functionality == minimal", nothing else.
Is this a normal behavior in case of lte-passthrough or a bug?

regards

What was the previos version where it worked? Enable the LTE logging topic and check the log file. What Firmware version you have fro the modem?

klaus007 · Mon Aug 21, 2017 10:02 am

Hallo!
It is/was running perfect with 6.40.1 since it was released und before with 6.39.2. The Firmware of the modem is 11.617.06.00.00. To activate the logging is only with RC helpful, isn't it? I will try it once more in the evening.

Mon Aug 21, 2017 5:03 pm

Hallo!
It is/was running perfect with 6.40.1 since it was released und before with 6.39.2. The Firmware of the modem is 11.617.06.00.00. To activate the logging is only with RC helpful, isn't it? I will try it once more in the evening.

We tested and 909s-120 works with such firmware in RouterOS6.41rc16
Try to specify the init-delay in the System Routerboard settings to 9s and then reboot the board.
Also check if it works when you do a usb power reset option.

kd6icz · Mon Aug 21, 2017 8:27 pm

I'm happy to see support for Sierra AirPrime 7750. That's a pretty old card. The MC7455 is the current "all US carrier / all US band" card.

Any chance it would be to difficult to add whatever parameters are necessary to support the MC7455? It would be the end all be all card for two or three years.

Sent from my XT1650 using Tapatalk

klaus007 · Mon Aug 21, 2017 9:03 pm

Hallo!
It is/was running perfect with 6.40.1 since it was released und before with 6.39.2. The Firmware of the modem is 11.617.06.00.00. To activate the logging is only with RC helpful, isn't it? I will try it once more in the evening.
We tested and 909s-120 works with such firmware in RouterOS6.41rc16
Try to specify the init-delay in the System Routerboard settings to 9s and then reboot the board.
Also check if it works when you do a usb power reset option.

So, after a bit of testing the solution was, that I have to do a usb power reset over CLI. Over Winbox it doesn't work and after the next reboot I have to handle the same procedure. I think there is a problem with the USB-power-reset after reboot in 6.41RC16. After a downgrade to 6.40.1 everything works fine.
The passthrough itself was working as expectet, but I can't set it on a VLAN, only physical interfaces are supported. Would it be possible to support Vlan-interfaces too?

Tue Aug 22, 2017 9:45 am

Hallo!
It is/was running perfect with 6.40.1 since it was released und before with 6.39.2. The Firmware of the modem is 11.617.06.00.00. To activate the logging is only with RC helpful, isn't it? I will try it once more in the evening.
We tested and 909s-120 works with such firmware in RouterOS6.41rc16
Try to specify the init-delay in the System Routerboard settings to 9s and then reboot the board.
Also check if it works when you do a usb power reset option.
So, after a bit of testing the solution was, that I have to do a usb power reset over CLI. Over Winbox it doesn't work and after the next reboot I have to handle the same procedure. I think there is a problem with the USB-power-reset after reboot in 6.41RC16. After a downgrade to 6.40.1 everything works fine.
The passthrough itself was working as expectet, but I can't set it on a VLAN, only physical interfaces are supported. Would it be possible to support Vlan-interfaces too?

Have you tried to specify that init-delay?
What does it show in the log when you enable the lte logging?
It should support the Vlan interface as well - what error message did it show?

klaus007 · Tue Aug 22, 2017 11:09 am

With 9 seconds init-delay the lte modem doesn't start. When the moden isn't running, I get no errors in the log. Only after a manual usb power reset it start working and also I can see messages in the log.
If I try to set a Vlan, there is no error message. But after a export I see that nothing has changed and sfp1 is still set for passthrough.
Today I will try it on my second device too.

eworm · Tue Aug 22, 2017 12:49 pm

I am having issues with CAPsMAN on 6.41rc13... Looks like cap interfaces with CAPsMAN forwarding do not pass any traffic.

The issue persists with 6.41rc16... Just downgraded to 6.41rc11 and wireless is up and running.

dcolli · Tue Aug 22, 2017 3:05 pm

Bug with pppoe + ipv6 + dhcp6server + static

When static addresses are created in /ipv6 dhcp-server binding (server = all) it is placed in the pool (/ipv6 pool used) after the user disconnects the pppoe it is removed from the / ipv6 pool used, and after reconnection does not return the Address for /ipv6 pool used.

commands:

/ipv6 pool used print
/ipv6 dhcp-server binding make-static numbers=0
ipv6 dhcp-server binding set 0 server=all
/ipv6 pool used print
/ppp active remove 0
/ipv6 pool used print

idlemind · Tue Aug 22, 2017 4:30 pm

Working on a new RB750Gr3 (hex). I installed 6.41rc9 and I'm unable to get an access port working for a VLAN on the new VLAN aware bridges. A similar configuration is working on a RB750Gr3 running 6,41rc6.

  MMM      MMM       KKK                          TTTTTTTTTTT      KKK
  MMMM    MMMM       KKK                          TTTTTTTTTTT      KKK
  MMM MMMM MMM  III  KKK  KKK  RRRRRR     OOOOOO      TTT     III  KKK  KKK
  MMM  MM  MMM  III  KKKKK     RRR  RRR  OOO  OOO     TTT     III  KKKKK
  MMM      MMM  III  KKK KKK   RRRRRR    OOO  OOO     TTT     III  KKK KKK
  MMM      MMM  III  KKK  KKK  RRR  RRR   OOOOOO      TTT     III  KKK  KKK

  MikroTik RouterOS 6.41rc9 (c) 1999-2017       http://www.mikrotik.com/

[?]             Gives the list of available commands
command [?]     Gives help on the command and list of arguments

[Tab]           Completes the command/word. If the input is ambiguous,
                a second [Tab] gives possible options

/               Move up to base level
..              Move up one level
/command        Use command at the base level

[admin@rtr1] > export
# aug/07/2017 13:27:40 by RouterOS 6.41rc9
# software id = 247N-DPAI
#
# model = RouterBOARD 750G r3
# serial number = xxxxxxxxxxxx
/interface bridge
add admin-mac=6C:3B:6B:bb:xx:yy auto-mac=no fast-forward=no igmp-snooping=no name=br1 vlan-filtering=yes
/interface ethernet
set [ find default-name=ether1 ] name=eth1
set [ find default-name=ether2 ] name=eth2
set [ find default-name=ether3 ] name=eth3
set [ find default-name=ether4 ] name=eth4
set [ find default-name=ether5 ] name=eth5
/ip neighbor discovery
set eth1 discover=no
/interface vlan
add interface=br1 name=br1-vlan11 vlan-id=11
add interface=br1 name=br1-vlan12 vlan-id=12
add interface=br1 name=br1-vlan999 vlan-id=999
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip hotspot profile
set [ find default=yes ] html-directory=flash/hotspot
/ip pool
add name=default-dhcp ranges=192.168.88.10-192.168.88.254
add name=vlan11 ranges=10.214.11.100-10.214.11.199
add name=vlan12 ranges=10.214.11.100-10.214.11.199
add name=vlan13 ranges=10.214.11.100-10.214.11.199
/ip dhcp-server
add address-pool=default-dhcp disabled=no interface=br1 name=defconf
add address-pool=vlan11 disabled=no interface=br1-vlan11 name=vlan11
add address-pool=vlan12 disabled=no interface=br1-vlan12 name=vlan12
/interface bridge port
add bridge=br1 hw=no interface=eth2 pvid=11
add bridge=br1 hw=no interface=eth3
add bridge=br1 hw=no interface=eth4
add bridge=br1 hw=no interface=eth5
/interface bridge vlan
add bridge=br1 untagged=eth2 vlan-ids=11
/ip address
add address=192.168.88.1/24 comment=defconf interface=br1 network=192.168.88.0
add address=10.214.11.254/24 interface=br1-vlan11 network=10.214.11.0
add address=10.214.12.254/24 interface=br1-vlan12 network=10.214.12.0
/ip dhcp-client
add comment=defconf dhcp-options=hostname,clientid disabled=no interface=eth1
/ip dhcp-server network
add address=10.214.11.0/24 dns-server=10.214.0.1 domain=123.local gateway=10.214.11.254
add address=10.214.12.0/24 dns-server=10.214.0.1 domain=123.local gateway=10.214.12.254
add address=192.168.88.0/24 comment=defconf gateway=192.168.88.1
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.88.1 name=router.lan
/ip firewall nat
add action=masquerade chain=srcnat ipsec-policy=out,none out-interface=eth1
/system package update
set channel=release-candidate
#error exporting /system routerboard mode-button
/tool mac-server
set [ find default=yes ] disabled=yes
add interface=br1
add interface=br1-vlan11
/tool mac-server mac-winbox
set [ find default=yes ] disabled=yes
add interface=br1
add interface=br1-vlan11

A packet capture shows STP frames and discovery frames from the relevant VLAN interface, in this case br-vlan11, but does not seem to forward other traffic. I'm unable to mac-telnet into the router despite allowing it on the br1-vlan11 interface. I cannot ping the IP address assigned to br-vlan11 despite seeing it in the CDP message in WireShark (both interface and IP).

I am seeing something very similar on a CRS210-8G-2S+ switch... CDP/LLDP passes just fine... I even get ARP in the right VLAN(s), but no dice when sending from the neighboring device on the same VLAN.

Turns out I missed adding the VLAN as tagged to my bridge in /interface bridge vlan

If you're already doing that check the docs. I remember a model or two of CRS was unsupported with the new bridges initially. I think they have it rectified now though

idlemind · Tue Aug 22, 2017 6:58 pm

What's new in 6.41rc3 (2017-Jul-26 09:32):
*) ippool6 - try to assign desired prefix for client if prefix is not being already used;

@MikroTik - @strods

Multiple people have asked in this thread without a reply about this feature line. Specifically your users are requesting the ability to "hint" what they want to be assigned for both the network and host portion of an address. This can be seen in practice in OpenWRT as class hints (source: https://wiki.openwrt.org/doc/uci/network6) for the network hinting portion.

I've also placed a support case for clarification. It is #2017082222001255.

Threads (will link as I dig them back out):

viewtopic.php?f=2&t=120254&p=591415&hil ... nt#p591415

Wed Aug 23, 2017 11:44 am

What's new in 6.41rc17 (2017-Aug-22 11:58):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

*) bridge - fixed "R" state for bridge interfaces on x86 and CHR installations (introduced in v6.41rc12);
*) capsman - added "vlan-mode=no-tag" option;
*) ipsec - added DH groups 19, 20 and 21 support for phase1 and phase2 (CLI only);
*) ipsec - allow to specify "remote-peer" address as DNS name;
*) lcd - fixed unresponsive LCD (introduced in v6.41rc15);
*) lte - added Passthrough support (CLI only);
*) pppoe - fixed invalid PPPoE server or client after reboot or "interface" edit (introduced in v6.41rc9);
*) snmp - fixed bridge host requests on devices with multiple bridge interfaces;
*) winbox - added possibility to define "comment" for "/routing bgp network" entries;
*) winbox - do not show LCD menu for devices which does not have it;
*) www - fixed unresponsive Web services (introduced in v6.40);

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

Wed Aug 23, 2017 12:52 pm

I am having issues with CAPsMAN on 6.41rc13... Looks like cap interfaces with CAPsMAN forwarding do not pass any traffic.
The issue persists with 6.41rc16... Just downgraded to 6.41rc11 and wireless is up and running.

Please provide us more info on your setup and how to reproduce the problem as we tested locally and the CAPsMAN forwarding is working.

irghost · Wed Aug 23, 2017 12:55 pm

What's new in 6.41rc17 (2017-Aug-22 11:58):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

*) bridge - fixed "R" state for bridge interfaces on x86 and CHR installations (introduced in v6.41rc12);
*) capsman - added "vlan-mode=no-tag" option;
*) ipsec - added DH groups 19, 20 and 21 support for phase1 and phase2 (CLI only);
*) ipsec - allow to specify "remote-peer" address as DNS name;
*) lcd - fixed unresponsive LCD (introduced in v6.41rc15);
*) lte - added Passthrough support (CLI only);
*) pppoe - fixed invalid PPPoE server or client after reboot or "interface" edit (introduced in v6.41rc9);
*) snmp - fixed bridge host requests on devices with multiple bridge interfaces;
*) winbox - added possibility to define "comment" for "/routing bgp network" entries;
*) winbox - do not show LCD menu for devices which does not have it;
*) www - fixed unresponsive Web services (introduced in v6.40);

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

SXT LTE?

Wed Aug 23, 2017 1:00 pm

irghost - What is the question about SXT LTE? Are you referring to Passthrough support? if you do, then take a look at this list:
https://wiki.mikrotik.com/wiki/Supporte ... and_modems

Siona · Wed Aug 23, 2017 1:02 pm

irghost - What is the question about SXT LTE? Are you referring to Passthrough support? if you do, then take a look at this list:
https://wiki.mikrotik.com/wiki/Supporte ... and_modems

Is it possible to add this future in future release?

irghost · Wed Aug 23, 2017 1:11 pm

irghost - What is the question about SXT LTE? Are you referring to Passthrough support? if you do, then take a look at this list:
https://wiki.mikrotik.com/wiki/Supporte ... and_modems

in last 3 release
we have

*) lte - added Passthrough support (CLI only);

but why still no support For most important LTE device "SXT LTE"

Wed Aug 23, 2017 1:45 pm

Currently SXT LTE does not support this functionality.

If you see the same changelog entry in multiple rc versions then it is a new feature which is being implemented and changelog entry is simply moved up on each rc when additional work on it has been done.

raffav · Wed Aug 23, 2017 4:32 pm

@ Mikrotik Support

*) pppoe - fixed invalid PPPoE server or client after reboot or "interface" edit (introduced in v6.41rc9);

what this suppose to fix?
because even after this RC all my pppoe don't show up either

Wed Aug 23, 2017 4:37 pm

raffav - What do you mean with "don`t show up either"? Be more specific. This fixed as written in changelog "invalid PPPoE server or client after reboot or "interface" edit". Did you upgrade device and you see invalid (red) PPPoE server or client interface?

raffav · Wed Aug 23, 2017 4:51 pm

raffav - What do you mean with "don`t show up either"? Be more specific. This fixed as written in changelog "invalid PPPoE server or client after reboot or "interface" edit". Did you upgrade device and you see invalid (red) PPPoE server or client interface?

i thought that fix applied to my case too ( pppoe interfaces disappears after reboot/upgrade)

but never mind, i just saw answer (Ticket#2017080722001328) on my mail.

klaus007 · Wed Aug 23, 2017 11:19 pm

Hallo!
It is/was running perfect with 6.40.1 since it was released und before with 6.39.2. The Firmware of the modem is 11.617.06.00.00. To activate the logging is only with RC helpful, isn't it? I will try it once more in the evening.
We tested and 909s-120 works with such firmware in RouterOS6.41rc16
Try to specify the init-delay in the System Routerboard settings to 9s and then reboot the board.
Also check if it works when you do a usb power reset option.
So, after a bit of testing the solution was, that I have to do a usb power reset over CLI. Over Winbox it doesn't work and after the next reboot I have to handle the same procedure. I think there is a problem with the USB-power-reset after reboot in 6.41RC16. After a downgrade to 6.40.1 everything works fine.
The passthrough itself was working as expectet, but I can't set it on a VLAN, only physical interfaces are supported. Would it be possible to support Vlan-interfaces too?
Have you tried to specify that init-delay?
What does it show in the log when you enable the lte logging?
It should support the Vlan interface as well - what error message did it show?

With RC17 I was able to set a Vlan for passthrough but the LTE-Modem doesn't start with 0,3,6 and 9 seconds init-delay. Also a total power-reset with a duration of more than 1 minute, didn't solve the problem. After a munual usb power-reset with a duration of 1 second, the LTE-interface starts. Tested with 2 RB922UAGS-5HPacT (current Firmware 3,41) with Huawei ME909s-120. With 3.40.1 or older I never had such problems (init-delay 1s)

heaven · Thu Aug 24, 2017 8:23 am

PPPoE failed again in new RC(

dancsa · Thu Aug 24, 2017 12:19 pm

We've bought several CRS326 for our network expansion plan, as we had no major issues with MT routers. As I see the future is the new offloaded bridge feature, so I tried the RC line as the 6.41 will be probably released before these switches become prod.

As for switching between ports, they work, this bridge configuration looks more comfortable than the old switch menu (which i unfamiliar).
But no mater how i tried I couldn't bring up packages to the "router", and couldn't find any pointers how should i do that. How can i create a vlan interface, for example management purpose.

Thu Aug 24, 2017 12:59 pm

What's new in 6.41rc18 (2017-Aug-24 07:52):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

*) bridge - changed "Host" and "MDB" table column order;
*) ipv6 - add dynamic "/ip dns" server address from RA when RA is permitted by configuration;
*) log - optimized "poe-out" logging topic logs;
*) lte - added Passthrough support (CLI only);
*) poe-out - fixed router reboot after "poe-out-status" changes;
*) userman - fixed "limitation" and "profile-limitation" update;
*) webfig - allow to open table entry even if table is not sorted by # (introduced in v6.40);
*) webfig - allow to unset "rate-limit" for DHCP leases;
*) winbox - added "notrack-chain" setting to IPSec peers;
*) winbox - do not show FAN related information under "/system health" menu for devices which does not have it;
*) winbox - fixed ARP table update after entry changes state to incomplete;

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

idlemind · Thu Aug 24, 2017 5:30 pm

What's new in 6.41rc18 (2017-Aug-24 07:52):

*) ipv6 - add dynamic "/ip dns" server address from RA when RA is permitted by configuration;

Almost there, now allow us to control the DNS server distributed in RA to enable our IPv6 clients to use the local MikroTik resolver cache.

Add an option to /ipv6 nd to specify the DNS servers!

buzzdee · Fri Aug 25, 2017 6:49 pm

*) ipsec - allow to specify remote peer address as DNS name (CLI only);
does this mean ipsec tunnels can be established between 2 sites with dynamic ip addresses, so I can get rid of the additional L2TP Tunnel?

In road warrior setups, yes.

I tried that setup, mikrotik routers on both ends. Router 1 uses a dns-name as peer address, router 2 is set to 0.0.0.0/0. If I don't want to use any tunneling, I still have to specify the SA Dst. Address in router 1's policy-action. Are there plans to also make the use of dns-names possible in SA Address fields of policies?

Thanks,

BuzzDee

Edit: Seems, I'm not alone - see
viewtopic.php?f=2&t=124502&p=612878&hil ... ns#p612878
viewtopic.php?f=1&t=123534&p=610966&hil ... ns#p610966

eworm · Mon Aug 28, 2017 3:13 pm

I am having issues with CAPsMAN on 6.41rc13... Looks like cap interfaces with CAPsMAN forwarding do not pass any traffic.
The issue persists with 6.41rc16... Just downgraded to 6.41rc11 and wireless is up and running.
Please provide us more info on your setup and how to reproduce the problem as we tested locally and the CAPsMAN forwarding is working.

Opened Ticket#2017082822000816 with more details.

Mon Aug 28, 2017 3:22 pm

Hallo!
It is/was running perfect with 6.40.1 since it was released und before with 6.39.2. The Firmware of the modem is 11.617.06.00.00. To activate the logging is only with RC helpful, isn't it? I will try it once more in the evening.
We tested and 909s-120 works with such firmware in RouterOS6.41rc16
Try to specify the init-delay in the System Routerboard settings to 9s and then reboot the board.
Also check if it works when you do a usb power reset option.
So, after a bit of testing the solution was, that I have to do a usb power reset over CLI. Over Winbox it doesn't work and after the next reboot I have to handle the same procedure. I think there is a problem with the USB-power-reset after reboot in 6.41RC16. After a downgrade to 6.40.1 everything works fine.
The passthrough itself was working as expectet, but I can't set it on a VLAN, only physical interfaces are supported. Would it be possible to support Vlan-interfaces too?
Have you tried to specify that init-delay?
What does it show in the log when you enable the lte logging?
It should support the Vlan interface as well - what error message did it show?

With RC17 I was able to set a Vlan for passthrough but the LTE-Modem doesn't start with 0,3,6 and 9 seconds init-delay. Also a total power-reset with a duration of more than 1 minute, didn't solve the problem. After a munual usb power-reset with a duration of 1 second, the LTE-interface starts. Tested with 2 RB922UAGS-5HPacT (current Firmware 3,41) with Huawei ME909s-120. With 3.40.1 or older I never had such problems (init-delay 1s)

Could you make a support output file after the reboot when the interface doesn't work and send that to support@mikrotik.com?
The problem also happens when you are not using the passthrough mode?

w0lt · Mon Aug 28, 2017 4:47 pm

I've been to testing IGMP-Snooping using ROS 6.41 rc18, and have found the multicast device (and group) I'm listening to seems to time out after about 5 minutes. I was working just fine up till then with a correct entry in the "Bridge MDB" section. Do you think that rc18 has a multicast time-out issue? Seems to work just fine other than that.

-tp

klaus007 · Mon Aug 28, 2017 6:20 pm

We tested and 909s-120 works with such firmware in RouterOS6.41rc16
Try to specify the init-delay in the System Routerboard settings to 9s and then reboot the board.
Also check if it works when you do a usb power reset option.
So, after a bit of testing the solution was, that I have to do a usb power reset over CLI. Over Winbox it doesn't work and after the next reboot I have to handle the same procedure. I think there is a problem with the USB-power-reset after reboot in 6.41RC16. After a downgrade to 6.40.1 everything works fine.
The passthrough itself was working as expectet, but I can't set it on a VLAN, only physical interfaces are supported. Would it be possible to support Vlan-interfaces too?
Have you tried to specify that init-delay?
What does it show in the log when you enable the lte logging?
It should support the Vlan interface as well - what error message did it show?

With RC17 I was able to set a Vlan for passthrough but the LTE-Modem doesn't start with 0,3,6 and 9 seconds init-delay. Also a total power-reset with a duration of more than 1 minute, didn't solve the problem. After a munual usb power-reset with a duration of 1 second, the LTE-interface starts. Tested with 2 RB922UAGS-5HPacT (current Firmware 3,41) with Huawei ME909s-120. With 3.40.1 or older I never had such problems (init-delay 1s)
Could you make a support output file after the reboot when the interface doesn't work and send that to support@mikrotik.com?
The problem also happens when you are not using the passthrough mode?

Hallo Uldis!

I have sent you the support.rif.
At the moment I have fixed it with a script after startup an a delay of 10s (It was disabled for the support-file).
Yes, the problem is still there without passthrough.

Tue Aug 29, 2017 11:16 am

What's new in 6.41rc20 (2017-Aug-29 06:41):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

!) bridge - implemented software based vlan-aware bridges;
https://wiki.mikrotik.com/wiki/Manual:I ... _Filtering
!) switch - "master-port" conversion into a bridge with hardware offload "hw" option;
https://wiki.mikrotik.com/wiki/Manual:S ... Offloading
!) bridge - general development of hw-offload bridge implementation (introduced in v6.40rc36);
*) bridge - added initial support for hardware "igmp-snooping" on CRS1xx/2xx;
*) bridge - fixed "fast-forward" counters;
*) bridge - implemented software based "igmp-snooping";
*) bridge - implemented software based MSTP;
*) bridge - removed "master-port" parameter;
*) dhcpv6 client - added IAID check in reply;
*) dhcpv6-client - fixed IA check on solicit when "raoud-commit" is enabled;
*) dhcpv6-server - do not release address of static binding from pool after server removal;
*) export - fixed export for PoE-OUT related settings;
*) ipsec - kill PH1 on "mode-config" address failure;
*) led - fixed RB711UA ether1 LED (introduced in v6.38rc16);
*) lte - added Passthrough support (CLI only);
*) lte - integrated IP address acquisition without DHCP client for wAP LTE kit-US;
*) userman - fixed "limitation" and "profile-limitation" update;
*) userman - fixed CoA packet processing after changes in "/tool user-manager router" configuration;

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

patrick7 · Tue Aug 29, 2017 12:25 pm

What's the difference between /interface ethernet switch vlan/ports and the bridge VLAN implementation?
What is the correct way to create a switch with multiple VLANs (tagged and untagged) with a management IP on a vlan?

ivicask · Tue Aug 29, 2017 1:28 pm

So how is this new bridge HW offload supposed to work?I upgraded my WAP AC and than I printed my bridges after upgrade and they all say hw=no, tried creating new bridge, still says no.
Also I see there is new option Bridge Fast forward, what does it do?I tried ticking it again i see no differences anywhere regarding CPU load or anything else.

timberwolf · Tue Aug 29, 2017 1:35 pm

How would one realize inter-vlan routing or generally vlan interfaces with the new bridge implementation?
Can't find anything on this except some emtpy placeholder topic in the Wiki.

idlemind · Tue Aug 29, 2017 2:30 pm

How would one realize inter-vlan routing or generally vlan interfaces with the new bridge implementation?
Can't find anything on this except some emtpy placeholder topic in the Wiki.

Yes the wiki needs it documented formally! In the meantime:

Add your VLAN interfaces and set their interface as your bridge. Apply your IP and DHCP servers to the VLAN interfaces. Then go into /interface bridge vlan and add your VLANs and be sure to tag the bridge interface.

So it would look something like this if you were to make a brand new bridge, add VLANs 11 and 12 (10.99.11.0/24 and 10.99.12.0/24), create a VLAN 11 access port on ether2, create a VLAN 12 access port on ether3 and a trunk on ether4 with VLAN 1 as the native VLAN and allow VLANs 11 and 12 to be tagged.

/interface bridge add vlan-filtering=no name=br1

/interface vlan add interface=br1 vlan-id=11 name=br1-vlan11
/interface vlan add interface=br1 vlan-id=12 name=br1-vlan12

/ip address add interface=br-vlan11 address=10.99.11.254/24
/ip address add interface=br-vlan11 address=10.99.12.254/24

/interface bridge vlan add bridge=br1 vlan-ids=11 tagged=br1,ether4 untagged=ether2
/interface bridge vlan add bridge=br1 vlan-ids=12 tagged=br1,ether4 untagged=ether3

/interface bridge port add bridge=br1 interface=ether2 pvid=11 frame-types=admit-only-untagged-and-priority-tagged
/interface bridge port add bridge=br1 interface=ether3 pvid=12 frame-types=admit-only-untagged-and-priority-tagged
/interface bridge port add bridge=br1 interface=ether4 pvid=1 frame-types=admit-all

/interface bridge set [ find where name=br1 ] vlan-filtering=yes

Ker-blamo, you have a 2 VLAN network with an access port in each and a trunk port on ether4 to uplink to your network.

Tue Aug 29, 2017 3:30 pm

What's new in 6.41rc20 (2017-Aug-29 06:41):

uuuu, winbox support for new bridge implementation....

idlemind · Tue Aug 29, 2017 3:36 pm

What's new in 6.41rc20 (2017-Aug-29 06:41):
*) bridge - added initial support for hardware "igmp-snooping" on CRS1xx/2xx;

Strods, is the CRS1xx/2xx now able to do the new bridge based VLANs without mucking around in the Ethernet switch menu? I know in the first releases it was indicated by MikroTik posts that this was required at the time. I don't own one of these types of devices so I can't test myself but I do see posts in other threads and would like to be able to help those users if possible and be as consistent as possible in my advice. I do love the new bridge implementation so far though. Good work.

Tue Aug 29, 2017 3:42 pm

Also I see there is new option Bridge Fast forward, what does it do?

That is a special case of bridge FastPath that only works when you have exactly two interfaces in a bridge. My understanding is that this option has nothing to do with bridge HW offloading. And it's not that new, it first appeared in 6.39.

w0lt · Tue Aug 29, 2017 5:13 pm

v6.41rc20 has some really cool stuff. I'm still having a problem with IGMP-Snooping where it drops an ACTIVE multicast group (after about 4-5 Min.). I'm not sure why it is doing this and to remedy it, I have to deactivate IGMP-Snooping and redeploy PIM (v6.40.2). I can't seem to find the ability to list the "Master Port" under Interface/Ethernet anymore. This might have been on purpose, just asking. I believe you folks are coming along nicely on IGMP-Snooping though it needs some tweaks (time will tell, right?). Would the ability to "Query" for IGMP Groups help in my case? Just spit-balling there..

Thanks,

-tp

biatche · Tue Aug 29, 2017 5:14 pm

@andirys and mikrotik

*) bridge - implemented software based MSTP;

thank you for making this happen

sindudas · Wed Aug 30, 2017 1:10 pm

@andirys and mikrotik

*) bridge - implemented software based MSTP;
thank you for making this happen

+1

timberwolf · Wed Aug 30, 2017 1:52 pm

...snip...
Ker-blamo, you have a 2 VLAN network with an access port in each and a trunk port on ether4 to uplink to your network.

Thanks, will give it a shot.

boldsuck · Wed Aug 30, 2017 1:56 pm

- ipv6 - fixed IPv6 address request from pool (introduced in 6.41rc1);

RB2011UAS v6.41rc1 - rc20
IPv6 address assignment is broken State is 'invalid'

Just for INFO:
MikroTik have managed to reproduce the problem. The error only occurs with me and a few others. MikroTik are working on it. But I fear this will remain an eternal bug.
I can live with the router not to reboot.

Since 6.41rc13 the DHCPv6 client has no more prefix. The IPv6 address could therefore not be assigned manually. Since 6.41rc20 gets the DHCPv6 client again a prefix which I then manually assigned.

I can not test the feature with the dynamic subprefix.
- Ippool6 - try to assign the requested prefix for client if prefix is not being already used;

Wed Aug 30, 2017 2:10 pm

Seems that I managed to reproduce the problem with invalid IPv6 address on rc version. We will try to fix this as soon as possible.

Wed Aug 30, 2017 5:43 pm

How would one realize inter-vlan routing or generally vlan interfaces with the new bridge implementation?
Can't find anything on this except some emtpy placeholder topic in the Wiki.

The example "InterVLAN Routing by Bridge" has been updated:
https://wiki.mikrotik.com/wiki/Manual:I ... _Bridge.29

timberwolf · Wed Aug 30, 2017 6:13 pm

The example "InterVLAN Routing by Bridge" has been updated:
https://wiki.mikrotik.com/wiki/Manual:I ... _Bridge.29

Thanks!

patrick7 · Wed Aug 30, 2017 9:41 pm

How about HW switching if STP and Layer3 Routing is needed? (bridge vlan disables HW)

idlemind · Thu Aug 31, 2017 7:17 pm

How about HW switching if STP and Layer3 Routing is needed? (bridge vlan disables HW)

Patrick, the new bridge automatically toggles HW support as you enable or disable features. This doesn't require you to manually switch between /interface Ethernet switch and /interface bridge when your feature need changes or you work on different models of hardware.

https://wiki.mikrotik.com/wiki/Manual:S ... Offloading

If you scroll down you'll see a table of each switches capabilities. Depending on which product you have you'll only get certain capabilities.

It's important to note that regardless of switch chip / hardware offloading, layer 3 interactions like inter-vlan routing have always been performed in CPU (per a MikroTik support case I opened).

jondavy · Thu Aug 31, 2017 8:30 pm

What's the difference between /interface ethernet switch vlan/ports and the bridge VLAN implementation?
What is the correct way to create a switch with multiple VLANs (tagged and untagged) with a management IP on a vlan?

I believe that the new implementation inside bridge of tag and tag was very simple to understand,
but for compatibility and understanding issues could be created dynamic interfaces VLAN and bridges for tagging or untagging vlans into interfaces menu

patrick7 · Thu Aug 31, 2017 8:52 pm

I'm aware of that. VLAN aware bridges disables HW offload on small switches (RB750GL etc). I'd like to have routing (this will be in CPU) AND switching (in hardware) on the same device as it was possible before 6.41rc. STP is needed too. I don't see a way how to solve this.

idlemind · Thu Aug 31, 2017 8:56 pm

I'm aware of that. VLAN aware bridges disables HW offload on small switches (RB750GL etc). I'd like to have routing (this will be in CPU) AND switching (in hardware) on the same device as it was possible before 6.41rc. STP is needed too. I don't see a way how to solve this.

If the underlying hardware supports it I imagine the new bridge implementation will catch up. Just watch the release notes for updates.

NoXy · Fri Sep 01, 2017 12:12 pm

InterVLAN routing with CRS326 (ROS 6.41rc20) works well.
I have a setup like this:
- ether1 (routed, DHCP client, Internet access)
- other ports in a bridge, separated to two different vlans (ID:2,3)
- each vlan has DHCP-Server, address etc.

I see poor bandwidth (max 25-40Mbps) between host connected to any inside vlan and Internet. Do you guys have same issue?
Ports are working in offload mode, hosts on same vlan can communicate wirespeed, with few precentage of CPU usage, which shows me that hw-offload is working well.

Is it a known problem?

Fri Sep 01, 2017 1:42 pm

Version 6.40.3 has been released:
viewtopic.php?f=21&t=125163

Fri Sep 01, 2017 1:59 pm

What's new in 6.41rc21 (2017-Sep-01 08:56):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

!) bridge - implemented software based vlan-aware bridges;
https://wiki.mikrotik.com/wiki/Manual:I ... _Filtering
!) switch - "master-port" conversion into a bridge with hardware offload "hw" option;
https://wiki.mikrotik.com/wiki/Manual:S ... Offloading
!) bridge - general development of hw-offload bridge implementation (introduced in v6.40rc36);
*) arp - properly update dynamic ARP entries after interface related changes;
*) bridge - added initial support for hardware "igmp-snooping" on CRS1xx/2xx;
*) bridge - implemented software based "igmp-snooping";
*) bridge - implemented software based MSTP;
*) bridge - removed "master-port" parameter;
*) ike1 - remove PH1 and PH2 when "mode-config" exchange fails;
*) interface - added "/interface reset-counters" command (CLI only);
*) ipsec - added DH groups 19, 20 and 21 support for phase1 and phase2 (CLI only);
*) lcd - fixed "flip-screen=yes" state after reboot;
*) lte - added "/interface lte apn" menu (Passthrough requires reconfiguration) (CLI only);
*) lte - added Yota non-configurable modem support;
*) lte - fixed mode initialization after reboot;
*) sniffer - fixed VLAN tag reporting for TX packets (introduced 6.41rc14);
*) tile - improved reliability on MPLS package processing;
*) wireless - pass interface MAC address in Sniffer TZSP frames;
*) wireless - updated United Kingdom regulatory domain 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 suspected or after crash.

gtj · Fri Sep 01, 2017 4:23 pm

I tried to upgrade a lab CRS-226-24P-2S+ from 6.40.1 to 6.41.rc18 and had major issues.

The switch is set up as a simple dumb switch, no vlans except the default and all ports switched. After the upgrade I had no IP connectivity to the switch and no connectivity through the switch. The switch was emitting LLDP since the upstream switch (also a CRS226 running 6.40.1) was showing it in the neighbors list but that's it. No mac-telnet either. Hooked up serial port and looked at the config. It "looked" correct (I have a supout which I'll send to support).

Now here's where the fun starts...
The switches are connected via SFP+ direct attach cables. After the upgrade, I lost connectivity to the UPSTREAM switch.
If I unplug the direct attach cable between the 2 switches, I get connectivity back to the upstream switch.
If I plug it back in again, I lose it. If I plug it in and change the bridge protocol on the upgraded switch to "none", I get connectivity back to the upstream switch but still no connectivity to the upgraded switch. After about an hour of playing with different settings, I decided to reset the config on the upgraded switch thinking that maybe the conversion process had an issue. No help.

Finally I did a reset with no default config and set the switch up manually by creating the bridge and adding the ports. YAY! It worked...
Except, I still have an SFP problem, but different. I no longer lose connectivity to the upstream switch but I still can't pass any traffic to the upgraded switch via that SFP port. With the 2 switches connected via ether1, no problem (I should have tried that earlier actually). Also, a Quanta 10G switch that's downstream from the upgraded switch is fine using the upgraded switch's SFP ports.

HMMM. As I'm typing this, I just heard the upgraded switch beep and sure enough, it's rebooting.

Anyway, I'm actually going to downgrade the switch back to 6.40.1 and retry the upgrade again to see if the connectivity issue was solely related to the SFP port or whether there was really a problem with the converted or default config.

JimmyNyholm · Fri Sep 01, 2017 5:08 pm

Unfortunately, currently SXT LTE does not support passthrough mode.

irghost - What is the question about SXT LTE? Are you referring to Passthrough support? if you do, then take a look at this list:
https://wiki.mikrotik.com/wiki/Supporte ... and_modems

Is there a plan for this or even and ETA? SXT LTE is the ultimate platform to get this feature.

w0lt · Fri Sep 01, 2017 5:34 pm

v6.41rc20 has some really cool stuff. I'm still having a problem with IGMP-Snooping where it drops an ACTIVE multicast group (after about 4-5 Min.). I'm not sure why it is doing this and to remedy it, I have to deactivate IGMP-Snooping and redeploy PIM (v6.40.2). I can't seem to find the ability to list the "Master Port" under Interface/Ethernet anymore. This might have been on purpose, just asking. I believe you folks are coming along nicely on IGMP-Snooping though it needs some tweaks (time will tell, right?). Would the ability to "Query" for IGMP Groups help in my case? Just spit-balling there..

Thanks,

-tp

Still having the same problem with v6.41 rc21

-tp

irghost · Fri Sep 01, 2017 6:01 pm

Unfortunately, currently SXT LTE does not support passthrough mode.

irghost - What is the question about SXT LTE? Are you referring to Passthrough support? if you do, then take a look at this list:
https://wiki.mikrotik.com/wiki/Supporte ... and_modems
Is there a plan for this or even and ETA? SXT LTE is the ultimate platform to get this feature.

+1 For SXT LTE

Mon Sep 04, 2017 2:45 pm

What's new in 6.41rc23 (2017-Sep-04 09:07):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

*) address - show warning on IPv6 address when acquire from pool has failed;
*) bridge - fixed connectivity issues when there are multiple VLAN interfaces on bridge;
*) bridge - show bridge interface local addresses in the host table;
*) crs317 - added initial support for HW offloaded MPLS forwarding;
*) dhcp - fixed DHCP services failing after reboot when DHCP option was used;
*) dhcpv4-client - allow to use DUID for client ID;
*) dhcpv6-client - require pool name to be unique;
*) routerboard - fixed "/system routerboard upgrade" for CRS212-8G-4S;

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

TmH · Mon Sep 04, 2017 9:26 pm

*) bridge - fixed connectivity issues when there are multiple VLAN interfaces on bridge;
.

I gave the new rc a go because of the multiple VLAN option, however after upgrading from the previous rc21 now the link is not stable anymore.
Every few minutes the link goes down and comes up again (from the mikrotik log).
Other than the new rc no changes were made to hardware [mikrotik hAP ac, RB962UiGS-5HacT2HnT] or settings. (same config etc)

Config used is blank, one bridge using all ports no vlans configured, dhcp-client on bridge interface, no firewall rules

Tue Sep 05, 2017 3:53 pm

DANGER

If you are running CAPSMAN avoid 6.41rc23

6.41rc23 breaks CAP communication with CAPSMAN, at least when using a tunelled datapath. Downgrading to 6.41rc20 does not fix the problem

Mikrotik support are aware of this issue.

anuser · Tue Sep 05, 2017 5:01 pm

DANGER

If you are running CAPSMAN avoid 6.41rc23

6.41rc23 breaks CAP communication with CAPSMAN, at least when using a tunelled datapath. Downgrading to 6.41rc20 does not fix the problem

Mikrotik support are aware of this issue.

Too late. My users complain that they are connected to the wifi, but there´s hardly any or only few traffic is getting through the connection.

idlemind · Tue Sep 05, 2017 6:05 pm

You can download prior versions of the RC by manually adjusting the URL from the download page if you wanted to revert back to an RC that it still works at for you to retain the new bridge.

Tue Sep 05, 2017 6:07 pm

DANGER

If you are running CAPSMAN avoid 6.41rc23

6.41rc23 breaks CAP communication with CAPSMAN, at least when using a tunelled datapath. Downgrading to 6.41rc20 does not fix the problem

Mikrotik support are aware of this issue.
Too late. My users complain that they are connected to the wifi, but there´s hardly any or only few traffic is getting through the connection.

How are you connecting the CAP to the CAPsMAN? Are you using Local-forwarding or CAPsMAN forwarding? Are you using VLAN in our setup?

Tue Sep 05, 2017 6:09 pm

You can download prior versions of the RC by manually adjusting the URL from the download page if you wanted to revert back to an RC that it still works at for you to retain the new bridge.

There is bug that after the downgrade from the newest RC you need to do a soft reboot of the board as the dhcp-client doesn't start in the first boot. Powercycle will not help, you need to do a sift reboot.

stucki · Tue Sep 05, 2017 7:44 pm

How many troubles will come with V8?

Tue Sep 05, 2017 10:54 pm

How are you connecting the CAP to the CAPsMAN? Are you using Local-forwarding or CAPsMAN forwarding? Are you using VLAN in our setup?

Hi Uldis, it is Layer3 with CAPsMAN forwarding.

Even downgrading to the previously working 6.41rc20 through Package/Downgrade, the problem still remains

anuser · Wed Sep 06, 2017 7:57 am

There is bug that after the downgrade from the newest RC you need to do a soft reboot of the board as the dhcp-client doesn't start in the first boot. Powercycle will not help, you need to do a sift reboot.

Well, it doesn't matter what older version I used. I downgraded and then "telnet-mac" into the access point to add an dhcp-client interface which took ~ 30 seconds to be added. After a reboot the access points worked again (I went back to 6.40.3).

Wed Sep 06, 2017 9:31 am

nz_monkey, are you using VLAN interfaces and Bridge interfaces as in v6.41RC versions there are lot of changes to the Bridge implementation that could cause some problem.

hzdrus · Wed Sep 06, 2017 11:06 am

*) crs317 - added initial support for HW offloaded MPLS forwarding;

Can you elaborate on this feature? It applies solely when acting as a transit P router or when encapsulating/decapsulating l2circuit also?

P.S. Congrats on the work to implement multicast snooping. Looking forward to a stable release.

mrz · Wed Sep 06, 2017 2:53 pm

@hzdrus currently only as a P router.

Fri Sep 08, 2017 9:42 am

What's new in 6.41rc26 (2017-Sep-07 13:26):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

!) bridge - general development of hw-offload bridge implementation (introduced in v6.40rc36);
*) chr - added KVM memory balloon support;
*) chr - added suspend support;
*) crs1xx/2xx - fixed 1 Gbps forced mode for several SFP modules;
*) crs317 - added initial support for HW offloaded MPLS forwarding;
*) dhcp - fixed unresponsive DHCP service caused by inability to read not set RAW options;
*) e-mail - auto complete file name on "file" parameter (introduced in v6.40);
*) eoip - made L2MTU parameter read-only;
*) hotspot - fixed missing "/ip hotspot server profile" if invalid "dns-name" was specified;
*) lte - added Passthrough support (CLI only);
*) lte - added support for ZTE ME3630 E1C;
*) lte - fixed mode initialization after reboot;
*) ppp - fixed missing PPP client interface after reboot (introduced in v6.41rc);
*) rb931-2nd - fixed startup problems (requires additional reboot after upgrade);
*) userman - fixed unresponsive RADIUS server (introduced in v6.40.3);
*) webfig - improved reliability of login 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 suspected or after crash.

irghost · Fri Sep 08, 2017 11:39 am

What's new in 6.41rc26 (2017-Sep-07 13:26):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

!) bridge - general development of hw-offload bridge implementation (introduced in v6.40rc36);
*) chr - added KVM memory balloon support;
*) chr - added suspend support;
*) crs1xx/2xx - fixed 1 Gbps forced mode for several SFP modules;
*) crs317 - added initial support for HW offloaded MPLS forwarding;
*) dhcp - fixed unresponsive DHCP service caused by inability to read not set RAW options;
*) e-mail - auto complete file name on "file" parameter (introduced in v6.40);
*) eoip - made L2MTU parameter read-only;
*) hotspot - fixed missing "/ip hotspot server profile" if invalid "dns-name" was specified;
*) lte - added Passthrough support (CLI only);
*) lte - added support for ZTE ME3630 E1C;
*) lte - fixed mode initialization after reboot;
*) ppp - fixed missing PPP client interface after reboot (introduced in v6.41rc);
*) rb931-2nd - fixed startup problems (requires additional reboot after upgrade);
*) userman - fixed unresponsive RADIUS server (introduced in v6.40.3);
*) webfig - improved reliability of login 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 suspected or after crash.

is there any news about SXT LTE?

HasanAlawlaki · Fri Sep 08, 2017 2:40 pm

In this vertion ..!

What about netcut and ip scanner for who using hotspot and not managed switch with ubnt AP's ?

Fri Sep 08, 2017 2:56 pm

is there any news about SXT LTE?

Your question was already answered!

Unfortunately, currently SXT LTE does not support passthrough mode.

What about netcut and ip scanner for who using hotspot and not managed switch with ubnt AP's ?

Sorry, I don't understand, what are you talking about?

HasanAlawlaki · Fri Sep 08, 2017 4:05 pm

Sorry i mean

The netcut program and another ip scanner can we control and block them by this new bridge features ?

irghost · Fri Sep 08, 2017 4:29 pm

is there any news about SXT LTE?
Your question was already answered!

Unfortunately, currently SXT LTE does not support passthrough mode.

What about netcut and ip scanner for who using hotspot and not managed switch with ubnt AP's ?
Sorry, I don't understand, what are you talking about?

Does SXT LTE Support passthrough in this version?
the answer is "NO"

Jotne · Sat Sep 09, 2017 7:05 pm

Could you please add Address List to the Queue module.
In firewall you can use Address List to make more flexible rules.
In Queue and Simple Queue you can only use IP or range of IP.

diasem · Sat Sep 09, 2017 8:49 pm

Strods Please include dns resolution on interface torch.

cXXcoder · Mon Sep 11, 2017 5:37 am

What's new in 6.41rc6 (2017-Aug-01 11:30):
[...]
*) ppp - added support for Sierra MC7750, Verizon USB730L;
[...]

For the Verizon USB730L / Novatel Global Mode USB730L, would it work if plugged into USB slot of the RB750UPr2? If not, which MikroTik routers compatible? And if yes, please point me to the relevant chapters/sections of documentation, or tutorials?

Please forgive my ignorance: I do software, not networks. :-(

Thank you!

JimmyNyholm · Mon Sep 11, 2017 4:15 pm

is there any news about SXT LTE?
Your question was already answered!

Unfortunately, currently SXT LTE does not support passthrough mode.

Normis could you Elaborate.
Your answer and Wiki is ambiguous:
Saying It's not supported and it can not be done due to hardware limitations.
OR
It is currently not supported, it can be done but we have not yet made a decision If or When?.

Yours J

Mon Sep 11, 2017 4:18 pm

Passthrough is not currently supported on SXT LTE and we do not have plans to implement such functionality in near future.

idlemind · Mon Sep 11, 2017 4:46 pm

Passthrough is not currently supported on SXT LTE and we do not have plans to implement such functionality in near future.

strods, breaking hearts on a Monday. Love it.

Siona · Mon Sep 11, 2017 5:00 pm

Passthrough is not currently supported on SXT LTE and we do not have plans to implement such functionality in near future.

Why? It would be really nice to have this functionality...

Tue Sep 12, 2017 2:24 pm

What's new in 6.41rc28 (2017-Sep-11 12:37):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

*) console - do not stop "/certificate sign" process if console times out in 1 minute;
*) crs317 - added L2MTU support;
*) crs3xx - added port ingress and egress rate limiting;
*) log - added "bridge" topic;
*) lte - added Passthrough support (CLI only);

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

JimmyNyholm · Tue Sep 12, 2017 3:01 pm

Passthrough is not currently supported on SXT LTE and we do not have plans to implement such functionality in near future.

Thanks for the elaboration.

Looking at the SXT LTE device it is the perfect fit for this function. We will buy many more of these units when this is available.

JimmyNyholm · Wed Sep 13, 2017 1:51 pm

Got my first Batch of CRS317-1G-16S+ 's unpacking the first and trying out this test version.

Connected Copper (1g) and startet winbox clearing conf. Looking around and tried to change l2mtu.

/interface ethernet set l2mtu=10000 numbers=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15

Boom ether1 stoped working (interface nr 0) the switch rebooted and didn't let me in again over winbox.
serialport connect reset conf and back in buissnesss.

I did notice that ether1 is connected to the same switch chip (swtich1) and perhaps this is the wrong way to change mtu. But at the same if I want 10K frames on the sfpports and no switch connectivity to the ether1 how is this accomplished with the new implementation. is there a manual for this new implementation or some pointers to get our heads round to test it properly..

Wed Sep 13, 2017 2:06 pm

JimmyNyholm - Did this happen when you used 6.41rc28?

JimmyNyholm · Fri Sep 15, 2017 11:24 am

JimmyNyholm - Did this happen when you used 6.41rc28?

Yes!

admin@MikroTik] > system package print
Flags: X - disabled
# NAME VERSION SCHEDULED
0 routeros-arm 6.41rc28
1 system 6.41rc28
2 X ipv6 6.41rc28
3 X wireless 6.41rc28
4 X hotspot 6.41rc28
5 X dhcp 6.41rc28
6 mpls 6.41rc28
7 routing 6.41rc28
8 X ppp 6.41rc28
9 security 6.41rc28
10 advanced-tools 6.41rc28
[admin@MikroTik] >

JimmyNyholm · Fri Sep 15, 2017 2:47 pm

What's new in 6.41rc26 (2017-Sep-07 13:26):
*) crs317 - added initial support for HW offloaded MPLS forwarding;

Is this gona be not bridged intefaces can hardware switch depending on label but ldp is running on ip so one would have to configure ip adresses and a routing protocol say ospf to get routes that would be hardware switched on labels without cpu. the cpu would only run routing protocol and ldp and the hardware chip would switch/route incoming mpls packes according to ldp. being a router no l2 domain but doing it true switching on ldp labels... Like the big guys....
Is this Initial something that works now in cli or is it the first door and something to be enabled later in the rc branch.

Mon Sep 18, 2017 12:02 pm

What's new in 6.41rc30 (2017-Sep-15 11:50):

Important note!!! Backup before upgrade!
RouterOS (v6.40rc36-rc40 and) v6.41rc1+ contains new bridge implementation that supports hardware offloading (hw-offload).
This update will convert all interface "master-port" configuration into new bridge configuration, and eliminate "master-port" option as such.
Bridge will handle all Layer2 forwarding and the use of switch-chip (hw-offload) will be automatically turned on based on appropriate conditions.
The rest of RouterOS Switch specific configuration remains untouched in usual menus for now.
Please, note that downgrading to previous RouterOS versions will not restore "master-port" configuration, so use backups to restore configuration on downgrade.

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

Changes since previous 6.41rc release:

*) crs317 - added L2MTU support;
*) crs326 - fixed packet processing speed on switch chip if individual port link speed differs;
*) crs3xx - added port ingress and egress rate limiting;
*) export - fixed wireless "ssid" and "supplicant-identity" compact export;
*) ppp - fixed situation when part of PPP configuration was reset to default values after reboot;
*) wireless - added "allow-signal-out-of-range" option for Access List entries (CLI only);

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

Chupaka · Mon Sep 18, 2017 12:12 pm

added "allow-signal-out-off-range" option

should be 'out of range' or 'off-range', but not both, I think

Mon Sep 18, 2017 12:39 pm

Chupaka - Thanks! Fixed the typo in changelog.

Chupaka · Mon Sep 18, 2017 1:01 pm

Any use cases for this option?

bajodel · Mon Sep 18, 2017 4:12 pm

Just tested CRS326-24G-2S+ on 6.41rc30
- started from clean config (reset w/o default)
- simple config: all port in a bridge, RSTP active
- ip dhcp client on bridge interface
- set identity and users

Reboot >> device dead

Via console I see the device is booting correctly >> startup services >> login (and after 1 sec) >> System rebooting (but the board stuck there w/o rebooting).
Note: the ether1 was the only cable plugged in and the led was off.

I was not able to create a supout (too fast in locking down); netinstall to 6.40.3 and we are in business again

Mon Sep 18, 2017 4:37 pm

bajodel - Can you please send to support@mikrotik,.com precise commands which you execute to reproduce this problem? We added all ports into bridge, added DHCP client on bridge, rebooted device and it is working just fine.

bajodel · Mon Sep 18, 2017 5:27 pm

Sure, as soon as possible I'll try to redo the same setup.
Now I remember that I also changed default MACs on etherXX interfaces and set admin-MAC on bridge one.

Mon Sep 18, 2017 5:44 pm

Any use cases for this option?

Here is the discussion about that option:
viewtopic.php?f=7&t=124884

idlemind · Mon Sep 18, 2017 6:12 pm

Any use cases for this option?
Here is the discussion about that option:
viewtopic.php?f=7&t=124884

Interesting how fast some options appear compared to others, cough useful IPv6 changes.

Yes, I'm heckling you because well it's apparently needed.

Side-note: It seems the pace is slowing on this RC. I imagine this means we'll be seeing 6.41rc moving to GA and 6.42 started? Will we see a general theme targeted in this next cycle like we say with the new bridge implementation?

juliokato · Mon Sep 18, 2017 6:36 pm

Interesting how fast some options appear compared to others, cough useful IPv6 changes.

Yes, I'm heckling you because well it's apparently needed.

Side-note: It seems the pace is slowing on this RC. I imagine this means we'll be seeing 6.41rc moving to GA and 6.42 started? Will we see a general theme targeted in this next cycle like we say with the new bridge implementation?

Good observation!
I am waiting until today for a simple reset counter:

viewtopic.php?f=1&t=108552&p=614961&hil ... er#p614961

bajodel · Mon Sep 18, 2017 7:11 pm

bajodel - Can you please send to support@mikrotik,.com precise commands which you execute to reproduce this problem? We added all ports into bridge, added DHCP client on bridge, rebooted device and it is working just fine.

Board: CRS326-24G-2S+

1) netinstalled 6.40.3
2) upgraded to 6.41rc30
3) reset w/o default
4) create bridge and put all port into it
5) change all Ethernet MACs (sample below)

/interface ethernet
set [ find default-name=ether1 ] mac-address=CC:4E:24:00:EE:01
set [ find default-name=ether2 ] mac-address=CC:4E:24:00:EE:02
set [ find default-name=ether3 ] mac-address=CC:4E:24:00:EE:03
set [ find default-name=ether4 ] mac-address=CC:4E:24:00:EE:04
set [ find default-name=ether5 ] mac-address=CC:4E:24:00:EE:05
set [ find default-name=ether6 ] mac-address=CC:4E:24:00:EE:06
set [ find default-name=ether7 ] mac-address=CC:4E:24:00:EE:07
set [ find default-name=ether8 ] mac-address=CC:4E:24:00:EE:08
set [ find default-name=ether9 ] mac-address=CC:4E:24:00:EE:09
set [ find default-name=ether10 ] mac-address=CC:4E:24:00:EE:10
set [ find default-name=ether11 ] mac-address=CC:4E:24:00:EE:11
set [ find default-name=ether12 ] mac-address=CC:4E:24:00:EE:12
set [ find default-name=ether13 ] mac-address=CC:4E:24:00:EE:13
set [ find default-name=ether14 ] mac-address=CC:4E:24:00:EE:14
set [ find default-name=ether15 ] mac-address=CC:4E:24:00:EE:15
set [ find default-name=ether16 ] mac-address=CC:4E:24:00:EE:16
set [ find default-name=ether17 ] mac-address=CC:4E:24:00:EE:17
set [ find default-name=ether18 ] mac-address=CC:4E:24:00:EE:18
set [ find default-name=ether19 ] mac-address=CC:4E:24:00:EE:19
set [ find default-name=ether20 ] mac-address=CC:4E:24:00:EE:20
set [ find default-name=ether21 ] mac-address=CC:4E:24:00:EE:21
set [ find default-name=ether22 ] mac-address=CC:4E:24:00:EE:22
set [ find default-name=ether23 ] mac-address=CC:4E:24:00:EE:23
set [ find default-name=ether24 ] mac-address=CC:4E:24:00:EE:24
set [ find default-name=sfp-sfpplus1 ] mac-address=CC:4E:24:00:EE:25
set [ find default-name=sfp-sfpplus2 ] mac-address=CC:4E:24:00:EE:26

>> Reboot

On console you'll see..

BootROM 1.41
Booting from SPI flash
BootROM: Image checksum verification PASSED


RouterBOOT booter 3.41

CRS326-24G-2S+

CPU frequency: 800 MHz
  Memory size: 512 MiB
 Storage size:  16 MiB

Press <delete> key within 4 seconds to enter setup....

loading kernel... OK
setting up elf image... OK
jumping to kernel code
Starting...
Starting services...

Rebooting...
Stopping services...

The board is stuck (not really rebooting); unplugging power cable you start again as above.

Chupaka · Tue Sep 19, 2017 10:17 am

I am waiting until today for a simple reset counter:

viewtopic.php?f=1&t=108552&p=614961&hil ... er#p614961

so, now it's available in 6.41rc?

Tue Sep 19, 2017 10:39 am

Chupaka, juliokato - Yes, it is:
*) interface - added "/interface reset-counters" command (CLI only);

juliokato · Tue Sep 19, 2017 4:01 pm

OK thanks, I'll test if it works I do not need to wait for V.7 .....

I'll just wait for the stable version.