Community discussions

MikroTik App
 
User avatar
emils
Forum Veteran
Forum Veteran
Topic Author
Posts: 906
Joined: Thu Dec 11, 2014 8:53 am

v7.3rc [testing] is released!

Wed Apr 13, 2022 2:12 pm

RouterOS version 7.3rc1 has been released "v7 testing" channel!

Before an upgrade:
1) Remember to make backup/export files before an upgrade and save them on another storage device;
2) Make sure the device will not lose power during upgrade process;
3) Device has enough free storage space for all RouterOS packages to be downloaded.

What's new in 7.3rc1 (2022-May-27 11:50):

*) bgp - moved "interface bgp-vpls" menu to "routing bgp vpls";
*) bgp - remove unused commands and parameters;
*) bluetooth - improved long-term service stability;
*) bridge - fixed TCP, UDP port parsing for loop detect warning;
*) capsman - fixed bridge disabling when using L2 connection;
*) ccr - improved interface link stability on CCR2004-16G-2S+PC;
*) chr - fixed Cloud DDNS update after license renewal;
*) console - fixed "terminal inkey" command;
*) crs1xx/2xx - improved system stability during switch reset;
*) defconf - do not add passthrough ports to local bridge on CCR2004-1G-2XS-PCIe;
*) ipv6 - fixed dynamic non link-local addresses displaying;
*) l2tp - added VRF support for L2TP client;
*) l3hw - greatly improved route offloading speed;
*) l3hw - log HW routes count and the shortest offloaded subnet prefix if the HW memory gets full;
*) l3hw - offload only main routing table;
*) l3hw - partial routing table offload for Marvell Prestera DX4000/DX8000 switch chip series;
*) lhgg - improved system stability (introduced in v7.2);
*) lte - improved LTE interface initialization process on LtAP-2HnD;
*) mpls - made LDP bindings work on PPP interfaces;
*) ospf - ignore instance route when originate-default=if-installed is enabled;
*) ovpn - fixed server instance not responding to incoming connections after reboot on CHR;
*) profile - added "wireguard" process classificator;
*) profile - added "zerotier" process classificator;
*) qsfp - reset module only when all ports are disabled;
*) queue - allow to set higher limits than 4G;
*) queue - display warning for CAKE type in simple and tree setups when "bandwidth" parameter is configured;
*) resource - fixed CPU type display under system resources for ARM and ARM64;
*) routerboot - prevent enabling "protected-routerboot" on unsupported factory firmware versions;
*) smb - fixed SMB2 file list reporting;
*) snmp - added VRF support;
*) ssh - fixed private key usage after downgrade;
*) winbox - added "Default Cost" parameter under "Routing/OSPF/Area" menu;
*) winbox - fixed "Type" values under "IP/Route" menu;
*) winbox - fixed minor typo in reboot confirmation prompt;
*) winbox - made wireless access list entries sortable when using the wifiwave2 package;
*) ww2 - general stability and throughput improvements;
*) x86 - added support for Solarflare SFC1920 NIC;
*) x86 - fixed soft-id reading on virtualized x86 installations (introduced in v7.2);

RouterOS version 7.3beta37 has been released "v7 testing" channel!

What's new in 7.3beta37 (2022-Apr-25 15:29):

*) bonding - fixed LACP flapping for RB5009 and CCR2004-16G-2S+ devices;
*) bridge - fixed packet marking for IP/IPv6 firewall;
*) dot1x - improved server stability when using re-authentication;
*) fetch - improved full disk detection;
*) gps - fixed minor value unit typo;
*) l3hw - improved offloading for directly connected hosts on CRS305, CRS326-24G-2S+, CRS328, CRS318, CRS310;
*) led - fixed QSFP+, QSFP28 activity LEDs when using 40Gbps modules (introduced in v7.3beta33);
*) lte - disabled wait for LTE auto attach;
*) mpls - fixed MPLS MTU and path MTU selection;
*) ovpn - fixed hardware offloading support on CHR;
*) ovpn - improved Windows client disconnect procedure in UDP mode;
*) ovpn - moved authentication failure messages to "info" logging level;
*) ppp - added warning when using prefix length other than /64 for router advertisement;
*) ppp - fixed "remote-ipv6-prefix" parameter unsetting;
*) ppp - fixed issue with multiple active sessions when "only-one" is enabled;
*) routerboot - properly reset system configuration when protected bootloader is enabled and reset button used;
*) rsvp-te - improved stability when "Resv" received for non-existing session;
*) sfp - improved QSFP/SFP interface initialization for 98DXxxxx switches;
*) switch - fixed missing stats from traffic-monitor for 98DXxxxx and 98PX1012 switches;
*) system - fixed RouterOS bootup when wifiwave2 package is installed (introduced in v7.3beta34);
*) system - fixed rare partial loss of RouterOS configuration after package upgrade/downgrade/install/uninstall;
*) user-manager - improved stability when received EAP attribute with non-existing state attribute;
*) vpls - fixed "pw-l2mtu" parameter usage;

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

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 some problem has appeared on device

Please keep this forum topic strictly related to this particular RouterOS release.
 
msatter
Forum Guru
Forum Guru
Posts: 2897
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 2:24 pm

filesystem - improved UBIFS stability and data integrity after downgrade to RouterOS v6 and upgrade to RouterOS v7

I assume that was all the fuss about for 7.21. This is much clearer and informative. :-)

Think about adding this to the before upgrade recommendations, by default if it is incremented: *) winbox - minimal required version is vx.xx;
 
User avatar
ufm
Member Candidate
Member Candidate
Posts: 103
Joined: Fri Nov 15, 2013 12:02 pm
Location: Ukraine

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 3:01 pm

Where can read about lacp-user-key?
 
User avatar
Znevna
Forum Guru
Forum Guru
Posts: 1347
Joined: Mon Sep 23, 2019 1:04 pm

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 3:03 pm

*) torch - properly capture all related IPv6 traffic;
Thank you!
 
User avatar
Larsa
Forum Guru
Forum Guru
Posts: 1025
Joined: Sat Aug 29, 2015 7:40 pm
Location: The North Pole, Santa's Workshop

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 3:08 pm

*) bgp - added initial support for prefix limit;

Excellent! Any docs regarding this?
 
EdPa
MikroTik Support
MikroTik Support
Posts: 274
Joined: Fri Sep 15, 2017 10:05 am
Location: Riga
Contact:

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 3:15 pm

Where can read about lacp-user-key?
The setting is documented on https://help.mikrotik.com/docs/display/ ... escription
LACP key can be monitored with:
/interface bonding monitor-slaves
 
User avatar
benlg
just joined
Posts: 10
Joined: Mon Jan 31, 2022 2:50 pm

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 3:47 pm

*) switch - added option to match source and destination IP addresses in ARP packets for RB5009 (requires mac-protocol=arp setting);

Good news !
So the rule : ...
/interface ethernet switch rule add dst-address=192.168.192.200/32 new-vlan-id=100 ports=ether2 switch=switch1
also needs the following one on RB5009 : ...
/interface ethernet switch rule add dst-address=192.168.192.200/32 new-vlan-id=100 ports=ether2 switch=switch1 mac-protocol=arp
... to have something similar to CRS317, which properly handles related ARP traffic with the first rule only.
Right ?

Is mac-protocol=arp setting requirement (so the need for the second rule) a limitation from the RB5009 switch chip (88E6393X) ?

Many thanks !
 
User avatar
ufm
Member Candidate
Member Candidate
Posts: 103
Joined: Fri Nov 15, 2013 12:02 pm
Location: Ukraine

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 3:55 pm

Where can read about lacp-user-key?
The setting is documented on https://help.mikrotik.com/docs/display/ ... escription
LACP key can be monitored with:
/interface bonding monitor-slaves
Now I have the same key on all the bonding interfaces. As far as I understand, this is normal. Could you give an example when need to manually change the key?
 
hecatae
Member Candidate
Member Candidate
Posts: 244
Joined: Thu May 21, 2020 2:34 pm

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 4:17 pm

*) lte - added MCS, CQI and RI value reporting for Fibocom FG621;
what details would you require for supporting the L860 and L850?
just a supout?
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 4:44 pm

- "Old style" routing filters add (like v6), not only syntax
You post that in every release topic, but it is completely unclear what you mean.
I agree to your other requests.
 
goodbye
newbie
Posts: 46
Joined: Sat Feb 25, 2017 12:48 am

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 4:44 pm

*) gps - added GPS package support for Chateau devices;
*) lte - added SMS sending support for MBIM protocol;
*) lte - improved stability when configuring multiple APN's at the same time in MBIM mode;
*) lte - improved stability when upgrading LTE firmware on Chateau 5G;
<3
Love to see this love working to fully support the Quectel chips advertised as fully supported in your Chateau 5G devices!
 
EdPa
MikroTik Support
MikroTik Support
Posts: 274
Joined: Fri Sep 15, 2017 10:05 am
Location: Riga
Contact:

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 4:47 pm

Is mac-protocol=arp setting requirement (so the need for the second rule) a limitation from the RB5009 switch chip (88E6393X) ?
Correct, the second rule is needed due to switch limitation. For CRS3xx, there is a slightly more advanced ACL matcher that can correctly find ARP and IPv4 packets using a single rule.

Now I have the same key on all the bonding interfaces. As far as I understand, this is normal. Could you give an example when need to manually change the key?
It is perfectly fine to use the same key for multiple LACPs. We received a feature request asking for this option, I guess it was up to their network policy to use unique keys for each LACP. It was fairly easy to implement it in RouterOS, so here you go. :wink:
 
aussetg
just joined
Posts: 19
Joined: Sat Jan 16, 2021 7:31 pm

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 5:15 pm

> *) sfp - added 2.5Gbps rate for SFP+ and QSFP+ interfaces on 98DXxxxx and 98PX1012 switches (requires disabled auto-negotiation);

Do you mean HGSMII ? :o
 
tpedko
just joined
Posts: 23
Joined: Wed May 22, 2019 9:58 am

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 5:43 pm

When will container support be added?
 
mikegleasonjr
Frequent Visitor
Frequent Visitor
Posts: 55
Joined: Tue Aug 07, 2018 3:14 am

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 7:01 pm

Is the changelog something carried over or new things compared to 7.2?
 
msatter
Forum Guru
Forum Guru
Posts: 2897
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 7:18 pm

Ask Jotne, see this result from of a spreadsheet.

viewtopic.php?t=184778#p923984
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 7:26 pm

I have not looked at 7.3beta, but my guess is that change log is the difference from 7.2 or 7.2.1
 
mafiosa
Member Candidate
Member Candidate
Posts: 266
Joined: Fri Dec 09, 2016 8:10 pm
Location: Kolkata, India
Contact:

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 8:04 pm

Beta 33? Out of the world version numbering.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 8:04 pm

Posting it in every topic won't make it happen faster. As it was already mentioned in one of the topics we will try to think of some user friendly GUI method to add routing filters but doing that and implement it is not going to happen right away.
 
mafiosa
Member Candidate
Member Candidate
Posts: 266
Joined: Fri Dec 09, 2016 8:10 pm
Location: Kolkata, India
Contact:

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 8:12 pm

*) torch - properly capture all related IPv6 traffic;
Thanks a ton. However please refer to SUP-78389. @normis @emilis @edpa
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 8:17 pm

Currently there is no mechanism to count exact session prefixes, That is why this parameter is not even set. If you want to know exact prefixes installed in the routing table received from a specific peer, then use /roruting route print command with appropriate filtering options, like "belongs-to" or "bgp.peer-cache-id"
 
mafiosa
Member Candidate
Member Candidate
Posts: 266
Joined: Fri Dec 09, 2016 8:10 pm
Location: Kolkata, India
Contact:

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 8:19 pm

RB5009 still does not show cpu type in /system/resources. Also after every reboot VxLAN Mac address changes.
 
User avatar
strods
MikroTik Support
MikroTik Support
Posts: 1616
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 8:26 pm

Beta 33? Out of the world version numbering.
How do you think where the fixes for 7.2.1 were tested? :)
 
OlofL
Member Candidate
Member Candidate
Posts: 113
Joined: Mon Oct 12, 2015 2:37 pm

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 8:40 pm

When containers?
 
mafiosa
Member Candidate
Member Candidate
Posts: 266
Joined: Fri Dec 09, 2016 8:10 pm
Location: Kolkata, India
Contact:

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 8:46 pm

How do you think where the fixes for 7.2.1 were tested? :)
[/quote]
Did you know that you can send me testing images for testing?
 
User avatar
Cha0s
Forum Guru
Forum Guru
Posts: 1135
Joined: Tue Oct 11, 2005 4:53 pm

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 9:01 pm

Currently there is no mechanism to count exact session prefixes, That is why this parameter is not even set. If you want to know exact prefixes installed in the routing table received from a specific peer, then use /roruting route print command with appropriate filtering options, like "belongs-to" or "bgp.peer-cache-id"
Doesn't sound the new routing engine was very well thought out before implementing.
How is it possible that basic features were not even considered during the design phase?

BGP Prefix count per session
BGP Advertisements
Routing filters with no clear plan on how to make it GUI friendly and in line with all the rest of ROS/Winbox syntax/UI.
No BFD

It's sad to have great new hardware for the datacenter being released, and no viable software yet to use them.
Without a fully working BGP (and I mean production, business ready, not beta testing), v7 is useless to me.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 10:43 pm

Doesn't sound the new routing engine was very well thought out before implementing.
How is it possible that basic features were not even considered during the design phase?
+1
Not only that, but it takes ages and many versions to get it fixed.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 10:50 pm

As it was already mentioned in one of the topics we will try to think of some user friendly GUI method to add routing filters but doing that and implement it is not going to happen right away.
It would already be nice when the old /routing filter rule add syntax could be accepted and converted on-the-fly to new syntax and stored.
The code for that should be available as it is also done for v6-to-v7 upgrades.
Bonus points for allowing a v6 style "route filter +" operation in the GUI with the same result (a v7 compatible filter rule).

I of course understand that the hard part would be to then "modify" a rule created this way, but that could be done later.
In fact the same thing as above would also be nice for /routing bgp instance and /routing bgp peer commands. Accept v6 form and convert to v7 on the fly.
This would make it easier to write configuration guidelines and automatic configuration generators that work on both versions.
For people wanting to join our HAMNET network I have a config generator that creates appropriate v6 config automatically, ready for cut-and-paste.
Of course I will update that for v7 (once it is viable to use it in the network) but I can guess that others have similar things, HOWTOs etc. which were made useless by the config changes in v7.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 10:55 pm

Currently there is no mechanism to count exact session prefixes, That is why this parameter is not even set.
But it will have to be written for the prefix limit handling anyway, isn't it? When that is done, can't it be shown in the session table as well?
Also, please make that session table auto-refreshing as it was in v6. We cannot be tricked by showing an Uptime counter that is ticking on and on even when the session is actually down (which becomes apparent when pressing F5). In v6 the table shows the actual session status and uptime, as it should be, without pressing F5.
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v7.3beta [testing] is released!

Wed Apr 13, 2022 11:44 pm

It seems 6to4 interface routes are not installed in vrf with 7.3.
/interface 6to4
add !keepalive mtu=1480 name=HE remote-address=X.X.X.X

/ip vrf
add interfaces=HE name=VRF-HE

/ipv6 address
add address=2001:470:xxxx:cc::2 advertise=no interface=HE no-dad=yes

/routing/route/pr det where immediate-gw=HE
Ac afi=ip6 contribution=active dst-address=2001:470:xxxx:cc::/64 routing-table=main gateway=HE immediate-gw=HE distance=0 scope=10
belongs-to="Connected route" local-address=2001:470:xxxx:cc::2%HE
debug.fwp-ptr=0x20243720

Ac afi=ip6 contribution=active dst-address=fe80::%HE/64 routing-table=main gateway=HE immediate-gw=HE distance=0 scope=10 belongs-to="Connected route"
local-address=fe80::3:5797:fc5d%HE
debug.fwp-ptr=0x20243300
 
User avatar
nz_monkey
Forum Guru
Forum Guru
Posts: 2095
Joined: Mon Jan 14, 2008 1:53 pm
Location: Over the Rainbow
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 3:02 am

Currently there is no mechanism to count exact session prefixes, That is why this parameter is not even set. If you want to know exact prefixes installed in the routing table received from a specific peer, then use /roruting route print command with appropriate filtering options, like "belongs-to" or "bgp.peer-cache-id"
I sincerely hope that Mikrotik developers are working on a solution to this.

I am still in awe that critical and basic operational BGP features such as:

- Set max-prefix-limit and a restart time on a per peer basis
- View advertised-prefixes on a per peer basis
- View received-prefixes on a per peer basis


Were not considered in the design of the new routing engine.

The ability to view advertised and received prefixes on a per peer basis was raised as a requirement well in advance of V7 routing existing:
viewtopic.php?t=114186&hilit=advertised ... es#p566169
viewtopic.php?t=93106&hilit=advertised+prefixes#p533595

And I never thought such a critical feature like max-prefix-limit could be overlooked!
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 3:57 am

I think they always intended to implement the prefix count for received prefixes, otherwise the field to display the prefix count would not be there, rather than being there but displaying zero instead of the correct value. For the other things, I agree, I'm not sure why they weren't anticipated as being needed.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 4:22 am

Just tested v7.3beta33 to see how VPLS works given that this finally has MPLS fixes. VPLS still hangs the device. One ping goes through the tunnel and gets responded to, followed by one of the four CPU's on my 4011 going to 100% CPU utilization and the device becoming completely unresponsive, requiring me to pull the power and plug it back in physically to get it working again.

I know VPLS is working for some people but others have the same problems as me, and I can't risk even deploying this to a remote location as a test device if the only fix is to physically pull the power which may require a trip.
Last edited by mducharme on Thu Apr 14, 2022 4:49 am, edited 1 time in total.
 
User avatar
StubArea51
Trainer
Trainer
Posts: 1739
Joined: Fri Aug 10, 2012 6:46 am
Location: stubarea51.net
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 4:38 am


- View received-prefixes on a per peer basis[/b]

This is the only way I have been able to get received prefix count by peer - it's a bit buried

Came across it when I was doing testing of full table convergence on the CCR2216s because I needed to evaluate total route count
[zuul@ccr2216-02.test.lab.ipa] > routing/stats/origin/print interval=1 where instance-id=1686070274
Flags: Y - synthetic; Z - terminal; X - stopping; D - owner-dead; H - hold; U - attrs-updated; M - attrs-merge 
12         name="BGP IP routes from 198.18.92.254" instance-id=1686070274 publisher-idx=12 route-type="8" owner=28 route-count=0,387726,0,0,0,0,0,0,0,0,0,0,0 total-route-count=387726 

13         name="BGP IP routes from 198.18.92.253" instance-id=1686070274 publisher-idx=13 route-type="8" owner=30 route-count=0,329737,0,0,0,0,0,0,0,0,0,0,0 total-route-count=329737 

14         name="BGP IP routes from 100.126.100.1" instance-id=1686070274 publisher-idx=14 route-type="8" owner=31 route-count=0,517453,0,0,0,0,0,0,0,0,0,0,0 total-route-count=517453 
 
Railander
Frequent Visitor
Frequent Visitor
Posts: 85
Joined: Thu Jun 16, 2016 11:30 pm

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 9:44 am

Please allow us to select Address Lists for the Networks in OSPF interface-templates, we can already do this with BGP.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 10:11 am

Doesn't sound the new routing engine was very well thought out before implementing.
How is it possible that basic features were not even considered during the design phase?
+1
Not only that, but it takes ages and many versions to get it fixed.
Don't be ridiculous. Bare essential functionality is very well though out and has the highest development priority. Which means that features that are not absolutely essential for BGP to work or their functionality can be done alternatively with other already existing features but in a bit less convenient way has lower priority. What you are asking here are mostly cosmetic things with lower priority. Pretty GUI and convenient counters are not the things that are needed for BGP to work properly, but it does not mean that these features will not be implemented ever (as already mentioned in this topic and other topics).

From your requests should we stop working for example, on BFD support, just to implement cosmetic counter in session stats? Or should we stop fixing found problems just to try to make pretty GUI for routing filters?
Prefix count per peer
Prefix count per peer can easily be extracted from /routing route print count only or from /routing stats origin
- View received-prefixes on a per peer basis
Already possible. from /routing route menu, see few posts above
- View advertised-prefixes on a per peer basis
Already possible starting from v7.2
max-prefix-limit
You are commenting on the versions topic where this is already possible
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 10:36 am


