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:
Remember to make backup/export files before an upgrade and save them on another storage device;
Make sure the device will not lose power during upgrade process;
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.
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..
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.
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:
Remember to make backup/export files before an upgrade and save them on another storage device;
Make sure the device will not lose power during upgrade process;
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.
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
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.
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.
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?
