CHR 7.0 beta4 vrrp kernel panic

RouterOS RouterOS beta
1

Hi,

I am playing with CHR 7.0 beta4 running in ESXi. Creating vrrp on bridge port cause router reboot when vrrp becomes master:

jan/12/2020 11:51:46 system,error,critical router was rebooted without proper shutdown
jan/12/2020 11:51:46 system,error,critical kernel failure in previous boot

Steps to reproduce

  • create bridge port and add ether1 into it


  • create vrrp interface on bridge port


  • add IP address to vrrp interface to enable it

When vrrp becomes master router will reboot. When you set vrrp priority to 255 you have endless reboot loop.

Configuration export (edited)

[admin@VRT] > /export hide-sensitive 
# jan/12/2020 11:54:21 by RouterOS 7.0beta4
# software id = 
#

/interface bridge
add igmp-snooping=yes name=bridge-lan protocol-mode=none
/interface ethernet
set [ find default-name=ether1 ] disable-running-check=no
/interface vrrp
add disabled=yes interface=bridge-lan name=vrrp-lan
/interface bridge port
add bridge=bridge-lan interface=ether1
/ipv6 settings
set accept-router-advertisements=yes
/ip address
add address=10.0.0.200/24 interface=bridge-lan network=10.0.0.0
add address=10.0.0.202/24 interface=vrrp-lan network=10.0.0.0
2

Address on VRRP interface should be a /32 not a /24.

3

Thanks, it seems work with /32. Anyway, other boxes with 6.46 does not crash with mask /24 on vrrp interface

4

Agreed, but you need to report it to MikroTik support.

5

Why? This isn’t really a support issue; it’s a v7 beta bug, which is precisely the purpose of this forum section.

6

Because that’s what it says here:
http://forum.mikrotik.com/t/how-to-report-issues-in-v7-beta/133088/1

Send them an email referencing this thread. Not hard is it?

7

This is neither a v6 bug, nor a security vulnerability, though.