+1
Not only that, but it takes ages and many versions to get it fixed.
Don't be ridiculous. Bare essential functionality is very well though out and has the highest development priority. Which means that features that are not absolutely essential for BGP to work or their functionality can be done alternatively with other already existing features but in a bit less convenient way has lower priority. What you are asking here are mostly cosmetic things with lower priority. Pretty GUI and convenient counters are not the things that are needed for BGP to work properly, but it does not mean that these features will not be implemented ever (as already mentioned in this topic and other topics).

From your requests should we stop working for example, on BFD support, just to implement cosmetic counter in session stats? Or should we stop fixing found problems just to try to make pretty GUI for routing filters?
I have posted the list of features we NEED to have to be able to deploy v7 several times. BFD is certainly at the top of that list, but there are several others:
- working aggregation, both as a source and when processing/forwarding aggregated routes
- working route refresh (when filters are changed, for example)
- meaningful error messages when some connection fails, not "Holdtime expired, session *=0x30110240" but a session NAME instead. nor "Write to bgp failed (32) { #buf=1 max=64 sk=Socket{ 5[" but some message that includes a session name instead, so I can know where to look for a potential problem.

And, monitoring the situation is not "purely cosmetic"! Monitoring is important. We have tens of BGP peers, others have hundreds. It has always been kind of tricky with MikroTik (e.g. no SNMP support for BGP monitoring) but then at least I could write some scripts that send e-mail when certain things change, and have a winbox open to the main router displaying a table of BGP sessions, which I can glance at a couple of times per day. When I suddenly see a lot more blank spaces and/or unfamiliar prefix counts I know something is wrong and I need to look closer.

A lot of these facilities have been removed for a BGP rewrite that frankly brings us absolutely nothing. I can understand it was important for those that want to do full table internet BGP, but we are not doing that. We use BGP in a closed network with routes numbered in the hundreds, not hundreds of thousands. The old BGP in v6 worked FINE, within the limitations of BGP as a protocol that is (we would have liked to have a routing protocol that optimizes for wireless links of varying quality!).

I do support that you improve things for others, but I do not like that at the same time you take away basic features for other users. And I'm sure there are more like us, who use BGP as an autorouting protocol in a smaller network.
It would have been best when BGP had been made an optional package, like in the past was done with wireless a couple of times, where a user could choose between v6 BGP and v7 BGP, and select between the existing working version and experimenting with the new version. In that case we could have upgraded all our routers to v7 already and continue to use the existing BGP. But I understand that was too much work and wasn't feasible. However what I do not understand is why this new v7 with the new BGP takes so long to get feature-complete. After all, we are hearing nearly 10 years from MikroTik about this exciting new routing engine that will be part of v7 and will end all troubles. After all that preparation it could have been a bit more polished.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 11:04 am

You are missing the point, should we stop working on these features then just to implement prefix counter to show up in BGP session?
You are willing to tolerate BGP crashes that we could fix instead of possibility to get a counter in a specific manner?

You already can get prefix count with methods mentioned previously. If you already had a script to get prefix count for monitoring of ROS v6, then only difference is that this script line will look a bit different for ROS v7. Its not like you cannot get prefix count at all.
I have posted the list of features we NEED to have to be able to deploy v7 several times. BFD is certainly at the top of that list, but there are several others:
- working aggregation, both as a source and when processing/forwarding aggregated routes
- working route refresh (when filters are changed, for example)
- meaningful error messages when some connection fails, not "Holdtime expired, session *=0x30110240" but a session NAME instead. nor "Write to bgp failed (32) { #buf=1 max=64 sk=Socket{ 5[" but some message that includes a session name instead, so I can know where to look for a potential problem.
 
mafiosa
Member Candidate
Member Candidate
Posts: 266
Joined: Fri Dec 09, 2016 8:10 pm
Location: Kolkata, India
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 11:10 am

You are missing the point, should we stop working on these features then just to implement prefix counter to show up in BGP session?
You are willing to tolerate BGP crashes that we could fix instead of possibility to get a counter in a specific manner?

You already can get prefix count with methods mentioned previously. If you already had a script to get prefix count for monitoring of ROS v6, then only difference is that this script line will look a bit different for ROS v7. Its not like you cannot get prefix count at all.
VxLAN tunnels keep lose their previous mac address after every reboot. It is a big issue because on one of our peering LANs we have mac filtering. Kindly take a note. Already opened a ticket a month ago. If any internal testing is needed for the same I am willing to do it.
 
User avatar
Larsa
Forum Guru
Forum Guru
Posts: 1025
Joined: Sat Aug 29, 2015 7:40 pm
Location: The North Pole, Santa's Workshop

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 11:41 am

Meaningful error messages when some connection fails, not "Holdtime expired, session *=0x30110240" but a session NAME instead. nor "Write to bgp failed (32) { #buf=1 max=64 sk=Socket{ 5[" but some message that includes a session name instead, so I can know where to look for a potential problem.
Regarding cryptic error messages, I am really surprised that MT didn't take the opportunity to introduce error numbering in V7 that could be explained in more details on, for example, the help page and a corresponding text file with error messages (which is a good solution if you want to keep the program size down)

However what I do not understand is why this new v7 with the new BGP takes so long to get feature-complete. After all, we are hearing nearly 10 years from MikroTik about this exciting new routing engine that will be part of v7 and will end all troubles. After all that preparation it could have been a bit more polished.
Just speculating but perhaps MT made a decision that instead of starting from an OSS version, develops its own BGP stack from scratch which is a challenge when it comes to adding new features.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 11:46 am

You are missing the point, should we stop working on these features then just to implement prefix counter to show up in BGP session?
You are willing to tolerate BGP crashes that we could fix instead of possibility to get a counter in a specific manner?
No, but every new release there are many items in the changelist that are about fixing features that are new to v7 and usually there are almost no changelist items related to BGP.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 11:50 am

Meaningful error messages when some connection fails, not "Holdtime expired, session *=0x30110240" but a session NAME instead. nor "Write to bgp failed (32) { #buf=1 max=64 sk=Socket{ 5[" but some message that includes a session name instead, so I can know where to look for a potential problem.
Regarding cryptic error messages, I am really surprised that MT didn't take the opportunity to introduce error numbering in V7 that could be explained in more details on, for example, the help page and a corresponding text file with error messages (which is a good solution if you want to keep the program size down)
And also to filter and recognize error messages in either internal scripts or an external system...
But of course there is always something we can wish to have additionally. However what I wanted to indicate is that the above messages are only relevant to a programmer at MikroTik, who has the software running under a debugger. For a customer they are meaningless, they do not know how to map those pointer or fd values to configuration items like BGP sessions. And it is not like it is a multi-day job to print a session name instead of a pointer to a control block. Probably more time has been spent on discussing the problem than would have to be spent on fixing it.
 
hecatae
Member Candidate
Member Candidate
Posts: 244
Joined: Thu May 21, 2020 2:34 pm

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 11:53 am

Has anyone updated a chateau yet?
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 11:58 am

and usually there are almost no changelist items related to BGP.
Exactly because of the above mentioned priorities. According to forum users "bgp advertisements" and "prefix limits" were the most essential features, so it was set as a highest priority and took all the development time instead of fixing actually important problems.
It is all about the priorities you guys are pushing.
develops its own BGP stack from scratch which is a challenge
Exactly that and it was not just a BGP that got a rewrite, whole routing stack was completely rewritten.

More user friendly BGP logging is in a TODO list.
 
User avatar
slimmerwifi
just joined
Posts: 15
Joined: Tue Aug 01, 2017 6:05 pm
Location: Netherlands

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 12:13 pm

It is all about the priorities you guys are pushing.
Fair enough! Then I'd like to push these and thank you for the amazing work you've done so far on V7!

P1 - Support desk needs help, we have 3 tickets waiting on response since January.
P2 - Finish the new wifi driver, make it available for current wave2 devices
P3 - Capsman V7 with new wifi driver
P4 - Announce Cap AX and Cap AX-E 2x2 & 4x4
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 12:18 pm

and usually there are almost no changelist items related to BGP.
Exactly because of the above mentioned priorities. According to forum users "bgp advertisements" and "prefix limits" were the most essential features, so it was set as a highest priority and took all the development time instead of fixing actually important problems.
It is all about the priorities you guys are pushing.
Actually I have mentioned my BGP priorities from the first time I ran a v7 beta and that was way before those things came up.
But as far as I'm concerned, the only thing that was fixed that helped me was the route filtering (that had obvious bugs)...
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 12:41 pm

The same question again, do you think that we should stop working on BFD or fixing crashes to make pretty BGP logs?
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 12:48 pm

I have not experienced any crashes so far. But I think having readable logs is important, only second to making BFD work. When you see things like this in the log regularly:
Apr/06/2022 10:39:06 route,bgp,error HoldTimer expired
Apr/06/2022 10:39:06 route,bgp,error     Session *=0x30100010
Apr/06/2022 10:39:12 route,bgp,error HoldTimer expired
Apr/06/2022 10:39:12 route,bgp,error     Session *=0x301a0470
Apr/06/2022 10:39:14 route,bgp,error HoldTimer expired
Apr/06/2022 10:39:14 route,bgp,error     Session *=0x30190240
Apr/06/2022 10:40:00 script,info 194.109.6.8 is up
Apr/06/2022 10:40:35 route,bgp,error HoldTimer expired
Apr/06/2022 10:40:35 route,bgp,error     Session *=0x30080010
Apr/06/2022 10:40:57 route,bgp,info Connection closed 
Apr/06/2022 10:40:57 route,bgp,info     Session *=0x30180010
Apr/06/2022 10:41:03 script,warning 44.137.0.1 is down
Apr/06/2022 10:41:06 route,bgp,info Connection closed 
Apr/06/2022 10:41:06 route,bgp,info     Session *=0x30190240
Apr/06/2022 10:41:07 route,bgp,info Connection closed 
Apr/06/2022 10:41:07 route,bgp,info     Session *=0x30100010
Apr/06/2022 10:41:13 route,bgp,error HoldTimer expired
Apr/06/2022 10:41:13 route,bgp,error     Session *=0x30160470
it is clear that this is not about "making the log pretty". It is about making the log USABLE.
 
User avatar
Larsa
Forum Guru
Forum Guru
Posts: 1025
Joined: Sat Aug 29, 2015 7:40 pm
Location: The North Pole, Santa's Workshop

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 12:51 pm

And also to filter and recognize error messages in either internal scripts or an external system...
Hear, hear... Fighting with scripts and filters that fails is a challenge when there is no way to capture error messages (or the lack of error numbers)

Probably more time has been spent on discussing the problem than would have to be spent on fixing it.
Yeah, I know the feeling. Should be the opposite, ie 20% troubleshooting and 80% fixing the problems.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 12:57 pm

Maybe create the poll? Should we stop fixing crashes and switch to working on pretty logs because you do not experience crashes ?
 
hecatae
Member Candidate
Member Candidate
Posts: 244
Joined: Thu May 21, 2020 2:34 pm

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 12:59 pm

Has anyone updated a chateau yet?
Chateau12 updated, running well
 
huntermic
Member Candidate
Member Candidate
Posts: 111
Joined: Wed Oct 26, 2016 3:42 pm

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 1:08 pm

Maybe create the poll? Should we stop fixing crashes and switch to working on pretty logs because you do not experience crashes ?
No poll needed, continue as you are currently doing.
It took way to long to come with some form of V7 so we are all a bit grumpy that after many years there still is a lot wrong.
But i think you are on the right track last few years.
 
User avatar
iossol
just joined
Posts: 14
Joined: Wed Apr 16, 2014 6:27 pm
Location: Nuremberg / Germany

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 1:21 pm

chr updatet from 7.2.1 to 7.3beta33 with success

still no ipv6 traffic over eoip (ipv4) interface
no traffic over an eoip-bond (active-backup with arp-monitoring) when interface is assigned to a bridge, monitoring ip of bonding-interface moves to bridge ?
same setup with ros 6.49 works as expected
 
Pl07R3K
just joined
Posts: 14
Joined: Fri Feb 11, 2022 4:15 pm

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 2:10 pm

Still can't configure HT MCS for quad stream in CAPsMAN (/caps-man/rates/set 0 ht-supported-mcs=mcs-24,...), unlike outside CAPsMAN where it is possible (/interface/wireless/set 0 ht-supported-mcs=mcs-24,...).
Does anyone know why and if this is a bug?

By the way do you know when WAVE2 support in CAPsMAN is planned?
 
psannz
Member Candidate
Member Candidate
Posts: 127
Joined: Mon Nov 09, 2015 3:52 pm
Location: Renningen, Germany

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 2:30 pm

Maybe create the poll? Should we stop fixing crashes and switch to working on pretty logs because you do not experience crashes ?
Please do not.
While each and everyone of us has various priorities, we can not forget, that we as users will never see the complete picture in terms of problems and issues.

Maybe instead offer us an overview of new features and/or improvements, that are currently beeing worked on.
Some of us may be sad to see their idea in the backlog, while others may be happy to see work has acutually started on theirs.

Or actually do a poll, on what *new features* or *improvements* should be worked on next. Security and Bugfixes obviously always come first.
Just don't forget to feed the poll the enterprise feedback you recieve outside of the forums ;)

Then again, we'd still be bitching. It's simply impossible to make everyone happy :D
 
User avatar
anthonws
Frequent Visitor
Frequent Visitor
Posts: 76
Joined: Sat Jan 09, 2016 6:46 pm

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 3:02 pm

The same question again, do you think that we should stop working on BFD or fixing crashes to make pretty BGP logs?
Fixing bad code vs implementing needed (basic) features is not a sane tradeoff to ask customers.
And to be honest, your tone was not the most polite with that "ridiculous" comment.
If you're asking customers to prioritize bug fix vs feature then something is wrong at your engineering priorities.
Either you need more resources to focus on code stability or you need to re-work your priorities and be *upfront* to your customers about those (explain the roadmap, lack of resources challenge, re-write of core features, etc.).
What the other users have said is totally legit. From the outside, it does seem basic things were not accounted for. And this is only natural to be folks observation that are sitting from outside, that have no context about what are the issues right now in your code base and engineering resources.
Long story short. You have an amazing customer base, that is willing to endure a lot and provide a lot of feedback and take risks in testing things and being part of a true community.
People believe in you and MT is doing an amazing work.
Your comment should have been something along the lines of: "We acknowledge the lack of these basic things. Please note that there are a couple of workarounds right now that we hope are useful for you. Please understand that we are working hard on fixing major bugs before adding them and focusing on other core major features are top priority olfor our large customer base.".

My 2 cents

anthonws.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 3:20 pm

Literally that is what was said when this conversation started.
 
kowal
newbie
Posts: 30
Joined: Sun Jul 06, 2014 2:23 am

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 4:14 pm

Will containers be continued? I have hAP ac3 on version 7.1rc4 but if this feature needs more work I will update to 7.2.1.
 
cma1kep
just joined
Posts: 9
Joined: Tue Sep 11, 2012 8:32 am

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 4:27 pm

any news on BGP multipathing(ECMP)?
 
ormandj
just joined
Posts: 18
Joined: Tue Jun 15, 2021 12:25 am

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 5:24 pm

@mrz

SUP-68278 Has been unanswered since December. You mention focusing on real issues and not cosmetics and I and others have massive port flapping issues on CRS328 series switches that seem to be associated with NAND writes that started with the very first 7.x updates and have persisted through all new versions. Can someone please look at this? It’s now affecting even Ethernet ports and not just SFP+. This is a massively serious issue for us.

I am unclear why we can get no response on a ticket for coming up on four months now, with multiple acknowledged cases of this very instance on this forum across multiple release threads. I don’t want to spam every thread like some keep doing, but this has made this hardware nearly unusable.
Last edited by ormandj on Fri Apr 15, 2022 2:30 pm, edited 5 times in total.
 
hecatae
Member Candidate
Member Candidate
Posts: 244
Joined: Thu May 21, 2020 2:34 pm

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 5:32 pm

Any RB5009 owners updated?
 
elgrandiegote
newbie
Posts: 40
Joined: Tue Feb 05, 2013 6:02 am
Location: Buenos Aires, Argentina

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 6:14 pm

ovpn udp keeps disconnecting like in previous versions, it's already frustrating to try and keep going the same...
 
mafiosa
Member Candidate
Member Candidate
Posts: 266
Joined: Fri Dec 09, 2016 8:10 pm
Location: Kolkata, India
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 14, 2022 7:19 pm

Any RB5009 owners updated?
Yup but why?
 
User avatar
Znevna
Forum Guru
Forum Guru
Posts: 1347
Joined: Mon Sep 23, 2019 1:04 pm

Re: v7.3beta [testing] is released!

Fri Apr 15, 2022 6:08 am

Yes, keep asking for fixes for kritikal features like openvpn and socks5 and other crap, that helps the team focus on the right stuff.
 
User avatar
benlg
just joined
Posts: 10
Joined: Mon Jan 31, 2022 2:50 pm

Re: v7.3beta [testing] is released!

Fri Apr 15, 2022 8:27 am

Yes, IPsec / IKEv2 should rather be used instead IMO...
Properly supported by MikroTik, and by all OSes / mobiles devices etc...
Much nicer solution...
 
DenisPDA
Frequent Visitor
Frequent Visitor
Posts: 63
Joined: Tue Sep 04, 2018 5:42 pm

Re: v7.3beta [testing] is released!

Fri Apr 15, 2022 10:12 am

7.3beta33 MT killer
CHR - Kernel panic
hap ac2 - unable to load configuration
You do not have the required permissions to view the files attached to this post.
 
rpingar
Long time Member
Long time Member
Posts: 592
Joined: Fri May 28, 2004 2:46 pm
Location: Italy

Re: v7.3beta [testing] is released!

Fri Apr 15, 2022 10:28 am

7.3beta33 fixed MikroTik support #[SUP-78769]: x86 v7.2 all rcs always reports interfaces intel E810-C as running!

regrds
Ros
 
User avatar
pekr
Member Candidate
Member Candidate
Posts: 169
Joined: Tue Feb 22, 2005 9:05 pm
Location: Czech Republic
Contact:

Re: v7.3beta [testing] is released!

Fri Apr 15, 2022 10:36 am

P3 - Capsman V7 with new wifi driver
P4 - Announce Cap AX and Cap AX-E 2x2 & 4x4

+1 here. I would like to experiment with the Aruba replacement :-)
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Fri Apr 15, 2022 10:45 am

Yes, IPsec / IKEv2 should rather be used instead IMO...
Properly supported by MikroTik, and by all OSes / mobiles devices etc...
Much nicer solution...
This week I was researching why my Chromebook L2TP/IPsec VPN (to a CCR running RouterOS v6.49.5) was no longer working after an update. It cut out after 3 minutes.
Turns out to be a bug in the Chromebook, it seems it no longer supports IPsec DPD (firewall issue?). As L2TP of course has its own keepalive I have disabled the DPD in the IPsec profile used for L2TP/IPsec connections, and it works again (I explain it here because maybe other users are helped by this).
However, as part of this excercise I thought I'd just set it to IKEv2. I have a configuration ready on our router, but unfortunately ChromeOS does not support IKEv2.
Having solved the original problem I tried IKEv2 on Android. Wanted to use split-tunnel with multiple networks behind the VPN. I have a Mode Config with 3 networks in the Split Include. Does not work, Android takes only the first one (in L2TP/IPsec you can manually configure a list of networks in the client. a lot of fiddling but at least it works).
The whole IPsec VPN support on different architectures is still in a sad, sad state! No wonder that people devise ad-hoc solutions like OpenVPN and Wireguard all the time.
 
User avatar
benlg
just joined
Posts: 10
Joined: Mon Jan 31, 2022 2:50 pm

Re: v7.3beta [testing] is released!

Fri Apr 15, 2022 10:51 am

I agree about split-tunnelling issue with multiple networks, only the first subnet is considered by some clients, and especially macOS.
SUP-59668 created months ago regarding this, MikroTik knows the issue and will fix it (as the problem is on RouterOS side), but no ETA unfortunately :-/

For Android, strongSwan client should help :)
 
ZupoLlask
just joined
Posts: 17
Joined: Mon Jan 26, 2015 1:26 pm

Re: v7.3beta [testing] is released!

Fri Apr 15, 2022 11:17 am

Sorry about this one guys, but every time we have a new version released I see some kind of battle here and I sort of (unfortunately) understand both sides.

Thing is: it is non-sense to ask a customer if MikroTik should focus or not on any (kind of) feature that... crashes one device. Crashing is that kind of behavior that should (almost) never happen.

I'm sorry but that kind of "feedback" from MikroTik is non-constructive and feeds some anger in the customers/community.

