Page 2 of 2

Re: v7.1.1 is released!

Posted: Sun Jan 09, 2022 4:26 pm
by mafiosa
they are just tables, you can use IPv4 and IPv6 routes with them. For adding IPv6 routes to a table other than main, you currently have to use the cli, winbox still doesn't show the routing-table parameter.
Thanks

Re: v7.1.1 is released!

Posted: Sun Jan 09, 2022 4:37 pm
by mac112
Atom 270N does not work
This kernel requries an x86-64 CPU, but only detected an i686 CPU

Re: v7.1.1 is released!

Posted: Sun Jan 09, 2022 4:57 pm
by eenpahlefi
BGP > Template , disable or enable on click, erorr
RouterOS 7.1.1

Re: v7.1.1 is released!

Posted: Sun Jan 09, 2022 5:10 pm
by mkx
Atom 270N does not work
This kernel requries an x86-64 CPU, but only detected an i686 CPU
Atom N270 is a 32-bit only processor: https://ark.intel.com/content/www/us/en ... z-fsb.html

Re: v7.1.1 is released!

Posted: Sun Jan 09, 2022 5:23 pm
by Chupaka
Image

BGP > Template , disable or enable on click, erorr
RouterOS 7.1.1
You may want to try /routing/bgp/template/print in Terminal: it can show you the reason why it's Inactive
It definitely would help if you provide more details to describe problems.
Do you ask your doctor for help saying "I'm feeling ill"? :)
I'm sure veterinarians have to deal with this :) Sorry...

Re: v7.1.1 is released!

Posted: Sun Jan 09, 2022 5:52 pm
by Pomo
Also, quick set, now there is no check for updates buton?
Sure there is one.
Sure...

Re: v7.1.1 is released!

Posted: Sun Jan 09, 2022 7:22 pm
by fragtion
Hi. I'm seeing these two issues with v7.1 & v7.1.1 on two RB5009's. It manifests the same way on both routers..

1. some interfaces will see roughly 50% packet loss. One ping goes through, next times out, next goes through, next times out, etc... Direct LAN cable (under 1m) to neighbor device. If I disable the connection for a few minutes and re-enable, the pings are fine for a few seconds and then packet loss starts again.
Edit: this specific issue could have been caused by bridging VLANs incorrectly.

While this is happening, interface traffic graphs show similar gaps in coverage, like this:
issue.png
2. All interfaces (including eoips) randomly crash / go into "down" state together, and then come back up a few seconds later. Port flapping basically ...
The issue comes and goes. Some days it happens continuously and is bad, other days nothing. I don't know what's causing it.

Is this likely hardware-related, or software related? / Are either or both of these issues known ?

Re: v7.1.1 is released!

Posted: Sun Jan 09, 2022 8:34 pm
by mac112
Dual core AMD G-T48E 64bit CPU
does not work, the router still restarts
I have a Wyse D10DP

Re: v7.1.1 is released!

Posted: Sun Jan 09, 2022 8:46 pm
by pe1chl


Sure there is one.
Sure...
Increase your window size, it should be under what is shown for System.
Else check that you did not make a skin definition for webfig, that now also affects winbox.

Re: v7.1.1 is released!

Posted: Sun Jan 09, 2022 9:28 pm
by Pomo


Sure...
Increase your window size, it should be under what is shown for System.
Else check that you did not make a skin definition for webfig, that now also affects winbox.
Thanks.
Still cannot for the life of me make clients connect to 5GHz anything else than 5180. And yes, I am aware of dfs waiting periods.
Ideas?
/interface wireless
set [ find default-name=wlan1 ] adaptive-noise-immunity=ap-and-client-mode band=2ghz-g/n basic-rates-a/g=\
    9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mbps basic-rates-b="" country=no_country_set disabled=no \
    distance=indoors frequency-mode=manual-txpower mode=ap-bridge ssid=Matija station-roaming=enabled \
    supported-rates-a/g=9Mbps,12Mbps,18Mbps,24Mbps,36Mbps,48Mbps,54Mbps supported-rates-b="" wireless-protocol=\
    802.11 wps-mode=disabled
set [ find default-name=wlan2 ] adaptive-noise-immunity=ap-and-client-mode band=5ghz-a/n/ac channel-width=\
    20/40/80mhz-XXXX disabled=no distance=indoors installation=indoor mode=ap-bridge skip-dfs-channels=\
    10min-cac ssid=Matija station-roaming=enabled wireless-protocol=802.11 wps-mode=disabled
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk eap-methods="" group-key-update=1h mode=dynamic-keys \
    supplicant-identity=MikroTik
add authentication-types=wpa-psk,wpa2-psk eap-methods="" group-key-update=1h mode=dynamic-keys name=ivukovic \
    supplicant-identity=""
/interface wireless
add disabled=no hide-ssid=yes keepalive-frames=disabled mac-address=66:D1:54:3C:DC:28 master-interface=wlan1 \
    multicast-buffering=disabled name=ivukovic security-profile=ivukovic ssid=ivukovic station-roaming=enabled \
    wds-cost-range=0 wds-default-cost=0 wps-mode=disabled
add disabled=no hide-ssid=yes keepalive-frames=disabled mac-address=66:D1:54:3C:DC:27 master-interface=wlan2 \
    multicast-buffering=disabled name=ivukovic_5 security-profile=ivukovic ssid=ivukovic station-roaming=\
    enabled wds-cost-range=0 wds-default-cost=0 wps-mode=disabled

Re: v7.1.1 is released!

Posted: Mon Jan 10, 2022 4:48 pm
by mroccella
Any chance of getting QuickSet fixed so that CAPsMAN setup on the RB4011 works? The router will not find its internal radios or any CAPS until you enter:
/interface wireless cap set enabled=yes interfaces=wlan1,wlan2 caps-man-addresses=127.0.0.1 bridge=bridge
Then, CAPsMAN works like a charm.

Re: v7.1.1 is released!

Posted: Mon Jan 10, 2022 5:27 pm
by gotsprings
Any chance of getting QuickSet fixed so that CAPsMAN setup on the RB4011 works? The router will not find its internal radios or any CAPS until you enter:
/interface wireless cap set enabled=yes interfaces=wlan1,wlan2 caps-man-addresses=127.0.0.1 bridge=bridge
Then, CAPsMAN works like a charm.
The WAVE2 driver works SO MUCH BETTER on the 5Ghz radio... why would you want to handicap the radio performance with the old drivers?
(now that I got my smart ass comment out of the way.)
Many routers running caps-man are either not wireless enabled, or placed in such a location where having their radio on is point less.

Re: v7.1.1 is released!

Posted: Mon Jan 10, 2022 5:32 pm
by pe1chl
The WAVE2 driver works SO MUCH BETTER on the 5Ghz radio... why would you want to handicap the radio performance with the old drivers?
Because the stupid WAVE2 driver does not support the 2.4 GHz radio and cannot work together with the old drivers for 2.4 GHz.
No idea why that was ever implemented that way... it is ridiculous. A WiFi driver for a commercially sold 2.4+5GHz device that supports only the 5 GHz radio and makes use of the 2.4 GHz radio impossible.

Re: v7.1.1 is released!

Posted: Mon Jan 10, 2022 6:06 pm
by infabo
Lol! Heard that for the first time. I guess people would stop asking for a slimmed down wave2 package for other devices with less flash, when they would know that there is no 2.4ghz support right now.

Re: v7.1.1 is released!

Posted: Mon Jan 10, 2022 6:14 pm
by mkx
It's not that 2.4GHz is not supported ... the problem is what @pe1chl wrote that wave2 driver can not coexist with legacy drivers and that chipset running 2.4GHz wireless on RB4011 is not supported by wave2. 2.4GHz works just fine with wave2 drivers on Audience ...

Re: v7.1.1 is released!

Posted: Mon Jan 10, 2022 6:16 pm
by pe1chl
2.4GHz works just fine with wave2 drivers on Audience ...
Frankly I don't give a sh*t about how well it works with Audience, it does not work on my RB4011 which is a relatively modern and high-end device in the MikroTik line. It should be supported well.
"RB4011iGS+5HacQ2HnD-IN (WiFi model) is dual band, four chain unit with a supported data rate of up to 1733 Mbps in 5GHz. For legacy devices, the unit also has a dual chain 2GHz wireless card installed in miniPCI-e slot."
Ok. So the 2 GHz card is apparently changeable (I never opened this router). I think MikroTik should provide free replacement mini-PCI-e cards for users of the RB4011 who want the WiFi to be supported together with 5 GHz.

Re: v7.1.1 is released!

Posted: Mon Jan 10, 2022 7:17 pm
by mkx
I guess that MT will eventually support combination of wave2 drivers and legacy drivers in parallel... I just hope it'll be in 7.2 rather than 7.38 ...

