Did your BGP config survive during update? Do you have multiple routing tables?
On mine, the BGP config was lost together with multiple routing table config.
Inconsistency on syntax of RouterOS it is a pain in the…
Ex:
/routing/bgp/connection/print where address-families → ip, ipv6, vpnv4, vpnv6
/routint/route/print where afi → ip, ipv6, vpv4, vpn6
Another thing that is getting blurry for me is the concepts of RIB and FIB in RouterOS.
It is clear that /ip/route/ and /ipv6/route/ are the same thing, just with a hidden address-family filter.
In winbox, by counting routes, this becomes even more evident.
And this same table seems to be the /routing/route/ table.
But how can I print the differences between RIB and FIB?
Isn’t there the concept of RIB-ONLY?
The Intel AX adapters are hot garbage. Last week I literally had a laptop with an AX200 card sitting next to one with a Realtek 8852CE. The Realtek was connecting to my cAP ax in the next room at 1201 Mbs (max rate) and the AX200 was connecting at 300 Mbs. It also randomly decides to connect to 2.4Ghz on a far AP even when sitting underneath a cAP ax, which requires turning WiFi off and back on to fix. This is in Windows 11 23H2 connecting to cAP ax units running ROS 7.15.1.
I do not blame Mikrotik for this, as I have a ton of Wireless devices (Apple, Android, Google Home, Nvidia Shield, Chromecasts, etc) and it’s ONLY the devices with AX cards that act weird.
We have noticed that all complaints relating to client connection to mikrotik 802.11ax AP are related with these intel chips. It seems that there is a known bug in the linux kernel, specifically relating to this intel chip. Like I said somewhere else in the forum, we are investigating if we can somehow work around this known issue
Well, it is probably not just a Linux issue with these Intel AX cards. Kaldek is running Windows. It is more likely their Intel device firmware (firmware is proprietary binary regardless of OS/platform AFAIK)
I have ZERO issues with ax200/210 cards on Windows 10 or 11 with the latest drivers. The only problem I ever had was with the Known sleep bug which was fixed a fair few iterations back. Of course I am using 7.16RC1 not 7.15. something…
The ax200 card connected to the cap-wifi1 is in another room with the door closed and still getting 1201 up down with internal antennas.
Is there any known reason why Routing->Tables and Routing->BGP configuration is lost on upgrade?
This was also reported earlier in beta by someone else.
Please do not release before this is solved, risk of lock-out of remote routers!
Here in Europe (Germany) I’ve had an issue with all AX2XX and BE200 Cards ive owned with any channel above 124.
Above Channel 124 they only want to connect to 5GHz wifi if the channel width is a max of 20mhz.
Otherwise they connect with limited wifi speed.
I’ve had similar issues running a Qualcomm WCN685x. Which I think is an AMD Version.
The AMD RZ600 Qualcomm worked fine tho.
And a realtek card worked fine aswell.
Other devices dont seem to have any issues either. (specifically Phones with AX)
It may be related to incorrect country/region specific information.
There are several manufacturers where updating that info is a mess.
Probably the feeds of correct information are not that clear or are sometimes in error.
The more patches you need, the more complicated it becomes (and of course it needs much more time) to upgrade the kernel.
Not sure if that’s good or bad.