And as I sort of recognize/understand the tone of @mrz, I guess that he's in real need of vacations! 🙃
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Fri Apr 15, 2022 11:36 am

I agree about split-tunnelling issue with multiple networks, only the first subnet is considered by some clients, and especially macOS.
SUP-59668 created months ago regarding this, MikroTik knows the issue and will fix it (as the problem is on RouterOS side), but no ETA unfortunately :-/
Ah thanks, I believed it was an Android issue. Well, hopefully it will be solved sometime.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Fri Apr 15, 2022 11:47 am

Sorry about this one guys, but every time we have a new version released I see some kind of battle here and I sort of (unfortunately) understand both sides.

Thing is: it is non-sense to ask a customer if MikroTik should focus or not on any (kind of) feature that... crashes one device. Crashing is that kind of behavior that should (almost) never happen.
The "so you think we should not focus on bugs that crash the device" is a non-sequitur introduced by mrz. Of course I am not against working on solving crashes. But I am against promoting a new major release to "stable" status (and prominently recommending it for installation on the webpage) before it is even feature-complete relative to the previous one (and without mentioning that in the description).

There apparently is a (human) resource bottleneck in working on BGP and other (auto)routing. I do not know which of the MikroTik employees is/are working on this and if we ever see them here, but it looks like they are overburdened in finishing their work. I somehow doubt that all of the employees work on all of the issues, and that fixing problems that crash the router e.g. via some kernel panic has much impact on the work that can be done on e.g. BFD or logging. But maybe I am wrong.
 
User avatar
NetHorror
just joined
Posts: 21
Joined: Fri Dec 06, 2013 8:12 am

Re: v7.3beta [testing] is released!

Fri Apr 15, 2022 2:34 pm

*) zerotier - added support for Controller configuration;

any documentation?
 
User avatar
StubArea51
Trainer
Trainer
Posts: 1739
Joined: Fri Aug 10, 2012 6:46 am
Location: stubarea51.net
Contact:

Re: v7.3beta [testing] is released!

Sat Apr 16, 2022 5:29 am

Tested prefix limit in BGP. It works but requires a manual clearing of the peering. Would be nice to have a timer and retry in future releases.

[zuul@ccr2216-01.test.lab.ipa] > routing/bgp/connection/disable 0
[zuul@ccr2216-01.test.lab.ipa] > routing/bgp/connection/set input.limit-process-routes-ipv4=5000 0
[zuul@ccr2216-01.test.lab.ipa] > routing/bgp/connection/enable 0
[zuul@ccr2216-01.test.lab.ipa] > routing/bgp/session/print 
Flags: E - established 
 0   remote.address=198.18.91.254 .refused-cap-opt=no 
     local.address=198.18.91.1 
     output.last-notification=ffffffffffffffffffffffffffffffff0015030601 limit-exceeded 
[zuul@ccr2216-01.test.lab.ipa] > routing/bgp/connection/set input.limit-process-routes-ipv4=1000000 0
[zuul@ccr2216-01.test.lab.ipa] > routing/bgp/session/clear 0
flag: 
input-last-notification  limit-exceeded  output-last-notification  refused-cap-opt  stopped
flag: limit-exceeded
[zuul@ccr2216-01.test.lab.ipa] > routing/bgp/session/print 
Flags: E - established 
 0 E remote.address=198.18.91.254 .as=65101 .id=198.18.91.254 .refused-cap-opt=no .capabilities=mp,rr,role,gr,as4 .messages=227341 .bytes=22502859 .eor="" 
     local.address=198.18.91.1 .as=8675309 .id=100.127.100.101 .capabilities=mp,rr,gr,as4 .messages=1 .bytes=19 .eor="" 
     output.procid=60 .filter-chain=deny-all .last-notification=ffffffffffffffffffffffffffffffff0015030601 
     input.procid=60 .limit-process-routes=1000000 ebgp 
     hold-time=3m keepalive-time=1m uptime=34s270ms 
[zuul@ccr2216-01.test.lab.ipa] > 
 
markonen
just joined
Posts: 23
Joined: Tue Aug 11, 2020 4:28 pm

Re: v7.3beta [testing] is released!

Sat Apr 16, 2022 10:11 am

But I am against promoting a new major release to "stable" status (and prominently recommending it for installation on the webpage) before it is even feature-complete relative to the previous one (and without mentioning that in the description). … There apparently is a (human) resource bottleneck in working on BGP and other (auto)routing. I do not know which of the MikroTik employees is/are working on this and if we ever see them here, but it looks like they are overburdened in finishing their work.
I think MikroTik's strategy has painted them into a corner here. On one hand, they have been forced to start shipping an OS with a newer Linux kernel because they can no longer reasonably backport hardware support to the old kernels. The writing has been on the wall for two years now, with the introduction of the CCR2004-1G-12S+2XS it became obvious that ROS v6 could not be made to support all new hardware properly.

On the other hand, they continue to introduce brand new hardware models in 2022 with 16MB of storage and insist that all of these models must run the same OS image. That has the practical consequence that they have to write every single component of RouterOS by themselves, because no open source components fit these absurd constraints. From trivial things like the SSH daemon that still doesn't support EC keys to all of the routing protocol implementations, industry standard open source implementations are off the table.

A CCR2216 would be an amazing box to run something like Bird, FRR, OpenBGPD etc on. And perhaps the Docker support will make that possible one day. But today we can't have a full-featured, battle-tested BGP implementation in a €2k router because it would not fit on a €30 hEX lite. That's called a "strategy tax".
 
Florian
Member Candidate
Member Candidate
Posts: 117
Joined: Sun Mar 13, 2016 9:45 am
Location: France

Re: v7.3beta [testing] is released!

Sat Apr 16, 2022 12:13 pm

*) sfp - added 2.5Gbps rate for SFP+ and QSFP+ interfaces on 98DXxxxx and 98PX1012 switches (requires disabled auto-negotiation);



It is possible to add this for TileGX based product ? I would love to be able to use my 2.5gb ONT HGSMII directly into one of the sfp+ port...
 
User avatar
Cha0s
Forum Guru
Forum Guru
Posts: 1135
Joined: Tue Oct 11, 2005 4:53 pm

Re: v7.3beta [testing] is released!

Sun Apr 17, 2022 12:13 am

You are missing the point, should we stop working on these features then just to implement prefix counter to show up in BGP session?
Actually, you are the one missing the point.

These things should have been part of the pre-alpha release of V7 BGP.
Not get implemented as an afterthought or as 'cosmetic niceties'.

Pretty GUI and convenient counters are not things needed for BGP to work properly, but are things needed for BGP to be USED properly.

If it is that much difficult to implement basic stuff like showing the prefix count and advertisements (and no, pcap dumps is a joke), that it would take sooo much time from implementing and fixing other BGP stuff, then something is seriously wrong with the new BGP implementation.
 
tangent
Forum Guru
Forum Guru
Posts: 1333
Joined: Thu Jul 01, 2021 3:15 pm
Contact:

Re: v7.3beta [testing] is released!

Sun Apr 17, 2022 12:35 am

If it is that much difficult to implement basic stuff like showing the prefix count and advertisements (and no, pcap dumps is a joke), that it would take sooo much time from implementing and fixing other BGP stuff, then something is seriously wrong with the new BGP implementation.

Either that, or you don't know how it's implemented and why it's implemented that way, and you're making prescriptions from that point of ignorance.

The old (v6) BGP implementation was single-threaded, which caused it to have serious scalability problems. We can no longer depend on more GHz to solve problems like this. Instead, we rely on more CPU cores, but to make use of that, you need a parallel implementation, which requires a rewrite. You can't just take a single-threaded program and launch N threads on it and expect it to work properly because reasons

In rewriting their BGP implementation to be multi-core friendly, they caused there to be no single location for certain details like these counters you're wanting. It's possible to bottleneck everything down to a single thread to collate these values, but in doing so, you throw away the speed advantage of v7's BGP implementation.

I get that you want all of the features, and you want them 2 years ago. However, you might want to consider the possibility that MikroTik's software developers are doing their best with the resources they have.
 
Fmarte
just joined
Posts: 8
Joined: Sun Sep 27, 2020 11:51 pm

Re: v7.3beta [testing] is released!

Sun Apr 17, 2022 10:47 pm

Hello Masters.

100% cpu after update 7.2 or 7.3beta, any ideas?

Test downgrading to 7.1.5 and there is no problem.

Please healp.
 
mafiosa
Member Candidate
Member Candidate
Posts: 266
Joined: Fri Dec 09, 2016 8:10 pm
Location: Kolkata, India
Contact:

Re: v7.3beta [testing] is released!

Sun Apr 17, 2022 10:53 pm

Which device are you using?
 
Fmarte
just joined
Posts: 8
Joined: Sun Sep 27, 2020 11:51 pm

Re: v7.3beta [testing] is released!

Sun Apr 17, 2022 11:32 pm

Oh sorry, very important fact.
x86 VPS.

As I check the cpu profile, it says that the cpu is at 100% in management.

:(
 
Fmarte
just joined
Posts: 8
Joined: Sun Sep 27, 2020 11:51 pm

Re: v7.3beta [testing] is released!

Mon Apr 18, 2022 1:36 am

I see a similar problem has been reported before.

viewtopic.php?p=927312#p927312
 
shyrwall
just joined
Posts: 19
Joined: Tue Nov 08, 2011 10:45 pm

Re: v7.3beta [testing] is released!

Mon Apr 18, 2022 8:14 am

If it is that much difficult to implement basic stuff like showing the prefix count and advertisements (and no, pcap dumps is a joke), that it would take sooo much time from implementing and fixing other BGP stuff, then something is seriously wrong with the new BGP implementation.

Either that, or you don't know how it's implemented and why it's implemented that way, and you're making prescriptions from that point of ignorance.

The old (v6) BGP implementation was single-threaded, which caused it to have serious scalability problems. We can no longer depend on more GHz to solve problems like this. Instead, we rely on more CPU cores, but to make use of that, you need a parallel implementation, which requires a rewrite. You can't just take a single-threaded program and launch N threads on it and expect it to work properly because reasons

In rewriting their BGP implementation to be multi-core friendly, they caused there to be no single location for certain details like these counters you're wanting. It's possible to bottleneck everything down to a single thread to collate these values, but in doing so, you throw away the speed advantage of v7's BGP implementation.

I get that you want all of the features, and you want them 2 years ago. However, you might want to consider the possibility that MikroTik's software developers are doing their best with the resources they have.

This is completely false and shows no understanding on threading. If we're able to use filters for export/import of prefixes that shows there should not be any reason not to also add a counter to that since there's already logic in place to permit or deny prefixes.
 
shyrwall
just joined
Posts: 19
Joined: Tue Nov 08, 2011 10:45 pm

Re: v7.3beta [testing] is released!

Mon Apr 18, 2022 8:17 am

You are missing the point, should we stop working on these features then just to implement prefix counter to show up in BGP session?
You are willing to tolerate BGP crashes that we could fix instead of possibility to get a counter in a specific manner?
Yes you should. You first implement basic features according to industry standard spec. Bugs will get found forever.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Mon Apr 18, 2022 10:14 am

This is completely false and shows no understanding on threading. If we're able to use filters for export/import of prefixes that shows there should not be any reason not to also add a counter to that since there's already logic in place to permit or deny prefixes.
Peeking from the outside in the black box it appears that the new BGP has a separate thread per peer, that just accepts all routes from the peer and puts them into a big table, and then the filtering is done in another thread that marks those table entries with a filtered/not_filtered status, and the active route is chosen from those that are not filtered.
So, the process handling the peer connections does not know how many of the received routes actually make it past the filtering, and the filtering process has no "counters".
It is possible to get counts by doing searches on the table, like "how many routes received from this peer are not filtered", but it is a "costly" operation as it has to walk the entire table every time you want to obtain the count. It can be done in a script, but it isn't done in the "session overview".
Also, the command-line language does not make it easy. E.g.:
/routing/route/print where belongs-to="BGP IP routes from 1.2.3.4"
neatly prints all routes received from that peer.
/routing/route/print count-only
prints the total number of routes in the table. but:
/routing/route/print count-only where belongs-to="BGP IP routes from 1.2.3.4"
always prints zero :-( so you need to write a script that actually does the full print and counts the lines. what a waste!

It can be difficult to make an existing algorithm multi-threaded. And it obviously was an objective of the BGP rewrite, as (especially at that time) MikroTik routers have lots of cores and a single-threaded BGP would not effectively use them. But it looks like while making the multithreaded design, this particular aspect was overlooked or considered not that important.
 
shyrwall
just joined
Posts: 19
Joined: Tue Nov 08, 2011 10:45 pm

Re: v7.3beta [testing] is released!

Mon Apr 18, 2022 11:17 am

This is completely false and shows no understanding on threading. If we're able to use filters for export/import of prefixes that shows there should not be any reason not to also add a counter to that since there's already logic in place to permit or deny prefixes.
Peeking from the outside in the black box it appears that the new BGP has a separate thread per peer, that just accepts all routes from the peer and puts them into a big table, and then the filtering is done in another thread that marks those table entries with a filtered/not_filtered status, and the active route is chosen from those that are not filtered.
So, the process handling the peer connections does not know how many of the received routes actually make it past the filtering, and the filtering process has no "counters".
It is possible to get counts by doing searches on the table, like "how many routes received from this peer are not filtered", but it is a "costly" operation as it has to walk the entire table every time you want to obtain the count. It can be done in a script, but it isn't done in the "session overview".
Also, the command-line language does not make it easy. E.g.:
/routing/route/print where belongs-to="BGP IP routes from 1.2.3.4"
neatly prints all routes received from that peer.
/routing/route/print count-only
prints the total number of routes in the table. but:
/routing/route/print count-only where belongs-to="BGP IP routes from 1.2.3.4"
always prints zero :-( so you need to write a script that actually does the full print and counts the lines. what a waste!

It can be difficult to make an existing algorithm multi-threaded. And it obviously was an objective of the BGP rewrite, as (especially at that time) MikroTik routers have lots of cores and a single-threaded BGP would not effectively use them. But it looks like while making the multithreaded design, this particular aspect was overlooked or considered not that important.
If they designed it without communication between the peer-processes and the filter process(es) then I can understand why it wouldn't work. But that would be a strange way of designing it. The filter process gets the remote peer ip etc also so it's not that it just sees routes flying in without knowing where they came from.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Mon Apr 18, 2022 11:45 am

If they designed it without communication between the peer-processes and the filter process(es) then I can understand why it wouldn't work. But that would be a strange way of designing it. The filter process gets the remote peer ip etc also so it's not that it just sees routes flying in without knowing where they came from.
The peer communication process sees routes coming in but does not keep a table of them to know how many unique routes there are.
The filtering process runs through the central table and applies the filters but it sees all the routes so it is "difficult" to keep counts per peer (also because the other processes are feeding new data all the time).
Likely the only way to get approximate counts is by walking the table as-it-is, and to get accurate counts you need to "lock" the table while doing that.
Not something you want to do every second to keep a dynamically updated display, like we have in v6.
 
shyrwall
just joined
Posts: 19
Joined: Tue Nov 08, 2011 10:45 pm

Re: v7.3beta [testing] is released!

Mon Apr 18, 2022 12:13 pm

If they designed it without communication between the peer-processes and the filter process(es) then I can understand why it wouldn't work. But that would be a strange way of designing it. The filter process gets the remote peer ip etc also so it's not that it just sees routes flying in without knowing where they came from.
The peer communication process sees routes coming in but does not keep a table of them to know how many unique routes there are.
The filtering process runs through the central table and applies the filters but it sees all the routes so it is "difficult" to keep counts per peer (also because the other processes are feeding new data all the time).
Likely the only way to get approximate counts is by walking the table as-it-is, and to get accurate counts you need to "lock" the table while doing that.
Not something you want to do every second to keep a dynamically updated display, like we have in v6.
There is the following matchers in filters,

bgp-input-local-addr The IP address of the local peer to which the prefix was sent
bgp-input-remote-addr The IP address of the remote peer from which the prefix was received
bgp-output-local-addr The IP address of the peer that will advertise the prefix
bgp-output-remote-addr The IP address of the peer to which the prefix will be advertised

So if it has this info how is it difficult to count per-peer prefix pre and post filtering?
 
ormandj
just joined
Posts: 18
Joined: Tue Jun 15, 2021 12:25 am

Re: v7.3beta [testing] is released!

Mon Apr 18, 2022 3:08 pm

If they designed it without communication between the peer-processes and the filter process(es) then I can understand why it wouldn't work. But that would be a strange way of designing it. The filter process gets the remote peer ip etc also so it's not that it just sees routes flying in without knowing where they came from.
The peer communication process sees routes coming in but does not keep a table of them to know how many unique routes there are.
The filtering process runs through the central table and applies the filters but it sees all the routes so it is "difficult" to keep counts per peer (also because the other processes are feeding new data all the time).
Likely the only way to get approximate counts is by walking the table as-it-is, and to get accurate counts you need to "lock" the table while doing that.
Not something you want to do every second to keep a dynamically updated display, like we have in v6.
There is no way to know how it is designed, and conjecture doesn’t get us any closer to a fix. It’s probably best if we don’t continue cluttering a release thread with a ton of what-ifs and instead stick to just reporting issues. We can create threads (see what I did there) to debate the finer points of optimal concurrent design of BGP daemons elsewhere. I would hope/assume everything is threaded and not designed to run as separate processes per-peer as that would be awfully inefficient and wasteful - but it’s a discussion topic for another thread.

I’m stuck with switches that have flapping Ethernet and SFP ports now, BGP is getting better but still needs work, etc. Discourse about why or how MikroTik has written something we have no access to actually see is just drawing attention away from the very issues leading to that discussion, and while interesting to see how some think concurrency is implemented, it just detracts from the posts of the actual symptom needing resolving.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Mon Apr 18, 2022 3:18 pm

There is no way to know how it is designed, and conjecture doesn’t get us any closer to a fix.
There have been occasional descriptions by MikroTik employees of what has changed in BGP operation, and we can see what is going on in the routing table (filtered routes now appear in the table).
I am posting this only because people write "it is stupid that they do not just include a prefix counter" and while I agree with the end-result of that, I try to explain why it is not that simple.
 
ormandj
just joined
Posts: 18
Joined: Tue Jun 15, 2021 12:25 am

Re: v7.3beta [testing] is released!

Mon Apr 18, 2022 5:17 pm

There is no way to know how it is designed, and conjecture doesn’t get us any closer to a fix.
There have been occasional descriptions by MikroTik employees of what has changed in BGP operation, and we can see what is going on in the routing table (filtered routes now appear in the table).
I am posting this only because people write "it is stupid that they do not just include a prefix counter" and while I agree with the end-result of that, I try to explain why it is not that simple.
I understand where you are coming from, but at the end of the day, Mikrotik needs to hear the feedback, and we should not be defending them. They can do that themselves, if so inclined. I'm sure there are a multitude of reasons things have taken this long to progress, but there are some very real and serious issues ongoing right now with these releases, that impact multiple users, and it seems like non-Mikrotik-employed forum members are postulating reasons as to why instead of leaning on Mikrotik to address it themselves. At a certain point they need to see the volume of complaints to gauge need/interest, as it's already been made clear that is how they are prioritizing. Artificially tamping down the complaints by defending them isn't going to help with prioritization of these needed features/functionality.

I'm polluting this thread now too, so I will stop adding to the problem. I do appreciate and value your input, btw, and I think it is an interesting read (as are others who have been doing the same) - I just think we should keep it in other threads, not the main release thread.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Mon Apr 18, 2022 5:56 pm

I am not defending them, in fact I think it is a shame how version 7 BGP is dragging on and on and I have repeatedly expressed that here.
I am just explaining why (I think) it takes more than a "peer->prefix_count++" somewhere in that code to count the prefixes, while that was easy in v6.
In fact I would have preferred it when v6 BGP had been made available as an optional package so the users who use BGP only as a routing protocol for their private network could continue to use it (with full features and somewhat easier configuration) while those that use it for a couple of full internet routing tables could be considering switching over to a newer version with better performance.
 
buset1974
Frequent Visitor
Frequent Visitor
Posts: 86
Joined: Wed Sep 13, 2006 12:12 pm
Location: Jakarta

Re: v7.3beta [testing] is released!

Mon Apr 18, 2022 9:41 pm

v7 introduces years ago (i believe more than 5 years ago) and today in 2022 it's not even finished yet, how many years actually need to make the v7 full finished anyway?
 
User avatar
npeca75
Frequent Visitor
Frequent Visitor
Posts: 75
Joined: Thu Aug 03, 2017 3:12 pm

Re: v7.3beta [testing] is released!

Mon Apr 18, 2022 10:10 pm

rb760 iGS
still no SFP info
 
Guscht
Member Candidate
Member Candidate
Posts: 236
Joined: Thu Jul 01, 2010 5:32 pm

Re: v7.3beta [testing] is released!

Mon Apr 18, 2022 11:33 pm

It is perfectly fine to use the same key for multiple LACPs. We received a feature request asking for this option, I guess it was up to their network policy to use unique keys for each LACP. It was fairly easy to implement it in RouterOS, so here you go. :wink:
Sure this works?

I entered 5:
Screenshot 2022-04-18 222620.jpg

"5" in binary is "0101"
Screenshot 2022-04-18 222643.jpg

On the parnter/remote System:
Screenshot 2022-04-18 222953.jpg

But in the output 329 is shown:
Screenshot 2022-04-18 222721.jpg

And I am still confused when to use it? Do I have to use the same "key" on both ends of the trunk/bonding?
Whats the reason I should do this? I this a precaution so I cant accidentally plug-in the wrong ports on the other end?
What if I bond a ROS V6 with a V7? What is the default value on V6 systems?

And even with unmatching keys (5 / 329) and 17 on the remote system, the bond is Running and I can ping...
Screenshot 2022-04-18 223810.jpg
You do not have the required permissions to view the files attached to this post.
 
msatter
Forum Guru
Forum Guru
Posts: 2897
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v7.3beta [testing] is released!

Tue Apr 19, 2022 1:18 am

v7 introduces years ago (i believe more than 5 years ago) and today in 2022 it's not even finished yet, how many years actually need to make the v7 full finished anyway?
It will never be finished. The current plan is to finish first the new features and then bugfix things.

Still a lot to be done.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.3beta [testing] is released!

Tue Apr 19, 2022 3:53 am

And even with unmatching keys (5 / 329) and 17 on the remote system, the bond is Running and I can ping...
You missed this in the documentation I think:

lacp-user-key: Specifies the upper 10 bits of the port key. The lower 6 bits are automatically assigned based on individual port link speed and duplex.

So what you are seeing is correct and is the expected behavior. The lower 6 bits getting automatically assigned results in the 17 and 329.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.3beta [testing] is released!

Tue Apr 19, 2022 3:58 am

Still a lot to be done.
There is, but it is impressive the rate that things have been happening so far. They've been doing many many fixes. I think it is still a few months before I can consider putting it into limited production use but it is getting close.

And I think you meant to say, that they are focused on getting the things that were working properly in RouterOS v6 working properly in v7, and will then move on to focusing on bug fixes for the new features in v7 that were not in v6 as well as adding new features to v7.
Last edited by mducharme on Tue Apr 19, 2022 4:28 am, edited 1 time in total.
 
Fmarte
just joined
Posts: 8
Joined: Sun Sep 27, 2020 11:51 pm

Re: v7.3beta [testing] is released!

Tue Apr 19, 2022 4:16 am

Hello Mikrotik

please check the problem, error of 100% CPU X86 "management" process, it persists in 7.3 beta.

Both with Open VPN udp and tcp.

This error only occurs when the OpenVPN server is activated and some connections are established.

Thanks
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11381
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.3beta [testing] is released!

Tue Apr 19, 2022 7:50 am

please check the problem, error of 100% CPU X86 "management" process, it persists in 7.3 beta.
Which UI are you using when you observe this behaviour? If you're using winbox, does the same happen if you log in via ssh? Does the same happen if no management connection is alive (if you're using CHR, then you should be able to see VM resource usabe from hypervisor console)?
 
User avatar
NetHorror
just joined
Posts: 21
Joined: Fri Dec 06, 2013 8:12 am

Re: v7.3beta [testing] is released!

Tue Apr 19, 2022 1:09 pm

https://help.mikrotik.com/docs/display/ ... Tier-Moons

I found this page but "update-moon-json" not working
 
Guscht
Member Candidate
Member Candidate
Posts: 236
Joined: Thu Jul 01, 2010 5:32 pm

Re: v7.3beta [testing] is released!

Tue Apr 19, 2022 10:24 pm

You missed this in the documentation I think:

lacp-user-key: Specifies the upper 10 bits of the port key. The lower 6 bits are automatically assigned based on individual port link speed and duplex.

So what you are seeing is correct and is the expected behavior. The lower 6 bits getting automatically assigned results in the 17 and 329.

Thanks, this clears a bit the mystery - the left part is referred as "upper" part:
upper / lower
00000001 01001001

BUT, I updated now two devices to ROS 7.3, device1 with User key 10 and device2 with user key 15.
The bond comes up and works perfectly. Whats the benefit of the LACP User Key if UNmatching keys form a bond?

Is this simply a indicator in the monitoring section "Monitor Slaves" without any impact of the running state of the bond?
 
EdPa
MikroTik Support
MikroTik Support
Posts: 274
Joined: Fri Sep 15, 2017 10:05 am
Location: Riga
Contact:

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 8:16 am

This key is part of the IEEE 802.3ad standard, it determines the ability of one port to aggregate with another. You do not need to configure matching keys on both LACP nodes.

Edit:
Sadly, I cannot share any practical examples where this setting is really useful. You can continue to use the default value, it has not changed from previous versions of RouterOS, while others might find this setting useful in certain situations.
 
rpingar
Long time Member
Long time Member
Posts: 592
Joined: Fri May 28, 2004 2:46 pm
Location: Italy

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 8:50 am

may be a stupid question,
but implenting this:
*) bgp - added initial support for prefix limit;

is this an implication about internal counter of prefix received by a peer?
regards
Ros
 
User avatar
Gnubyte
just joined
Posts: 21
Joined: Sat Aug 15, 2020 7:31 pm
Location: Toulon - France

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 11:44 am

SNMP: SNMP feed seems unstable. Monitoring tools show discontinuous flows.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 1:07 pm

SNMP: SNMP feed seems unstable. Monitoring tools show discontinuous flows.
It is unclear what you mean. Do you mean the "OID not monotonically increasing" problem? It has plagued RouterOS for years, you will need to work around it.
(e.g. using -Cc option of snmpwalk)
Or do you mean that the responsetime to some queries is longer than others?
That is to be expected, as some queries basically just read memory information, while others may need to run some program or do some slow serial read of a sensor.
(unfortunately there even are some cases where reading certain sensors, e.g. temperature, is apparently done in "bit banging" fashion with interrupts disabled, and the action of reading it may cause an overrun or a link state flap on a network interface)
 
User avatar
emils
Forum Veteran
Forum Veteran
Topic Author
Posts: 906
Joined: Thu Dec 11, 2014 8:53 am

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 4:31 pm

What's new in 7.3beta34 (2022-Apr-20 08:23):

*) bgp - improved stability when editing BGP template;
*) ccr - added "passthrough" flag for interfaces on CCR2004-1G-2XS-PCIe;
*) dhcpv4-server - added "age" parameter for dynamic leases;
*) dhcpv4-server - fixed minor logging typo;
*) export - fixed value ID exporting that does not refer to any name;
*) fetch - fixed SFTP upload;
*) filesystem - fixed possible boot failure on RB850Gx2 and RB1100AHx2;
*) filesystem - improved long-term filesystem stability and data integrity;
*) ipsec - fixed IPsec IRQ initialization on startup on TILE;
*) leds - fixed ethernet LED behavior on wAP R ac;
*) lte - disabled extended signal info query for Telit LN940 module;
*) ospf - fixed GRE interface compatibility with OSPF;
*) ospf - improved stability when enabling or removing interface-template entries;
*) ovpn - improved stability when forwarding traffic on TILE;
*) ping - fixed socket allocation after VRF change;
*) ppp - fixed active sessions sometimes getting stuck;
*) queues - improved stability in large list of queue scenarios;
*) rb5009 - fixed 10G linking issues with Intel X520, XXV710 NICs;
*) ssh - fail non-interactive client after first invalid password;
*) supout - added IGMP-Proxy section;
*) winbox - added "Comment" parameter for BGP templates and connections;
*) winbox - made "Interface Templates" table sortable under "Routing/OSPF" menu;
*) winbox - made "MPLS Interface" table sortable under "MPLS" menu;
*) winbox - made 56 the default ping size;
*) winbox - moved "src-address-list" and "dst-address-list" parameters to "General" tab under "IPv6/Firewall" menu;
*) winbox - show correct file system type under "System/Disks" menu;

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

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 some problem has appeared on device
 