Re: v7.1.1 is released!

Posted: Mon Jan 10, 2022 7:57 pm
by WeWiNet
2.4GHz works just fine with wave2 drivers on Audience ...
Frankly I don't give a sh*t about how well it works with Audience, it does not work on my RB4011 which is a relatively modern and high-end device in the MikroTik line. It should be supported well.
"RB4011iGS+5HacQ2HnD-IN (WiFi model) is dual band, four chain unit with a supported data rate of up to 1733 Mbps in 5GHz. For legacy devices, the unit also has a dual chain 2GHz wireless card installed in miniPCI-e slot."
Ok. So the 2 GHz card is apparently changeable (I never opened this router). I think MikroTik should provide free replacement mini-PCI-e cards for users of the RB4011 who want the WiFi to be supported together with 5 GHz.
I concur your request, having a WifiWave2 upgrade option for RB4011 2.4Ghz would be great, mandatory.
Having such a high perf. product limited to old Wifi driver or 5Ghz only with Wifiwave 2 is a pitty...

Re: v7.1.1 is released!

Posted: Mon Jan 10, 2022 8:01 pm
by mkx
Wave2 driver won't work for 2.4GHz on RB4011 because hardware is not wave2 capable. The only possibility is what I wrote earlier: MT should enable co-existence of wave2 and legacy drivers.

Re: v7.1.1 is released!

Posted: Mon Jan 10, 2022 8:07 pm
by WeWiNet
Wave2 driver won't work for 2.4GHz on RB4011 because hardware is not wave2 capable. The only possibility is what I wrote earlier: MT should enable co-existence of wave2 and legacy drivers.
2.4Ghz Wifi in RB4011 is the R11E card, exact reference R11e-2HnD. I have device open in front of me.
Ideal would be to have a H/W upgrade via a 2x2 Qualcomm based Wifi card compatible with Qualcomm drivers/WifiWave2.

Re: v7.1.1 is released!

Posted: Mon Jan 10, 2022 8:20 pm
by mkx
If you find a mini-PCIe 2.4GHz wifi card based on QCA9984 chip, then you have a winner. This is chip driving the 4x4 MIMO 5GHz radio in Audience and per specs it supports 2.4GHz as well.
The card probably shouldn't be dual-band (selectable), ROS might be unable to select the band you want it to operate in.

Re: v7.1.1 is released!

Posted: Mon Jan 10, 2022 9:03 pm
by pe1chl
Yes that would be a solution, but I think it is not my task to find and purchase such a card, but rather it should be a replacement program via MikroTik.
I.e. they make a new R11e-2HnD-QCA card and supply one to everyone proving purchase of a RB4011iGS+5HacQ2HnD-IN.
(or of course they solve this issue in software in another way)

Re: v7.1.1 is released!

Posted: Mon Jan 10, 2022 11:53 pm
by fragtion
Yes that would be a solution, but I think it is not my task to find and purchase such a card, but rather it should be a replacement program via MikroTik.
I.e. they make a new R11e-2HnD-QCA card and supply one to everyone proving purchase of a RB4011iGS+5HacQ2HnD-IN.
(or of course they solve this issue in software in another way)
I tried loading wifiwave2 on a brand-new US (United States) model RB4011, and it was a total disaster. None of the bands for 5Ghz work because of channel/bandwidth limitations, and 2Ghz is obviously disabled. If they can't offer some kind of solution here there's probably going to be a lot of anger...to put it mildly

Re: v7.1.1 is released!

Posted: Tue Jan 11, 2022 1:22 pm
by llpax
sorry. 7.1.1 unusable: x3 cpu load
1. clear FW (only src-nat), no ip-lists.
ros7_emptyfw.jpg
2. and full config (filer + mange + nat) + Queue tree
ros7_3011.jpg

3 .VS ros6 full config (filer + mange + nat) + Queue tree
ros6_3011.jpg
Only one Im have a high cpu load rb3011 with ros7.1.1 ? (x3 compared with ros6)
one core processes IRQ full time! (100mbps Full Duplex static routing + queue)

Re: v7.1.1 is released!

Posted: Tue Jan 11, 2022 8:44 pm
by Maggiore81
@f1r3 I suggest you saving your config, reset the router to factory default and then reapply the config. Something is broken during upgrade.
I have some RB3011 upgraded to ROS7.1.1 and they works flawlessy.
About 100M traffic, and 120simple queues

Re: v7.1.1 is released!

Posted: Tue Jan 11, 2022 9:17 pm
by llpax
Hey, i have the same Problem with my RB3011.
The CPU is then at 75-85% and with ROS6 only at 20%
Yeep! Absolutely identical problem.
do you have 100 IRQ load for some one core?
/system resource cpu print

Re: v7.1.1 is released!

Posted: Tue Jan 11, 2022 9:26 pm
by llpax
@Maggiore81
reset the router to factory default and then reapply the config. Something is broken during upgrade.
im tested 7.1.1 and 7.1 with rb3011 after FULL RESET. Empty FW and mangle, with no queues, only 1 src-nat rule. And I get 50% load cpu with 100mbps full duplex.
Check end of previous page of this thread for my screens.
Ros 7 have problem with rb3011 and 4011. Its fact.
About 100M traffic, and 120simple queues
I doubt that it is. Or may be rb3011 have hardware differents(revisions), that cause this situation on some modification.

Re: v7.1.1 is released!

Posted: Tue Jan 11, 2022 10:41 pm
by mafiosa
With RB3011 pcc with 140+ 105mbps eats 86% cpu with zero firewall just a scr nat rule. Earlier it used to go maximum 35% . Mikrotik is so broken and they don't even acknowledge the problem. Same config on hap ac^2 I am getting maximum 27% CPU utilisation.

Re: v7.1.1 is released!

Posted: Tue Jan 11, 2022 10:52 pm
by llpax
Mikrotik is so broken and they don't even acknowledge the problem. Same config on hap ac^2 I am getting maximum 27% CPU utilisation.
Yes, its depends on hardware. hap ac2 with ros7.1.1 look better than 3011 or 4011... Exist some problem with drivers(hardware level layer) on some devices, I think. Obviously mikrotik not tested ros7 with all devices.

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 12:13 am
by leonardogyn
Just to register it here, as I have already submitted it as a support bug ticket (SUP-71205)

with 7.1.1, randomly and I could not find a way of reproducing it, a simple 'reboot' makes a ovpn-client interface dissapears. It's not 'it stops working', it's really GONE after the box returns online (and working absolutely fine). The ovpn-client interface, who was there and fully working 2 minutes earlier, when I issued the reboot connected to the box via that ovpn-client interface, is now gone. A /export shows absolutely no signs of it, neither logs from boot. It's simply gone without any traces. Firewall rules, based on that interface, all becames invalid.

Recreating the interface works just fine, no problem on that. But after facing it at least 5 times, I'm pretty sure this wasn't a one-time glitch and it's really happening.

I'm using TCP ovpn-client mode, hadn't migrated to UDP yet, the ovpn-client config is absolutely the same used from 6.4x.x era, no change on that after migrating to ROSv7

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 12:22 am
by pe1chl
with 7.1.1, randomly and I could not find a way of reproducing it, a simple 'reboot' makes a ovpn-client interface dissapears. It's not 'it stops working', it's really GONE
That may be just a special case of "under v7 sometimes config items disappear during a reboot".
When I reboot my RB4011 I lose the /ip ipsec identity records that are statically defined (the key of the IPsec tunnel). I have read other reports from people losing other things.
It appears there is some database with config information where updates are not always "committed" and get rolled back at a reboot.
When the router is running, a /export shows the relevant info. But when rebooted (either a reboot from the menu, or as part of an upgrade) it loses bits of config.
I always make a /export before I reboot and after the reboot or upgrade I do that again and diff them, to make sure I have not lost something without immediately noticing. Fortunately the router is otherwise very stable, I have not rebooted it since the upgrade to 7.1.1 which I did Dec 19 (when it was released).

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 12:32 am
by leonardogyn
with 7.1.1, randomly and I could not find a way of reproducing it, a simple 'reboot' makes a ovpn-client interface dissapears. It's not 'it stops working', it's really GONE
That may be just a special case of "under v7 sometimes config items disappear during a reboot".
[ .... ]
Fortunately the router is otherwise very stable, I have not rebooted it since the upgrade to 7.1.1 which I did Dec 19 (when it was released).
I'm being somehow forced to reboot it, at least once a week, because of a severe memory leak I have reported here ( viewtopic.php?t=180831&start=600#p897760 ) and also as SUP-68885. It was confirmed, on that support ticket, that the hotspot module (which I'm using) seems to be the problem, but no fix yet. So I need to reboot here and there.

