RouterOS v7.0beta2 bug fund

RouterOS RouterOS beta
1

One of my Splunk scripts does not work on v7.0 beta 2

{
:local SystemInformation true
if ($SystemInformation) do={
	:local version ([/system resource get version])
	:local board ([/system resource get board-name])
	:local model ([/system routerboard get model]);
	:local serial ([/system routerboard get serial-number])
	:local identity ([/system identity get name])
	:put "script=sysinfo version=\"$version\" board-name=\"$board\" model=\"$model\" serial=$serial identity=\"$identity\""
}
}

Why is /system routerboard menu missing? Does work fine on x86 6.46 beta and older.

2

Why this topic is locked?
http://forum.mikrotik.com/t/how-to-report-issues-in-v7-beta/133088/1

3

Not sure why its locked.

I will collect what I find here, and then send a email to support when I have a large list:

This commands fails from termianl. Works fine on <=6.46beta

/ip accounting uncounted print

not enough permissions (9)
4

If it were not locked, people might reply to the bug report instructions post with their bug report. The bugs are supposed to be submitted as new posts in the main forum, not as replies to the bug report instructions.

5

I installed the beta2 on a CHR (from .ova) for some testing.
Well, there are quite a number of small bugs that you can expect from a major overhaul, many of them are so apparent that I think it is not necessary to make reports for them.
(anyone in an in-house testing team will find them as well, and they probably have more efficient reporting/fixing tools available)

It is a bit disappointing how few changes in features are included, let’s hope many more will follow in upcoming betas. For now it looks like little more than a kernel update.

6

There is not much new because most of the new features were backported already to v6.
If you see trivial small bugs, list them here anyway

7
  • static IPv4 routes added are shown blue (inactive) but they work. after a long wait they become active.
  • changes in the routes show up in the log as “by admin” without saying what was done by admin
  • IPv4 route marking/rules appears to be dead
  • IPv6 route rule panel shows “ERROR: feature not implemented”
  • ethernet auto-negotiate on CHR under VMware ESXi 6.7u2 does not work (autoneg incomplete, cannot select “advertise 10G”, only 1G checkmark sticks, link is 10 Gbps and is up anyway)

Of course I am still hoping for more IPv6 features (including but not limited to route rules) to be on par with IPv4 features that have been offered for a long time.

8
  • IPv4 route marking/rules appears to be dead

Routing mark is configured differently, first you add the table and only then you can add routes to the table or use it in routing rules.

/routing table
add fib name=xx vrf=main
/ip route
add dst-address=8.8.8.8^xx gateway=10.155.101.1@main




/ip route rule 
add dst-address=1.1.1.1 action=lookup table=xx

But there are known problems that route rules may not work properly at the moment.

9

I guess it will become more clear what happens when using multiple route tables, route marking, route rules, and VRF at the same time (or as alternatives for the same config)?

10

SFP+ only works if mtu is set to 1500.
Tried intel, fiberstore and ubiquiti modules.

Router name: RB4011
Firmware: 6.46beta44
RouterOS: 6.46beta44 (testing)
Licence level: 5
Board name: RB4011iGS+5HacQ2HnD
Architecture: arm
Memory: 1073741824

/interface ethernet
set [ find default-name=sfp-sfpplus1 ] l2mtu=9000 loop-protect=on mtu=9000
rx-flow-control=auto tx-flow-control=auto
SFP+ works.

Router name: RB4011
Firmware: 7.0beta2
RouterOS: 7.0beta2 (development)
Licence level: 5
Board name: RB4011iGS+5HacQ2HnD
Architecture: arm
Memory: 1073741824

/interface ethernet
set [ find default-name=sfp-sfpplus1 ] l2mtu=9000 loop-protect=on mtu=1500
rx-flow-control=auto tx-flow-control=auto