rpingar
Long time Member
Long time Member
Posts: 592
Joined: Fri May 28, 2004 2:46 pm
Location: Italy

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 4:38 pm

*) ping - fixed socket allocation after VRF change;
cloud it fix the issue related to ticket[SUP-67221].

regards
 
rolling
just joined
Posts: 16
Joined: Wed Mar 11, 2020 5:15 pm

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 4:54 pm

*) rb5009 - fixed 10G linking issues with Intel X520, XXV710 NICs;

Thanks!
 
holvoetn
Forum Guru
Forum Guru
Posts: 5323
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 4:54 pm

hAP AC3
installation of 7.3b34 causes bootloop (coming from 7.3b33).
Trying netinstall now to recover.
 
biomesh
Long time Member
Long time Member
Posts: 561
Joined: Fri Feb 10, 2012 8:25 pm

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 6:02 pm

Is
*) ipsec - fixed IPsec IRQ initialization on startup on TILE;

Related to random high cpu seen on startup on TILE that shows as "networking" when using profile?
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 6:21 pm

*) ping - fixed socket allocation after VRF change;
cloud it fix the issue related to ticket[SUP-67221].

regards
No, problem described in that ticket is unrelated to VRFs
 
rpingar
Long time Member
Long time Member
Posts: 592
Joined: Fri May 28, 2004 2:46 pm
Location: Italy

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 6:25 pm

*) ping - fixed socket allocation after VRF change;
cloud it fix the issue related to ticket[SUP-67221].

regards
No, problem described in that ticket is unrelated to VRFs
are you aware about it, working to fix it or nothing yet?

regards
 
bublikoff
just joined
Posts: 8
Joined: Sat Apr 30, 2016 10:07 pm

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 6:43 pm

Had problems with beta34 on RB4011 ... had to recover previous beta33 with netinstall
 
holvoetn
Forum Guru
Forum Guru
Posts: 5323
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 6:50 pm

hAP AC3
installation of 7.3b34 causes bootloop (coming from 7.3b33).
Trying netinstall now to recover.
So far unsuccessful with netinstall.
It installs but after reboot, still bootloop.
Already tried 7.3b34, 7.3b33, 7.2, ...
 
User avatar
Znevna
Forum Guru
Forum Guru
Posts: 1347
Joined: Mon Sep 23, 2019 1:04 pm

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 7:32 pm

promising.
MikroTik, if you send me some testing devices I promise I'll test each release on them before you release it to public, does that sound like a good business? ;)
 
odge
Member Candidate
Member Candidate
Posts: 110
Joined: Mon Nov 29, 2010 2:53 pm

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 8:02 pm

Tested prefix limit in BGP. It works but requires a manual clearing of the peering. Would be nice to have a timer and retry in future releases.

[zuul@ccr2216-01.test.lab.ipa] > routing/bgp/connection/disable 0
[zuul@ccr2216-01.test.lab.ipa] > routing/bgp/connection/set input.limit-process-routes-ipv4=5000 0
[zuul@ccr2216-01.test.lab.ipa] > routing/bgp/connection/enable 0
[zuul@ccr2216-01.test.lab.ipa] > routing/bgp/session/print 
Flags: E - established 
 0   remote.address=198.18.91.254 .refused-cap-opt=no 
     local.address=198.18.91.1 
     output.last-notification=ffffffffffffffffffffffffffffffff0015030601 limit-exceeded 
[zuul@ccr2216-01.test.lab.ipa] > routing/bgp/connection/set input.limit-process-routes-ipv4=1000000 0
[zuul@ccr2216-01.test.lab.ipa] > routing/bgp/session/clear 0
flag: 
input-last-notification  limit-exceeded  output-last-notification  refused-cap-opt  stopped
flag: limit-exceeded
[zuul@ccr2216-01.test.lab.ipa] > routing/bgp/session/print 
Flags: E - established 
 0 E remote.address=198.18.91.254 .as=65101 .id=198.18.91.254 .refused-cap-opt=no .capabilities=mp,rr,role,gr,as4 .messages=227341 .bytes=22502859 .eor="" 
     local.address=198.18.91.1 .as=8675309 .id=100.127.100.101 .capabilities=mp,rr,gr,as4 .messages=1 .bytes=19 .eor="" 
     output.procid=60 .filter-chain=deny-all .last-notification=ffffffffffffffffffffffffffffffff0015030601 
     input.procid=60 .limit-process-routes=1000000 ebgp 
     hold-time=3m keepalive-time=1m uptime=34s270ms 
[zuul@ccr2216-01.test.lab.ipa] > 
Interesting, this came up in NOG group in our country, and it was strongly advised that a retry timer would be bad for the internet, and that's out of the latest IETF draft at https://datatracker.ietf.org/doc/draft- ... x-inbound/ written by both Max Stucchi and Job Snijders. Check section 2 point C.

The discussion on the group went on to point out the bgp oscillation should really be avoided at all costs. Some of it above my head.

Some of the equally educated members (the group also includes both of them), said Mikrotik should stick to the IETF recommendations here.
 
fragtion
Member Candidate
Member Candidate
Posts: 257
Joined: Fri Nov 13, 2009 10:08 pm
Location: Johannesburg, South Africa

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 8:08 pm

So far unsuccessful with netinstall.
It installs but after reboot, still bootloop.
Already tried 7.3b34, 7.3b33, 7.2, ...
If netinstall can even bring a Mikrotik router running OpenWRT back to RouterOS again, then surely it should easily recover a failed RouterOS incremental version upgrade? Is this just a case of ID10T user error, or should we all be a bit concerned at the dark irony of devices being bricked at alarmingly heightened rates, in spite of a series of alleged filesystem "improvements" to long-term filesystem stability and data integrity ? 🤔 Probably just another "rare" occurence ;) Any other volunteers want to jump to the front of the line? I'm normally excited about new releases, this time a bit hesitant If I'm honest ..😅

I guess that is a risk we take using bleeding-edge beta releases. We're basically "insider" testers by choice. At least there are stable versions (for most hardware at least) for those of us who require it :) The rest of us could probably benefit from a break out in nature with some sunshine and other things while such issues get ironed out, which I'm sure they will soon enough (Edit: speaking for myself here, just to be clear...lol) ;P It should be worth it in the end at least

Edit: Just bricked an rb433 here upgrading from 7.3beta33 to 7.3beta34. gotta netinstall it
Last edited by fragtion on Thu Apr 21, 2022 11:31 pm, edited 2 times in total.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5323
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 8:40 pm