About items dissapearing, i wasn't aware that it's also happening with other items. If that's happening on other places, maybe it's really related. Funny is that at least 4-5 times I faced it, only the ovpn-client dissapeared, nothing else. It's funny its somehow "fixed" on some specific items, like you're having problem with ipsec identify only. Very weird ...

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 12:42 am
by pe1chl
I'm being somehow forced to reboot it, at least once a week, because of a severe memory leak I have reported here ( viewtopic.php?t=180831&start=600#p897760 ) and also as SUP-68885. It was confirmed, on that support ticket, that the hotspot module (which I'm using) seems to be the problem, but no fix yet.
That could be, I am not using that and my memory usage remains between 100 and 130 MB (I cannot explain the variation, there are some highs and one low during that month of uptime that I cannot correlate to changes I made). In a 1GB RAM router that of course means most memory is unused.
(I have asked several times to implement the RAMdisk on all routers, not just those with 16MB flash, but that never happened. maybe some time the container feature comes back and can use some memory)

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 11:30 am
by llpax
@ f1r3
Yes! One Core have 100% IRQ load.
ros 7 have some problem with the drivers for 3011 hardware, obviously. It's a pity.

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 3:55 pm
by rpingar
INTEL X710 hardware (x86 and CHR with passthrough like advised in the posted link) interface queue seems not correctly associated to cpus:

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 3:58 pm
by glow
Is that the queue or all 64 enumerable SR-IOV ports?

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 3:59 pm
by rpingar
Is that the queue or all 64 enumerable SR-IOV ports?
yes

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 4:47 pm
by holvoetn
Is that the queue or all 64 enumerable SR-IOV ports?
yes
And that's an answer to which question ?

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 4:50 pm
by rpingar

yes
And that's an answer to which question ?
sorry, its the queue

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 5:34 pm
by lele
Hey, i have the same Problem with my RB3011. With ROS6 i have with src nat, 40 Firewall rules, some mangle and two queue rules 200Mbit/s from my ISP and with ROS7 only 150Mbit/s. The CPU is then at 75-85% and with ROS6 only at 20%
An RB3011 is my home's main router, doing bgp, ospf, dhcp, firewall, nat, mangle, but no queues. With ROS 7.1.1 cpu gets 50%+ under load but I get 950Mb/s bidirectional over the gigabit upstream.

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 5:47 pm
by jorgeflange
Recently Upgraded CCR1072-1G-8S+ (tile)

All seems to be ok, the packages now are all in one ?

The router is Zero Config, planned for a replacement of actually in production BGP Router CCR1036-8G-2S+ (tile).

I´m configuring manually again this new router.

Any other with real experience in CCR1072 as BGP with V7.1.1 ?
just_one_package_routeros_7_1_1.jpg

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 6:51 pm
by rpingar
Recently Upgraded CCR1072-1G-8S+ (tile)

All seems to be ok, the packages now are all in one ?

The router is Zero Config, planned for a replacement of actually in production BGP Router CCR1036-8G-2S+ (tile).

I´m configuring manually again this new router.

Any other with real experience in CCR1072 as BGP with V7.1.1 ?

just_one_package_routeros_7_1_1.jpg

in this scenario I could load on ccr1072 the v6.49.2 with the backup of CCR1036 and then manually adjust the ports.
Only in a secon moment go about the upgrade to v7.1.1, that now seems fine to convert all the configs.
regards

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 7:04 pm
by pe1chl
Never load a backup from another device! backups are only to be loaded into the same device where they were made.
When you want to migrate the config from another device, use /export and /import only.

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 8:13 pm
by llpax
An RB3011 is my home's main router, doing bgp, ospf, dhcp, firewall, nat, mangle, but no queues. With ROS 7.1.1 cpu gets 50%+ under load but I get 950Mb/s bidirectional over the gigabit upstream.
"RB3011" and "950Mb/s bidirectional"
nice joke :)))
m.b. comutation - not routing and nat-ing

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 9:15 pm
by vasilaos
I bought a RB5009 and I have to address some problems with RouterOS 7
1. There is no routin-table parameter in the ping option (scripts for monitoring wan's depend on that in order to monitor same host's with different routing mark and in order to make a nice working script)
2. Packet marks in mangle not working as expected for download and upload. All download falls in upload rule after a while. Using chain forward and in or out interface is wan interface. Selected packet no-mark to not mark packets twice. Some have sugested to use parent in queue tree the wan interface for upload and bridge inteface for download. This does not fit in my situation since multiple wan interfaces and multiple bridges in place so i have to use global as parent as it was in RouterOS 6. If you delete the rules in mangle and make them new it works for a while as expected then again download is marked all as upload. I think there might be a bug with the no-mark parameter in order to not mark packets twice. I have tried also with the option bypass set to no.
3. After installing an extra package and rebooting the device i have lost part of the configuration like bridge ports and scripts.
4. No extra package for ups and a test package that i downloaded didn't work on my device. It is showing 0 ports and no usbhid1 port to select on ups.
5. Port 1 which is 2.5G is not working with my provider modem even after removing 2.5g advertisement. I read even after negotiating 2.5G speed correctly the router is performing worse than with 1G speed.

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 9:19 pm
by irmankurnia
translation address or to-address in hotspot didn't work, i have client with address 172.16.0.2 with to-address 192.168.1.2 it's not work after upgrade from v6 to v7

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 9:42 pm
by winap
vasilaos:
1.And what speed do you have now? And what from your provider?
2. Do you have also problems like me with port 1 aftter few minutes, if the cable is unplug?
When I unplug the cable, after 5-15 minutes the LED orange shine, no POE on port 1..so there is no reason to shine (a little).

Re: v7.1.1 is released!

Posted: Wed Jan 12, 2022 9:45 pm
by infabo
7.1.1 is a great thing

Re: v7.1.1 is released!

Posted: Thu Jan 13, 2022 1:20 am
by fragtion
It's possible to create a NAT rule with an "arbitrary" chain name (neither of dstnat, input, output, srcnat). Possible bug? I'm not sure if this would lead to corruption or not, I haven't tested. I'm using Winbox 3.32.

Re: v7.1.1 is released!

Posted: Thu Jan 13, 2022 8:11 am
by mkx
Ability to create firewall chain (filter, NAT,...) is not a bug, it's a feature. One then needs to add rule with action=jump jump-target=<custom chain> in one of standard chains (input, output, forward for filter or whatever standard chains for NAT). After packet passes custom chain without triggering any of rukes, the evaluation returns to original chain where next rule (after action=jump) gets evaluated. This enables to create some convoluted designs which either allow nicer designs (e.g. same rules for input and forward chains without entering same rules twice) or better performance (only select packets get handed off to custom chain, other packets skip evaluating those rules which reduces processing time).

Re: v7.1.1 is released!

Posted: Thu Jan 13, 2022 2:00 pm
by kovaga
One out of 4 RB4011 is constantly rebooting after the upgrade to 7.1.1. The maximum uptime i saw was about 5 minutes.
Have disabled IPSEC and now it runs for 3.5 hrs already-
The funny thing is that another RB4011 is handling IPSEC connection just fine and has an uptime of 5 days with pretty much identical config. WTF!?

How can you call it a stable release while it has so many problems is beyond me.

Re: v7.1.1 is released!

Posted: Thu Jan 13, 2022 3:58 pm
by pe1chl
I have a 4011 with several IPsec sessions that has been running since the day 7.1.1 was released, but it only has "client" sessions and it seems the problems mainly exist in the "server" side.
(L2TP/IPsec server, for example)

Re: v7.1.1 is released!

Posted: Fri Jan 14, 2022 10:08 am
by kovaga
I have a 4011 with several IPsec sessions that has been running since the day 7.1.1 was released, but it only has "client" sessions and it seems the problems mainly exist in the "server" side.
(L2TP/IPsec server, for example)

Indeed, thats exactly my case. The client ipsec RB4011 with 7.1.1 was working fine connected to server RB4011 running 6.49 for a week or so. So my assumption was that it is a second minor release, so that so far worked fine, considered it safe to upgraded the server ipsec RB4011 and thats when the fun begun.

What I also noticed is that changes to the NTP client configuration on RB4011 with 7.1.1 may result in the spontaneous reboot shortly after.

Re: v7.1.1 is released!

Posted: Fri Jan 14, 2022 11:46 pm
by jimmer
I also notice a jump in CPU load from 6.49.x to 7.1.x on my RB3011 - fortunately it has the extra grunt to absorb it, so much so that fasttrack only saves about 10% CPU usage, one other thing ive noticed to is that the amount of RAM that is being used creeps up too.. at first boot its using 80Mb of RAM.. over the course of the last 23 days it has crept up to over 100Mb used, I see a similar pattern on a RB2011 running 7.1, my hAPac2's are similarly doing it with a small creep upward running 7.1.1 but they are only running as CAPsMAN controlled AP's and do nothing else. it does look like 7.1.x may have a memory leak of some sort.

