Hello!
Just upgraded to v7.1b2 and spotted a few issues:
First and most important is routing marks don’t work
The second one is about wireguard. Why I can’t specify the port number for peer? Is it intended or a bug as well?
not able to put device in netboot mode in any way tried… short, direct cable from pc eth to eth2, i add this command:
/system routerboard settings set boot-device=try-ethernet-once-then-nand
then unplug power and eth, move eth to eth1 port, replug power, it never appears in netinstall…
left eth cable in eth1, unplug power, keep pressed reset for more than 2 minutes, nothing, never appeared in netinstall…
again, unplugged power, keep pressed reset, replug power, left reset after lights went off, nothing again…
windows firewall disabled, av disabled, ip pc 192.168.88.2/24–>.1, ip netboot 192.168.88.3…
L3 offloading happens on the switch chip.
That’s why it’s called “L3 offloading”. They offload the routing functionality from the CPU, to the switch chip, thus achieving wirespeed.
The switch chips used in those RB models (which are ASICs basically) do support L3 routing at wirespeed as per Marvell’s datasheet.
The hardware support was already there, but MikroTik just started supporting it on ROS.
@mrshark
You need to use a switch between pc and router. Direct connection is prone to fail, since you have a change on link state.
So, the netinstall “become” slow to detect the router.
Also, typically ether1 is used by netboot, except if is identified another port for that role.
There is no need to question the possibility of doing L3 routing on a switch, there have been competing switches from other companies that do wirespeed routing for a long time.
It must be like 20 years ago when I got my first 3com L3 switch and was amazed at how it could route so fast, for that price, when compared to Cisco routers of the day (3640 etc).
And indeed, it normally works as described: the first packet for a src/dst ip pair is handled by the CPU, then an item is programmed in the switch that forwards the remainder of the traffic.
Just like it is done for L2 switching (where a MAC table is kept in the switch hardware to know where to forward the traffic.
They still have to implement MPLS - I think that is the one major feature still missing from the current beta. Otherwise, there are probably many small fixes needed here and there.
Do a search on this forum and you find many answer. Netinstall is one way. You can also downgrade to an older version that is much smaller, like some 6.44.x version, then upgrade to latest.