Is this just a case of ID10T user error, ...
Errrmm ...
I am far from an expert as far as Tik devices are concerned but I'm having my hands on computers since 1980 (NOT for playing games !! I hate gaming ... ) so I know one or two things.
As far as I am aware, when netinstall installs successfully, it should install. Period. No ?
So unless there are some specific instructions to solve this particular problem (I'd like to hear about them ASAP then !), I guess there is an underlying problem with the netinstall process as well. And that is truly worrisome.

And yes, I am aware this is beta software and rest assured, this is not a production device (purely personal lab environment) but to my knowledge this is the first time I hear about netinstall not being able to install after indicating it did so successfully.
Only a pitty I am the guinea pig here ...
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 9:38 pm

There is a documentation page about netinstall. And it is wellknown that when you attempt it after a long time of not using it, it usually won't do what you want.
It requires experience and proficiency.
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 9:50 pm

I updated my CCR2004 and this time, all went well. No boot loops, no config is lost. I can't believe it myself.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5323
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 9:51 pm

There is a documentation page about netinstall. And it is wellknown that when you attempt it after a long time of not using it, it usually won't do what you want.
It requires experience and proficiency.
Good joke.
That documentation page show at the end of the process a "Reboot" button which is NOWHERE to be found on the versions I tried.
7.1 / 7.2 / 7.2.1 / 7.2rc4 / 7.3b33 / 7.3b34
Nada.

Install succeeds EACH TIME (at least that's what the tool indicates) yet after power cycle the device remains stuck in a bootloop.

Care to comment again ?

I am going to throw this towards Support ...

EDIT: I do see one difference... there is not status indicator "done". It does flip back from Installing to Ready.
So it might not install at all ? Even better then ...
Last edited by holvoetn on Wed Apr 20, 2022 10:02 pm, edited 1 time in total.
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 9:59 pm

Does the Router appear automatically again in Netinstall after you reboot it? Sure you didn't change /system/routerboard/settings/boot-device to ethernet?!
 
holvoetn
Forum Guru
Forum Guru
Posts: 5323
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 10:03 pm

Does the Router appear automatically again in Netinstall after you reboot it? Sure you didn't change /system/routerboard/settings/boot-device to ethernet?!
No it doesn't since it is stuck in some sort of bootloop.
Only when I power off, keep reset pressed and then power on again, it reappears in netinstall after a while.

And no, I did not change boot-device settings.
 
hecatae
Member Candidate
Member Candidate
Posts: 244
Joined: Thu May 21, 2020 2:34 pm

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 10:04 pm

Hap Lite successfully updated to 7.3beta34.
Not updating anything else until I give this a run in.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5323
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 10:34 pm

There is a documentation page about netinstall. And it is wellknown that when you attempt it after a long time of not using it, it usually won't do what you want.
It requires experience and proficiency.
Good joke.
That documentation page show at the end of the process a "Reboot" button which is NOWHERE to be found on the versions I tried.
7.1 / 7.2 / 7.2.1 / 7.2rc4 / 7.3b33 / 7.3b34
Nada.

Install succeeds EACH TIME (at least that's what the tool indicates) yet after power cycle the device remains stuck in a bootloop.

Care to comment again ?

I am going to throw this towards Support ...

EDIT: I do see one difference... there is not status indicator "done". It does flip back from Installing to Ready.
So it might not install at all ? Even better then ...
Solved.
Using Good Ol' Linux and CLI !! (told you I know a thing or two)

That laptop I used before, was already used several times for netinstalling Hex and MapLite, so why not now ?
 
User avatar
CTassisF
newbie
Posts: 35
Joined: Thu Jun 11, 2020 10:26 pm
Location: São Paulo, Brazil
Contact:

Re: v7.3beta [testing] is released!

Wed Apr 20, 2022 10:57 pm

Upgraded my hAP ac3 from 7.3beta33 to beta34 and now it is boot looping. Will try netinstall.

Edit: successfully recovered using 7.3beta33 netinstall on Windows.
 
User avatar
SiB
Forum Guru
Forum Guru
Posts: 1888
Joined: Sun Jan 06, 2013 11:19 pm
Location: Poland

Re: v7.3beta [testing] is released!

Thu Apr 21, 2022 12:50 am

Using Good Ol' Linux and CLI !! (told you I know a thing or two)
That laptop I used before, was already used several times for netinstalling Hex and MapLite, so why not now ?
Some laptops cannot detect receive package from device, change laptop and works our-of-box. I always use WireShark to watch if computer I use see incomming "BOOTP" request, if not... try uninstall AV and reboot - sometimes not help and only change laptop is option. I not discover why but I agree sometimes that happend.
 
tangent
Forum Guru
Forum Guru
Posts: 1333
Joined: Thu Jul 01, 2021 3:15 pm
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 21, 2022 1:46 am

The docs on netinstall recommend taking down all network interfaces but the one you know for a fact goes to the MT box you're trying to recover. If you don't, you can't predict which interface it will use short of trawling the mess of a routing table you get with modern OSes. The last time I made a Windows box barf up its default routing table, it was over a screenful!
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v7.3beta [testing] is released!

Thu Apr 21, 2022 2:28 am

the netinstall program is just a big mess. I don't understand why bootp is even required, completely unnecessary and overengineered. When starting in netinstall-mode the router should just listen to a predefined ip address and start up an sshd, so one can upload the system package using scp or sftp to the ram fs. When the upload is finished, reformat the partition, install the software and reboot with default config, done.
 
tangent
Forum Guru
Forum Guru
Posts: 1333
Joined: Thu Jul 01, 2021 3:15 pm
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 21, 2022 4:14 am

Your alternative to BOOTP — a protocol so simple it hasn't been high tech since about 1984 — is SSH? I love me some SSH, but you've got your complexity factors completely inverted there.

If you want a "why," it goes back to the ancient days of diskless workstations: RARP, BOOTP, TFTP… That's how those machines booted in the mid 1980s, so by the time we get to the mid-nineties where Routerboard became a thing, hardware costs had dropped to the point that you could do that on an embedded Linux board. The tech was there to be reused.
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11381
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.3beta [testing] is released!

Thu Apr 21, 2022 8:48 am

the netinstall program is just a big mess.
Most of times it's not a problem on device's side, it's machine hosting netinstall "server" that messes things up. The most frequent one is delayed NIC init after link re-establishes. Next one is the fact netinstall exec doesn't allow to explicitly select which interface to use and this is down to MT devs indeed (if wireshark can do it, why can't netinstall as well?). Only the third one is down to interaction between device and PC (the state where one selects packages to upload but device doesn't get or process them) ... and only with this one it's not really clear which end to blame, device or netinstall exec ... or even BOOTP. Other than that BOOTP is just fine.
 
ToTheCLI
Frequent Visitor
Frequent Visitor
Posts: 83
Joined: Mon Jan 04, 2016 3:54 am

Re: v7.3beta [testing] is released!

Thu Apr 21, 2022 8:58 am

*) sfp - added 2.5Gbps rate for SFP+ and QSFP+ interfaces on 98DXxxxx and 98PX1012 switches (requires disabled auto-negotiation);

Can this be added for RB5009 SFP+ Port?
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Thu Apr 21, 2022 11:34 am

The most frequent one is delayed NIC init after link re-establishes.
True, when I could not get it to work with a specific MikroTik device and a laptop, I fixed it by putting an unmanaged desktop switch between them so the laptop would see the link up all the time.
Next one is the fact netinstall exec doesn't allow to explicitly select which interface to use and this is down to MT devs indeed (if wireshark can do it, why can't netinstall as well?).
Yes that is a major problem as well! Both in the Windows and Linux version. I am very sure that in Linux it is easy to listen to a specific network interface instead of to a random one. They simply have to fix that to reduce a lot of issues with netinstall.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5323
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.3beta [testing] is released!

Thu Apr 21, 2022 11:37 am

The docs on netinstall recommend taking down all network interfaces but the one you know for a fact goes to the MT box you're trying to recover. If you don't, you can't predict which interface it will use short of trawling the mess of a routing table you get with modern OSes. The last time I made a Windows box barf up its default routing table, it was over a screenful!
I know about that requirement and I did disable ALL other network interfaces on my laptop (control panel , network, right-click disable on everything but ethernet).
Still it did not work. The device shows up in netinstall (so the network interface is correct, I would think ? ) but "install" did nothing.
Only one single cable between ether1 of Tik and ethernet port of laptop. Where else can the communication go then ?

And on a stupid Linux box from 2008 it worked on the first attempt WITHOUT disabling all other network interfaces, go figure.
Lesson learned for me: don't throw away that old Dell D830 yet (no battery anymore, keyboard is sometimes finicky but it can still do netinstall like a Pro !).
 
tangent
Forum Guru
Forum Guru
Posts: 1333
Joined: Thu Jul 01, 2021 3:15 pm
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 21, 2022 11:46 am

if wireshark can do it, why can't netinstall as well?

Wireshark does it with libpcap/WinPCap, which is fine because all it needs to do is receive raw packets. To do netinstall atop PCap, they’d have to write their own UDP/IP stack at least. It’d only have to handle the point-to-point case, but still nontrivial. Half a developer year to write and debug it, maybe? More if you need some subset of TCP as well.

Even if they ripped the BSD stack as so many others have done, it’s a huge integration effort.

Short of that, as far as I’m aware, the sockets API doesn’t let you force UDP out a specific interface without regard to the routing table. There may be lower-level hacks, but they’d be non-portable. You’d need separate Windows and Linux source code at least — meaning, not just a recompile — and I wouldn’t be surprised if Wine choked on the Windows hack because it used APIs no one has found valuable enough to emulate.

This is not one of those “just do it” type of things.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5323
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.3beta [testing] is released!

Thu Apr 21, 2022 11:55 am

the netinstall program is just a big mess.
Most of times it's not a problem on device's side, it's machine hosting netinstall "server" that messes things up. The most frequent one is delayed NIC init after link re-establishes. Next one is the fact netinstall exec doesn't allow to explicitly select which interface to use and this is down to MT devs indeed (if wireshark can do it, why can't netinstall as well?). Only the third one is down to interaction between device and PC (the state where one selects packages to upload but device doesn't get or process them) ... and only with this one it's not really clear which end to blame, device or netinstall exec ... or even BOOTP. Other than that BOOTP is just fine.
Funny you mention wireshark.
I did a wireshark trace on that interface I used yesterday before moving over to a Linux machine and even though the device showed up correctly in netinstall, I did not see any traffic towards that device after hitting "install". Nada.
I did see requests from my laptop with address 192.168.88.2 towards the default gateway to be used (as the docs specify: 192.168.88.1), so I'm pretty sure I was tracing the right interface.
Why was nothing send when hitting "install" ?
I also tried (just to see what happened) Tiny PXE server on Windows, it did show quite some requests coming from that Mikrotik device but was unable to do something with it (I think that's logical).
Therefor I am relatively sure the ethernet interface settings themselves on that Win-laptop were correct.

Might have to try that dumb switch trick to see if it has some impact using Windows.
 
tangent
Forum Guru
Forum Guru
Posts: 1333
Joined: Thu Jul 01, 2021 3:15 pm
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 21, 2022 11:55 am

control panel , network, right-click disable on everything but ethernet).
Still it did not work.

Show your routing table after this step, and the IP of the box you’re trying to netinstall.

The device shows up in netinstall (so the network interface is correct, I would think ?

Nah. A discovery protocol is one UDP broadcast on all interfaces followed by one reply packet. That tells you almost nothing about the subsequent BOOTP/TFTP/whatever steps.
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1070
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 21, 2022 11:28 pm

Both in the Windows and Linux version. I am very sure that in Linux it is easy to listen to a specific network interface instead of to a random one. [...]
I use a script that sets up a network namespace and required configuration before starting netinstall itself.

Feel free to give it a try:
https://aur.archlinux.org/cgit/aur.git/ ... netinstall

(For those running Arch Linux... Just install the netinstall package from AUR.)
 
tangent
Forum Guru
Forum Guru
Posts: 1333
Joined: Thu Jul 01, 2021 3:15 pm
Contact:

Re: v7.3beta [testing] is released!

Fri Apr 22, 2022 12:51 am

a script that sets up a network namespace

A related trick that should work is using any hypervisor with bridged networking support to present a single network interface to the VM, tied to a specific one on the host.

If there's a bug in the Windows netinstall.exe, this would also help you get around it by using a Linux VM to run its CLI version of netinstall. It'd be cheaper in terms of disk space and licensing annoyance than setting up Windows-in-Windows as well.
 
akakua
newbie
Posts: 49
Joined: Mon Apr 06, 2020 4:52 pm

Re: v7.3beta [testing] is released!

Fri Apr 22, 2022 6:08 am

What's new in 7.3beta34 (2022-Apr-20 08:23):

*) bgp - improved stability when editing BGP template;
*) ccr - added "passthrough" flag for interfaces on CCR2004-1G-2XS-PCIe;
*) dhcpv4-server - added "age" parameter for dynamic leases;
*) dhcpv4-server - fixed minor logging typo;
*) export - fixed value ID exporting that does not refer to any name;
*) fetch - fixed SFTP upload;
*) filesystem - fixed possible boot failure on RB850Gx2 and RB1100AHx2;
*) filesystem - improved long-term filesystem stability and data integrity;
*) ipsec - fixed IPsec IRQ initialization on startup on TILE;
*) leds - fixed ethernet LED behavior on wAP R ac;
*) lte - disabled extended signal info query for Telit LN940 module;
*) ospf - fixed GRE interface compatibility with OSPF;
*) ospf - improved stability when enabling or removing interface-template entries;
*) ovpn - improved stability when forwarding traffic on TILE;
*) ping - fixed socket allocation after VRF change;
*) ppp - fixed active sessions sometimes getting stuck;
*) queues - improved stability in large list of queue scenarios;
*) rb5009 - fixed 10G linking issues with Intel X520, XXV710 NICs;
*) ssh - fail non-interactive client after first invalid password;
*) supout - added IGMP-Proxy section;
*) winbox - added "Comment" parameter for BGP templates and connections;
*) winbox - made "Interface Templates" table sortable under "Routing/OSPF" menu;
*) winbox - made "MPLS Interface" table sortable under "MPLS" menu;
*) winbox - made 56 the default ping size;
*) winbox - moved "src-address-list" and "dst-address-list" parameters to "General" tab under "IPv6/Firewall" menu;
*) winbox - show correct file system type under "System/Disks" menu;

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

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 some problem has appeared on device
Wifiwave2 package causes a bootloop on this release for rb4011igs+5hacq2hnd-in
 
User avatar
BartoszP
Forum Guru
Forum Guru
Posts: 2855
Joined: Mon Jun 16, 2014 1:13 pm
Location: Poland

Re: v7.3beta [testing] is released!

Fri Apr 22, 2022 11:15 am

What do you quote full post for adding only one line of text?
Follow the link my signature please.
 
FezzFest
Frequent Visitor
Frequent Visitor
Posts: 86
Joined: Wed Jun 03, 2015 12:03 am

Re: v7.3beta [testing] is released!

Sat Apr 23, 2022 12:44 am

I know about that requirement and I did disable ALL other network interfaces on my laptop (control panel , network, right-click disable on everything but ethernet).
Still it did not work. The device shows up in netinstall (so the network interface is correct, I would think ? ) but "install" did nothing.
Only one single cable between ether1 of Tik and ethernet port of laptop. Where else can the communication go then ?
Windows 8/8.1/10 by any chance? I still have to run NetInstall in "Windows 7"-compatibility mode on Windows 10 machines to make it work properly.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5323
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.3beta [testing] is released!

Sat Apr 23, 2022 12:52 am

Nope. Win 11.
 
FezzFest
Frequent Visitor
Frequent Visitor
Posts: 86
Joined: Wed Jun 03, 2015 12:03 am

Re: v7.3beta [testing] is released!

Sat Apr 23, 2022 12:55 am

Ah well, there you have your problem.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5323
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.3beta [testing] is released!

Sat Apr 23, 2022 12:56 am

It worked before using that same laptop.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 11967
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: v7.3beta [testing] is released!

Sat Apr 23, 2022 12:57 am

I have been using Win 10 64 bit since 2020 and I have no problems when using Netinstall because I use a simple rule:
Only one network interface active when using netinstall, with fixed IPv4 over LAN.

Install did nothing because...
1) You not download the right files for that platform ???
2) You do not select the device before click on install ???
3) you do not select the package(s) after select the device ???
4) Afther the device shows up, try to close and re-open netinstall withouth touch anything???

Until now, I have not tested netinstall on Win 11
 
hecatae
Member Candidate
Member Candidate
Posts: 244
Joined: Thu May 21, 2020 2:34 pm

Re: v7.3beta [testing] is released!

Sat Apr 23, 2022 2:43 am

Wifiwave2 package causes a bootloop on this release for rb4011igs+5hacq2hnd-in
Thanks for the heads up,
Last edited by hecatae on Sun Apr 24, 2022 2:32 am, edited 1 time in total.
 
hecatae
Member Candidate
Member Candidate
Posts: 244
Joined: Thu May 21, 2020 2:34 pm

Re: v7.3beta [testing] is released!

Sat Apr 23, 2022 10:01 pm

Just to confirm 7.3beta34 boot looped my audience with wifiwave2 as well.
 
naxus
just joined
Posts: 2
Joined: Tue Jan 12, 2021 2:33 pm

Re: v7.3beta [testing] is released!

Sat Apr 23, 2022 11:27 pm

Just to confirm 7.3beta34 boot looped my audience with wifiwave2 as well.
Same here.
 
User avatar
loloski
Member Candidate
Member Candidate
Posts: 277
Joined: Mon Mar 15, 2021 9:10 pm

Re: v7.3beta [testing] is released!

Sun Apr 24, 2022 12:03 pm

7.3 beta34 has a fix for hotspot with simple queues, not in the change log glad it fix one of the nastiest bug in v7
 
User avatar
Amm0
Forum Guru
Forum Guru
Posts: 3169
Joined: Sun May 01, 2016 7:12 pm
Location: California

Re: v7.3beta [testing] is released!

Mon Apr 25, 2022 10:04 am

Just to confirm 7.3beta34 boot looped my audience with wifiwave2 as well.
Same here.
Yup, wifiwave2 on Audience broke 1 year streak of avoiding netinstall. I don't have any other device with enough memory for wifiwave2, so hard to know if just Audience...

Took a second to figure what was caused it. I thought it was lost config, so netinstall'ed with the same package I was using (including wifiwave2, not, dude, zerotier) & still a "boot loop". The dude was my first guess, with wifiwave2 being the last... Anyway half-dozen "netinstalls" – from Mac, with linux netinstall running on virtual Ubuntu in VMWare Fusion, bridged to an ethernet dongle, through a switch even – at least that does work & the Mac can still be on Wi-Fi ;)
 
hecatae
Member Candidate
Member Candidate
Posts: 244
Joined: Thu May 21, 2020 2:34 pm

Re: v7.3beta [testing] is released!

Mon Apr 25, 2022 11:14 am

So that's hap ac3, rb4011 and audience that need to avoid 7.3beta34.
 
User avatar
Znevna
Forum Guru
Forum Guru
Posts: 1347
Joined: Mon Sep 23, 2019 1:04 pm

Re: v7.3beta [testing] is released!

Mon Apr 25, 2022 11:28 am

only if you want to use wifiwave2 it seems?
 
hecatae
Member Candidate
Member Candidate
Posts: 244
Joined: Thu May 21, 2020 2:34 pm

Re: v7.3beta [testing] is released!

Mon Apr 25, 2022 2:05 pm

only if you want to use wifiwave2 it seems?
Although could someone explain to me why the device does not just disable the package and boot?
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Mon Apr 25, 2022 5:15 pm

The system is not prepared to handle a crash that could be resolved by removing a package...
Exception is the use of partitioning. When you would partition the device, copy and upgrade a partition, and it fails to boot, it would boot the old (copied) partition and you would be back without netinstall.
 
User avatar
Amm0
Forum Guru
Forum Guru
Posts: 3169
Joined: Sun May 01, 2016 7:12 pm
Location: California

Re: v7.3beta [testing] is released!

Mon Apr 25, 2022 5:25 pm

only if you want to use wifiwave2 it seems?
Although could someone explain to me why the device does not just disable the package and boot?
The package is fine, it's the driver that install it that likely crashes ;). What to do about that isn't so clear, downgrade to "stock" wireless and convert the config?

In fairness, it's the testing build & you'd generally want something to crash, as the core dump has exactly what went wrong, so it can be fixed.

I did open a bug on the issue.
 
User avatar
Amm0
Forum Guru
Forum Guru
Posts: 3169
Joined: Sun May 01, 2016 7:12 pm
Location: California

Re: v7.3beta [testing] is released!

Mon Apr 25, 2022 5:28 pm

Exception is the use of partitioning. When you would partition the device, copy and upgrade a partition, and it fails to boot, it would boot the old (copied) partition and you would be back without netinstall.
That's a good point. That Audience has the space for a 2nd partition. We use a lot of wAPacR, so there not room for even one partition (or even the wifiwave2 package)
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11381
Joined: Thu Mar 03, 2016 10:23 pm

Re: v7.3beta [testing] is released!

Mon Apr 25, 2022 7:12 pm

Exception is the use of partitioning. When you would partition the device, copy and upgrade a partition, and it fails to boot, it would boot the old (copied) partition and you would be back without netinstall.
That's a good point. That Audience has the space for a 2nd partition. We use a lot of wAPacR, so there not room for even one partition (or even the wifiwave2 package)

No, actually partitioning on Audience is not a feasible option when running wifiwave2 package. I tried it with 7.2rc5 and it worked just fine. However when I tried to upgrade to 7.2 final, it failed due to lack of free space and I had to revert to single partition. My audience currently uses around 52MB of flash (no removeable files exist), download packages for 7.2.1 are 26.4MB (12.4MB for main and 14.0MB for wifiwave2), altogether it doesn't fit 64MB partition (half of installed 128MB flash). Using RAM disk would help (my audience is currently at stable 142MB RAM used, so around 100MB unused), but sadly RAM disk is not an option on these devices.

The situation is probably identical on all other devices elligible for wifiwave2 drivers with flash size less than 256MB.
 
User avatar
Amm0
Forum Guru
Forum Guru
Posts: 3169
Joined: Sun May 01, 2016 7:12 pm
Location: California

Re: v7.3beta [testing] is released!

Mon Apr 25, 2022 7:37 pm

That's a good point. That Audience has the space for a 2nd partition. We use a lot of wAPacR, so there not room for even one partition (or even the wifiwave2 package)
No, actually partitioning on Audience is not a feasible option when running wifiwave2 package.
And here I thought I was being lazy. I do think @pe1chl's partitioning advice is a good one, although unfortunately seemingly inpractical...
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Mon Apr 25, 2022 7:41 pm

Using RAM disk would help (my audience is currently at stable 142MB RAM used, so around 100MB unused), but sadly RAM disk is not an option on these devices.
I have asked for enabling RAM disk on ALL devices for a long time...
 
holvoetn
Forum Guru
Forum Guru
Posts: 5323
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.3beta [testing] is released!

Mon Apr 25, 2022 9:06 pm

And it's not like some magic needs to be done.
It's standard Linux.
 
User avatar
Anime4000
just joined
Posts: 18
Joined: Fri Nov 13, 2020 3:12 pm
Contact:

Re: v7.3beta [testing] is released!

Mon Apr 25, 2022 10:05 pm

*) sfp - added 2.5Gbps rate for SFP+ and QSFP+ interfaces on 98DXxxxx and 98PX1012 switches (requires disabled auto-negotiation);
*) sfp - improved Q/SFP interface initialization and stability for 98DXxxxx and 98PX1012 switches;
At my github repo...
CRS305-1G-4S+IN now can running 2.5Gbps @ HiSGMII PHY of ODI DFP-34X-2C2 (XPON ONU SFP Stick), user @stich86 manage to get 2.1Gbps speedtest
 
User avatar
megacrash
just joined
Posts: 2
Joined: Sat Sep 11, 2021 2:03 am
Location: Tashkent
Contact:

Re: v7.3beta [testing] is released!

Tue Apr 26, 2022 12:32 am

Please, add WOL command on context menu in the dhcp leases table for static entries! ))
 
User avatar
emils
Forum Veteran
Forum Veteran
Topic Author
Posts: 906
Joined: Thu Dec 11, 2014 8:53 am

Re: v7.3beta [testing] is released!

Tue Apr 26, 2022 10:17 am

What's new in 7.3beta37 (2022-Apr-25 15:29):

*) bonding - fixed LACP flapping for RB5009 and CCR2004-16G-2S+ devices;
*) bridge - fixed packet marking for IP/IPv6 firewall;
*) dot1x - improved server stability when using re-authentication;
*) fetch - improved full disk detection;
*) gps - fixed minor value unit typo;
*) l3hw - improved offloading for directly connected hosts on CRS305, CRS326-24G-2S+, CRS328, CRS318, CRS310;
*) led - fixed QSFP+, QSFP28 activity LEDs when using 40Gbps modules (introduced in v7.3beta33);
*) lte - disabled wait for LTE auto attach;
*) mpls - fixed MPLS MTU and path MTU selection;
*) ovpn - fixed hardware offloading support on CHR;
*) ovpn - improved Windows client disconnect procedure in UDP mode;
*) ovpn - moved authentication failure messages to "info" logging level;
*) ppp - added warning when using prefix length other than /64 for router advertisement;
*) ppp - fixed "remote-ipv6-prefix" parameter unsetting;
*) ppp - fixed issue with multiple active sessions when "only-one" is enabled;
*) routerboot - properly reset system configuration when protected bootloader is enabled and reset button used;
*) rsvp-te - improved stability when "Resv" received for non-existing session;
*) sfp - improved QSFP/SFP interface initialization for 98DXxxxx switches;
*) switch - fixed missing stats from traffic-monitor for 98DXxxxx and 98PX1012 switches;
*) system - fixed RouterOS bootup when wifiwave2 package is installed (introduced in v7.3beta34);
*) system - fixed rare partial loss of RouterOS configuration after package upgrade/downgrade/install/uninstall;
*) user-manager - improved stability when received EAP attribute with non-existing state attribute;
*) vpls - fixed "pw-l2mtu" parameter usage;

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

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 some problem has appeared on device
 