Re: v7.1.1 is released!

Posted: Sat Jan 15, 2022 6:32 am
by yottabit
IPIP+IPSec tunnels are still broken if the default keepalive is left enabled. If you unset the keepalive, the tunnels come right up.

I am using ROS 7.1.1 on one end and ROS 6.49.2 on the other end.

I saw this reported in the beta and it is still not fixed.

Re: v7.1.1 is released!

Posted: Sun Jan 16, 2022 4:26 am
by mobyfab
Wanted to try sr-iov on chr but sadly the bnx2x drivers I need have not been included so it won't work.

Re: v7.1.1 is released!

Posted: Sun Jan 16, 2022 10:26 pm
by dll2003
I would recommend Mikrotik to create a wiki page containing all relevant changes when upgrading from V6 to v7. Not everybody has to ask the same questions all over again.
Even the small changes like "?" on CLI or the invertion of hide-sensitive to show-sensitive of export command.
Name the breaking changes and don't let people left in the dark.
I fully support this post.
So far, the lack of such information greatly slows down upgrade to ver.7.x.x.

Re: v7.1.1 is released!

Posted: Mon Jan 17, 2022 3:50 pm
by moiskey
Greetings. i lost compatibility with my old network card in mikroitk x86 (qlogic bmc5709c).
When configuring, it is simply with the status of the network cable disconnected (it does not change the status of running).
I hope it can be solved
Image

Re: v7.1.1 is released!

Posted: Mon Jan 17, 2022 11:23 pm
by Jotne
Not a quick fix, but if you do run RouterOS x86 you can change to RouterOS CHR (run on VmWare).

Re: v7.1.1 is released!

Posted: Tue Jan 18, 2022 3:42 am
by dtaht
1. it isn't stable and finished
2. it is likely not the optimal type for the usage scenarios hinted by the type name you would use such queues
Hmm.. I strongly disagree there. I've been part of the bufferbloat testers for over a decade now. fq_codel can be enabled for everything you'd like to try it on, and would probably already yield better results than the older current queue types. CAKE has also been widely tested and usually ends up better than sfq for wifi, even with CAKE defaults, but hey. If you mean to say you have not tested them with mikrotik hardware, I'd say go ahead and try. Try default to fq_codel for the internet port and run some tests. Switch all Flow Control to Off for that port (Interfaces > Ethernet > Tx and Rx Flow Control > Off), and maybe default to CAKE for wireless facing interface(s) and run some tests and compare.
fq_codel and cake work brilliantly with flow control on and without a shaper. why turn it off?

Re: v7.1.1 is released!

Posted: Tue Jan 18, 2022 3:48 am
by mducharme
fq_codel and cake work brilliantly with flow control on and without a shaper. why turn it off?
I am curious as to what you mean by "without a shaper" - do you mean setting fq_codel or cake as the interface queue? MikroTik abstracts away many of the parts of tc (which I haven't used on regular Linux, only MikroTik's abstraction of it), and so I do not have a complete understanding of what "without a shaper" means in this context.

Re: v7.1.1 is released!

Posted: Tue Jan 18, 2022 11:16 am
by kos
"/tool mac-server set allowed-interface-list=none" doesn't disable mac telnet until reboot.

Re: v7.1.1 is released!

Posted: Tue Jan 18, 2022 3:57 pm
by mktwifi
Hi All,
HTTPS within the HOTSPOT service doesn't work anymore.
Upgraded from 6.79.2 to 7.1.1 no changes in already working Hap Lite, now I get Handshake failure.
Downgraded and it works back again.

Re: v7.1.1 is released!

Posted: Tue Jan 18, 2022 4:17 pm
by holvoetn
Hi All,
HTTPS within the HOTSPOT service doesn't work anymore.
Upgraded from 6.79.2 to 7.1.1 no changes in already working Hap Lite, now I get Handshake failure.
Downgraded and it works back again.
Hotspot is an issue in general since ROS 7.

Re: v7.1.1 is released!

Posted: Tue Jan 18, 2022 4:59 pm
by maaathieu
I found something weird on my RB750Gr3 running v7.1.1:

when this rule is enabled:
 0    ;;; defconf: masquerade
      chain=srcnat action=masquerade out-interface-list=internet ipsec-policy=out,none
my pppoe client are stable.

as soon as I disable this rule, that I don't need, my ppp clients are disconnected after a few seconds, whith this message in the log:
terminating... - peer is not responding
If a re-enable this rule, everything goes back to normal.

Re: v7.1.1 is released!

Posted: Tue Jan 18, 2022 5:25 pm
by maaathieu
forget my previous message: a script couldn't run without this rule, then believed internet was down and disabled the lan port. my bad.

Re: v7.1.1 is released!

Posted: Tue Jan 18, 2022 6:10 pm
by mktwifi
Hi All,
HTTPS within the HOTSPOT service doesn't work anymore.
Upgraded from 6.79.2 to 7.1.1 no changes in already working Hap Lite, now I get Handshake failure.
Downgraded and it works back again.
Hotspot is an issue in general since ROS 7.
now it works back with 7.2 rc1.

Re: v7.1.1 is released!

Posted: Tue Jan 18, 2022 7:15 pm
by holvoetn
Other issues with cpu and accessibility preventing me to use that version.

Re: v7.1.1 is released!

Posted: Tue Jan 18, 2022 10:26 pm
by rodpp
I had a Wireguard problem here, maybe someone can check.

I configured an external paid VPN service. To change the contry the connection output will be, I have to change the endpoint field in the Peer configuration.

The problem is that after changing the endpoint address, the RouterOS ramdomly connect to the old and to the new value.

For example, the endpoint is configured as us.samplevpn.com. I change it to de.samplevpn.com. After that, RouterOS connect to us.samplevpn.com, disconnect and connect to de.samplevpn.com, disconnect and connect to us.samplevpn.com again, and so on...

Rebooting the router after the configuration change fix the problem.

Re: v7.1.1 is released!

Posted: Tue Jan 18, 2022 11:02 pm
by eworm
That's how Wireguard works... If a package with valid authentication from a peer is received the current endpoint address is updated automatically. Generally this is a good think as it help for a stable connection when peers are roaming.

I guess the reboot helps as it clears your tracked connections. I would suggest to try two things here:
  • Remove the old connection from tracking (/ip/firewall/connection/) or
  • Update the listen port on wireguard interface
Not tested, but either of both should fix the issue.

Re: v7.1.1 is released!

Posted: Wed Jan 19, 2022 1:01 pm
by andacb
Could someone please comment on the availability of "Dude Server" in 7.x.x versions?

Thank you,

Re: v7.1.1 is released!

Posted: Wed Jan 19, 2022 1:43 pm
by alfonzz
I have 7.1.1 on RB4011 with CAPS-man - here is some bug with bridge/capsman - any change with bridge (disable port, or change mode to rstp/none) cause almost frozen routerboard, reboot required.

Simple: create bridge with eth ports, create caps-man with datapath add to bridge, then add cap.
without capsman disable/enable bridge, change rtsp etc. works normally, but with bridge/port/dynamic cap interfaces = "death"

tested on latest RC 7 build and same result, on ROS6 - no problem
This configuration was applied on reseted device with v7 - so its no relevant to upg with config from v6 to v7.

Re: v7.1.1 is released!

Posted: Thu Jan 20, 2022 11:17 pm
by indy
sorry. 7.1.1 unusable: x3 cpu load
1. clear FW (only src-nat), no ip-lists.
ros7_emptyfw.jpg
2. and full config (filer + mange + nat) + Queue tree
ros7_3011.jpg

3 .VS ros6 full config (filer + mange + nat) + Queue tree
ros6_3011.jpg
Only one Im have a high cpu load rb3011 with ros7.1.1 ? (x3 compared with ros6)
one core processes IRQ full time! (100mbps Full Duplex static routing + queue)
I am also having massive performance problems with the RB3011 and RouterOS v7.
Other devices like HAP-AC2 or mAP do not suffer from this.

Not to be too negative though - this is a great release with many desirable features!

Re: v7.1.1 is released!

Posted: Fri Jan 21, 2022 12:17 am
by ivicask
I have 7.1.1 on RB4011 with CAPS-man - here is some bug with bridge/capsman - any change with bridge (disable port, or change mode to rstp/none) cause almost frozen routerboard, reboot required.

Simple: create bridge with eth ports, create caps-man with datapath add to bridge, then add cap.
without capsman disable/enable bridge, change rtsp etc. works normally, but with bridge/port/dynamic cap interfaces = "death"

tested on latest RC 7 build and same result, on ROS6 - no problem
This configuration was applied on reseted device with v7 - so its no relevant to upg with config from v6 to v7.
Noticed same bug with same setup.

Re: v7.1.1 is released!

