There are no plans to support running both packages at the same time, no.
The wifiwave2 package beta is offered as a preview of wireless functionality developed for future products. For currently available products, the regular wireless package is still being maintained and improved.
Is cake crashing RoS with beta6?
So do we have any chance to get wpa3 on older devices with 2.4GHz ?
FToms already answered this above
Release notes end with:
other minor fixes and improvements;
Is there an elaboration on what those fixes are?
Is one of those fixes OpenVPN Server in UDP mode?
On 7.1b5 I noticed OpenVPN in UDP mode would randomly stop moving packets after an hour or two despite everything looking like it was connected perfectly. the same behaviour didn’t happen with the TCP mode on 7.1b5 (as per previous RouterOS versions) - this was on the RB750Gr3 - I’ve just upgraded to a RB3011 and will try again and report back.
Appreciate all the hard work that’s gone into the 7.1 development tree!
Kind Regards,
Jim.
Totally agree. Also it would be interesting in seeing progress on protocols here: https://help.mikrotik.com/docs/display/ROS/v7+Routing+Protocol+Status
Im sure there is a lot of work behind the scenes that doesnt show up in the changelogs. But just looking at changelog from beta5 to beta6, there isnt much progress.
!) added MLAG support for CRS3xx devices (CLI only);
Any doco on this? This is a LONG awaited feature…
Trying to perform a downgrade on 7.1b6 on an RB3011 results in this appearing on the serial console:
system will reboot shortly
Rebooting…
[ 746.341100] Internal error: Oops: 17 [#1] SMP ARM
[ 746.341143] CPU: 1 PID: 298 Comm: sysinit Not tainted 5.6.3 #60
[ 746.344785] Hardware name: RB3011
[ 746.350515] PC is at _stext+0x2c610/0x4338e8
[ 746.353985] LR is at _stext+0x2c5c8/0x4338e8
[ 746.358324] pc : [<8012c610>] lr : [<8012c5c8>] psr: 60000093
[ 746.362580] sp : bab9dbb8 ip : 00000000 fp : 00000000
[ 746.368568] r10: 8087d23c r9 : 00000004 r8 : 8087d23c
[ 746.373776] r7 : ba9d1900 r6 : 00000001 r5 : bcabfe00 r4 : 00000000
[ 746.378989] r3 : 00000001 r2 : 00000001 r1 : 07ffffff r0 : 00000000
[ 746.385585] Flags: nZCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment non
e
[ 746.392097] Control: 10c5787d Table: 7a9b406a DAC: 00000051
[ 746.399300] Process sysinit (pid: 298, stack limit = 0x29cb3e70)
[ 746.405122] {bab9dbe4} _stext+0x2c820/0x4338e8
[ 746.411211] {bab9dbfc} switch_switchdev_event+0x1cc/0x244 [switch@0x7f0e9000]
[ 746.415456] {bab9dc1c} _stext+0x32ab4/0x4338e8
[ 746.422651] {bab9dc3c} _stext+0x32c70/0x4338e8
[ 746.426990] {bab9dc4c} _stext+0x32c8c/0x4338e8
[ 746.431446] {bab9dc5c} br_switchdev_fdb_notify+0xbc/0xc4 [bridge2@0x7f0f7000]
[ 746.435868] {bab9dc74} br_fdb_find_port+0x73c/0xdb0 [bridge2@0x7f0f7000]
[ 746.443070] {bab9dc9c} br_fdb_find_port+0xa88/0xdb0 [bridge2@0x7f0f7000]
[ 746.449839] {bab9dd84} br_fdb_delete_by_port+0x88/0xb4 [bridge2@0x7f0f7000]
[ 746.456522] {bab9dda4} br_device_event+0x1b0/0x1dc [bridge2@0x7f0f7000]
[ 746.463195] {bab9ddc4} _stext+0x32ab4/0x4338e8
[ 746.469784] {bab9dde4} _stext+0x32d28/0x4338e8
[ 746.474299] {bab9ddf4} _stext+0x36124c/0x4338e8
[ 746.478727] {bab9de04} _stext+0x366d54/0x4338e8
[ 746.483154] {bab9de24} _stext+0x3673d0/0x4338e8
[ 746.487665] {bab9de3c} _stext+0x3e44c8/0x4338e8
[ 746.492182] {bab9de8c} _stext+0x3e66ac/0x4338e8
[ 746.496696] {bab9def4} _stext+0x3490fc/0x4338e8
[ 746.501208] {bab9df34} _stext+0xdd9cc/0x4338e8
[ 746.505723] {bab9df3c} _stext+0xdded0/0x4338e8
[ 746.510235] {bab9dfa4} _stext+0x1000/0x4338e8
[ 746.514662] Exception stack(0xbab9dfa8 to 0xbab9dff0)
[ 746.519109] dfa0: 7efffbd0 0002d390 00000003 00008914 7efff
b88 7efffb18
[ 746.524156] dfc0: 7efffbd0 0002d390 00000002 00000036 00000001 00000003 00000
000 00000000
[ 746.532302] dfe0: 0002d018 7efffb00 00015410 76fced14
[ 746.540463] Code: 01a04003 0a000003 e1a0000b ebfffcd0 (e5940000)
[ 746.545486] —[ end trace 9851032d4f912bef ]—
[ 746.552560] Kernel panic - not syncing: Fatal exception in interrupt
[ 746.556261] CPU0: stopping
[ 746.562580] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G D 5.6.3 #
60
[ 746.565098] Hardware name: RB3011
[ 746.572304] {80901f04} _stext+0x97a4/0x4338e8
[ 746.575775] {80901f0c} _stext+0x420060/0x4338e8
[ 746.580118] {80901f1c} _stext+0xbef0/0x4338e8
[ 746.584455] {80901f34} _stext+0x1b348c/0x4338e8
[ 746.588970] {80901f4c} _stext+0x1acc/0x4338e8
[ 746.593308] Exception stack(0x80901f50 to 0x80901f98)
[ 746.597836] 1f40: 008ca8d0 00000000 008ca
8d0 801142a0
[ 746.602888] 1f60: 80900000 00000001 80903e24 80903e60 80824a38 512f04d0 10c53
87d 00000000
[ 746.611040] 1f80: 00000000 80901fa0 80106f60 80106f50 60000013 ffffffff
[ 746.619182] {80901f9c} _stext+0x6f50/0x4338e8
[ 746.625602] {80901fa4} _stext+0x3a0d8/0x4338e8
[ 746.630116] {80901fbc} _stext+0x3a368/0x4338e8
[ 746.634457] {80901fc4} _sinittext+0x934/0x20d80
[ 746.650717] flash_ioctl: programming injected settings id 8
[ 746.686565] spi_program_sector 00000020
after further investigation it looks like it kernel panics on every reboot before it shows the boot loader.
Edit: from the console logs on first login:
may/19/2021 21:42:10 system,error,critical kernel failure in previous boot
may/19/2021 21:54:50 system,error,critical kernel failure in previous boot
may/19/2021 21:58:20 system,error,critical kernel failure in previous boot
I haven’t tested yet. I will when I’m back home tomorrow.
My OSPF stoped working after upgrade. When I downgrade back to 7.1beta5 it works again.
Thanks for the new features like MLAG!
Were the issues with OSPFv3 checksum fixed?
issues found (X86):
- winbox crashes opend the window about ipv6 bgp peer
- ip route crashes loading the fullroute where there are routes with big communities
- routing filter rules still not finished, they miss all the action about set bgp (so not all routing filter roules are ported from v6 backup)
- rpki session stays in connecting state
- router configuration about osfp is not ported from v6
regards
Ros
There seems to be a bug with the MTU - Size in bridge - generation.
After generating a new bridge and adding the first port ( Ethernet ) to it, the wrong MTU - size is used.
It seems, the L2 MTU ( 1598 ) instead of the real MTU ( 1500 ) is used as MTU for the bridge !
To fix this, the MTU of the Ethernet Port has to be changed and put back to 1500.
After that, the bridge uses the correct MTU too.
RouterOS version 7.1beta5 has been released in public “development” channel!
*) wifiwave2 - improved interface stability with multiple WPA3 authenticated clients;
I would like to request a separate wifiwave2 package for IPQ4018/IPQ4019 devices with 16MB of ROM. With such a package a lot of more users could test this it, send feedbacks and bug reports which will result in an earlier available bugfree stable release.
.
this also happened to me, I found that if the config for interface templates looks like this, it will not work:
/routing ospf interface-template
add area=ospf-area-0 interfaces=ovpn-in1,ovpn-in2 networks="" type=ptp
add area=ospf-area-0 interfaces=OSPF_vlan networks=""
.
removing the networks= fixed for me:
.
/routing ospf interface-template
add area=ospf-area-0 interfaces=OSPF_vlan
add area=ospf-area-0 interfaces=ovpn-in1,ovpn-in2 type=ptp
I just noticed that MPLS is back in Winbox! Also, I keep getting crashes with L2TP and Android 11.
Thank you! It really worked. Do you know if it is already possible to set costs for OSPF?
All the features of v6.49beta46?
Regards,
My hAP ac3 hasn’t crashed after setting cake as my download qeue type in queue tree so far, so that’s an improvement.
VRF (with a VLAN and a WireGuard interface) still doesn’t work and leads to WinBox crashing when showing IP → Routes.
Yes, now you can set cost in interface template