User avatar
strods
MikroTik Support
MikroTik Support
Posts: 1616
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v7.3beta [testing] is released!

Tue Apr 26, 2022 10:19 am

Everyone, thank you very much for all the input regarding the configuration loss problem. For your reports in the forum and support tickets. By putting our heads together and combining all of your reports we managed to reproduce this problem and seems that we have resolved it. The fix is included in v7.3beta37 and, of course, if it will be proven safe (we have tested it ourselves reliably, but would like to see the feedback from beta releases), then it will be included in stable releases as well.

Please note that the upgrade happens on the old version, not the version which you try to install. So the fix applies only when you try to upgrade FROM 7.3beta37 or a later version. Downgrade to older versions than 7.3beta37 still will be affected.
 
mafiosa
Member Candidate
Member Candidate
Posts: 266
Joined: Fri Dec 09, 2016 8:10 pm
Location: Kolkata, India
Contact:

Re: v7.3beta [testing] is released!

Tue Apr 26, 2022 10:24 am

Everyone, thank you very much for all the input regarding the configuration loss problem. For your reports in the forum and support tickets. By putting our heads together and combining all of your reports we managed to reproduce this problem and seems that we have resolved it. The fix is included in v7.3beta and, of course, if it will be proven safe (we have tested it ourselves reliably, but would like to see the feedback from beta releases), then it will be included in stable releases as well.

Please note that the upgrade happens on the old version, not the version which you try to install. So the fix applies only when you try to upgrade FROM 7.3beta37 or a later version.
Does that include vxlan interface mac changing on every reboot.?
 
User avatar
strods
MikroTik Support
MikroTik Support
Posts: 1616
Joined: Wed Jul 16, 2014 7:22 am
Location: Riga, Latvia

Re: v7.3beta [testing] is released!

Tue Apr 26, 2022 10:26 am

Everyone, thank you very much for all the input regarding the configuration loss problem. For your reports in the forum and support tickets. By putting our heads together and combining all of your reports we managed to reproduce this problem and seems that we have resolved it. The fix is included in v7.3beta and, of course, if it will be proven safe (we have tested it ourselves reliably, but would like to see the feedback from beta releases), then it will be included in stable releases as well.

Please note that the upgrade happens on the old version, not the version which you try to install. So the fix applies only when you try to upgrade FROM 7.3beta37 or a later version.
Does that include vxlan interface mac changing on every reboot.?
No, that is an unrelated problem. It will be fixed as soon as possible and the fix will be mentioned in the changelog.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Tue Apr 26, 2022 10:28 am

By putting our heads together and combining all of your reports we managed to reproduce this problem and seems that we have resolved it.
That is great news! Good that you (and we) remained persistent and not believed in that "well that happened but it is so rare that we just imagine that it did not happen and will go away by itself". Because that usually does not work in IT.
 
User avatar
colinardo
just joined
Posts: 18
Joined: Sun Jan 08, 2017 9:02 pm

Re: v7.3beta [testing] is released!

Tue Apr 26, 2022 1:25 pm

What's new in 7.3beta37 (2022-Apr-25 15:29):
*) dot1x - improved server stability when using re-authentication;
dot1x vlan assignment still broken
viewtopic.php?p=925819#p925819
 
User avatar
loloski
Member Candidate
Member Candidate
Posts: 277
Joined: Mon Mar 15, 2021 9:10 pm

Re: v7.3beta [testing] is released!

Tue Apr 26, 2022 3:43 pm

confirm dot1x still broken, but mac authentication is working
 
holvoetn
Forum Guru
Forum Guru
Posts: 5323
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.3beta [testing] is released!

Tue Apr 26, 2022 6:38 pm

*) system - fixed RouterOS bootup when wifiwave2 package is installed (introduced in v7.3beta34);
Confirmed on hAP AC3 using wifiwave2 package. Thanks !!
 
marlab
newbie
Posts: 25
Joined: Sun Mar 15, 2015 2:48 pm
Location: EU

Re: v7.3beta [testing] is released!

Tue Apr 26, 2022 10:29 pm

Unfortunately with 7.3beta37 my ARM routers with CAPsMAN active are still freezing after 3h 43m 26s of uptime... Tested with RB3011, RB4011, CRS326
So I had to deactivate CAPsMAN and configure all radios manually... :/
And even with that I still prefer to use ROS v7 because of features like VxLANs, OpenVPN+UDP and WireGuard.
 
mobyfab
just joined
Posts: 6
Joined: Tue Jul 03, 2018 4:45 pm
Location: France

Re: v7.3beta [testing] is released!

Tue Apr 26, 2022 10:51 pm

Switch rules for cpu port are still completely broken on a CRS317.
Identical rules tested on another device work fine.
Last edited by mobyfab on Wed May 04, 2022 11:31 am, edited 1 time in total.
 
guipoletto
Member Candidate
Member Candidate
Posts: 195
Joined: Mon Sep 19, 2011 5:31 am

Re: v7.3beta [testing] is released!

Tue Apr 26, 2022 10:53 pm

Unfortunately with 7.3beta37 my ARM routers with CAPsMAN active are still freezing after 3h 43m 26s of uptime... Tested with RB3011, RB4011, CRS326
So I had to deactivate CAPsMAN and configure all radios manually... :/
And even with that I still prefer to use ROS v7 because of features like VxLANs, OpenVPN+UDP and WireGuard.
Huum, are you really using CRS switches as CapsManagers? how did that work out for you?

I for now have refrained from updating any switches to V7 preciselly because of the unwanted "features" that comes with the "bundled" package (Mainly "Wireless" and "Hotspot")
I would rather use the space to have local graphing and maybe save a backup config?
 
marlab
newbie
Posts: 25
Joined: Sun Mar 15, 2015 2:48 pm
Location: EU

Re: v7.3beta [testing] is released!

Tue Apr 26, 2022 11:10 pm

Huum, are you really using CRS switches as CapsManagers? how did that work out for you?
It was just as a test to confirm the issue exists on different routers, I've run it there only for a few hours and then disabled it after the router hung up due to CAPsMAN.
But then while it was running - I've not noticed any serious side effects on the router itself.
 
rolling
just joined
Posts: 16
Joined: Wed Mar 11, 2020 5:15 pm

Re: v7.3beta [testing] is released!

Wed Apr 27, 2022 8:54 am

7.3beta37 working ok on mAP, wAP and RB750Ui.
thanks!
 
buset1974
Frequent Visitor
Frequent Visitor
Posts: 86
Joined: Wed Sep 13, 2006 12:12 pm
Location: Jakarta

Re: v7.3beta [testing] is released!

Wed Apr 27, 2022 10:39 am

BGP AFI vrf still problem in V7.3b37, for detail please refer to my ticket SUP-79812
 
X0E2003
just joined
Posts: 1
Joined: Wed Nov 05, 2014 7:19 pm

Re: v7.3beta [testing] is released!

Wed Apr 27, 2022 12:28 pm

why no routing-table ??? in ROS v7.x

connecting to mikrotik ros7.3b37:
[admin@Ros7.3b37] > /ip/firewall/mangle/add routing-table
expected end of command (line 1 column 25)
question - why NO routing-table in cli???
 
User avatar
Znevna
Forum Guru
Forum Guru
Posts: 1347
Joined: Mon Sep 23, 2019 1:04 pm

Re: v7.3beta [testing] is released!

Wed Apr 27, 2022 12:31 pm

 
rolling
just joined
Posts: 16
Joined: Wed Mar 11, 2020 5:15 pm

Re: v7.3beta [testing] is released!

Wed Apr 27, 2022 1:24 pm

*) sfp - added 2.5Gbps rate for SFP+ and QSFP+ interfaces on 98DXxxxx and 98PX1012 switches (requires disabled auto-negotiation);
Hi,

Will be posible implement on 88ExxxX switches and rbs this funcionality?

Best regards!
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v7.3beta [testing] is released!

Wed Apr 27, 2022 1:32 pm

why no routing-table ??? in ROS v7.x

connecting to mikrotik ros7.3b37:
[admin@Ros7.3b37] > /ip/firewall/mangle/add routing-table
expected end of command (line 1 column 25)
question - why NO routing-table in cli???
Wow... What's "realm"? It changes when I change "Routing Table" in WinBox and shows some numbers %)
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v7.3beta [testing] is released!

Wed Apr 27, 2022 6:10 pm

@marlab I have the exact same issue with my hap ac2 (also arm). The device reboots every ˜3h42m. I'm still trying to find the exact cause for it. This problem started with 7.2.0; 7.1.5 was stable.
Are you absolutely sure capsman is causing this? Anything else running on this device like eoip, wireguard, ospf?
 
marlab
newbie
Posts: 25
Joined: Sun Mar 15, 2015 2:48 pm
Location: EU

Re: v7.3beta [testing] is released!

Wed Apr 27, 2022 6:40 pm

@marlab I have the exact same issue with my hap ac2 (also arm). The device reboots every ˜3h42m. I'm still trying to find the exact cause for it. This problem started with 7.2.0; 7.1.5 was stable.
Are you absolutely sure capsman is causing this? Anything else running on this device like eoip, wireguard, ospf?

I had such problem with 7.1.5 too. I am pretty sure - once I disable CAPsMAN (CAPS manager) on the router (no other changes) - the freeze doesn't happen. The freeze also doesn't happen if CAPsMAN is active but no caps are connected/managed. Tested with latest beta. And I also use there OSPF, OVPN, L2PT, NTP, Wireguard, VxLANs. Once CAPsMAN is deactivated, the device runs fine for many hours. Once I activate it - it gets frozen after 3h43m26s. Additionaly after the reboot, the clock on the device is set backwards by exactly the same interval.

I am in contact with Mikrotik support (case SUP-77771), but they could not find the reason yet. It is not really a reboot, what happens for me is most of internal network services will freeze (I can still access the device via serial console), and it is the watchdog that does the reboot after one of internal IP addresses configured on the same device stops responding.
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v7.3beta [testing] is released!

Wed Apr 27, 2022 7:23 pm

exactly what happens on my device; technically it crashes and the router is unresponsive, it only reboots because I've enabled watchdog. Thanks for the input, I'll continue my testings. I also have filed a ticket (SUP-78584).
 
User avatar
memelchenkov
Member Candidate
Member Candidate
Posts: 202
Joined: Sun Oct 11, 2020 12:00 pm
Contact:

Re: v7.3beta [testing] is released!

Thu Apr 28, 2022 10:41 am

*) bridge - fixed packet marking for IP/IPv6 firewall;
Please tell, what exactly fixed? Will it fix SUP-72355?
 
hecatae
Member Candidate
Member Candidate
Posts: 244
Joined: Thu May 21, 2020 2:34 pm

Re: v7.3beta [testing] is released!

Thu Apr 28, 2022 1:31 pm

Hap Lite and Audience upgraded to 7.3beta37 successfully.

I would like to be on 7.2.1 but the Hap Lite is unusable on 7.2.1
 
uCZBpmK6pwoZg7LR
Frequent Visitor
Frequent Visitor
Posts: 54
Joined: Mon Jun 15, 2015 12:23 pm

Re: v7.3beta [testing] is released!

Thu Apr 28, 2022 6:00 pm

MPLS over Tunnels still broken
 
User avatar
ianmagsisi
just joined
Posts: 2
Joined: Fri Feb 11, 2022 4:55 am
Location: Philippines

Re: v7.3beta [testing] is released!

Fri Apr 29, 2022 5:40 pm

in PPP-active connection when you ping it says timeout but it is active and has a connection.
 
hecatae
Member Candidate
Member Candidate
Posts: 244
Joined: Thu May 21, 2020 2:34 pm

Re: v7.3beta [testing] is released!

Sat Apr 30, 2022 12:41 am

Chateau 5g upgraded without issue to beta37.
Chateau LTE12 also upgraded without issue and being used as Home Dual AP with LTE as backup.
 
User avatar
Ullinator
just joined
Posts: 8
Joined: Tue Jun 08, 2021 12:53 pm
Location: North-West Germany

Re: v7.3beta [testing] is released!

Wed May 04, 2022 4:42 pm

I´ve updated my 5 CRS Switches to 7.3Beta37 from 7.2.1, but my issue with the non working IPv6 after activating L3HW offloading and accidently changed STP is still present.
Even a factory reset didn´t help.....strange.
I will try a netinstall on one of them...
 
chiem
newbie
Posts: 41
Joined: Fri Oct 24, 2014 4:48 pm

Re: v7.3beta [testing] is released!

Thu May 05, 2022 8:59 pm

Is this enough user attention for a priority boost?

viewtopic.php?t=175513
 
User avatar
Znevna
Forum Guru
Forum Guru
Posts: 1347
Joined: Mon Sep 23, 2019 1:04 pm

Re: v7.3beta [testing] is released!

Thu May 05, 2022 11:01 pm

Sure, but no.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Fri May 06, 2022 10:36 am

Is this enough user attention for a priority boost?

viewtopic.php?t=175513
I sincerely hope the focus for the coming month will be on fixing things that are broken or still missing (relative to v6) and not on working on new features.
 
User avatar
Ullinator
just joined
Posts: 8
Joined: Tue Jun 08, 2021 12:53 pm
Location: North-West Germany

Re: v7.3beta [testing] is released!

Fri May 06, 2022 11:02 am

Ah, thanks for the LINK :-)
But IPv6 is even not working anymore (on all 5 CRS3xxx switches) even after a rebbot or a factory reset. Today I´ll try to reactivate it with a netinstall.
All other devices without L3HW offloading are working fine with IPv6....
 
mobyfab
just joined
Posts: 6
Joined: Tue Jul 03, 2018 4:45 pm
Location: France

Re: v7.3beta [testing] is released!

Fri May 06, 2022 8:49 pm

Tested on CCR2116: unstable after 3 hours, looses health info and fans spin up/down non stop.
Setting an interface to 2.5Gbps completely crashes the switch part (with 7.2 as well)
 
chiem
newbie
Posts: 41
Joined: Fri Oct 24, 2014 4:48 pm

Re: v7.3beta [testing] is released!

Fri May 06, 2022 11:29 pm

I sincerely hope the focus for the coming month will be on fixing things that are broken or still missing (relative to v6) and not on working on new features.
I'm not asking for it to be prioritized over stability fixes, but it's not even on the roadmap yet according to the last official statement on the matter. I think that ought to change given that 40% of worldwide traffic is on IPv6 already and in parts of the world, 2/3rds of users are on IPv6.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Fri May 06, 2022 11:46 pm

I sincerely hope the focus for the coming month will be on fixing things that are broken or still missing (relative to v6) and not on working on new features.
I'm not asking for it to be prioritized over stability fixes, but it's not even on the roadmap yet according to the last official statement on the matter. I think that ought to change given that 40% of worldwide traffic is on IPv6 already and in parts of the world, 2/3rds of users are on IPv6.
It is not like this feature is critical. It only means you need to buy a slightly more powerful device in order to handle the speed of your internet connection.
For example, I have a 180Mbps internet connection and a RB4011 router, and I do not need any fasttrack whatsoever (v4 nor v6).
 
msatter
Forum Guru
Forum Guru
Posts: 2897
Joined: Tue Feb 18, 2014 12:56 am
Location: Netherlands / Nīderlande

Re: v7.3beta [testing] is released!

Sat May 07, 2022 12:03 am

The 4011 is a fast router and it replaced one of my hEX-S, which needs fasttracking to archive speeds over 230Mbit/s.

Even encrypting traffic with the 4011 is a breeze and it archives almost line-speed. I needed two hEX-S in series (spliting up multiple connections), to archive 2/3 line-speed.
 
nereith
just joined
Posts: 6
Joined: Sat Dec 15, 2018 6:32 am

Re: v7.3beta [testing] is released!

Sat May 07, 2022 4:32 pm

*) sfp - added 2.5Gbps rate for SFP+ and QSFP+ interfaces on 98DXxxxx and 98PX1012 switches (requires disabled auto-negotiation);

CRS305 is using 98DX3236, CRS309 is using 98DX8208.

It looks like someone reported 2.5Gbps option is available in CRS305 when auto negotiation is disabled.

However, I don't see the 2.5Gbps option in CRS309 ...
 
rolling
just joined
Posts: 16
Joined: Wed Mar 11, 2020 5:15 pm

Re: v7.3beta [testing] is released!

Sat May 07, 2022 6:38 pm

*) sfp - added 2.5Gbps rate for SFP+ and QSFP+ interfaces on 98DXxxxx and 98PX1012 switches (requires disabled auto-negotiation);

I don't see it in CRS317 too... On beta37
 
chiem
newbie
Posts: 41
Joined: Fri Oct 24, 2014 4:48 pm

Re: v7.3beta [testing] is released!

Sat May 07, 2022 11:01 pm

It is not like this feature is critical. It only means you need to buy a slightly more powerful device in order to handle the speed of your internet connection.
For example, I have a 180Mbps internet connection and a RB4011 router, and I do not need any fasttrack whatsoever (v4 nor v6).
I have a CCR2004 on 3 gbps service. With this, I get around 90-95% of peak throughput on ipv6 with synthetic benchmarks, as it's bottlenecking on a single core. On real world usage, on things that I can configure to use ipv4 vs ipv6, the ipv6 performance is around 60% of ipv4 performance. So you're saying this $600 router isn't enough for 3 gbps and I need to step up to something "slightly more powerful"? What's the next step up? The $2800 CCR2216?

By your logic, getting missing 6.x features into 7.x isn't critical either, as one can just run 6.x.
 
nereith
just joined
Posts: 6
Joined: Sat Dec 15, 2018 6:32 am

Re: v7.3beta [testing] is released!

Sun May 08, 2022 6:31 am

*) sfp - added 2.5Gbps rate for SFP+ and QSFP+ interfaces on 98DXxxxx and 98PX1012 switches (requires disabled auto-negotiation);

I don't see it in CRS317 too... On beta37
Just got a reply from another thread indicating the option is only available via CLI and not WinBox at the moment.

viewtopic.php?t=166000#p931811
 
User avatar
Znevna
Forum Guru
Forum Guru
Posts: 1347
Joined: Mon Sep 23, 2019 1:04 pm

Re: v7.3beta [testing] is released!

Sun May 08, 2022 11:08 am

Not this version specific I think:
RB5009 - WinBox Health.PNG
On WebFig if you open that it looks fine though.
You do not have the required permissions to view the files attached to this post.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Sun May 08, 2022 11:27 am

It is not like this feature is critical. It only means you need to buy a slightly more powerful device in order to handle the speed of your internet connection.
For example, I have a 180Mbps internet connection and a RB4011 router, and I do not need any fasttrack whatsoever (v4 nor v6).
I have a CCR2004 on 3 gbps service. With this, I get around 90-95% of peak throughput on ipv6 with synthetic benchmarks, as it's bottlenecking on a single core. On real world usage, on things that I can configure to use ipv4 vs ipv6, the ipv6 performance is around 60% of ipv4 performance. So you're saying this $600 router isn't enough for 3 gbps and I need to step up to something "slightly more powerful"? What's the next step up? The $2800 CCR2216?

By your logic, getting missing 6.x features into 7.x isn't critical either, as one can just run 6.x.
Maybe 3Gbps is not as easy to route as you would hope.
Fasttrack was introduced to be able to route 500Mbps on 600 MHz MIPSBE devices. I.e. to extend the useful life of these a bit more, as they were designed in the times when 100Mbps was really the upper limit of what a user at home had.
It is more or less a stopgap measure. It has issues when you use the advanced features of the router. Which I do, so I always switch it off.
When I upgraded my line from 100 to 180 Mbps, I bought a new router. 3Gbps is not possible here, so I have no problem.
But I do use BGP and I do have problems with the v7 BGP implementation. So I rather think they should fix that first, as it worked in v6 and IPv6 fasttrack never did.
 
mafiosa
Member Candidate
Member Candidate
Posts: 266
Joined: Fri Dec 09, 2016 8:10 pm
Location: Kolkata, India
Contact:

Re: v7.3beta [testing] is released!

Mon May 09, 2022 1:36 pm

Expecting a new release today.
 
User avatar
sirbryan
Member Candidate
Member Candidate
Posts: 298
Joined: Fri May 29, 2020 6:40 pm
Location: Utah
Contact:

Re: v7.3beta [testing] is released!

Mon May 09, 2022 8:32 pm