Posted: Sat Jan 22, 2022 8:17 pm
by mducharme
That's not the question, I see it listed among the types. I'm curious why it's not being used..
I'm sure they will add defaults for those later. They probably do not consider it to be urgent at this time, and are focusing on fixing a lot of bugs instead of dealing with minor things like this.

Re: v7.1.1 is released!

Posted: Sun Jan 23, 2022 12:18 am
by leonardogyn
with 7.1.1, randomly and I could not find a way of reproducing it, a simple 'reboot' makes a ovpn-client interface dissapears. It's not 'it stops working', it's really GONE
That may be just a special case of "under v7 sometimes config items disappear during a reboot".
When I reboot my RB4011 I lose the /ip ipsec identity records that are statically defined (the key of the IPsec tunnel). I have read other reports from people losing other things.
......
.
I have uploaded a VERY strong case on 'dissapearing items on reboot' to Mikrotik (SUP-71205). I connected to a RB2011 running 7.1.1, generated a support file, issued a reboot, and mayhen was made: after the reboot, VLAN interfaces were gone, bridge interface was gone, ovpn-client interface was gone, etherNN interfaces that had custom names were all renamed back to etherNN default names (which breaks other things, like pppoe-client that was attached to ether1-EXTERNAL and became attached to no interface after reboot). I had to go physically to that RB to fix it, as the pppoe-client interface, now attached to nowhere, couldn't connect. While there, downgraded to 6.49.2. When locally on the box, on first access, I created a new support file and uploaded both (before and after reboot) to Mikrotik team, hope they can figure out what's happening, as I have absolutely no doubt it's a SEVERE bug, which can render boxes completly down and might require physical access to repair it, just like it happened to me.

Re: v7.1.1 is released!

Posted: Sun Jan 23, 2022 1:30 pm
by pe1chl
Yes it is a nasty issue but it could be easy to fix, maybe it is just a database thing where a transaction is used and it is not always properly committed. It could be a single line fix.

Re: v7.1.1 is released!

Posted: Sun Jan 23, 2022 3:02 pm
by fragtion
@leonardogyn Firstly well done for catching that rare gremlin with such a precise and correct methodical approach. Could I ask what prompted you to create the supout before the reboot? It's not like there's a need to create supouts randomly all the time. I'm guessing something went wrong?

I'm asking because, FWIW, personally I'm not fully convinced that the config loss issue is actually triggered on a reboot. I was once having an issue with a wireguard interface (I can't remember exactly what the issue was, but something wasn't saving or taking effect correctly..) So I rebooted, and then afterwards the wg interface was corrupt (I think private key changed to some AAAAAAAAAAAAAAz or something) along with other missing config post-reboot. It's like the database actually got corrupt while the router was still running, but still "appeared" fine in winbox (some kind of caching maybe?) - until reboot, then the real destruction became clear/apparent. If that's true, then your "VERY strong case" may not actually even reveal any culprit in spite of your thorough approach, which is even more haunting as to how elusive this bug is. I hope everyone is making regular backups until a definite fix for this appears in the changelogs

Re: v7.1.1 is released!