I have a CCR2004 on 3 gbps service. With this, I get around 90-95% of peak throughput on ipv6 with synthetic benchmarks, as it's bottlenecking on a single core. On real world usage, on things that I can configure to use ipv4 vs ipv6, the ipv6 performance is around 60% of ipv4 performance. So you're saying this $600 router isn't enough for 3 gbps and I need to step up to something "slightly more powerful"? What's the next step up? The $2800 CCR2216?

By your logic, getting missing 6.x features into 7.x isn't critical either, as one can just run 6.x.
The RB4011/RB5009/CCR2004 are quad-core CPU's that all seem to max out around 3-5Gbps, depending on the configuration and software version. Aside from the limited switch chip on 4011/5009, there is little offloaded to hardware (IPSEC is about it).

On my 4011's and 5009's I'm seeing a peak of about 5Gbps in/out through the SFP+ port (router-on-a-stick config). On the 2004, I'm lucky to route anything over 3Gbps on 6 or 7. Bridging on 7.2.x does perform as expected (6+Gbps no problem).

The next step up is the CCR2116 for roughly $800. It's a 16-port Layer 3 switch with a 40Gbps connection to the 16-core CPU. With IPv4 L3-Hw-offload enabled, CPU literally drops to 0% (but so does NAT/firewall functionality).

I've now deployed a half-dozen 2116's across my network, one of which replaced my busiest 2004. They can be found for just under US$800. They're essentially a CCR3XX switch with a 40Gbps connection to the CPUs, and so far I'm impressed with their performance.

Edit: I replaced the home/office 2004 with a 2116 and am able to go over 3Gbps without breaking a sweat. The bottleneck at this point is the 27km 80GHz shot running at 4Gbps.

To your original point, based on my experience, the 2004 should be able to route 3Gbps just fine with a handful of NAT rules, VPNs, etc. It performs better on 7 than it does on 6 (for the hardware revision capable of running 6).
Last edited by sirbryan on Wed May 11, 2022 5:16 pm, edited 1 time in total.
 
mvdswaluw
just joined
Posts: 13
Joined: Wed Sep 16, 2020 8:56 pm

Re: v7.3beta [testing] is released!

Wed May 11, 2022 11:26 am

In RouterOS 7.1 I had some problems with a memory leak in my CRS326. Now, since april 24th, with 7.3Beta34 installed the worst is gone, but still a small leak is left behind. The memory-consumption does follow the amount of data-throughput. During a week of holiday the leaked memory was less than the last few days. I've already tried clearing the log, and de/re-activating DNS-caching, and lowering max-ttl in DNS-cache and firewall connection tracking, but this does not free up any memory. Any thoughts on how I can find out what process is leaking this memory?

CRS Free memory:
20220511_CRS_Memory.JPG

RouterOS 7.1 Memory leak on yearly-graph:
20220511_CRS_Yearly.gif
You do not have the required permissions to view the files attached to this post.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Wed May 11, 2022 12:35 pm

Unfortunately, not. It would be nice when there was some form of "ps" command or the "tools->profile" would also show memory usage for different categories.
It could also be that more info is in a supout file. There is a supout viewer on the mikrotik.com website (login with your account), but unfortunately it is very limited.
It does not show the memory usage, probably there is much more info in this file and the support people have a better viewer, as they ask so often for a supout.rif file and frankly I see nothing of value in there aside of the configuration export and some packet counters. But the file is much bigger than an export, likely it contains lots of things like logs and a dump of /proc which includes the detailed memory usage per process.
 
chiem
newbie
Posts: 41
Joined: Fri Oct 24, 2014 4:48 pm

Re: v7.3beta [testing] is released!

Thu May 12, 2022 10:23 am

I've now deployed a half-dozen 2116's across my network, one of which replaced my busiest 2004. They can be found for just under US$800. They're essentially a CCR3XX switch with a 40Gbps connection to the CPUs, and so far I'm impressed with their performance.
Thanks for pointing out the CCR2116. What kind of performance are you seeing on it? If I'm bottlenecking at around 2.7-2.9 gbps with ipv6 on 1 out of 4 cores with the CCR2004, wouldn't I also bottleneck on 1 out of 16 cores with the CCR2116? Granted, the CCR2116's cores run at 2 ghz (vs 1.7 ghz on the CCR2004), so I'd get ~20% better performance in this scenario, but that's not a tempting reason to upgrade.
 
hecatae
Member Candidate
Member Candidate
Posts: 244
Joined: Thu May 21, 2020 2:34 pm

Re: v7.3beta [testing] is released!

Thu May 12, 2022 11:30 am

Hi Mikrotik,

Any more 7.3beta or are you looking at 7.4beta?

Happy to test whatever you are currently looking to pass to Stable so that Stable users do not cry.
 
User avatar
jbl42
Member Candidate
Member Candidate
Posts: 214
Joined: Sun Jun 21, 2020 12:58 pm

Re: v7.3beta [testing] is released!

Thu May 12, 2022 2:59 pm

wouldn't it also bottleneck on 1 out of 16 cores with the CCR2116?
A single TCP connection is always handled on 1 CPU core. This is required to avoid packet reordering.
So if you run a speedtest using only one TCP connection, it will max out 1 core also on CCR2116. But if you run several connection in parallel, the will be distributed among the CPU core. So the CCR2116 is expected to be a bit faster for a single connection due to higher core clock, but will handle parallel connections with more total throughput because of the higher number of cores.
 
User avatar
Larsa
Forum Guru
Forum Guru
Posts: 1025
Joined: Sat Aug 29, 2015 7:40 pm
Location: The North Pole, Santa's Workshop

Re: v7.3beta [testing] is released!

Thu May 12, 2022 3:14 pm

Just a hint. Google speed test (ie the one that's built-in the search page) by m-labs utilize udp using webrtc.
 
rolling
just joined
Posts: 16
Joined: Wed Mar 11, 2020 5:15 pm

Re: v7.3beta [testing] is released!

Thu May 12, 2022 5:55 pm

*) sfp - added 2.5Gbps rate for SFP+ and QSFP+ interfaces on 98DXxxxx and 98PX1012 switches (requires disabled auto-negotiation);
Hi:

Module ODI XPON DFP-34X-2C2 is detected by CRS317-1G-16S+RM but is imposible entablish link, with or without autonegotiation, setting half / full duplex, setting 100M, 1Gb, 2.5Gb, ...

On RB5009UG+S+IN it link OK.

Those devices on beta37.

Regards.
 
mobyfab
just joined
Posts: 6
Joined: Tue Jul 03, 2018 4:45 pm
Location: France

Re: v7.3beta [testing] is released!

Fri May 13, 2022 1:44 pm

I've now deployed a half-dozen 2116's across my network, one of which replaced my busiest 2004. They can be found for just under US$800. They're essentially a CCR3XX switch with a 40Gbps connection to the CPUs, and so far I'm impressed with their performance.
Thanks for pointing out the CCR2116. What kind of performance are you seeing on it? If I'm bottlenecking at around 2.7-2.9 gbps with ipv6 on 1 out of 4 cores with the CCR2004, wouldn't I also bottleneck on 1 out of 16 cores with the CCR2116? Granted, the CCR2116's cores run at 2 ghz (vs 1.7 ghz on the CCR2004), so I'd get ~20% better performance in this scenario, but that's not a tempting reason to upgrade.
Using around 15% cpu at 2Gbps (vs 0% with L3HW for ipv4), worst core at ~50%, using multiple connections.
On a single connection, 1.25Gbps (one core at 98%)
I am using vlan tagging
CCR2116 cores are Cortex-A72 vs A57 for the CCR2004 so that's another +25%.
Last edited by mobyfab on Sat May 14, 2022 3:39 pm, edited 1 time in total.
 
User avatar
emils
Forum Veteran
Forum Veteran
Topic Author
Posts: 906
Joined: Thu Dec 11, 2014 8:53 am

Re: v7.3beta [testing] is released!

Fri May 13, 2022 3:42 pm

What's new in 7.3beta40 (2022-May-11 12:18):

!) queue - do not allow using CAKE type in simple and tree setups (already configured queues will be disabled);
*) bgp - added "name" parameter for connections;
*) bgp - fixed "keepalive-timeout" value when upgrading from RouterOS v6;
*) bgp - fixed "l2vpn" distribution;
*) bridge - added more details for loop detection warning;
*) bridge - do not set VLAN on inactive port with a "set" command;
*) bridge - ignore VLAN tagged BPDU;
*) capsman - improved traffic processing over CAP communication tunnels:
*) chr - fixed Cloud DDNS update after license renewal;
*) dot1x - fixed RADIUS State attribute when client is reauthenticated;
*) dot1x - fixed port based VLAN ID assignment on devices without a switch chip;
*) dot1x - improved server system stability during authentication;
*) ipsec - fixed printing of active peer statistics;
*) l3hw - improved offloading in cases of HW table overflow for CRS305, CRS326-24G-2S+, CRS328, CRS318, CRS310;
*) l3hw - optimized offloading when dealing with large volume of directly connected hosts;
*) lte - added SMS sending support for MBIM protocol;
*) lte - allow only MCC/NMC format in "operator" parameter;
*) lte - clear SIM values when modem in "stopped" state;
*) mpls - improved LDP AF selection process and behavior;
*) ntp - do not allow setting port number in "server" parameter;
*) ovpn - adjusted SHA2 authentication algorithm naming to allow legacy OpenVPN implementations to connect;
*) ovpn - improved server stability under continous overload;
*) ovpn - reply with the same IP address that the connection was established to;
*) ppp - added support for VRF;
*) romon - fixed VLAN tagged packet processing;
*) route - fixed IPv6 /127 route nexthop resolution;
*) routerboot - prevent enabling "protected-routerboot" on unsupported factory firmware versions;
*) sfp - fixed link flap for QSFP+ and QSFP28 ports connected with a breakout cable, in cases where the base interface changes "running" state (introduced in v7.3beta33);
*) sfp - hide empty monitor values in console;
*) snmp - added VRF support (CLI only);
*) snmp - fixed reported disk size when multiple external disks are attached;
*) snmp - report "ifSpeed" as 0 if value out of bounds (use "ifHighSpeed" for high speed interfaces instead);
*) ssh - added AES-GCM cipher support;
*) ssh - removed DSA public key authentication support;
*) supout - added simplified IPv4 and IPv6 routing table prints;
*) switch - fixed "switch-cpu" port stats for 98DXxxxx and 98PX1012 switches (introduced in v7.3beta37);
*) switch - fixed missing stats in traffic-monitor for 98DXxxxx and 98PX1012 switches;
*) system - fixed Kernel timer consistency;
*) tunnels - improved packet handling over EoIP, IPIP and GRE tunnels;
*) vpls - fixed TE transport path usage after startup;
*) vrrp - fixed learning of bridged local MAC addreses;
*) winbox - added missing "IBGP", "EBGP", "Limit Exceeded" and "Stopped" parameters under "Routing/BGP/Sessions" menu;
*) winbox - added missing "Keep Sent Attributes" parameter under "Routing/BGP/Connection" menu;
*) winbox - added missing "Scan List" parameter for W60G interfaces;
*) winbox - added missing BGP session commands;
*) winbox - added support for 2.5Gbps and 100Gbps Ethernet speed options;
*) winbox - do not show "Session Uptime" parameter under "LTE" menu if not supported by modem;
*) winbox - fixed "Disconnect Timeout" parameter type under "CAPsMAN" menu;
*) winbox - fixed "IP/Cloud" window refreshing after changes are detected;
*) winbox - properly load band values under "LTE" menu;
*) winbox - removed obsolete "Routing Table" parameter under "IP/Firewall" menu;

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

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 some problem has appeared on device
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1070
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: v7.3beta [testing] is released!

Fri May 13, 2022 3:49 pm

*) ssh - added AES-GCM cipher support;
*) ssh - removed DSA public key authentication support;
Let's hope this is a preparation to get ed25519 keys in...
 
ivicask
Member
Member
Posts: 417
Joined: Tue Jul 07, 2015 2:40 pm
Location: Croatia, Zagreb

Re: v7.3beta [testing] is released!

Fri May 13, 2022 3:55 pm

@emils Can you explain this?
queue - do not allow using CAKE type in simple and tree setups (already configured queues will be disabled)
So where can we use Cake? Only as interface queue? Was it disabled due router instability and crashing problems ?
 
ormandj
just joined
Posts: 18
Joined: Tue Jun 15, 2021 12:25 am

Re: v7.3beta [testing] is released!

Fri May 13, 2022 4:18 pm

*) ssh - added AES-GCM cipher support;
*) ssh - removed DSA public key authentication support;
Let's hope this is a preparation to get ed25519 keys in...
Seeing movement on ciphers in SSH gets me excited. ed25519 would be wonderful.
Last edited by ormandj on Fri May 13, 2022 4:20 pm, edited 1 time in total.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Fri May 13, 2022 4:19 pm

*) bgp - added "name" parameter for connections;
Please explain. Connections always had a name parameter. Sure it would be nice when sessions had a name parameter too!
 
User avatar
SiB
Forum Guru
Forum Guru
Posts: 1888
Joined: Sun Jan 06, 2013 11:19 pm
Location: Poland

Re: v7.3beta [testing] is released!

Fri May 13, 2022 4:29 pm

Seams like new v6 that subversion vx.4 is first stable in ros. I wait for v7.4 and hope will be first stable for DataCenter installation.
 
Rfulton
Frequent Visitor
Frequent Visitor
Posts: 99
Joined: Tue Aug 08, 2017 2:17 am

Re: v7.3beta [testing] is released!

Fri May 13, 2022 4:57 pm

!) queue - do not allow using CAKE type in simple and tree setups (already configured queues will be disabled);

WTFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26290
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia

Re: v7.3beta [testing] is released!

Fri May 13, 2022 5:15 pm

CAKE type was always meant only for interface queue, it had no effect when used in simple queue.
 
ivicask
Member
Member
Posts: 417
Joined: Tue Jul 07, 2015 2:40 pm
Location: Croatia, Zagreb

Re: v7.3beta [testing] is released!

Fri May 13, 2022 5:23 pm

CAKE type was always meant only for interface queue, it had no effect when used in simple queue.
How are we now supposed to set different download/upload speeds for asymmetrical links? Can you add this to Cake queue it self? Now with this change we can't control it via simple/tree queue and by setting 2 different cake queue types one for download and one for upload.
 
User avatar
buvarbeno
just joined
Posts: 9
Joined: Thu Mar 07, 2019 12:11 pm

Re: v7.3beta [testing] is released!

Fri May 13, 2022 5:26 pm

CAKE type was always meant only for interface queue, it had no effect when used in simple queue.
Bad joke, it worked with queue tree, but was not stable. I made netwatch script, what disabled and reenabled the queue, only in rare situation was problem, and netwatch script always helped...
Please FIX IT!!!
 
Rfulton
Frequent Visitor
Frequent Visitor
Posts: 99
Joined: Tue Aug 08, 2017 2:17 am

Re: v7.3beta [testing] is released!

Fri May 13, 2022 6:02 pm

CAKE type was always meant only for interface queue, it had no effect when used in simple queue.
so my queue trees are worthless? I can only use cake with interface queue? is it always going to be like this?
 
mikegleasonjr
Frequent Visitor
Frequent Visitor
Posts: 55
Joined: Tue Aug 07, 2018 3:14 am

Re: v7.3beta [testing] is released!

Fri May 13, 2022 6:03 pm

The creator of Cake graced us with his presence and knowledge here and they still half baked it. Numerous persons and I created bug reports and suggested features to make it usable.

I was still using it over codel with relative success.

Now they killed it.

I asked why the feature/bug report was closed and they said it will be implemented later. Then another admin told me it won't be implemented at all, that's why it was closed.

I don't have the courage to build a case to show the common sense that was proposed and the lack of responsability shown by Mikrotik.

So how do you guys propose we use Cake now? What's the migration path?
 
mikegleasonjr
Frequent Visitor
Frequent Visitor
Posts: 55
Joined: Tue Aug 07, 2018 3:14 am

Re: v7.3beta [testing] is released!

Fri May 13, 2022 6:04 pm

CAKE type was always meant only for interface queue, it had no effect when used in simple queue.
so my queue trees are worthless? I can only use cake with interface queue? is it always going to be like this?
It had effect on queue trees, I was using them successfully. Even though I was not able to specify the direction.

You guys are lazy.
 
kevinb361
Frequent Visitor
Frequent Visitor
Posts: 82
Joined: Wed Jul 01, 2020 5:02 am

Re: v7.3beta [testing] is released!

Fri May 13, 2022 6:09 pm

It was working freaking great for me in simple queue's. Granted, that was with a 100/20 link.

Anyhow.. I changed the interface queue for my WAN interface to cake with a limit of my upload speed. It appears to be working well. With a few quick tests.. my flent tests appear about the same as before.
 
mikegleasonjr
Frequent Visitor
Frequent Visitor
Posts: 55
Joined: Tue Aug 07, 2018 3:14 am

Re: v7.3beta [testing] is released!

Fri May 13, 2022 6:12 pm

@dtaht please save us and explain to a hardware maker again how this should be implemented properly in their solution...

We could use Cake in queues before.. it's just we couldn't specify the direction as per viewtopic.php?p=878190#p878190. But it was working okay. Now we can't use it anymore.
 
mikegleasonjr
Frequent Visitor
Frequent Visitor
Posts: 55
Joined: Tue Aug 07, 2018 3:14 am

Re: v7.3beta [testing] is released!

Fri May 13, 2022 6:21 pm

The way they do it everywhere else is using queues, not interfaces. So you have 2 queues, one inbound one outbound to specify ingress/egress.

At least in OpenWRT and PFSense.

Also @normis, can you back that quote up?

What happens when it lands in the stable branch, you're still making breaking changes in the stable branch? You're beaking a stable API?
 
mikegleasonjr
Frequent Visitor
Frequent Visitor
Posts: 55
Joined: Tue Aug 07, 2018 3:14 am

Re: v7.3beta [testing] is released!

Fri May 13, 2022 6:33 pm

How do you specify the Cake bandwidth on asymetric links?

Cake needs a direction in its config to work properly, you can't use a single queue instance to manage both direction.

WTF
 
arm920t
Frequent Visitor
Frequent Visitor
Posts: 61
Joined: Sat Aug 03, 2019 8:02 am

Re: v7.3beta [testing] is released!

Fri May 13, 2022 6:50 pm



so my queue trees are worthless? I can only use cake with interface queue? is it always going to be like this?
It had effect on queue trees, I was using them successfully. Even though I was not able to specify the direction.

You guys are lazy.
I am using cake with queue tree too.It works well and i don't understand why CAKE can only be used with interface queue in ros.
 
User avatar
jbl42
Member Candidate
Member Candidate
Posts: 214
Joined: Sun Jun 21, 2020 12:58 pm

Re: v7.3beta [testing] is released!

Fri May 13, 2022 7:30 pm

CAKE type was always meant only for interface queue, it had no effect when used in simple queue.
I'm confused. I run 2 cake queue types on my WAN bridge interface in a simple queue and it works without issues.

In a WAN interface queue , how do i specify different rates for asymetric lines?
Further, there are different diffserv algorithms required for up/down. For uplink, diffserv3 is perfect. For download, only best effort makes sense, because the qeuing is happening at the ISPs end of the line.

@Normis
The creator of cake is around here in the forum. Maybe you contact him and let him explain how cake works.
Sorry, but this is embarassing.
 
Rfulton
Frequent Visitor
Frequent Visitor
Posts: 99
Joined: Tue Aug 08, 2017 2:17 am

Re: v7.3beta [testing] is released!

Fri May 13, 2022 7:34 pm

the cake was a lie all along bros....
 
evbocharov
newbie
Posts: 26
Joined: Tue May 25, 2021 11:06 pm

Re: v7.3beta [testing] is released!

Fri May 13, 2022 7:46 pm

did it get fixed in 7.3beta40: ping fixed socket allocation after VRF change ?
 
User avatar
jbl42
Member Candidate
Member Candidate
Posts: 214
Joined: Sun Jun 21, 2020 12:58 pm

Re: v7.3beta [testing] is released!

Fri May 13, 2022 7:55 pm

the cake was a lie all along bros....
:-) memories...
Image
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v7.3beta [testing] is released!

Fri May 13, 2022 7:59 pm

Remember this is just one beta version. MT do read this forum and they see user reaction to what they do. So no need 100 post about the same.
 
tangent
Forum Guru
Forum Guru
Posts: 1333
Joined: Thu Jul 01, 2021 3:15 pm
Contact:

Re: v7.3beta [testing] is released!

Fri May 13, 2022 8:11 pm

How do you specify the Cake bandwidth on asymetric links?

limit-at=DOWN/UP ?
 