Posted: Sun Jan 23, 2022 5:58 pm
by leonardogyn
@leonardogyn Firstly well done for catching that rare gremlin with such a precise and correct methodical approach. Could I ask what prompted you to create the supout before the reboot? It's not like there's a need to create supouts randomly all the time. I'm guessing something went wrong?
.
My idea to also create the supout file before the reboot was to "prove" the config, that was there minutes before, simply vanished, and that all was simply caused by a reboot. While I can't say the reboot is the culprit, it's very clear to us that a single reboot (that shouldn't be a big deal) at least makes the problem presents itself. As I had experienced that a few times before, I was prepared to "prove" what's going on. Instead of showing the "after" config and reporting what's missed, I created both (before and after) and now even the own Dev Team can compare configs, side by side, and *see* what's missing. That was my idea of generating both files, before and after reboot, because I was already expecting something to dissapear and, with both, comparing them would be trivial and stronger than just believing in my words that something went wrong.

I really don't know if that'll help on the solving itself. But I expect that's hard to question it's really happening, given the mayhen caused by a simple reboot on a config that was fully working 2 minutes ago. For that, I really believe having both files was a success.

And at the meantime, I have downgraded the few boxes I had upgraded to 7.1.1 back to 6.49.2. There's really no way I can afford to "lose" connectivity to remote located boxes. I'll personally give ROS7 a few more months of maturing. There's no question the evolution from ROS6 to ROS7, but I can't afford taking this risk.

Re: v7.1.1 is released!

Posted: Mon Jan 24, 2022 6:27 am
by jdodge
I just upgraded a RB1100AHx4 to 7.1.1 -- on reconnection after reboot I see a warning that I don't have a key:
I thought it might be a weird 7.1.1 glitch -- the other two RB1100AHx4's I've upgraded were running 7.1 not 7.1.1 - so I tried a downgrade to 7.1 -- no luck, same message:

MikroTik RouterOS 7.1 (c) 1999-2021 https://www.mikrotik.com/


ROUTER HAS NO SOFTWARE KEY
----------------------------
You have 14h18m to configure the router to be remotely accessible,
and to enter the key by pasting it in a Telnet window or in Winbox.
Turn off the device to stop the timer.
See www.mikrotik.com/key for more details.

Current installation "software ID": C67I-7SHJ
Please press "Enter" to continue!


How do I fix this??!!

Re: v7.1.1 is released!

Posted: Mon Jan 24, 2022 7:31 am
by EvgenyPlekhanov
Good afternoon.
Has anyone tried using chr-7.1.1 in EVE-NG?
When I created a node, the sequence of mac-addresses of interfaces was mixed up. In version 6.48.6 everything is fine.

Re: v7.1.1 is released!

Posted: Mon Jan 24, 2022 10:49 am
by elbob2002
I just upgraded a RB1100AHx4 to 7.1.1 -- on reconnection after reboot I see a warning that I don't have a key:
I thought it might be a weird 7.1.1 glitch -- the other two RB1100AHx4's I've upgraded were running 7.1 not 7.1.1 - so I tried a downgrade to 7.1 -- no luck, same message:

MikroTik RouterOS 7.1 (c) 1999-2021 https://www.mikrotik.com/


ROUTER HAS NO SOFTWARE KEY
----------------------------
You have 14h18m to configure the router to be remotely accessible,
and to enter the key by pasting it in a Telnet window or in Winbox.
Turn off the device to stop the timer.
See www.mikrotik.com/key for more details.

Current installation "software ID": C67I-7SHJ
Please press "Enter" to continue!


How do I fix this??!!
Contact support straight away. You're not likely to get an answer to that here on the forum.

Re: v7.1.1 is released!

Posted: Mon Jan 24, 2022 2:29 pm
by leonardogyn
Mikrotik answer on the dissapering config items on reboot couldn't be more frustrating ... boxes were working for years, problems started (as reported) right after upgrading to ROS7. Others are also complaining of similar problems. But more than not acknowledging the problem, Mikrotik just wants me to reinstall the ROS7. As said, I have already downgraded, will wait ROS7 get really mature.
.
Hello,

Your described configuration loss and long creation of supout file, may be due to disk errors, Please save your configuration and then perform Netinstall on this device to fix disk errors, after that reconfigure and monitor, if same issue appears again let us know.

Best regards,

Re: v7.1.1 is released!

Posted: Mon Jan 24, 2022 2:32 pm
by pe1chl
Mikrotik answer on the dissapering config items couldn't be more frustrating ... boxes were working for years, problems started (as reported) right after upgrading to ROS7. Others are also complaining of similar problems. But more than not acknowledging the problem, Mikrotik just wants me to reinstall the ROS7 ...
I can already assure you that this will not help! If anything, my problem has STARTED after I did that (I reinstalled and cleared the config and imported it from a saved export, from that time I am losing the ipsec identities after every reboot)...

Re: v7.1.1 is released!

Posted: Mon Jan 24, 2022 2:50 pm
by leonardogyn
Mikrotik answer on the dissapering config items couldn't be more frustrating ... boxes were working for years, problems started (as reported) right after upgrading to ROS7. Others are also complaining of similar problems. But more than not acknowledging the problem, Mikrotik just wants me to reinstall the ROS7 ...
I can already assure you that this will not help! If anything, my problem has STARTED after I did that (I reinstalled and cleared the config and imported it from a saved export, from that time I am losing the ipsec identities after every reboot)...
.
At the end, I just lost my time trying to create supout files to help. Will just stay at ROS6 until Mikrotik dev team solves this SEVERE problems on ROS7.

Re: v7.1.1 is released!

Posted: Mon Jan 24, 2022 8:19 pm
by mafiosa


Only one Im have a high cpu load rb3011 with ros7.1.1 ? (x3 compared with ros6)
one core processes IRQ full time! (100mbps Full Duplex static routing + queue)
I am also having massive performance problems with the RB3011 and RouterOS v7.
Other devices like HAP-AC2 or mAP do not suffer from this.

Not to be too negative though - this is a great release with many desirable features!
Same issue. WIth PCC 140+105 mbps I am getting 86-90% utilization. v7.2 RC1 doesn't solve the problem.

Re: v7.1.1 is released!

Posted: Tue Jan 25, 2022 12:31 am
by k0st3k
dell r420 ros x86 7.1.1. After ac power problems lost some config bridge, vlan, dhcp....

Re: v7.1.1 is released!

Posted: Tue Jan 25, 2022 7:24 am
by kevinlukas
I am using router hEX - 750 GR3, when I upgrade RouterOS version v7.1.1 (stable) or RouterOS version v7.2rc1 (testing), error occurs as shown below.

Image

Image

Bandwidth test is not full speed 1 Gbps on total Tx/Rx Current, even when I am using bonding ethers with command "send" or "both" , but before that I use RouterOS version 6.48.6 (long-term) this is not the case.

I have tried to reset configuration (back to default) and reconfigure step by step, but the situation is still not fixed.

Is RouterOS v7 not good support for old model routers, specifically architectures: MMIPS, MIPSBE ?!!

Thanks.

Re: v7.1.1 is released!

Posted: Tue Jan 25, 2022 10:47 am
by osc86
I think I just got this "ROUTER HAS NO SOFTWARE KEY" problem on an RB941-2nD. Before the device went offline, it showed 7.1.1 (Level 0) via snmp. I have to check tomorrow.

Re: v7.1.1 is released!

Posted: Tue Jan 25, 2022 1:40 pm
by mafiosa
I am really pissed with Mikrotik, opened a ticket on 12th Jan regarding high CPU utilization on RB3011. Sumitted supout.rif and all relevant info asked by them, no reply on the ticket till today.
https://help.mikrotik.com/servicedesk/s ... /SUP-71297

Re: v7.1.1 is released!

Posted: Tue Jan 25, 2022 1:53 pm
by mkx
I am really pissed with Mikrotik, ...
If this pisses you off so much, why don't you downgrade your very important router to 6.49 and wait for v7 to stabilise enough to meet your operational demands?

Re: v7.1.1 is released!

Posted: Tue Jan 25, 2022 3:53 pm
by mafiosa
I am really pissed with Mikrotik, ...
If this pisses you off so much, why don't you downgrade your very important router to 6.49 and wait for v7 to stabilise enough to meet your operational demands?
Already downgraded but that doesn't justify them not answering the ticket.

Re: v7.1.1 is released!

Posted: Tue Jan 25, 2022 4:27 pm
by sbhokray
hi!
after using the CHR for a while on hyper-v, I have upgraded to the all new CHR7.1 stable.
so far so good. the only thing am missing is, I am unable to uninstall functionality's which i do not use.
I tried uninstalling wireless, hotspot IPV6 but there is no option to do this under the packages in system menu.
am I finding them in a wrong menu? or Mikrotik 7.1 is made to stay with all this options.

Re: v7.1.1 is released!

Posted: Tue Jan 25, 2022 4:36 pm
by pe1chl
Yes, unfortunately this possibility was removed by putting the entire RouterOS except some really niche functions in one big package.
I agree that was good for some low-level functions like dhcp,ppp,security,ipv6 etc that have lots of inter-dependecies, but frankly I think wireless and hotspot do not belong there.
Nothing we are going to change about that...

Re: v7.1.1 is released!

Posted: Tue Jan 25, 2022 5:52 pm
by avaz
Forgive me for my english

I upgraded my CCR1036 to version 7.1.1 , but I noticed an item in openvpn

In ppp active sessions , I see two sessions in winbox for the same user but I can't see these sessions in the command line

Is this a winbox or os router bug?

Vonage SIP Problems

Posted: Tue Jan 25, 2022 6:16 pm
by sterod
I am writing to advise of a problem I encountered with a CCR1009-8G-1S-1S+ that was upgraded to v7.1.1. I received a call from the client that their Vonage VOIP service was not working. At first I thought it was a problem with the Vonage VTA adaptor and I proceeded to replace it with a spare. After doing so, the problem remained and the two numbers associated with the Vonage service would not register (could not be provisioned). I tried a variety of things such as disabling the SIP helper, adding NAT rules for TCP/UDP 5060 and nothing worked. I then took the VTA adaptor to a different location on another network and found that it worked immediately. This was very odd. I took the adaptor back to the office and plugged it into the CCR and again, the numbers would not register. After tearing my hair out with a very unhelpful Vonage support person, I proceeded to downgrade the CCR back to 6.49.2 and on the subsequent reboot the Vonage VTA immediately started working. I have no explanation for this, but there must be some issue with 7.1.1 and SIP with the CCR1009.

EDIT: My problem is the same as that of post #281 as I also have a WAN over PPPoE VLAN connection on this CCR.

Re: v7.1.1 is released!

Posted: Tue Jan 25, 2022 6:17 pm
by RohanAJoshi
I am really pissed with Mikrotik, ...
If this pisses you off so much, why don't you downgrade your very important router to 6.49 and wait for v7 to stabilise enough to meet your operational demands?
Stabilize ?
Stable version = Stabilized Version, right ?
I am with ccr2004 with random reboot issues from nearly 1.5yrs, no fix till now, there is whole topic going on.
Support asked spout, I gave, nothing in that spout, then support asked spout via serial cable with watchdog disabled, which means router will not reboot, i need manual reboot, router was in remote location, I cant do that., but others did and support find nothing in it. 1.5 yrs, same situation.

They released half baked 7.1.1 as stable 7.1.1, which is not stable at all. its not even alpha capable, forgot beta release.
7.1.1 is rebooting for all ccr1009 users, there are lot of complaints about cpu going nuts.
So, its obvious that users will get pissed.

Re: v7.1.1 is released!

Posted: Tue Jan 25, 2022 6:28 pm
by mkx
If this pisses you off so much, why don't you downgrade your very important router to 6.49 and wait for v7 to stabilise enough to meet your operational demands?
Stabilize ?
Stable version = Stabilized Version, right ?

Wrong. If you can't afford downtime or are not willing to chase bugs, then

  1. closely follow discussions on this vivid forum to assess general opinion on stability of a particular version on your particular hardware
  2. create lab setup where you can test and verify both upgrade procedure and fitness for your particular setup and if not satisfied, go back to #1

Nothing that software producer states about some particular release shouldn't make you skip any of steps above, it can only intrigue you into looking at some particular release more closely.

Re: Vonage SIP Problems

Posted: Tue Jan 25, 2022 8:16 pm
by pe1chl
I am writing to advise of a problem I encountered with a CCR1009-8G-1S-1S+ that was upgraded to v7.1.1.
Why did you upgrade it? The issue you describe is known, and there should be no reason to upgrade a CCR router to 7.1.1 unless maybe you want higher
performance BGP and are working in an experimental setting. Certainly not on a customer site!

Re: Vonage SIP Problems

Posted: Tue Jan 25, 2022 8:49 pm
by sterod
I am writing to advise of a problem I encountered with a CCR1009-8G-1S-1S+ that was upgraded to v7.1.1.
Why did you upgrade it? The issue you describe is known, and there should be no reason to upgrade a CCR router to 7.1.1 unless maybe you want higher
performance BGP and are working in an experimental setting. Certainly not on a customer site!
I haven't had issues with 7.1.1 on any other my client sites so I decided to give it a try. would you be kind enough to tell me where this problem is known so I can read about it please?

Re: v7.1.1 is released!

Posted: Tue Jan 25, 2022 9:06 pm
by pe1chl
E.g. message #281 in this topic, but also other places where issues with SIP are discussed. it is likely related to DSCP. I have issues with DSCP i.c.w. PPPoE as well.

Re: v7.1.1 is released!

Posted: Wed Jan 26, 2022 10:47 am
by draid
Hello guys,

Recently I've found that all of the information for the SFP interface is missing on v7.1.1. At the moment there is no information listed at all, something that was present in v6.x.x. Currently using Hex S and S-85DLC05DI module. Anyone having the same problem on v7?
Screenshot 2022-01-26 104432.jpg

Re: v7.1.1 is released!

Posted: Wed Jan 26, 2022 12:48 pm
by Ullinator
Hello guys,

Recently I've found that all of the information for the SFP interface is missing on v7.1.1. At the moment there is no information listed at all, something that was present in v6.x.x. Currently using Hex S and S-85DLC05DI module. Anyone having the same problem on v7?

Screenshot 2022-01-26 104432.jpg
It´s not a general bug in V7.1.1, because in my ARM and MIBSBE devices all SFP+ interfaces reports correctly.
Unfortunatly I have no MMIPS device running with SFP modules to verify.
hc_097.jpg

Re: v7.1.1 is released!

Posted: Wed Jan 26, 2022 1:27 pm
by tigro11
Hi Guys, I noticed that the OpenVPN in UDP sessions remain active even if I am disconnected.
Check if possible.
Thank you
Valerio

Ciao Ragazzi, ho notato che la OpenVPN in UDP, le sessioni rimangono attive anche se mi sono scollegato.
Se possibile verificare.
Grazie
Valerio

Re: v7.1.1 is released!

Posted: Wed Jan 26, 2022 6:08 pm
by draid
Hello guys,

Recently I've found that all of the information for the SFP interface is missing on v7.1.1. At the moment there is no information listed at all, something that was present in v6.x.x. Currently using Hex S and S-85DLC05DI module. Anyone having the same problem on v7?
It´s not a general bug in V7.1.1, because in my ARM and MIBSBE devices all SFP+ interfaces reports correctly.
Unfortunatly I have no MMIPS device running with SFP modules to verify.
It seems to be working for you. Interesting enough it was working on v6.x.x without any problems. I've tested it now with another SFP module and it seems to not be from it. With both modules the problems remains. Don't have a SM module to test but I'd say that this is most likely coming from the v7 and as you mentioned it isn't a general thing for all SFP modules and architectures. The connection is working fine but no information. I'm using OM2 cable.

Re: v7.1.1 is released!

Posted: Wed Jan 26, 2022 6:47 pm
by BitHaulers
The number of problems I've solved by NetInstalling , or NetInstalling and THEN factory resetting and importing my config is staggering. I don't care if the file system check says the install is good, there's some NVRAM corruption going on that can't be measured/detected, but NetInstall fixes the issue 99% of the time, and factory reset after a NetInstall and upgrading the bootloader solves the rest of the problems. If that SOP (standard operating procedure) doesn't fix it, and a downgrade with NetInstall doesn't fix it, I just replace the whole device. If I can't get a board to NetInstall, but other ones do, I replace the equipment. Something is wrong with the bootloader. It will act up in the future.

Before you deploy any Tik in an operational environment, I think you should NetInstall it, upgrade the bootloader, and factory reset it. Straight out of the box, even. I've gotten "new" things from suppliers that were obvious returns once I logged in.

NetInstall has a history of being flaky, but I think I've found a solution. Use a cheap USB to ethernet adapter with a Realtek chipset. Now, NetInstall works every time. There's some issue with Windows 10+ and integrated Intel NICs. It works until it doesn't, and then it never works again. Plug in the USB adapter, now it works every time. Go figure. Didn't have these problems with Windows 7, but we obviously can't keep that around for NetInstall.

So if I "fix" a problem with NetInstall, and it happens again, and I fix it a second time with NetInstall, I replace the board, because I suspect bad NVRAM. That's cheaper than the labor to chase the bug down. This solves almost all of my problems to date.

I read most of these threads, and I think every one of us should be NetInstalling and importing your existing config afterwards when trying out these new releases, before you post, just to take that variable out of the equation. I'd put money on that being a reason Mikrotik can't reproduce a lot of these problems in the lab. I bet they NetInstall all the time to start with a clean slate, and you guys haven't reformatted that NVRAM...ever, and still expect it to all just "work".

Re: v7.1.1 is released!

Posted: Wed Jan 26, 2022 9:55 pm
by draid
A quick update on the problem with the missing information from the SFP module on my Hex S. I've tried some things in order to resolve the problem but nothing seems to be working, tried even the v7.2 but without any success. Few minutes ago I downgraded back to 6.42.2 and surprise everything on the SFP worked as expected. Now I'm more than convinced that this is a problem with v7 on Hex S or MMIPS in general.

Re: v7.1.1 is released!

Posted: Fri Jan 28, 2022 12:17 am
by avaz
Hello everyone

I encountered another strange event after upgrading to router OS to 7.1 ,7.1.1 or 7+.

On site-to-site ipsec tunnels ( with 3des + sha1 ) and CISCO routers I noticed an error in the cisco log "%CRYPTO-4-RECVD_PKT_MAC_ERR:
decrypt:" , from what I found 3DES encryption presents some divergence in version 7.1 for this case, when rolling back to 6.49, everything works again

Re: v7.1.1 is released!

Posted: Fri Jan 28, 2022 2:45 am
by maxb
Router hexS, upgrade from 6.49.2 to 7.1.1
Connection WAN PPPoE over VLAN

After the update, SIP connections to external servers are no longer working.
Before mikrotik I had the same problem with same connection but a different gateway, registration of SIP clients was impossible.

After downgrade to version 6.49.2 everything works again.


Stefano
I'm experiencing the same issues

Re: v7.1.1 is released!

Posted: Fri Jan 28, 2022 11:39 am
by pe1chl
We are all experiencing the same issues. No need to keep reporting that.

Re: v7.1.1 is released!

Posted: Mon Jan 31, 2022 6:44 am
by prawira
hello all,

i manage to make a small lab for OSPF within ros v7.1.1 while read the documentation on https://help.mikrotik.com/docs/pages/vi ... eId=328218
the above doc said :
Notes
OSPF protocol supports two types of metrics:
type1 - OSPF metric is the sum of the internal OSPF cost and the external route cost
type2 - OSPF metric is equal only to the external route cost.

question: how to set the ospf metric as type1 or type2 for the interface under ros v7.1.1 ?

thank you

Re: v7.1.1 is released! ( RB4011iGS Unusable )

Posted: Mon Jan 31, 2022 10:14 am
by hifigraz
Before the upgrade, the RB4011iGS's (I've got three of them) were working perfectly stable. Now they are completely rubbish.
RX-Package drops though they are not loaded at all. And render completely broken after a couple of days. Only a reboot helps.
Support is informed, but no answer by now.