realmark
just joined
Posts: 11
Joined: Fri Feb 12, 2021 7:15 pm

Re: v7.3beta [testing] is released!

Fri May 13, 2022 10:23 pm

Any word on a milestone we might expect BFD to show up in the beta? BFD, at least from our perspective, is now the biggest missing feature of v7.
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Fri May 13, 2022 11:01 pm

Any word on a milestone we might expect BFD to show up in the beta? BFD, at least from our perspective, is now the biggest missing feature of v7.
Indeed, the number of changes in BGP is a bit disappointing. We also need BFD. Now we get
*) bgp - added "name" parameter for connections;
and I already asked for clarification of this item because as far as I know, "name" parameter for connections was present from the beginning of v7 releases, later I thought "maybe they mean the connection name parameter from now on is shown in BGP log messages" but NO, we still get those completely meaningless messages:

May/13/2022 21:38:23 route,bgp,error HoldTimer expired
May/13/2022 21:38:23 route,bgp,error Session *=0x30150240
 
User avatar
loloski
Member Candidate
Member Candidate
Posts: 277
Joined: Mon Mar 15, 2021 9:10 pm

Re: v7.3beta [testing] is released!

Sat May 14, 2022 4:50 am

Confirm dot1x is working now again for the device w/o switch chip with vlan id assignment
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.3beta [testing] is released!

Sat May 14, 2022 5:26 am

Disappointing about cake. We need more options to use it other than just interface queues. There are many instances like downlink where you may have multiple downlink interfaces going through the same internet connection, and then there is no way of specifying a single download amount with cake across all interfaces. This may indicate that MikroTik's queue system, based on HTB, is somewhat in need of an overhaul and a redesign, in order to properly incorporate some of these new options and add some missing features.
 
dtaht
Member Candidate
Member Candidate
Posts: 209
Joined: Sat Aug 03, 2013 5:46 am

Re: v7.3beta [testing] is released!

Sat May 14, 2022 6:50 am

I have tried to reach out to mikrotik before on how better to implement cake and fq_codel, even better than it was already working. I'm easily found at dave dot taht at gmail dot com. Or on the cake mailing list on lists.bufferbloat.net. I've been working for free, here, on getting a quality implementation shipped. I happen to really like mikrotik gear. I'd be happy to help get back in there and see what I can do to help resolve any problems that remain.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.3beta [testing] is released!

Sat May 14, 2022 7:28 am

@dtaht I hope they take up on on that offer. I know they are trying to get v7 stabilized at the moment, and agree with that and hope that happens as soon as possible, but after that I do want to see cake as a functional solution in the reasonably near term.
 
ixel
just joined
Posts: 3
Joined: Fri Aug 27, 2021 12:00 am

Re: v7.3beta [testing] is released!

Sat May 14, 2022 10:50 am

Highly disappointing about CAKE. Feels like the recent change is perhaps lazy, not thought through or both. A massive step back. It was working fine in my queue tree, now I can't specify different ingress and egress rates if I upgrade.
 
User avatar
jbl42
Member Candidate
Member Candidate
Posts: 214
Joined: Sun Jun 21, 2020 12:58 pm

Re: v7.3beta [testing] is released!

Sat May 14, 2022 1:37 pm

How do you specify the Cake bandwidth on asymetric links?

limit-at=DOWN/UP ?
There is no limit-at=DOWN/UP for interface queues.
 
hecatae
Member Candidate
Member Candidate
Posts: 244
Joined: Thu May 21, 2020 2:34 pm

Re: v7.3beta [testing] is released!

Sat May 14, 2022 3:06 pm

7.3beta40 is available, why is it buried in this thread.

Hap lite updated.
 
User avatar
borr
just joined
Posts: 20
Joined: Wed May 18, 2016 10:23 pm

Re: v7.3beta [testing] is released!

Sat May 14, 2022 5:16 pm

hex, hap ac^2 -- wireguard peers still cannot use IPv6 simultaneously on 7.3beta40, SUP-78547, viewtopic.php?p=933150, last working version is 7.1rc4 (downgrading from any version after to 7.1rc4 without touching the config)
 
holvoetn
Forum Guru
Forum Guru
Posts: 5323
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: v7.3beta [testing] is released!

Sat May 14, 2022 5:57 pm

7.3beta40 is available, why is it buried in this thread.
It was mentioned on post 230 ;)

hAP AC3 using wifiwave2 upgraded.
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v7.3beta [testing] is released!

Sat May 14, 2022 8:19 pm

7.3beta40 is available, why is it buried in this thread.
This is how beta are posted. Look at older beta threads and you will find all beta version in just one thread for each main version.
 
User avatar
colinardo
just joined
Posts: 18
Joined: Sun Jan 08, 2017 9:02 pm

Re: v7.3beta [testing] is released!

Sat May 14, 2022 8:30 pm

What's new in 7.3beta40 (2022-May-11 12:18):
*) dot1x - fixed RADIUS State attribute when client is reauthenticated;
*) dot1x - fixed port based VLAN ID assignment on devices without a switch chip;
*) dot1x - improved server system stability during authentication;

Confirming dot1x auth with dynamic vlan assignment now working again in beta40 👍. Thanks for your work!
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7038
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7.3beta [testing] is released!

Sat May 14, 2022 10:06 pm

*) bgp - added "name" parameter for connections;
Please explain. Connections always had a name parameter. Sure it would be nice when sessions had a name parameter too!
It supposed to be session
[admin@MikroTik] /routing/bgp/session> print 
Flags: E - established 
 0 E name="test_large_community-1" 
     remote.address=x.x.x.x .as=456 .id=10.155.255.186 .refused-cap-opt=no 
     .capabilities=mp,rr,gr,as4 .afi=ip,ipv6 .messages=1 .bytes=19 .eor="" 
     local.address=y.y.y.y .as=444 .id=192.168.44.2 .capabilities=mp,rr,gr,as4 
     .afi=ip,ipv6 .messages=4 .bytes=219 .eor="" 
     output.procid=20 .filter-chain=bgp_out .network=test_list .keep-sent-attributes=yes 
     input.procid=20 .filter=bgp_in_large_comm ebgp 
     hold-time=3m keepalive-time=1m uptime=58s350ms 

 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Sat May 14, 2022 10:19 pm

Ok that is great, but unfortunately there is no "Name" column that can be selected in winbox...
 
chiem
newbie
Posts: 41
Joined: Fri Oct 24, 2014 4:48 pm

Re: v7.3beta [testing] is released!

Sun May 15, 2022 6:12 am

On a single connection, 1.25Gbps (one core at 98%)
I am using vlan tagging
Pretty depressing performance there.
Using around 15% cpu at 2Gbps (vs 0% with L3HW for ipv4), worst core at ~50%, using multiple connections.
CCR2116 cores are Cortex-A72 vs A57 for the CCR2004 so that's another +25%.
Good to know.
 
fragtion
Member Candidate
Member Candidate
Posts: 257
Joined: Fri Nov 13, 2009 10:08 pm
Location: Johannesburg, South Africa

Re: v7.3beta [testing] is released!

Sun May 15, 2022 1:57 pm

Is cake going to make a return to simple queues & queue tree? @normis is not correct that cake has no effect on simple queues, actually it works with simple queues so what is the real reason why it was removed ??
Last edited by fragtion on Sun May 15, 2022 7:04 pm, edited 1 time in total.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 11967
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: v7.3beta [testing] is released!

Sun May 15, 2022 6:41 pm

Have you contacted the Alcatel-Lucent user forum?
 
mobyfab
just joined
Posts: 6
Joined: Tue Jul 03, 2018 4:45 pm
Location: France

Re: v7.3beta [testing] is released!

Sun May 15, 2022 7:56 pm

CCR2116 with ISP SFP ALCATELLUCENT firmware V7.37beta. Got PSU 1 & 2 fail after some's day's. The fan go up and down and the healt status was wrong. Look like the SFP was not supported and cause this issue. I already tested with all v7 release, beta and stable. The longuor working release was the v7.37beta. The issue started 24h after power outage. I did the reboot and work fine for more 26H. Now I did reboot and upgrade to v7.40beta to see if I still have the same issue. I open ticket (SUP-82215) for more analyses.
I have exactly the same issue after around 3 hours of uptime.
I'm using another GPON SFP from FS.com which works fine in a CRS317.
Last edited by mobyfab on Thu May 19, 2022 8:10 pm, edited 1 time in total.
 
nkourtzis
Member Candidate
Member Candidate
Posts: 214
Joined: Tue Dec 11, 2012 12:56 am
Location: Greece

Re: v7.3beta [testing] is released!

Sun May 15, 2022 10:31 pm

CAKE type was always meant only for interface queue, it had no effect when used in simple queue.

This is hugely inaccurate at best, if not a straight out lie.

I used many cake-based simple queues which not only had effect, but brought very significant improvements as measured by the test at https://www.waveform.com/tools/bufferbloat. When configured carefully by hand, thay could improve a connection bufferbloat result from category F to B or even A. The problem was that the queue operation was not stable, even on powerful routers. Often the queues would stop forwarding traffic for a short while, then resume, then stop again, etc.

The decision to only allow CAKE queues on interfaces is not a solution but a lazy cover-up of the problem and a MAJOR setback, as we CANNOT do the following:
  • Set different rates for UL and DL (like on DSL or assymetrical wireless links)
  • Set cake queues on vlan internet uplinks over the same physical interface, which may be capped by the provider to speeds less than the interface (say, two separate 100Mbps vlans over a 1Gbps ethernet port)

Dear Mikrotik, cake was very long overdue and now that you finally implemented it, you are negating this implementation. PLEASE take the offer of @dtaht above to iron out the problems and make this a really shiny feature of RouterOS!

-- A very loyal friend
 
curtdept
just joined
Posts: 2
Joined: Wed Nov 17, 2021 8:00 am

Re: v7.3beta [testing] is released!

Mon May 16, 2022 1:13 am

My Sierra EM7411 modem hasnt worked on my RB5009 since 7.1.5 (where it worked well). Any chance I could get a fix for that?
 
dominiaz
just joined
Posts: 20
Joined: Sat Jan 08, 2011 7:17 am

Re: v7.3beta [testing] is released!

Mon May 16, 2022 6:26 am

IP address on vlan over vpls interface caused Kernel Panic and reboot on all 7.x versions. Please fix it.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.3beta [testing] is released!

Mon May 16, 2022 7:20 am

I still don't have VPLS working at all on my test environment. One ping goes through and then CPU goes to 100% and the device becomes unresponsive - have to disconnect power from it and plug it back in.

Is there any headway on fixing this issue? I'm not the only one having it - others on the forum reported it too, although more people report VPLS works fine for them. I really can't even test v7 as a part of our production environment until it can reliably handle VPLS without freezing. Many of our devices are remote and a freeze like this would require a long distance trip to fix.
 
User avatar
buvarbeno
just joined
Posts: 9
Joined: Thu Mar 07, 2019 12:11 pm

Re: v7.3beta [testing] is released!

Mon May 16, 2022 9:29 am

Remember this is just one beta version. MT do read this forum and they see user reaction to what they do. So no need 100 post about the same.
Precisely this is why we need write down 100 times to pressure should be high enough on Mikrotik...
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3279
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: v7.3beta [testing] is released!

Mon May 16, 2022 9:56 am

100 email to support@mikrotik.com would be better.
 
User avatar
buvarbeno
just joined
Posts: 9
Joined: Thu Mar 07, 2019 12:11 pm

Re: v7.3beta [testing] is released!

Mon May 16, 2022 10:00 am

100 email to support@mikrotik.com would be better.
I wrote one with atached supout.riff, but the max they pointet that I set wrong bucket size (it was a mistake in my set up commands), but the problems remained with default bucket sizes too, what I notified via e-mail too...

Then came the new beta with disabled CAKE :D
 
kaixinwang
just joined
Posts: 4
Joined: Tue Oct 19, 2021 12:41 pm

Re: v7.3beta [testing] is released!

Mon May 16, 2022 1:04 pm

Why delete CAKE? CAKE works very well in RB5009 7.2.3
 
fragtion
Member Candidate
Member Candidate
Posts: 257
Joined: Fri Nov 13, 2009 10:08 pm
Location: Johannesburg, South Africa

Re: v7.3beta [testing] is released!

Mon May 16, 2022 3:57 pm

Give us CAKE back please this is the most senseless decision and is holding me back from upgrading to latest beta.
Otherwise please give us valid reason for relegating it to interface only, because the reason normis provided has been invalidated by several users now. This bizzare change is being questioned by everyone who was using cake, please provide a proper explanation to your concerned community of beta testers so we can also understand why this happened in the first place!!
 
ixel
just joined
Posts: 3
Joined: Fri Aug 27, 2021 12:00 am

Re: v7.3beta [testing] is released!

Mon May 16, 2022 8:48 pm

Give us CAKE back please this is the most senseless decision and is holding me back from upgrading to latest beta.
Otherwise please give us valid reason for relegating it to interface only, because the reason normis provided has been invalidated by several users now. This bizzare change is being questioned by everyone who was using cake, please provide a proper explanation to your concerned community of beta testers so we can also understand why this happened in the first place!!
Agreed, I would try the latest beta version if it wasn't for this unnecessary restriction being applied (with an invalid reason). I hope the restriction on CAKE is removed/reverted, at the very least. If they really want to have a better CAKE integration then they should engage for discussion and assistance. This restriction is both unnecessary and feels like a lazy decision.
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.3beta [testing] is released!

Tue May 17, 2022 6:43 am

I'm guessing that they may have found that the stability issues with cake happen when using it with HTB even on regular Linux, outside of RouterOS. dtaht did say that cake wasn't really designed with HTB in mind. But if that is the case I'm not sure why they wouldn't take dtaht up on his offer as that might be something that he is able to fix.
 
Sit75
just joined
Posts: 12
Joined: Thu Mar 11, 2021 9:43 pm

Re: v7.3beta [testing] is released!

Tue May 17, 2022 10:31 am

Hi guys, I need help. Is there any chance how to override default MTU for PPPoE introduced in Release 7.2rc1?
*) pppoe - use default MTU of 1492;
I need higher (1500) but it is always changed to 1492 automatically. Previous versions were fine.
Thank you for any advice.
You do not have the required permissions to view the files attached to this post.
 
Trunkz
just joined
Posts: 5
Joined: Mon Dec 02, 2019 5:44 pm

Re: v7.3beta [testing] is released!

Tue May 17, 2022 11:09 am

Hi guys, I need help. Is there any chance how to override default MTU for PPPoE introduced in Release 7.2rc1?
*) pppoe - use default MTU of 1492;
I need higher (1500) but it is always changed to 1492 automatically. Previous versions were fine.
Thank you for any advice.
Providing your ISP supports baby jumbo frame; you need to first set the eth port to MTU 1508; then PPP will use MTU 1500 :)
 
Sit75
just joined
Posts: 12
Joined: Thu Mar 11, 2021 9:43 pm

Re: v7.3beta [testing] is released!

Tue May 17, 2022 11:19 am

Hi guys, I need help. Is there any chance how to override default MTU for PPPoE introduced in Release 7.2rc1?
*) pppoe - use default MTU of 1492;
I need higher (1500) but it is always changed to 1492 automatically. Previous versions were fine.
Thank you for any advice.
Providing your ISP supports baby jumbo frame; you need to first set the eth port to MTU 1508; then PPP will use MTU 1500 :)
<br>
Done already, as I have mentioned it worked fine before. But Mikrotik "wisely" decided to use default 1492. And now is only 1492. :-)
 
User avatar
SiB
Forum Guru
Forum Guru
Posts: 1888
Joined: Sun Jan 06, 2013 11:19 pm
Location: Poland

Re: v7.3beta [testing] is released!

Tue May 17, 2022 11:43 am

What's new in 7.2 (2022-Mar-31 12:11):
*) pppoe - use default MTU of 1492;
 
pe1chl
Forum Guru
Forum Guru
Posts: 10185
Joined: Mon Jun 08, 2015 12:09 pm

Re: v7.3beta [testing] is released!

Tue May 17, 2022 11:49 am

It means that your ISP does not support RFC4638, which is required to transport those 1508 byte PPPoE frames.
My ISP does, and it works fine (MTU/MRU of the PPPoE interface remains at 1500 when configured that way)
Part of RFC4638 is to "test" sending a large frame, and when it fails the default MTU is to be used (normally 1492, was 1480 for a long time in RouterOS for unclear reasons).
 
Trunkz
just joined
Posts: 5
Joined: Mon Dec 02, 2019 5:44 pm

Re: v7.3beta [testing] is released!

Tue May 17, 2022 12:02 pm

Ditto the above; I'm running 7.2.3 here and have MTU 1500 :)
 
User avatar
Znevna
Forum Guru
Forum Guru
Posts: 1347
Joined: Mon Sep 23, 2019 1:04 pm

Re: v7.3beta [testing] is released!

Tue May 17, 2022 3:09 pm

@Sit75 try leaving max mtu/mru to auto and set mtu 1508 on interface vlan-848
 
ivicask
Member
Member
Posts: 417
Joined: Tue Jul 07, 2015 2:40 pm
Location: Croatia, Zagreb

Re: v7.3beta [testing] is released!

Tue May 17, 2022 10:18 pm

Just noticed bug which costed me 2 hours of debuging... For some reason when importing my mangle rules which contain routing marks it duplicated them and i had multiple tables with SAME NAME.So mangle marks looked ok and my table name was right, but it was "wrong right one"....
Why would you even allow creating multiple tables with same name??
You do not have the required permissions to view the files attached to this post.
 
User avatar
Chupaka
Forum Guru
Forum Guru
Posts: 8709
Joined: Mon Jun 19, 2006 11:15 pm
Location: Minsk, Belarus
Contact:

Re: v7.3beta [testing] is released!

Wed May 18, 2022 12:29 pm

So, I'm trying to use Cake on my WAN interface but fail:
 > queue/interface/set pppoe-out1 queue=cake-512k 
failure: non rate limit queues are useless on this interface
What's the right way to do that?
 
infabo
Long time Member
Long time Member
Posts: 586
Joined: Thu Nov 12, 2020 12:07 pm

Re: v7.3beta [testing] is released!

Wed May 18, 2022 9:16 pm

I second this: how to use cake on an interface directly?
 
User avatar
osc86
Member Candidate
Member Candidate
Posts: 197
Joined: Wed Aug 09, 2017 1:15 pm

Re: v7.3beta [testing] is released!

Wed May 18, 2022 10:01 pm

I also noticed when interacting with cake, like adding a new queue, trying to apply it to an interface, printing the queue type list, it always generates a 5 second lag on my router. At first I thought the router crashed.
 
User avatar
nithinkumar2000
Member Candidate
Member Candidate
Posts: 157
Joined: Wed Sep 11, 2019 7:42 am
Location: Coimbatore
Contact:

Re: v7.3beta [testing] is released!

Thu May 19, 2022 8:11 am

Please Solve issue of PPP Accounting of not sending IPv6 PD in radius accounting packet.............. Because of this we are unable to implement IPv6 in our network
 
mafiosa
Member Candidate
Member Candidate
Posts: 266
Joined: Fri Dec 09, 2016 8:10 pm
Location: Kolkata, India
Contact:

Re: v7.3beta [testing] is released!

Thu May 19, 2022 11:04 am

Please Solve issue of PPP Accounting of not sending IPv6 PD in radius accounting packet.............. Because of this we are unable to implement IPv6 in our network
Soon you will find certain forum gurus reply to your post that why you don't need PPP Accounting of sending IPv6 PD in radius accounting packet and justify mikrotik for it's non implementation.
 
User avatar
SiB
Forum Guru
Forum Guru
Posts: 1888
Joined: Sun Jan 06, 2013 11:19 pm
Location: Poland

Re: v7.3beta [testing] is released!

Thu May 19, 2022 12:49 pm

+1 for Accounting
+1 for CAKE
+999 for stable/mature ros7.3
 
mducharme
Trainer
Trainer
Posts: 1777
Joined: Tue Jul 19, 2016 6:45 pm
Location: Vancouver, BC, Canada

Re: v7.3beta [testing] is released!

Fri May 20, 2022 5:51 am

Soon you will find certain forum gurus reply to your post that why you don't need PPP Accounting of sending IPv6 PD in radius accounting packet and justify mikrotik for it's non implementation.
We do need this, but it is not a bug - it is instead a feature that they have not implemented yet. It is an important feature, but I can understand why they are prioritizing it below fixing things that were working in ROS 6.

Who is online

Users browsing this forum: bpwl, Netstumble, pe1chl, Rox169 and 25 guests