Consider not upgrading to ROS 7 if you are using a RB4011iGS ...

Re: v7.1.1 is released!

Posted: Mon Jan 31, 2022 10:53 am
by pe1chl
I have been running my RB4011 on 7.1.1 for more than a month without issue. Now I have upgraded to 7.2rc3 (7.2rc1 was rubbish here).
The RX drops appear to be related to reading the device temperature. You may have SNMP monitoring that regularly reads the temperature.
It appears that during each temperature reading there is some chance of RX drops (maybe it disables interrupts for too long).

Re: v7.1.1 is released!

Posted: Mon Jan 31, 2022 3:25 pm
by clambert
I have been running my RB4011 on 7.1.1 for more than a month without issue. Now I have upgraded to 7.2rc3 (7.2rc1 was rubbish here).
The RX drops appear to be related to reading the device temperature. You may have SNMP monitoring that regularly reads the temperature.
It appears that during each temperature reading there is some chance of RX drops (maybe it disables interrupts for too long).

I have experienced the same behavior on the RB1100AHx4 on RouterOS v6 with temperature readings via SNMP queries.

Re: v7.1.1 is released!

Posted: Mon Jan 31, 2022 3:46 pm
by jbl42
Consider not upgrading to ROS 7 if you are using a RB4011iGS ...
It depends.
For serious routing and working IPv6 support, RB4011 better stays on 6.49.2

For more home/small office/lab oriented setups (some VLAN/bridging, some queues for VOIP, some firewalling, outgoing srcNAT, no IPv6) RB4011 works well with ROS 7.1.1 and brings nice features like bridge VLAN filter hw offloading, cake/fq_codel queues and Wireguard

Re: v7.1.1 is released!

Posted: Wed Feb 02, 2022 4:37 pm
by berdux
Not sure if its a bug or not but after I upgraded from 7.1 to 7.1.1 some (70%) of my DHCP static lease entries got dropped (RB5009UG+S+)
In my case it has happened twice now, but not right after the upgrade.
Just at two random times in the last month about half of my dhcp leases got lost, different ones each time (hAP ac^2) (model: RBD52G-5HacD2HnD)

Is there anything on this?

Re: v7.1.1 is released!

Posted: Wed Feb 02, 2022 5:31 pm
by pe1chl
Just at two random times in the last month about half of my dhcp leases got lost, different ones each time (hAP ac^2) (model: RBD52G-5HacD2HnD)

Is there anything on this?
Did you reboot at that time? There is lots of mention about random pieces of configuration going missing at a reboot in 7.1 and 7.1.1
Hopefully it is now fixed in 7.2rc3 but I have not verified it yet.

Re: v7.1.1 is released!

Posted: Wed Feb 02, 2022 8:46 pm
by berdux
Did you reboot at that time? There is lots of mention about random pieces of configuration going missing at a reboot in 7.1 and 7.1.1
Hopefully it is now fixed in 7.2rc3 but I have not verified it yet.
Hmmm, both times could have been after a reboot. It reboots every morning at 4:30 am..
I will disable that for now

Re: v7.1.1 is released!

Posted: Thu Feb 03, 2022 8:21 am
by vecernik87
Somehow, ARP pings don't seem to work... Tested on 7.1.1, hAP ac2, tested both VLAN as well as normal bridge interface. Another router with v6 (and almost same config) works without issue.
winbox_SR6SkIwePJ.png
Can anyone confirm? (just to be clear, interface is correct. If the interface was wrong, it would simply timeout but notice the status - "ping failed")

Re: v7.1.1 is released!

Posted: Thu Feb 03, 2022 8:40 am
by Sob
Confirmed with CHR 7.1.1, same "ping failed" for ARP pings.

Re: v7.1.1 is released!

Posted: Thu Feb 03, 2022 11:07 am
by eworm
Yes, also confirmed by Mikrotik in SUP-69080 ("ARP ping fails (v7)").

Re: v7.1.1 is released!

Posted: Thu Feb 03, 2022 11:43 am
by stormeporm
So ive updated my CCR1009-8G-1S-1S+ it worked until I updated the routerboard firmware.
Now its in a bootloop.

I had v7RC4 running on it as a test and it was working fine.]

A fresh netinstall fixed it. But it does not make me very eager to use this thing in production

Re: v7.1.1 is released!

Posted: Thu Feb 03, 2022 2:50 pm
by harry66
Something weird in proxy access rules. Winbox 3.32 and Console config show different.
RB5009/ROS7.1.1 here
Bildschirmfoto zu 2022-02-03 13-49-40.png

Re: v7.1.1 is released!

Posted: Thu Feb 03, 2022 3:45 pm
by Elisium91
I got Kernel panic/reboot on CCR1036-12G-4S after upraded to v7.1.1, so back to v6 where I had over 1 year of uptime..
Too bad because I liked bgp on v7, so I'm waiting for the next Stable.
Same situation. Kernel failure \ reboot. CCR1016-12G ROS v7.1.1\v7.2rc3. Running OSPF\LDP\MPLS (no BGP enable)

Router crashed after 1-2 min when i have enabled any VPLS connection. When i disable VPLS links - router works well =\

Re: v7.1.1 is released!

Posted: Fri Feb 04, 2022 12:53 pm
by bda
ROS7.1.1 causes CCR1009-7G-1C-1S+ to crash with one ovpn session!
Any suggestions?

Re: v7.1.1 is released!

Posted: Fri Feb 04, 2022 1:15 pm
by pe1chl
ROS7.1.1 causes CCR1009-7G-1C-1S+ to crash with one ovpn session!
Any suggestions?
1. try 7.2rc3
2. when not fixed, install 6.49.2

Re: v7.1.1 is released!

Posted: Fri Feb 04, 2022 10:08 pm
by bda
ROS7.1.1 causes CCR1009-7G-1C-1S+ to crash with one ovpn session!
Any suggestions?
1. try 7.2rc3
2. when not fixed, install 6.49.2
Hi, thanx but 6.49.2 has no ovpn-udp, like all 6.x

Re: v7.1.1 is released!

Posted: Sat Feb 05, 2022 11:55 am
by pe1chl
That is true, but 7.x is not in a state with usable OpenVPN. So for now, the only way to have OpenVPN is to run it on a separate device (server).

Re: v7.1.1 is released!

Posted: Sat Feb 05, 2022 8:35 pm
by dimacbz
v7.1.1 RB5009 Link SFP+ <---> any device with SFP (SFP+) packet loss 35-50%, regardless of the load. Tested on two RB5009.
v6.49.2 CRS328 Link SFP+ <---> any device with SFP (SFP+) packet loss 0%, regardless of the load.

Re: v7.1.1 is released!

Posted: Sun Feb 06, 2022 10:34 am
by prawira
hi all,

i did the OSPF lab with 3 hap-mini routers with ros v7.1.1 today.
what i found are :
+ on /ip route table, no more pref-source that ussualy came from the ip addresses added on /ip address. so, what is the pref-source for ?
+ export not working, wait almost forever and the result is nothing
+ Make supout.rif stop at 85%

is it the bug for hap-mini only or for v7.1.1 or hap-mini too small for v7.1.1 ?

EDITED: i try to add the mpls config on it and end-up with error
[admin@MikroTik] > /ip/address/print
Columns: ADDRESS, NETWORK, INTERFACE
# ADDRESS         NETWORK      INTERFACE
0 172.16.1.2/32   172.16.1.2   loopback 
1 10.1.1.2/30     10.1.1.0     ether1   
2 192.168.2.1/29  192.168.2.0  ether2   
3 10.1.2.1/30     10.1.2.0     ether3   
[admin@MikroTik] > /mpls/ldp/add lsr-id=172.16.1.2
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)
P

Re: v7.1.1 is released!

Posted: Sun Feb 06, 2022 12:19 pm
by pe1chl
pref-source is the source address that the router uses when making outbound connections to an address in that range.
when you have a number of routers that are interconnected using link subnets, it may be a good idea to have "the main router address" (e.g. the router address on the LAN) as the pref-source everywhere.

Re: v7.1.1 is released!

Posted: Mon Feb 07, 2022 4:14 am
by prawira
one of our RB1100AHx2 having boot-loop after upgrade to v7.1.1 with error message kernel failure.
unfortunatelly the ether13 port has been maffunction and no chance to do netinstall.
how to get the working firmware file for RB1100AHx2 ? AFAIK the file with extention .fwf

tia

Re: v7.1.1 is released!

Posted: Mon Feb 07, 2022 11:12 am
by mkx
Download NPK file, open it with 7z ... fwf files are in /etc directory. Make sure you select file with name exactly matching firmware-type shown by /systen/routerboard/print.

Copy file to CCR and it should be shown as available for upgrading routerboot.

Edit: just hit me: with device in boot-loop the above procedure will not work. I hope there's option to upgrade routerboot via serial port ...

Re: v7.1.1 is released!

Posted: Mon Feb 07, 2022 12:31 pm
by pe1chl
Users should learn to partition their device prior to upgrading, when they have a router like RB1100AHx2 where that is a possibility.

Re: v7.1.1 is released!

Posted: Mon Feb 07, 2022 3:31 pm
by k0st3k
vlan inside eoiptunnel inside openvpn. When adding to bridge eoip couses system reboot ;) Works fine in 6.xx........x86

Re: v7.1.1 is released!

Posted: Mon Feb 07, 2022 10:52 pm
by dmq
The WAVE2 driver works SO MUCH BETTER on the 5Ghz radio... why would you want to handicap the radio performance with the old drivers?
Because the stupid WAVE2 driver does not support the 2.4 GHz radio and cannot work together with the old drivers for 2.4 GHz.
No idea why that was ever implemented that way... it is ridiculous. A WiFi driver for a commercially sold 2.4+5GHz device that supports only the 5 GHz radio and makes use of the 2.4 GHz radio impossible.
I just ordered a RB4011iGS+5HacQ2HnD-IN. Can someone tell me that it will be ever possible to use the new WifiWave2 without deactivating the 2.4 GHz radio (legacy driver in parallel)? This would be really sad if not possible. Maybe it is on the roadmap? Thanks in advance.

Re: v7.1.1 is released!

Posted: Tue Feb 08, 2022 10:12 pm
by ahmedelbarbary
Updated from last v6 release, i can't ping in routing table in Tools ping this option is removed ?

Re: v7.1.1 is released!

Posted: Wed Feb 09, 2022 12:52 pm
by jimmer
I am not sure if its a 7.1.0 or a 7.1.1 issue, I remember it showing in 6.49.x but I am not seeing any client/station association, disassociation and signal strength logging at all from either of my CAP's or the CAPsMAN controller, ive checked the logging, I am seeing log entries from all devices, e.g. winbox login, logging changes ete, no station information at all.

I have a PC that is dropping in and out and I cant see what reason it is disassociating for anywhere in the logs.

Anyone else seeing the same problem?

I am logging to a syslog destination, firewall, winbox login messages - everything else is appearing in the logs except for CAPsMAN related (dis)associations

Kind Regards,
Jim.

Re: v7.1.1 is released!

Posted: Thu Feb 10, 2022 3:21 am
by mducharme
+ export not working, wait almost forever and the result is nothing
+ Make supout.rif stop at 85%
This is fixed in 7.2rc2.

Re: v7.1.1 is released!

Posted: Thu Feb 10, 2022 8:20 am
by Jotne
This is fixed in 7.2rc2.
Still very long export time on devices with little CPU in 7.2rc2 (compare to 6.x)
viewtopic.php?p=908897#p908897

Re: v7.1.1 is released!

Posted: Thu Feb 10, 2022 10:28 am
by emils
New version v7.1.2 has been released:

viewtopic.php?t=183109