v7.8 [stable] is released!

Mon Feb 27, 2023 10:52 am

RouterOS version 7.8 has been released in the "v7 stable" 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.8 (2023-Feb-24 11:03):

!) storage - added new "rose-storage" package support for extended disk management and monitoring functionality (ARM, ARM64, Tile and x86) (CLI only);
*) bgp - fixed setting of "default-prepend" parameter;
*) bridge - fixed adding disabled MSTI;
*) bridge - fixed DHCP packet flow when using DHCP snooping, HW offloading and "use-ip-firewall";
*) bridge - fixed possible DHCP packet corruption when using DHCP snooping;
*) bridge - fixed PVID warning typo;
*) bridge - improved HW offloading logic;
*) certificate - fixed export of a certificate when the last line of the certificate is exactly 64 bytes long;
*) certificate - fixed PBES2 certificate import;
*) certificate - improved certificate management, signing and storing processes;
*) certificate - improved multiple certificate import process;
*) conntrack - improved system stability when changing connection tracking state;
*) conntrack - improved system stability when PPTP helper is used;
*) console - added "as-string" parameter to the ":execute" command;
*) container - added authentication option for registry (CLI only);
*) container - fixed ".type" file ownership;
*) container - fixed file ownership after system upgrade for containers running on internal disk;
*) container - fixed multiple container automatic startup on boot;
*) dhcpv4-client - send DHCPv4 unicast requests to DHCPv4 relay, instead of server when it is being used;
*) disk - limit maximum TMPFS size;
*) dns - added configurable DoH concurrent query limitation parameters;
*) dns - do not cache results from ":resolve" command with specific server;
*) dns - fixed CNAME reading from the cache;
*) dns - limited "DoH max concurrent queries reached" logging messages to once per minute;
*) dns - respond with "NOERROR" to DNS requests for static domain names when appropriate type record is not configured or found on upstream server;
*) firewall - fixed bridge priority target;
*) firewall - fixed DSCP priority target for IPv6 Mangle;
*) firewall - fixed netmap range maximum address calculation for IPv6 NAT;
*) graphing - fixed hiding of target queues when "allow-target" is disabled;
*) graphing - fixed sorting of interface and queue graphs;
*) graphing - properly handle disabled and static-binding interface graphs;
*) graphing - removed "move" command for graphing rules;
*) health - fixed "temperature" and "power-consumption" readings for RB1100AHx4;
*) hotspot - fixed setting of "address" parameter for IP binding;
*) hotspot - restore cookie timeout on reboot;
*) ike2 - added support for "address", "key-id" and "dn" for Remote ID matching (CLI only);
*) ike2 - fixed active SA flush on responder after an unsuccessful peer connection attempt;
*) ipsec - added support for "Framed-Route" RADIUS attribute support;
*) ipsec - do not match incoming IKE requests by unresolved DNS name peers;
*) ipsec - fixed peer matcher for incoming connection with unresolved DNS;
*) ipv6 - added "pref64" option configuration for RA;
*) ipv6 - improved handling of "advertise" IPv6 address status changes;
*) ipv6 - limited "hop-limit" parameter value range to 255;
*) ipv6 - made distributed DNS lifetime RFC8106 compliant;
*) l3hw - added destination MAC address check for offloaded FastTrack connections;
*) led - fixed signal reading for KNOT device;
*) leds - always require to set interface name when setting "modem-signal" indication;
*) lte - added AT support for Telit LE910C4 in MBIM mode;
*) lte - fixed APN setting usage on initial connection attempt for AT based Quectel and Neoway modems;
*) lte - fixed automatic antenna selection on Chateau LTE12/LTE18;
*) lte - fixed dialing for Fibocom L850-GL module;
*) lte - fixed displaying of "subscriber-number";
*) lte - fixed possible memory leak when using passthrough mode on Chateau 5G;
*) lte - improved AT port matching for SIMCom, Huawei, WeLink, Cinterion, BandLuxe and Sierra modems;
*) lte - improved modem detection speed in lower mini-PCIe slot on LtAP;
*) lte - improved stability for R11e-LTE6, skip connection reset on first EEMGINFO command timeout;
*) lte - LtAP improved modem detection in lower mini-PCie slot ("/system routerboard upgrade" required);
*) lte - parse USSD even if encoding is unsupported;
*) mpls - fixed handling of more than 9 VRF's;
*) mpls - fixed LDP listen socket creation before IPv6 address is ready for use;
*) mpls - improved stability when neighboring router reboots;
*) ospf - fixed "ospf-type" parameter for OSPFv3 routes;
*) ospf - fixed simple auth for OSPFv3;
*) ovpn - added AES-GCM and multicore encryption support;
*) ovpn - improved server stability;
*) ovpn - improved TLS-related error logging;
*) pimsm - improved system stability;
*) poe - added LLDP power management support for 802.3at PSE;
*) poe - properly turn off power when link not detected on hAP ax2 and hAP ax3;
*) port - fixed modem channel number on KNOT;
*) pppoe - fixed PPPoE client scan showing only one server;
*) resource - show filesystem related statistics on CCR2004;
*) route - fixed IPv6 default route presence when received from RA;
*) route - fixed printing of routing table's "count-only" parameter;
*) route - show hoplimit and MTU properties under the "/routing route" menu for SLAAC routes;
*) routerboot - fixed format storage for RBM33G device ("/system routerboard upgrade" required);
*) routerboot - fixed protected routerboot for RBM33G device ("/system routerboard upgrade" required);
*) sfp - fixed false link detection with S+RJ10 on RB5009;
*) sfp - fixed reading of SFP EEPROM on single SFP port devices;
*) sfp - improved optical modules SFP compatibility on CCR2004-16G-2S+, CCR2004-1G-12S+2XS, CCR2116-12G-4S+ devices;
*) sms - improved reporting of SMS sending errors;
*) sms - log USSD response when USSD is sent over MBIM;
*) sniffer - added additional filtering parameters;
*) snmp - do not show identity in LLDP when branding is used with hide SNMP data;
*) snmp - fixed handling of disabled routes;
*) snmp - fixed reporting of total number of routes counter;
*) ssh - hard-coded "localhost" address for forwarding requests;
*) ssh - improved system stability when processing none-crypto SSH connection;
*) sstp - fixed TLS session establishment when "connect-to" is DNS name;
*) switch - fixed SFP rate select for CRS354 devices;
*) switch - improved 10G, 25G, 40G and 100G interface stability for 98DX8208, 98DX8212, 98DX8332, 98DX3257, 98DX4310, 98DX8525, 98DX3255, 98PX1012 switches;
*) switch - improved system stability for 98DXxxxx switch chips;
*) swos - removed "/system swos" menu for CRS5xx series switches;
*) torch - allow "without-paging" parameter for Torch;
*) traffic-generator - increased maximum allowed stream count;
*) upgrade - show error message when license prohibits upgrade;
*) usb - changed USB auto detect behavior to default to the external USB, when no internal USB devices detected;
*) vxlan - added "dont-fragment" setting that allows managing fragmentation;
*) vxlan - added "max-fdb-size" parameter;
*) vxlan - added FastPath support;
*) webfig - allow setting numeric values in time interval fields;
*) webfig - fixed accessing of WebFig when "Interface" menu is disabled by skin;
*) webfig - fixed editing of multi-field parameters with "not" checkbox;
*) webfig - fixed handling of empty skin files;
*) webfig - improved navigation responsiveness;
*) webfig - improved skin file parsing;
*) webfig - improved terminal operation;
*) webfig - properly escape all reserved URI characters;
*) webfig - updated WebFig and graph web pages to HTML5;
*) wifiwave2 - added wireless sniffer tool to capture wireless transmissions (CLI only);
*) wifiwave2 - adjust monitoring of station interfaces to report when an interface is authorized, not just connected;
*) wifiwave2 - enabled additional channels in UNII-3 and UNII-4 bands for Europe and USA on hAP ax^2, hAP ax^3 and Chateau ax;
*) wifiwave2 - fixed compatibility with third-party devices when using SAE hash-to-element authentication with DH groups 20 and 21;
*) wifiwave2 - fixed SAE authentication for interfaces in station mode when trying to connect to APs which require an anti-clogging token (introduced in RouterOS 7.4);
*) wifiwave2 - implement 802.11w management protection SA Query procedures;
*) wifiwave2 - improve protections from denial-of-service attacks on WPA3;
*) winbox - added "Connect" button under "WifiWave2/Scan" menu;
*) winbox - added "Disable/Enable" buttons under "WifiWave2" menu;
*) winbox - added "Match Subdomain" parameter under "IP/DNS/Static" menu;
*) winbox - added "Provision" button under "WifiWave2" menu;
*) winbox - added "Start On Boot" checkbox under "Container" menu;
*) winbox - added "Tx Rate" and "Rx Rate" columns under "WifiWave2/Registration" menu;
*) winbox - added missing properties when setting "Use DoH Server";
*) winbox - added missing WifiWave2 related parameters under "WifiWave2" menu;
*) winbox - added support for manual RAM file system (TMPFS) creation under "System/Disk" menu;
*) winbox - added Type "https-get" parameter under "Tools/Netwatch" menu;
*) winbox - allow selecting bridge for static entries under "Bridge/MDB" menu;
*) winbox - fixed displaying of "Default Prepend" value under "Routing/BGP/Sessions" menu;
*) winbox - fixed displaying of "Tx/Rx CCQ" values under "Wireless/Registration" menu;
*) winbox - fixed displaying of flags under "System/Console" menu;
*) winbox - fixed displaying of multiple character flags;
*) winbox - fixed usage of IPv6 family addresses under "IP/Web Proxy/Access" menu;
*) winbox - hide "TTL" value for static DNS entries with FWD type;
*) winbox - hide unnecessary properties for virtual interfaces under "WifiWave2" menu;
*) winbox - improved mouseover hint for "local" policy under "System/Users/Groups" menu;
*) winbox - rename "Multicast Router" monitoring property to "Is Multicast Router" under "Bridge" menu;
*) winbox - show "Gateway" column by default under "IPv6/Routes" menu;
*) x86 - added support for TP-Link TG-3468;
*) x86 - fixed SR-IOV support for Intel X710 series NIC;
*) x86 - improved Intel 500 series 10G SFP module support;
*) x86 - improved stability for Intel X550 series NIC with SR-IOV;
*) zerotier - fixed routes after VRF change;

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 or through support system. File must be generated while the router is not working as suspected or after some problem has appeared on the device

Please keep this forum topic strictly related to this particular RouterOS release.

denisnk · Mon Feb 27, 2023 10:58 am

No sector writes statistics on hAP ac^2 (WinBox 64bit v3.37). But is present in terminal.

miasharmse84 · Mon Feb 27, 2023 11:09 am

Thank you for this new release @Mikrotik.
We have been running version 7.8rc3 on some of our routers which has been quite stable.
Are there any differences between 7.8rc3 and 7.8stable?

Znevna · Mon Feb 27, 2023 11:34 am

These changes from 7.8beta3 viewtopic.php?t=192810#p981950 are missing even in the 7.8rc releases changelogs:

*) console - improved ":execute" command to output a string when a file is not specified;
*) route - added hoplimit and metric parameters to SLAAC routes;
*) winbox - added missing cipher properties for OVPN server and client;
*) winbox - added missing filtering properties under "Tools/Packet Sniffer" menu;

Are they just missing from the changelog and were silently added or ? ¯\_(ツ)_/¯

rextended · Mon Feb 27, 2023 11:48 am

[…]
Are they just missing from the changelog and were silently added or ? ¯\_(ツ)_/¯

I do not check the others but this is simply REMOVED so no valid for 7.8:

*) console - improved ":execute" command to output a string when a file is not specified;

because is REPLACED with

*) console - added "as-string" parameter to the ":execute" command;

?

And for "*) route - […]" can be probably REMOVED for increase stability for be added later on 7.9alpha, but I do not chek that.

parham · Mon Feb 27, 2023 11:59 am

Hi all,

why there is missing zero tier on Arm?!!!

channel: stable
installed-version: 7.7
latest-version: 7.8
status: zerotier-7.8-arm.npk missing, use ignore-missing or disable package(s)

I know I can use ignore but that is not my question.

Thanks

Znevna · Mon Feb 27, 2023 12:04 pm

@rextended: obviously I've only compared exact lines, and left out the bugs introduced/fixed in rc/beta, didn't look for renamed changes..

memelchenkov · Mon Feb 27, 2023 12:06 pm

why there is missing zero tier on Arm?!!!

It's there, in all_packages-arm-7.8.zip file.

peri · Mon Feb 27, 2023 12:22 pm

No sector writes statistics on hAP ac^2 (WinBox 64bit v3.37).
res.png

me too

nichky · Mon Feb 27, 2023 12:27 pm

When route-reflector can be fix?

rextended · Mon Feb 27, 2023 12:28 pm

SPOILER:

lognames code

[–]
    enum Topic {
	_BAD_TOPIC,
	INFO,
	WARNING,
[–]
        NETWATCH,
	VPLS,
	NETINSTALL,
    };
[–]

Someone is try to add directly NETINSTALL on DHCP server?...

THANKS STAFF!!!

Babujnik · Mon Feb 27, 2023 12:56 pm

ROSE-MANAGER still cannot mount iscsi devices from QNAP/Synology NAS to CHR:

[237610.752320] iSCSI_F:iscsi_target_login.c:803:iscsi_post_login_handler Login - I[MikroTik][MTK_IP:42944], T[iqn.2000-01.com.synology:valhalla.default-target.cf7d36ec4c8][SYNOLOGY_IP:3260], P[iSCSI/TCP]
[237610.788037] iSCSI:target_core_transport.c:1735:target_cmd_size_check TARGET_CORE[iSCSI]: Expected Transfer Length: 2048 does not match SCSI CDB Length: 0 for SAM Opcode: 0x12
[237610.803688] iSCSI:iscsi_target_datain_values.c:116:iscsit_set_datain_values_yes_and_yes ITT: 0x0000002f read_data_left is zero!
[237610.815245] iSCSI:iscsi_target.c:3227:iscsit_send_datain iscsit_get_datain_values failed for ITT: 0x0000002f
[237610.825176] iSCSI_F:iscsi_target.c:4746:iscsit_close_connection Close - I[MikroTik][MTK_IP:42944], T[iqn.2000-01.com.synology:valhalla.default-target.cf7d36ec4c8]

rumahnetmks · Mon Feb 27, 2023 1:03 pm

Update RB4011iGS+5HacQ2HnD-IN, hAPAC3, RB450Gx4 to 7.8
Seem no error 30mins passed...

ErfanDL · Mon Feb 27, 2023 1:10 pm

High CPU usage after upgrade to 7.8 Stable. Device is RB2011UiAS-2HnD.

Screenshot (146).jpg

rextended · Mon Feb 27, 2023 1:11 pm

High CPU usage after upgrade to 7.8 Stable:

All the CPU is used for MANAGE the device...
It stop when you close winbox, or probably when SNMP stop syncronizing with the device...
Reinstall 7.7 and check.

liviu2004 · Mon Feb 27, 2023 1:17 pm

No sector writes statistics on hAP ac^2 (WinBox 64bit v3.37).
res.png

Available on RB5009 still.

ErfanDL · Mon Feb 27, 2023 1:19 pm

High CPU usage after upgrade to 7.8 Stable:
All the CPU is used for MANAGE the device...
It stop when you close winbox, or probably when SNMP stop syncronizing with the device...
Reinstall 7.7 and check.

But there was no problem with 7.8 RC3 !

rextended · Mon Feb 27, 2023 1:19 pm

Is the same release, just change the name on the files.....

Pl07R3K · Mon Feb 27, 2023 1:25 pm

I have two 64MiB partitions on Audience, after downloading the update (ROS 7.8 + wifiwave2) there was only left 1% free, it barely fit in it.
After the actualization 41MiB of 64.3 MiB used (believe me I don't store files on the router).
@MIKROTIK Can it be slimmed down?

rextended · Mon Feb 27, 2023 1:27 pm

reboot, and if this nott fix, netinstall

usx · Mon Feb 27, 2023 1:28 pm

Following works ok:

RBmAP2n ("mAP 2n") -- FLASH storage

RBD25G-5HPacQD2HPnD ("Audience") -- NAND storage: has Sector Writes statistics

2011UiAS-2HnD -- NAND storage: has Sector Writes statistics

hAP RB951Ui-2nD ("hAP") -- FLASH storage

RB4011iGS -- NAND storage: has Sector Writes statistics

hEX 750G r3 ("hEX") -- FLASH storage

Rox169 · Mon Feb 27, 2023 1:31 pm

Following works ok:
RBmAP2n ("mAP 2n")

RBD25G-5HPacQD2HPnD ("Audience")

2011UiAS-2HnD

hAP RB951Ui-2nD ("hAP")

RB4011iGS

hEX 750G r3 ("hEX")

Thanks for this...more confirmation please...any 60Ghz or AX tested?

If I use Zerotier I should not upgrade then?

rextended · Mon Feb 27, 2023 1:32 pm

With a (just) newly released OS that doesn't have any improvements for 60GHz???

Rox169 · Mon Feb 27, 2023 1:34 pm

With a (just) newly released OS that doesn't have any improvements for 60GHz???

I can read I know there is no change for 60Ghz...but noone is gonna instal it on 60Ghz?

Mon Feb 27, 2023 1:50 pm

No sector writes statistics on hAP ac^2 (WinBox 64bit v3.37).
res.png
Available on RB5009 still.

I don't see this problem on RB5009. Sector writes (total and since reboot) do have values on my setup.

rextended · Mon Feb 27, 2023 1:52 pm

I can read I know there is no change for 60Ghz...but noone is gonna instal it on 60Ghz?

It makes no sense to risk in a device that does not benefit from it, then with a version of RouterOS that has just come out...

Mon Feb 27, 2023 1:55 pm

Thanks for this...more confirmation please...any 60Ghz or AX tested?

AC3 and AX3 upgraded, so far no issues seen.

Mon Feb 27, 2023 2:05 pm

Regarding the missing changelog entries - the release does not differ from the rc3. Simply changelog has been updated a little bit. Some changes were merged or rewritten. There is no need to look for something more than simple changelog improvements.

Pl07R3K · Mon Feb 27, 2023 2:14 pm

I have two 64MiB partitions on Audience, after downloading the update (ROS 7.8 + wifiwave2) there was only left 1% free, it barely fit in it.
After the actualization 41MiB of 64.3 MiB used (believe me I don't store files on the router).
@MIKROTIK Can it be slimmed down?

probably something is wrong since routeros 7.8 + wifiwave2 + container use 32.6 MiB of 64.5 MiB on hAP ax^3

jookraw · Mon Feb 27, 2023 2:14 pm

*) sfp - fixed false link detection with S+RJ10 on RB5009;

I can confirm that this is fixed, now I can use 2.5G NIC's when using the RB5009 with the S+RJ10 on the SFP+ slot. Also 10G on the same module is also working fine.

anav · Mon Feb 27, 2023 2:17 pm

@parham @rox169 ---> Zerotier and wifiwave2 are separate packages ( like others ) and for each new version you have to re-install those as well. Bit of a pain but minimal and then we get access to great functionality without overloading older routers if all included in the main file. Kudos to MT for making this type of setup.
[ But I didnt find the zerotrust cloudflare tunnel options package? ;-)) ]

darklord · Mon Feb 27, 2023 2:23 pm

Scripts run count on my CCR2004 is always 0. When I run script from winbox, this counter increases, but once I close and reopen winbox, I have 0 again. ROS 7.7, after update to 7.8 still the same. This is not happening on rb4011, so maybe only related to arm64?

ToTheCLI · Mon Feb 27, 2023 2:29 pm

RB5009 on 7.8 Stable does not recognize Huawei MA5671A GPON SFP at all (with auto-neg on or off) was working fine on 7.7 stable (with auto-neg on and off fixed 2.5Gbps)

Rox169 · Mon Feb 27, 2023 2:30 pm

@parham @rox169 ---> Zerotier and wifiwave2 are separate packages ( like others ) and for each new version you have to re-install those as well. Bit of a pain but minimal and then we get access to great functionality without overloading older routers if all included in the main file. Kudos to MT for making this type of setup.
[ But I didnt find the zerotrust cloudflare tunnel options package? ;-)) ]

you are wrong....normally when you have the package already installed the upgrade in winbox automaticaly upgrade the package installed.

Mon Feb 27, 2023 3:10 pm

It did when I upgraded AC3 and AX3 earlier (wifiwave2 package).

wavestar · Mon Feb 27, 2023 3:12 pm

Update MikroTik RB5009UG+S+IN to 7.8
No errors after 60mins passed...

anav · Mon Feb 27, 2023 3:15 pm

Well I upgraded a 7.6 to 7.8rc2 last night and it did not. I had to install the wifi wave separately, maybe for betas its different?? Of course today they effing coming out with 7.8 stable LOL.

Update, ahh okay, I never usually use the udpate button as take router off line to do updates and thus use downloads.......................... something satisfying about dragging files over ;-PPP

jovaf32128 · Mon Feb 27, 2023 3:28 pm

hap ac3:

system, error, cricical: error while running customized default configuration script: no such item

Both wifi interfaces named as defaulf: wifi1 (+ wifi1-guest) and wifi2 (+ wifi2-guest)

oeyre · Mon Feb 27, 2023 4:07 pm

Hi, is it possible to please elaborate on this one?

*) mpls - improved stability when neighboring router reboots;

lluu131 · Mon Feb 27, 2023 4:24 pm

ospf v3 still not working in 7.8

viewtopic.php?t=192529

mkx · Mon Feb 27, 2023 5:08 pm

I have two 64MiB partitions on Audience, after downloading the update (ROS 7.8 + wifiwave2) there was only left 1% free, it barely fit in it.
After the actualization 41MiB of 64.3 MiB used (believe me I don't store files on the router).
@MIKROTIK Can it be slimmed down?

Upgrading ROS+wifiwave2 on my audience with partitioned disks failed with earlier ROS versions (it might be when upgrading from 7.5 to 7.6 or something). It actually refused to download upgrade stuff due to lack of free space.

But then, why do you worry about (temporary) lack of space, it gets freed immediately after upgrade is done?

pe1chl · Mon Feb 27, 2023 5:33 pm

you are wrong....normally when you have the package already installed the upgrade in winbox automaticaly upgrade the package installed.

It probably has been made more intelligent, when a package has no changes it simply isn't upgraded.
E.g. when I upgraded from 7.8beta2 up to 7.8rc2 the "rose-storage" package remained at 7.8beta2 but it still was working.
The zerotier package isn't upgraded (it does not follow the available releases, it seems) so it will remain at 7.7 when you upgrade.
When you explicitly upload the 7.8 version from all_packages.zip it will happily "upgrade" it but is still the same old zerotier version.

sirca · Mon Feb 27, 2023 5:35 pm

Is still not recommended for CRSs ?
Best Regards from Rome
Andrea

liviu2004 · Mon Feb 27, 2023 5:36 pm

I saw somewhere in rc that it was now.

pe1chl · Mon Feb 27, 2023 5:37 pm

But then, why do you worry about (temporary) lack of space, it gets freed immediately after upgrade is done?

I would not want to upgrade with so little free space, maybe it needs a little temporary space during the upgrade and the disk-full situation isn't properly handled, resulting in invisible corrupted installation.
Apparently partitioning a 128MB device with wifiwave2 package is no longer possible/advisable. 128MB flash will become the new 16MB flash...

Network5 · Mon Feb 27, 2023 5:55 pm

ospf v3 still not working in 7.8

viewtopic.php?t=192529

Our backbone is up and running in dual-stack since 7.5. What part of OSPFv3 is not working for you?

benkreuter · Mon Feb 27, 2023 5:57 pm

ospf v3 still not working in 7.8

viewtopic.php?t=192529

Same, I am not seeing proper LSA exchanges or routes being installed between neighbors. This is a regression from v7.7 and needs to be treated as a critical bug.

[edit: this seems to be a problem when interoperating with v7.7 neighbors, the bug may be in v7.7; perhaps this is related to the ospf-type fix mentioned in the changelog?]

tigran · Mon Feb 27, 2023 6:14 pm

Hi there!

We have found an issue in the latest release.

Please check the following configuration
LtAP router with factory fitted R11e-LTE6 and another extra R11e-LTE6 module in the upper mini-PCIe slot.
After each reboot/restart top modem hangs up and is not reachable. USB bus reset helps (each time).

krafg · Mon Feb 27, 2023 6:47 pm

Thanks a lot

Guscht · Mon Feb 27, 2023 7:25 pm

just my smooll home-network, no issues so far :)

Screenshot 2023-02-27 182517.jpg

Chat-GPT did this for you <3

Oh Mikrotik, we sing your praise
For the gift of ROS v7.8 released today
Your routers and switches, they work so well
With your firmware updates, they'll never fail

Your powerful features are second to none
We rely on your stability, it's always on
With this new release, we'll surely soar
Our networks will thrive, forever more

Thank you Mikrotik, for all that you do
For keeping our networks fast, and always true
We'll continue to trust in your brand
As you lead us into the future, hand in hand

# # #

O Mikrotik, mēs dziedājam par tavu godu
Par dāvanu - ROS v7.8 izlaišanu šodien
Tavi maršrutētāji un komutatori darbojas tik labi
Ar tavām programmatūras atjauninājumiem, tie nekad nenokrīt

Tavi spēcīgie iespējām nav nekas līdzīgs
Mēs paļaujamies uz tavu stabilitāti, kas vienmēr ir pieejama
Ar šo jauno izlaišanu mēs noteikti gādāsim augšup
Mūsu tīkli būs veiksmīgi, uz mūžu

Paldies, Mikrotik, par visu, ko tu dari
Par to, ka uztur mūsu tīklus ātrus un drošus
Mēs turpināsim ticēt tavam zīmolam
Kamēr tu ved mūs nākotnē, roku rokā.

josser · Mon Feb 27, 2023 7:36 pm

Still miss

 /interface/wifiwave2/info contry-info "Country"

since 7.7 :(

fornuftFTW · Mon Feb 27, 2023 7:37 pm

This update broke my containers because disk1 was automatically renamed to usb1-part1 for some reason, and then disk1 was automatically re-added, so the update corrupted all the paths.

When I try to change the container root dir, I just the error "Couldn't change Container - Can't change root directory. (6).

How do I fix the bug?

pe1chl · Mon Feb 27, 2023 7:41 pm

You can rename the disk to something of your liking, and then it will not change again. That is why this change was made (disk1 wasn't a stable name).

fornuftFTW · Mon Feb 27, 2023 7:45 pm

I don't care about the name, usb1-part1 is fine. How do I change the container root dir to that?

andkar · Mon Feb 27, 2023 8:41 pm

Sector write statistics on various devices that I've tested upgrading 7.7 > 7.8:

Statistics Ok > Gone: RB750Gr3, CRS326-24G-2S+, RBwAPGR-5HacD2HnD, RBD52G-5HacD2HnD, RB750Pr2, RBcAPGi-5acD2nD
Statistics Ok > Ok: RB2011iL
Statistics Gone > Ok: RB3011UiAS (IIRC, gone in v7.5) Total sector count have been reset and seem to start over from zero.

strzinek · Mon Feb 27, 2023 9:32 pm

*) ike2 - added support for "address", "key-id" and "dn" for Remote ID matching (CLI only);

Hello, still no mention in the documentation regarding the use of this: https://help.mikrotik.com/docs/display/ROS/IPsec.

strzinek · Mon Feb 27, 2023 9:44 pm

*) ike2 - added support for "address", "key-id" and "dn" for Remote ID matching (CLI only);
Hello, still no mention in the documentation regarding the use of this: https://help.mikrotik.com/docs/display/ROS/IPsec.

Ah, there is a change in the doc description column, but new values are still missing from the property column enum.

Can I use some regex or wildcards for these matchers?

verbovet · Mon Feb 27, 2023 9:46 pm

This update broke my dhcp client.

Normally, it was always in status bound. In ver. 7.8 it is bound for 5 min., then status becomes "renewing" for 5 min, then I get

dhcp,critical,error dhcp-client on wan2 lost IP address XX.XXX.XXX.X - lease expired

and then the cycle repeat. 10 min is the expiration time for leases from my ISP.

I downgraded to 7.7 and now the dhcp client works as usual.

nickcarr · Mon Feb 27, 2023 10:17 pm

Hi.
RB750G and hAP-Ac3 of mine, too.
Downgraded to 7.7: all goes fine.
I will wait for RB1100xx a and CCR2216

High CPU usage after upgrade to 7.8 Stable. Device is RB2011UiAS-2HnD.

Screenshot (146).jpg

Nadol · Tue Feb 28, 2023 12:37 am

Chateau LTE12 RBD53G-5HacD2HnD
No go, same as 7.7

lluu131 · Tue Feb 28, 2023 1:31 am

ospf v3 still not working in 7.8

viewtopic.php?t=192529
Same, I am not seeing proper LSA exchanges or routes being installed between neighbors. This is a regression from v7.7 and needs to be treated as a critical bug.

[edit: this seems to be a problem when interoperating with v7.7 neighbors, the bug may be in v7.7; perhaps this is related to the ospf-type fix mentioned in the changelog?]

Yes, the ipv6 neighbors have been bad since 7.6, 7.7 like the cluster, 7.8 too, and have fallen back to 7.6.

dlemery · Tue Feb 28, 2023 1:43 am

Urgent issue - LLDP-MED (auto voice VLAN for phones) is not functioning after upgrading from 7.7 to 7.8 on CRS328-24p

EDIT: Turning on PoE LLDP seems to solve it, but it doesn't function if that is off per port (off is the default setting when upgrading).

rextended · Tue Feb 28, 2023 2:00 am

Urgent issue - LLDP-MED (auto voice VLAN for phones) is not functioning after upgrading from 7.7 to 7.8 on CRS328-24p

Urgent?
Did you do not do any test on lab before put the release on production?

murrayis · Tue Feb 28, 2023 2:02 am

BFD!!!!! WHEN!!!! Come on guys - If you are having issues deploying it tell us!

A lot of us have fleets of CCR2004 we cannot use or if we are using them they are so unstable but we cannot go to v7 without BFD!

dlemery · Tue Feb 28, 2023 2:13 am

Urgent issue - LLDP-MED (auto voice VLAN for phones) is not functioning after upgrading from 7.7 to 7.8 on CRS328-24p
Urgent?
Did you do not do any test on lab before put the release on production?

@rextended - Urgent as in someone else here, with phones, might upgrade since everything else is working fine and this was released as stable.
Yes, tested on one switch before rolling out to all. Thank you for that useful comment though.

Looks like it actually might have to do with the recent addition of PoE LLDP. After manually turning that on per port (in the lab) the phones seem to eventually pull the voice VLAN ID again. Makes sense, but I'd imagine it will scare several VoIP people out there after initially upgrading.

SumNathan · Tue Feb 28, 2023 2:27 am

PPPoE scan appears to be broken after upgrading from 7.7 stable to 7.8 stable.

version 7.7 Stable

[admin@lab-cpe] > interface pppoe-client/scan interface=ether1 duration=10s
Columns: MAC-ADDRESS, AC-NAME
MAC-ADDRESS        AC-NAME      
00:AA:BB:CC:DD:EE  lab-core02

[admin@lab-cpe] >

version 7.8 Stable

[admin@lab-cpe] > interface pppoe-client/scan interface=ether1 duration=10s

[admin@lab-cpe] > interface pppoe-client/scan interface=ether1
-- [Q quit|D dump|C-z pause]

Left it scanning for 5 minutes and still got nothing.

Downgrading to 7.7 Stable made PPPoE scan work again.

dlemery · Tue Feb 28, 2023 2:36 am

ospf v3 still not working in 7.8

viewtopic.php?t=192529
Same, I am not seeing proper LSA exchanges or routes being installed between neighbors. This is a regression from v7.7 and needs to be treated as a critical bug.

[edit: this seems to be a problem when interoperating with v7.7 neighbors, the bug may be in v7.7; perhaps this is related to the ospf-type fix mentioned in the changelog?]

ospf v2 and v3 between v7.7 and v7.8 is working ok for me. I tried to recreate this issue before upgrading anything in production just in case, but can't seem to. All IPv6 routes working. Any other specific situation you might have we should look out for / try?

Pomo · Tue Feb 28, 2023 6:18 am

Still miss
Code: Select all
 /interface/wifiwave2/info contry-info "Country"
since 7.7 :(

Thanks, I thought I was going nuts.
Some of us actually use Mikrotik for wireless.
Why is this missing? It is still present in old wifi package.

blacksnow · Tue Feb 28, 2023 6:24 am

Just want to call out that L2HW firewall compatibale offloading is still broken as of version 7.6+. viewtopic.php?t=193770

Tue Feb 28, 2023 7:11 am

ZeroTier and WW2 packages are present on download servers and must be upgraded automatically if the "check-for-updates" feature is used. If that is not happening for someone, then please contact us through support@mikrotik.com.

own3r1138 · Tue Feb 28, 2023 7:20 am

The OVPN service is unstable, and it will cause a Kernel crashes after 2,3 hours of uptime.
SUP-96432

Tue Feb 28, 2023 7:41 am

denisnk - Thank you for your report. Although it is not version related. We will try to fix this as soon as possible. Yes, several devices might not show this on WinBox.
parham - Please contact us through support@mikrotik.com. These files are not missing on upgrade servers. We would like to figure out what is going on here with your router.
nichky - What kind of an issue do you refer to? Contact support@mikrotik.com and please leave this topic strictly related to the issues introduced in. v7.8 that were not present in v7.7.
Babujnik, tigran, fornuftFTW, strzinek, dlemery - We will look into this.
ErfanDL, jovaf32128, benkreuter, verbovet, nickcarr, SumNathan, blacksnow - Please send supout.rif file from this router running v7.8 to support@mikrotik.com.
Pl07R3K - We do not increase packages for some particular reason. Packages grow with extra functionality that is added and requested by our users. We do our best that each and every router can be upgraded without problems with the RouterOS package installed. The upgrade is working properly for each and every model device that we manufacture at the moment with pre-defined packages installed (GPS< WifiWave2, etc.) and default configuration running.
darklord - I can not reproduce the problem. Please contact us through support@mikrotik.com so we can find the root cause of this issue.
ToTheCLI - Thank you for your report. We will look into this.
lluu131 - Please see this - viewtopic.php?t=192529#p987012
sirca - No, you can use this version with CRS as well.
Nadol - Why? There was no problem description.
murrayis - We can only repeat that this is a work in progress. It will be ready when it will be ready. Unfortunately, using release topics in order to raise this question will not help in any way. So please, stick with the main purpose of these topics - discovering issues introduced in the particular release.

Reinis · Tue Feb 28, 2023 8:13 am

Urgent issue - LLDP-MED (auto voice VLAN for phones) is not functioning after upgrading from 7.7 to 7.8 on CRS328-24p

EDIT: Turning on PoE LLDP seems to solve it, but it doesn't function if that is off per port (off is the default setting when upgrading).

We're sorry for the caused inconvenience. The information just have been added to documentation.

Rox169 · Tue Feb 28, 2023 8:25 am

Hi,
im not sure if it is ROS 7.8 bug but my Wireguard is not working as before.... I have wireguard server A where I connect location B and C. I can login to A,B,C directly but I can not ping from B to C, I did not change any setup just upgrade ROS.

Tue Feb 28, 2023 8:29 am

Probably something in config ?
I have upgraded yesterday noon 3 devices at home to 7.8 and wireguard works just fine (remotely so I was using wireguard :lol: )
Best to start new thread with all needed info (esp. export of config and network diagram).

lap · Tue Feb 28, 2023 8:49 am

Anybody else having issues with Nextdns after upgrading to v7.8? It started giving me:

 DoH server connection error: Address not available

It was working just fine for many months and several RouterOs upgrades.
Setting Nextdns again according to their instructions didn't help so I had to disable Nextdns on my router.

ilmars · Tue Feb 28, 2023 8:51 am

BFD!!!!! WHEN!!!! Come on guys - If you are having issues deploying it tell us!

A lot of us have fleets of CCR2004 we cannot use or if we are using them they are so unstable but we cannot go to v7 without BFD!

Same - we would be using several of CCR2116 and upgrading our whole MikroTik fleet to v7 if there was working BFD implementation.
Till than we are using v7 only for some of setups were BFD does not come into play.
As seen at viewtopic.php?p=980891

rpingar · Tue Feb 28, 2023 9:26 am

pppoe still crashes on 7.8 and pppoe client dynamic interface some time don't get running after authentication.
[SUP-97493] updated with supout.

regards
Ros

Nadol · Tue Feb 28, 2023 9:40 am

Nadol - Why? There was no problem description.

I don't know why. It start with 7.7, clicking download&install using winbox, reboot and still at 7.6
Same story with 7.8. Package is downloaded, router is rebooting but new version is not applied.
Please point me what information you need about uprgrade process on my router and how to get it.

Railander · Tue Feb 28, 2023 9:56 am

Is still not recommended for CRSs ?
Best Regards from Rome
Andrea

would like to know as well. remember the changelog in the release candidates saying to not use on CRS devices, is that still the case?

depth0cert · Tue Feb 28, 2023 10:28 am

RouterOS version 7.8 has been released in the "v7 stable" channel!

Hello.

SUP-108056
Clean netinstalled 7.8 from chr-7.8.vdi not print /ip/ipsec/installed-sa/print, only after reboot.
supout.rif from r1 and r2 in attachment SUP-108056

Command r1:

/certificate/add name="r1-ca" common-name="r1-ca" subject-alt-name="email:r1-ca" key-size=prime256v1 key-usage=key-cert-sign,crl-sign
:do {/certificate/sign [find name=r1-ca] name=r1-ca} on-error={:delay 2}
/certificate/add name="r1" common-name="192.168.2.14" subject-alt-name="IP:192.168.2.14" key-size=prime256v1 key-usage=digital-signature,content-commitment,key-encipherment,key-agreement,tls-server
:do {/certificate/sign [find name=r1] ca=r1-ca name=r1} on-error={:delay 2}
/certificate/add name="r1-r2" common-name="r1-r2" subject-alt-name="email:r1-r2" key-size=prime256v1 key-usage=digital-signature,key-encipherment,data-encipherment,key-agreement,tls-client
:do {/certificate/sign [find name=r1-r2] ca=r1-ca name=r1-r2} on-error={:delay 2}
:delay 2
/certificate/export-certificate r1-ca file-name=r1-ca
/certificate/export-certificate r1 file-name=r1
/certificate/export-certificate r1-r2 file-name=r1-r2 type=pkcs12 export-passphrase=passphrase
/ip/pool/add name=r1-r2 ranges=192.168.1.2
/ip/ipsec/mode-config/add address-pool=r1-r2 address-prefix-length=32 name=r1-r2 split-include=0.0.0.0/0 system-dns=no
/ip/ipsec/policy/group/add name=group1
/ip/ipsec/profile/add dh-group=ecp256 enc-algorithm=aes-256 hash-algorithm=sha256 name=profile1 prf-algorithm=sha256 proposal-check=strict
/ip/ipsec/peer/add exchange-mode=ike2 local-address=192.168.2.14 name=peer1 passive=yes profile=profile1
/ip/ipsec/proposal/add auth-algorithms=sha256 enc-algorithms=aes-256-cbc,aes-256-gcm lifetime=8h name=proposal1 pfs-group=ecp256
/ip/ipsec/identity/add auth-method=digital-signature certificate=r1 generate-policy=port-strict match-by=certificate mode-config=r1-r2 peer=peer1 policy-template-group=group1 remote-certificate=r1-r2
/ip/ipsec/policy/add dst-address=192.168.1.0/24 group=group1 proposal=proposal1 src-address=0.0.0.0/0 template=yes

Command r2:

/certificate/import file-name="r1-ca.crt" name="r1-ca" passphrase=""
/certificate/import file-name="r1.crt" name="r1" passphrase=""
/certificate/import file-name="r1-r2.p12" name="r1-r2" passphrase="passphrase"
/ip/ipsec/mode-config/add name=cfg1 responder=no
/ip/ipsec/policy/group/add name=group1
/ip/ipsec/profile/add dh-group=ecp256 enc-algorithm=aes-256 hash-algorithm=sha256 name=profile1 prf-algorithm=sha256 proposal-check=strict
/ip/ipsec/peer/add address=192.168.2.14/32 exchange-mode=ike2 name=peer1 profile=profile1
/ip/ipsec/proposal/add auth-algorithms="" enc-algorithms=aes-256-gcm lifetime=8h name=proposal1 pfs-group=ecp256
/ip/ipsec/identity/add auth-method=digital-signature certificate=r1-r2 generate-policy=port-strict match-by=certificate mode-config=cfg1 my-id=dn peer=peer1 policy-template-group=group1 remote-certificate=r1
/ip/ipsec/policy/add dst-address=0.0.0.0/0 group=group1 proposal=proposal1 src-address=0.0.0.0/0 template=yes

r1:

r1.png

r2:

r2.png

Bug not always reproduced, many need netinstall few times.
supout.rif from r1 and r2 in attachment SUP-108056

Please, fix it.

dksoft · Tue Feb 28, 2023 10:47 am

You can rename the disk to something of your liking, and then it will not change again. That is why this change was made (disk1 wasn't a stable name).

Can you please advice how to rename the disk?
I habe usb1 or nvme1 and if I change the name, the error "can not change device type (6)" appears.

Thanks
dksoft

lluu131 · Tue Feb 28, 2023 10:51 am

denisnk - Thank you for your report. Although it is not version related. We will try to fix this as soon as possible. Yes, several devices might not show this on WinBox.
parham - Please contact us through support@mikrotik.com. These files are not missing on upgrade servers. We would like to figure out what is going on here with your router.
nichky - What kind of an issue do you refer to? Contact support@mikrotik.com and please leave this topic strictly related to the issues introduced in. v7.8 that were not present in v7.7.
Babujnik, tigran, fornuftFTW, strzinek, dlemery - We will look into this.
ErfanDL, jovaf32128, benkreuter, verbovet, nickcarr, SumNathan, blacksnow - Please send supout.rif file from this router running v7.8 to support@mikrotik.com.
Pl07R3K - We do not increase packages for some particular reason. Packages grow with extra functionality that is added and requested by our users. We do our best that each and every router can be upgraded without problems with the RouterOS package installed. The upgrade is working properly for each and every model device that we manufacture at the moment with pre-defined packages installed (GPS< WifiWave2, etc.) and default configuration running.
darklord - I can not reproduce the problem. Please contact us through support@mikrotik.com so we can find the root cause of this issue.
ToTheCLI - Thank you for your report. We will look into this.
lluu131 - Please see this - viewtopic.php?t=192529#p987012
sirca - No, you can use this version with CRS as well.
Nadol - Why? There was no problem description.
murrayis - We can only repeat that this is a work in progress. It will be ready when it will be ready. Unfortunately, using release topics in order to raise this question will not help in any way. So please, stick with the main purpose of these topics - discovering issues introduced in the particular release.

Thank you very much. Just an update. Using CRS317, ip address configured on a vlan (vlan belongs to a bridge with L3 HW enabled), currently after turning off IGMP Snooping for the bridge, ospfv3 works fine. The problem is whether IGMP Snooping is blocking some packets of ipv6

giulianoz · Tue Feb 28, 2023 11:00 am

Hello,
Just FYI
On hap ac3 on 7.7 with a single usb flash drive mounted on /usb and adguard container running from usb drive, after the upgrade to 7.8 I’ve got
* usb drive is now mounted on /usb1-part1
* trying to change back to /usb results in an incorrect partition size error…
* existing docker containers fails to start becaus of root path is now not existing (and cannot be changed, apparently)
* pulling an image from dockerhub results in error 401 (known issue from other posts)
* recreated the container after updating the mount points and uploading the container tar file, but it does not start and no logs whatsoever except for the image import success notice…

I’ve deleted the container and used a raspberry pi to run it :(

pe1chl · Tue Feb 28, 2023 11:40 am

You can rename the disk to something of your liking, and then it will not change again. That is why this change was made (disk1 wasn't a stable name).
Can you please advice how to rename the disk?
I habe usb1 or nvme1 and if I change the name, the error "can not change device type (6)" appears.

What you need to change is the "slot" parameter.

mkx · Tue Feb 28, 2023 11:47 am

Nadol - Why? There was no problem description.
I don't know why. It start with 7.7, clicking download&install using winbox, reboot and still at 7.6

When upgrade fails, it's usually something in logs about the cause of it. So after you try to upgrade and it fails, immediately after reboot check logs to see the reason.

eddieb · Tue Feb 28, 2023 11:54 am

while upgrading my HEX (RB750Gr3) with DUDE I was surprised that the partition of the SDcard containing the DUDE data was renamed !

fixed this with
/dude set data-directory=sd1-part1

all other systems running fine after upgrade

lluu131 · Tue Feb 28, 2023 11:55 am

ospf v3 still not working in 7.8

viewtopic.php?t=192529
Same, I am not seeing proper LSA exchanges or routes being installed between neighbors. This is a regression from v7.7 and needs to be treated as a critical bug.

[edit: this seems to be a problem when interoperating with v7.7 neighbors, the bug may be in v7.7; perhaps this is related to the ospf-type fix mentioned in the changelog?]

Have you turned on IGMP Snooping?

Tue Feb 28, 2023 12:17 pm

ROSE-MANAGER still cannot mount iscsi devices from QNAP/Synology NAS to CHR:

Thanks we will check this

Can you please advice how to rename the disk?
I habe usb1 or nvme1 and if I change the name, the error "can not change device type (6)" appears.

thanks, this is Winbox bug, should work from CLI -
disk set usb1 slot=lala

MTL7 · Tue Feb 28, 2023 12:37 pm

I've this problem since v7.7 --> viewtopic.php?t=192427&start=300#p982228.
No follow up or update from Mikrotik staff. I guess either i don't know what i'm doing or they don't ... :-)
Anyway, I just reboot the box a few times more until it is happy to have the usb name matches with what i put in the Adguard container configuration. Not perfect but this is the way it is now ...

Hello,
Just FYI
On hap ac3 on 7.7 with a single usb flash drive mounted on /usb and adguard container running from usb drive, after the upgrade to 7.8 I’ve got
* usb drive is now mounted on /usb1-part1
* trying to change back to /usb results in an incorrect partition size error…
* existing docker containers fails to start becaus of root path is now not existing (and cannot be changed, apparently)
* pulling an image from dockerhub results in error 401 (known issue from other posts)
* recreated the container after updating the mount points and uploading the container tar file, but it does not start and no logs whatsoever except for the image import success notice…

I’ve deleted the container and used a raspberry pi to run it :(

pe1chl · Tue Feb 28, 2023 12:43 pm

I've this problem since v7.7 --> viewtopic.php?t=192427&start=300#p982228.
No follow up or update from Mikrotik staff. I guess either i don't know what i'm doing or they don't ... :-)

The change that others are complaining about now, was made exactly to prevent the problem that you had!
Instead of "scanning the devices at boot and assigning them numbered names" like disk1 usb1 etc, now disks get fixed "slot" names that you can assign yourself.

MTL7 · Tue Feb 28, 2023 12:45 pm

Thank you for your information. I will give v7.8 a try then.

I've this problem since v7.7 --> viewtopic.php?t=192427&start=300#p982228.
No follow up or update from Mikrotik staff. I guess either i don't know what i'm doing or they don't ... :-)
The change that others are complaining about now, was made exactly to prevent the problem that you had!
Instead of "scanning the devices at boot and assigning them numbered names" like disk1 usb1 etc, now disks get fixed "slot" names that you can assign yourself.

saimens · Tue Feb 28, 2023 1:36 pm

SFP no longer runs (= no link) in v7.8. The hardware still shows up. Everything comes back after downgrading to v7.7

The problem persists also on a clean installation after a full reset. Works in v7.7 but not in v7.8.

Any ideas what to try?

SFP: CTS SFP-31W2A(SM-10)-DR
Board: hEX S (MMIPS)

nonolk · Tue Feb 28, 2023 1:44 pm

Hello,

RB5009 on 7.8 Stable does not recognize Huawei MA5671A GPON SFP at all (with auto-neg on or off) was working fine on 7.7 stable (with auto-neg on and off fixed 2.5Gbps)

I encounter the same with another gpon sfp module (FS GPON-ONU-34-20BI), the module is not detected anymore (Module present in GUI is unchecked), reverting back to v7.7 solve the issue.

I would like to add 3 other issues:
- CPU usage is definitivly higher on v7.8: going from more or less 22% at 350 mhz on v7.7 to 30% at 1400 mhz on v7.8 (in basic router operation with ipv4 and ipv6, no containers, no ospf, no vpn, but capsman) for arround 500 Mbs download speed.
- IPV6, firewall connection tab is reporting no connections (in web-gui, working fine in winbox) but this existing since at least v7.3.
- On RB5009 activating bridge filter rules still disable ipv4 fasttrack..... (sadly for now switch filter rules are not supported for new-vlan-priority)

I hope this will help.

MightySlaytanic · Tue Feb 28, 2023 2:07 pm

Updated my hAP AC2 from 7.7 to 7.8, still having the problem that FastTracking stops working after few hours until you reboot the router (with a performance drop Speedtest over PPPoE from 930Mbps to 350Mbps).
I have updated the support case I've opened for the issue on 7.7.
Everything else seems ok, I've only noticed that the USB drive on which I schedule backus has been renamed from disk2 to usb1-part1.

saimens · Tue Feb 28, 2023 2:09 pm

I encounter the same with another gpon sfp module (FS GPON-ONU-34-20BI), the module is not detected anymore (Module present in GUI is unchecked), reverting back to v7.7 solve the issue.

SFP seems to be a systematic problem with v7.8. At least on some boards

viewtopic.php?t=193986#p987210

Pl07R3K · Tue Feb 28, 2023 2:40 pm

iPhone 12 with iOS 16.3.1 cannot connect to WiFi if wpa3-psk is enabled.

nonolk · Tue Feb 28, 2023 2:52 pm

SFP seems to be a systematic problem with v7.8. At least on some boards

viewtopic.php?t=193986#p987210

I did a bit more testing, and I can say this issue depends on the sfp module.
For me on rb 5009 running v7.8:
- FS GPON-ONU-34-20BI is not detected and therefore not working
- Mikrotik S-RJ01 is working perfectly

Of course rolling back to v7.7 makes both modules running properly.

Tue Feb 28, 2023 3:12 pm

Chateau LTE12 RBD53G-5HacD2HnD
No go, same as 7.7

Can you please explain in more detail what issues are you facing with the Chateau LTE12? Do you already have a support ticket open?

cdemers · Tue Feb 28, 2023 3:23 pm

@Pl07R3K try setting: /interface/wifiwave2/security/set yourWiFiprofile sae-pwe=hunting-and-pecking

dioeyandika · Tue Feb 28, 2023 3:46 pm

need change to my backup script, on system disk something change too sd1-part1, is this on the changelog?

noradtux · Tue Feb 28, 2023 4:43 pm

Thank you very much. Just an update. Using CRS317, ip address configured on a vlan (vlan belongs to a bridge with L3 HW enabled), currently after turning off IGMP Snooping for the bridge, ospfv3 works fine. The problem is whether IGMP Snooping is blocking some packets of ipv6

I had a ticket (SUP-105105) open for this issue on ROS 7.7. Reply was

OSPF relies on multicast to send HELLO packets, altering those multicast packets in any way (including igmp proxy, nat etc) will cause OSPF not to work properly.

and after inquiring if this was expected behaviour I got

As mentioned previously, OSPF may not work properly with features enabled that alter multicast packets and it does not matter OSPFv3 or OSPFv2.

.
I didn't push any further since I don't need IGMP snooping ¯\_(ツ)_/¯. I consider it a bug, though.

MightySlaytanic · Tue Feb 28, 2023 4:51 pm

need change to my backup script, on system disk something change too sd1-part1, is this on the changelog?

I've noticed the same, my disk2 changed to usb1-part1. I've changed my backup scripts as you did.

mrz · Tue Feb 28, 2023 5:08 pm

OSPF relies on multicast to send HELLO packets, altering those multicast packets in any way (including igmp proxy, nat etc) will cause OSPF not to work properly.
and after inquiring if this was expected behaviour I got
As mentioned previously, OSPF may not work properly with features enabled that alter multicast packets and it does not matter OSPFv3 or OSPFv2.
.
I didn't push any further since I don't need IGMP snooping ¯\_(ツ)_/¯. I consider it a bug, though.

How it is an OSPF bug if igmp snooping is blocking?
You can add static MLD entries for all the addresses ospfv3 is using
https://help.mikrotik.com/docs/display/ ... centries.1

/interface bridge mdb
add bridge=bridge1 group=ff02::5 ports=bridge1,ether2,ether3,ether4,ether5
add bridge=bridge1 group=ff02::6 ports=bridge1,ether2,ether3,ether4,ether5

Pl07R3K · Tue Feb 28, 2023 5:36 pm

@Pl07R3K try setting: /interface/wifiwave2/security/set yourWiFiprofile sae-pwe=hunting-and-pecking

Thank you for your advice, unfortunately it does not work, anyway the default should be both.
The message 'Unable to join the network "xxxxx"' pops up, no log entry.

hecatae · Tue Feb 28, 2023 5:40 pm

Chateau LTE12 RBD53G-5HacD2HnD
No go, same as 7.7

Can I have some more details please, my Chateau LTE12 is running 7.8rc3 testing without issues, what issues have you seen on 7.7 and 7.8 stable?
Are you updating Routerboard as well as RouterOS, kernel failure usually means your Routerboard version is causing an incompatibility with RouterOS.

Tue Feb 28, 2023 5:47 pm

Hello,

LtAP router with factory fitted R11e-LTE6 and another extra R11e-LTE6 module in the upper mini-PCIe slot.
After each reboot/restart top modem hangs up and is not reachable. USB bus reset helps (each time).

The possible initialization race condition with the dual R11e-LTE6 modem setup is reproduced and fixed, fix will be included in the next RouterOS v7 releases.

As an alternative to USB power reset, the following modem "re-plug" script can be used (copy/paste in CLI):

/system script remove [find name=ltap_dual_lte_enabler]
/system script add dont-require-permissions=yes name=ltap_dual_lte_enabler policy=read,write source="\
    :local iTimeout 60\r\
    \n\r\
    \n:local iLoop 0\r\
    \n:while ([/interface/lte/print as-value count-only]!=2 and \$iLoop<\$iTimeout) do={\r\
    \n  :set iLoop (\$iLoop+1)\t\t\r\
    \n  :delay 1s\r\
    \n  }\r\
    \n:if ([/interface/lte/print as-value count-only]=2) do={\r\
    \n  :local usbType [/system/routerboard/usb/get type]\r\
    \n  :log info \"setting USB to USB-type-A\"\r\
    \n  :put \"setting USB to USB-type-A\"\r\
    \n  /system routerboard usb set type=USB-type-A\r\
    \n  :delay 1s\r\
    \n  :log info (\"restoring initial USB type setting: \".\$usbType)\r\
    \n  :put (\"restoring initial USB type setting: \".\$usbType)\r\
    \n  /system routerboard usb set type=\$usbType\r\
    \n  }\r\
    \n:log info \"script ended\"\r\
    \n"
/system scheduler remove [find name=ltap_dual_lte_enabler]
/system scheduler add name=ltap_dual_lte_enabler on-event=ltap_dual_lte_enabler policy=read,write start-time=startup

This will be faster and will not reset the modem or another device without necessity.

Tue Feb 28, 2023 6:25 pm

Pl07R3K please write to support@mikrotik.com ,let us know what security profile settings you have configured, and share a supout.rif file with us, made after a connection attempt.

tigran · Tue Feb 28, 2023 6:57 pm

Hello,

LtAP router with factory fitted R11e-LTE6 and another extra R11e-LTE6 module in the upper mini-PCIe slot.
After each reboot/restart top modem hangs up and is not reachable. USB bus reset helps (each time).
The possible initialization race condition with the dual R11e-LTE6 modem setup is reproduced and fixed, fix will be included in the next RouterOS v7 releases.

Dear Artis,

Thank you for your fast input. We will check this tomorrow and give you a feedback on this.

P.S. If possible issue a new release ASAP, because we use LtAP installation all across our Latvian country in emmergency vehicles (police and ambulances). New routers come with 6.* version installed, but we need to upgrade to 7.* before we proceed fitting new installations in 100 new ambulances... Paldies! :)

connectlife · Tue Feb 28, 2023 7:31 pm

Hi, the ospf outgoing filters seem to no longer work on 7.8. Putting a complete reject on 7.7 the routes are not announced while on 7.8 everything passes despite the filter with reject on the chain out..

pe1chl · Tue Feb 28, 2023 7:47 pm

P.S. If possible issue a new release ASAP, because we use LtAP installation all across our Latvian country in emmergency vehicles (police and ambulances). New routers come with 6.* version installed, but we need to upgrade to 7.* before we proceed fitting new installations in 100 new ambulances... Paldies! :)

Please tell them you need BFD!

dakobg · Tue Feb 28, 2023 8:17 pm

+1 for BFD please what is tue problem to be delayed so long ..

Maggiore81 · Tue Feb 28, 2023 8:32 pm

After a quick check on this topic, I see the 7.8 as an ALPHA... not a "stable" release...

jvanhambelgium · Tue Feb 28, 2023 8:44 pm

Updated my RB5009. No issues so far. The "flashing" SFP interface window in Winbox seems fixed and remains stable. My SFP S+RJ10 works just fine.

Screenshot from 2023-02-28 19-43-00.png

The only thing is this usb-drive mapping/naming. Now it became usb2-part1 (it was usb1-part1 on 7.7) so my container did not start etc,etc.

Tue Feb 28, 2023 8:47 pm

Strange, on my rb5009 it staid as usb1-part1.
I went from 7.6 to 7.7 to 7.8rc2 an rc3 and now 7.8.

But I don't use container package.

mhugo · Tue Feb 28, 2023 9:31 pm

Please update https://help.mikrotik.com/docs/display/ ... l+Overview so we know if there are changes.

Im hoping BFD, /31 and working L3HW working with BGP peering will soon be green fields.

rb9999 · Tue Feb 28, 2023 9:35 pm

I think 7.8 is a bit broken.. upgraded CCR2004-16G-2S+ from v7.7 to v7.8 yesterday. At first it seems to work just fine but the strangest things happen - winbox shows blank windows and it's hard to reboot (e.g. it doesn't respond for system/reboot for couple of minnutes, but then out of the blue - it reboots). rolling back to v7.7

Tue Feb 28, 2023 9:37 pm

Maggiore81 - Why do you say so? If we sum up the topic, then basically we have found out that few SFP modules are not working properly, which were working on v7.7. Rest of the issues discussed here are already known issues from previus versions, misconfiguraiton, or minor bug reports about trivial issues or issues from older versions (not introduced in 7.8 ). Of course many posts are not realted to release at all.

mkx · Tue Feb 28, 2023 9:45 pm

After a quick check on this topic, I see the 7.8 as an ALPHA... not a "stable" release...

Could be. But my Audience (running wave2 driver) lijes it very much, since upgrade to 7.8 WiFi works much smoother, I don't have to play tricks with Huawei MediaPad T5 tablet to use 5GHz band (it used to stick to 2.4GHz a lot).

Pl07R3K · Tue Feb 28, 2023 9:49 pm

After a quick check on this topic, I see the 7.8 as an ALPHA... not a "stable" release...

Unfortunately, I think you're right.
I have an idea for a new challenge for Viktor, guess what spectacular new functionality MT will throw into next ROS instead of polishing defects?

Containers and rose-storage have set the bar high.
I'm betting on the ROS's TikTok client, this would be a real game changer.

More seriously, how about reminding them what we're waiting for?
I am waiting for support for the switch chip in the IPQ-6010, CAPsMAN and traffic tagging in wifiwave2 (they forgot about the Audience).

pe1chl · Tue Feb 28, 2023 9:51 pm

Could be. But my Audience (running wave2 driver) lijes it very much, since upgrade to 7.8 WiFi works much smoother, I don't have to play tricks with Huawei MediaPad T5 tablet to use 5GHz band (it used to stick to 2.4GHz a lot).

Well, I can tell you that I don't like the fact that my RB4011 still is not supported by wave2 driver while retaining 2GHz support. It is one of their flagship routers for the home, and a workaround to make both drivers work alongside (each on their respective bands) still has not been made. I can understand that for a first try, but after so many releases...

massinia · Tue Feb 28, 2023 9:59 pm

with Huawei MediaPad T5 tablet to use 5GHz band (it used to stick to 2.4GHz a lot).

I thought I was the only one in the world this this damn tablet 😂

mkx · Tue Feb 28, 2023 10:01 pm

with Huawei MediaPad T5 tablet to use 5GHz band (it used to stick to 2.4GHz a lot).
I thought I was the only one in the world this this damn tablet 😂

Nah, we're two ... and a a few million Chineze ....

Tue Feb 28, 2023 10:10 pm

Well, I can tell you that I don't like the fact that my RB4011 still is not supported by wave2 driver while retaining 2GHz support. It is one of their flagship routers for the home,...

Sorry but that's not how I see it.
That position has been taken by RB5009 already last year.

The fact you don't like it, I completely understand. But it is what it is.

infabo · Tue Feb 28, 2023 10:29 pm

Chateau LTE12 and mAP lite here. No known issues. Auto update (!) went smoothly.

RafGan · Tue Feb 28, 2023 11:23 pm

Discs names are changed. Dude, scripts, scheduler, smb and other settings to manual correct.

Nadol · Wed Mar 01, 2023 12:34 am

Chateau LTE12 RBD53G-5HacD2HnD
No go, same as 7.7
Can I have some more details please, my Chateau LTE12 is running 7.8rc3 testing without issues, what issues have you seen on 7.7 and 7.8 stable?
Are you updating Routerboard as well as RouterOS, kernel failure usually means your Routerboard version is causing an incompatibility with RouterOS.

Finally I found the problem. When I try install 7.7 something went wrong and I get 0 hdd free space.
Netinstall solved the problem but from beginning of my journey with this router it was 3rd time when I was forced to used it :(
Now I'm on 7.8 and it looks good, especially after LTE modem firmware upgade.

biomesh · Wed Mar 01, 2023 1:45 am

Upgraded the following with no issues (been running over 34 hours)

ccr2004-16g-2s+, crs317, crs326-24g, crs112, cap ac, chr, crs318

nichky · Wed Mar 01, 2023 1:48 am

nichky - What kind of an issue do you refer to? Contact support@mikrotik.com and please leave this topic strictly related to the issues introduced in. v7.8 that were not present in v7.7.

i'm about to do that, before that that , can you confirm whether Route-Reflector works together with VRF on v7.8?

sirca · Wed Mar 01, 2023 3:48 am

Hi,
I upgraded packages and firmware from 7.7 to 7.8 on:
CRS317
CRS305
CRS326-24G-2S+
From winbox gui, on ALL devices, are NOT reported neither "write-sect-total" nor "write-sect-since-reboot", but ARE reported in cli /system/resource/print
CHR (esxi) with "the dude", and the Windows client, after upgrade all seems OK.
Best Regards from Rome
Andrea

Simonej · Wed Mar 01, 2023 4:49 am

iPhone 12 with iOS 16.3.1 cannot connect to WiFi if wpa3-psk is enabled.

Which MT device? Try to forget and reconnect to the network.

PS: @MikroTik Staff, Audience devices with Wifiwave2 package are affected, from around v7.4, by an error at every reboot;

system,error,critical RBD25G-5HPacQD2HPnD: error while running customized default configuration script: bad command name wireless (line 985 column 25)

noticed on different devices, should not be related to my config, would be nice to have it fixed.
Are you aware of it? Or you need the tickets?

Wed Mar 01, 2023 8:02 am

I believe the root cause of that problem has been detected already in the past but somehow it slipped in again in one of the next beta-versions.

Found it:
See here viewtopic.php?t=188851#p955106
And then some posts down it is being discussed as well.

The solution is in post 96 of that same thread.

You could send that info to support, maybe someone will finally listen ;)

lluu131 · Wed Mar 01, 2023 8:04 am

and after inquiring if this was expected behaviour I got
.
I didn't push any further since I don't need IGMP snooping ¯\_(ツ)_/¯. I consider it a bug, though.
How it is an OSPF bug if igmp snooping is blocking?
You can add static MLD entries for all the addresses ospfv3 is using
https://help.mikrotik.com/docs/display/ ... centries.1
Code: Select all
/interface bridge mdb
add bridge=bridge1 group=ff02::5 ports=bridge1,ether2,ether3,ether4,ether5
add bridge=bridge1 group=ff02::6 ports=bridge1,ether2,ether3,ether4,ether5

Unfortunately, after setting the MDB entry in this way, ospfv3 does not work after snooping is turned on

ZupoLlask · Wed Mar 01, 2023 9:26 am

Sorry but that's not how I see it.
That position has been taken by RB5009 already last year.

The fact you don't like it, I completely understand. But it is what it is.

Is there a RB5009 with wireless?

Even if there is, what is the point of debating RB4011 vs RB5009 if there are older (and cheaper) products working without (major) issues with wifi2 package?

quadrifoglio · Wed Mar 01, 2023 11:02 am

RB750Gr3 - containers inside docker does not resolving local domains, says "bad address" and nslookup return some error with NXDOMAIN. Version 7.7 and older works fine.

bronco · Wed Mar 01, 2023 12:16 pm

The OVPN service is unstable, and it will cause a Kernel crashes after 2,3 hours of uptime.
SUP-96432

Observed this also here on a heX S. Version 7.7 ran flawlessly for weeks without any interruption, but 7.8 is an instability improvement concerning OVPN. :-(

Regards,
bronco

obscurus · Wed Mar 01, 2023 12:21 pm

The OVPN service is unstable, and it will cause a Kernel crashes after 2,3 hours of uptime.
SUP-96432

The same issue, but without Kernel crashes and any errors in log.
RB5009, udp ovpn client, BGP.
After 2 hours of uptime, traffic stops going into the ovpn-tunnel (ovpn client shows "Connected" and server tunnel ip get ping answer). Enabling/disabling the ovpn-interface does not solve the problem (shows "Connected"). Only reboot routerboard resolve it. But at the same time, when you click on the reboot, the router continues to work for about 40-60 seconds (usually the router goes into reboot instantly). Downgrade to v7.7 - none of the above problems!

RB750Gr3:
Wireguard+BGP - no issue on v7.8.

pe1chl · Wed Mar 01, 2023 12:22 pm

RB750Gr3 - containers inside docker does not resolving local domains, says "bad address" and nslookup return some error with NXDOMAIN. Version 7.7 and older works fine.

That report is much too vague and the problem is probably due to your own local configuration.

uCZBpmK6pwoZg7LR · Wed Mar 01, 2023 1:31 pm

Plase fix VPRN route reflector

gigabyte091 · Wed Mar 01, 2023 3:11 pm

Can report that on ax2 wifi is a little more stable but still devices sometimes disconnects for no reason. ax3 works just fine.

Note · Wed Mar 01, 2023 3:47 pm

chateau lte18 with basic setup works fine after upgrade.

Ramas · Wed Mar 01, 2023 4:47 pm

Also found minor bug on RB5009UPr+S+.
Buttons that do nothing in WinBox:

SystemHealth.png

gabacho4 · Wed Mar 01, 2023 5:53 pm

Curiously my RB5009UG only shows CPU temperature for system health. No PoE in voltage, no 2 pin voltage, no jack voltage, no board temperature...that's weird to me given that they are the same hardware minus PoE out.

rextended · Wed Mar 01, 2023 5:56 pm

"minus"...

wifi442 · Wed Mar 01, 2023 6:03 pm

/mpls traffic-eng path
Entries are still not working in WinBox. CLI only. This was reported back in early December if I recall.

DeGlucker · Wed Mar 01, 2023 8:20 pm

x86 WiFi Atheros AR-9380 still doesn't work. Forced to roll back to 7.6 again...

Joseph · Wed Mar 01, 2023 8:53 pm

HALNy HL-GSFP on RB4011 – doesn't work :(

Wakes up but can't connect to ISP. On 7.7 works fine.

tigran · Wed Mar 01, 2023 9:34 pm

Hello,

LtAP router with factory fitted R11e-LTE6 and another extra R11e-LTE6 module in the upper mini-PCIe slot.
After each reboot/restart top modem hangs up and is not reachable. USB bus reset helps (each time).
The possible initialization race condition with the dual R11e-LTE6 modem setup is reproduced and fixed, fix will be included in the next RouterOS v7 releases.

As an alternative to USB power reset, the following modem "re-plug" script can be used (copy/paste in CLI):
Code: Select all
/system script remove [find name=ltap_dual_lte_enabler]
/system script add dont-require-permissions=yes name=ltap_dual_lte_enabler policy=read,write source="\
    :local iTimeout 60\r\
    \n\r\
    \n:local iLoop 0\r\
    \n:while ([/interface/lte/print as-value count-only]!=2 and \$iLoop<\$iTimeout) do={\r\
    \n  :set iLoop (\$iLoop+1)\t\t\r\
    \n  :delay 1s\r\
    \n  }\r\
    \n:if ([/interface/lte/print as-value count-only]=2) do={\r\
    \n  :local usbType [/system/routerboard/usb/get type]\r\
    \n  :log info \"setting USB to USB-type-A\"\r\
    \n  :put \"setting USB to USB-type-A\"\r\
    \n  /system routerboard usb set type=USB-type-A\r\
    \n  :delay 1s\r\
    \n  :log info (\"restoring initial USB type setting: \".\$usbType)\r\
    \n  :put (\"restoring initial USB type setting: \".\$usbType)\r\
    \n  /system routerboard usb set type=\$usbType\r\
    \n  }\r\
    \n:log info \"script ended\"\r\
    \n"
/system scheduler remove [find name=ltap_dual_lte_enabler]
/system scheduler add name=ltap_dual_lte_enabler on-event=ltap_dual_lte_enabler policy=read,write start-time=startup
This will be faster and will not reset the modem or another device without necessity.

Dear Artis,

We have checked the script, but unfortunately this script resets the only working modem (lte1), but the non-working modem (lte2) is still there and w/o any changes.
I have reworked and this helps:

# RouterOS 7.8 bug workaround
:do {
	:set $msg "Checking if lte1 is alive...";
	:log info message="$msg"; :put "$msg";
	/interface lte at-chat lte1 input="AT";
} on-error={
	:set $msg "lte1 is dead, resetting usb bus(0)...";
	:log error message="$msg"; :put "$msg";
	/system routerboard usb power-reset bus=0 duration=1s;
	:delay 45s;
}
:do {
	:set $msg "Checking if lte2 is alive...";
	:log info message="$msg"; :put "$msg";
	/interface lte at-chat lte2 input="AT";
} on-error={
	:set $msg "lte2 is dead, resetting usb bus(0)...";
	:log error message="$msg"; :put "$msg";
	/system routerboard usb power-reset bus=3 duration=1s;
	:delay 45s;
}

kriszos · Wed Mar 01, 2023 10:04 pm

CRL checking on ikev2 with digital-signature is still broken SUP-108118

nickcarr · Wed Mar 01, 2023 11:01 pm

Hi.
Thanks for replying me. And sorry 'cause i'm late.
I updated them after the downgrade. And now it goes fine.

denisnk - Thank you for your report. Although it is not version related. We will try to fix this as soon as possible. Yes, several devices might not show this on WinBox.
parham - Please contact us through support@mikrotik.com. These files are not missing on upgrade servers. We would like to figure out what is going on here with your router.
nichky - What kind of an issue do you refer to? Contact support@mikrotik.com and please leave this topic strictly related to the issues introduced in. v7.8 that were not present in v7.7.
Babujnik, tigran, fornuftFTW, strzinek, dlemery - We will look into this.
ErfanDL, jovaf32128, benkreuter, verbovet, nickcarr, SumNathan, blacksnow - Please send supout.rif file from this router running v7.8 to support@mikrotik.com.
Pl07R3K - We do not increase packages for some particular reason. Packages grow with extra functionality that is added and requested by our users. We do our best that each and every router can be upgraded without problems with the RouterOS package installed. The upgrade is working properly for each and every model device that we manufacture at the moment with pre-defined packages installed (GPS< WifiWave2, etc.) and default configuration running.
darklord - I can not reproduce the problem. Please contact us through support@mikrotik.com so we can find the root cause of this issue.
ToTheCLI - Thank you for your report. We will look into this.
lluu131 - Please see this - viewtopic.php?t=192529#p987012
sirca - No, you can use this version with CRS as well.
Nadol - Why? There was no problem description.
murrayis - We can only repeat that this is a work in progress. It will be ready when it will be ready. Unfortunately, using release topics in order to raise this question will not help in any way. So please, stick with the main purpose of these topics - discovering issues introduced in the particular release.

nichky · Wed Mar 01, 2023 11:56 pm

Plase fix VPRN route reflector

what is wrong with that?

obscurus · Thu Mar 02, 2023 7:15 am

The OVPN service is unstable, and it will cause a Kernel crashes after 2,3 hours of uptime.
SUP-96432
The same issue, but without Kernel crashes and any errors in log.
RB5009, udp ovpn client, BGP.
After 2 hours of uptime, traffic stops going into the ovpn-tunnel (ovpn client shows "Connected" and server tunnel ip get ping answer). Enabling/disabling the ovpn-interface does not solve the problem (shows "Connected"). Only reboot routerboard resolve it. But at the same time, when you click on the reboot, the router continues to work for about 40-60 seconds (usually the router goes into reboot instantly). Downgrade to v7.7 - none of the above problems!

RB750Gr3:
Wireguard+BGP - no issue on v7.8.

Change OVPN udp to tcp - fix an issue. RB5009 now on v7.8. udp OVPN very unstable...

Maggiore81 · Thu Mar 02, 2023 7:34 am

Maggiore81 - Why do you say so? If we sum up the topic, then basically we have found out that few SFP modules are not working properly, which were working on v7.7. Rest of the issues discussed here are already known issues from previus versions, misconfiguraiton, or minor bug reports about trivial issues or issues from older versions (not introduced in 7.8 ). Of course many posts are not realted to release at all.

Sorry for my "rude" post, but I am using and testing the v7 release from the beginning.
Are some big issues that seriously limit the usage of this firmware. I dont speak about missing features, that is understable.
L3-HW is a known issue, that is one of the main highlights for the v7 release.

I use in production the 7.7 everywhere, some things were running well in 7.4.1 , I love upgrading and keep current, but there is a long series of updates and new features, and regularry each version change there are a lot of issues.

why dont you take a 7.x and then just BUGFIX that version to finally release a LTS ? why everytime just add a bunch of new features without fixing the previous issues? I dont think that is a productive way to build a software.

I love MT, I am also a trainer and diffuse mikrotik's verb everywhere... but it begins to become a difficult way to use them since I am no longer sure of the stability of the units in the long term.
for this reason we use a scheduled reboot for our routers, to avoid issues. We use scripts for the l3-hw restart, for a period reboot of the 4011s... and so on.
Please choose a release and bugfix it. 7.7.1 7.7.2 etc... going up is really bad since we introduce new features, keep the old bugs and introduce new...

just my 2 cents.

garlicbulb · Thu Mar 02, 2023 8:52 am

RB751U-2Hn running 7.7. Tried to upgrade twice. Same result.

Mar/01/2023 22:18:29
mar/01/2023 22:18:55 system,error,critical kernel failure in previous boot
mar/01/2023 22:18:55 system,error,critical out of memory condition was detected
mar/01/2023 22:20:28 system,error,critical,,,,,,,,,radius error while running cust
omized default configuration script: std failure: timeout (13)
mar/01/2023 22:38:55 system,critical,info cloud change time Mar/01/2023 22:22:23 =
> Mar/01/2023 22:38:55

Free memory is 7.1MB on 7.7
/radius print comes back blank on 7.7

chubbs596 · Thu Mar 02, 2023 9:58 am

BFD!!!!! WHEN!!!! Come on guys - If you are having issues deploying it tell us!

A lot of us have fleets of CCR2004 we cannot use or if we are using them they are so unstable but we cannot go to v7 without BFD!

+10, Real Production BGP network requires BFD

lurker888 · Thu Mar 02, 2023 10:39 am

Dear fellow Mikrotik users,

I am running an RB5009 with 7.8 stable. (Firmware also upgraded.)

There is a long standing problem with unicast addressing of DHCP requests when a relay is used, fixed according to the changelog:
*) dhcpv4-client - send DHCPv4 unicast requests to DHCPv4 relay, instead of server when it is being used;

Apperently it is not fixed.

First I obtain an IP address according to the following reply:

Mar/01/2023 23:56:07 dhcp,debug,packet debug: dhcp-client on vlan1000-wan received ack with id 3593833787 from 89.133.164.82
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     hops = 2
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     flags = broadcast
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     ciaddr = xxx
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     yiaddr = xxx
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     siaddr = 80.244.108.182
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     giaddr = 89.133.164.82
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     chaddr = DC:2C:6E:48:95:18
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     Subnet-Mask = 255.255.255.0
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     Unknown(2) = 00-00-0E-10
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     Router = 178.48.233.254
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     Unknown(4) = 50-F4-6C-B6
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     Domain-Server = 80.244.99.37,80.244.99.36
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     Domain-Name = "chello.hu"
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     Address-Time = 86400
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     Msg-Type = ack
Mar/01/2023 23:56:07 dhcp,debug,packet debug:     Server-Id = 80.244.108.182
Mar/01/2023 23:56:07 dhcp,debug,state debug: dhcp-client on vlan1000-wan entering <bound> state

Clearly, server address (siaddr) is 80.244.108.182 and relay address (giaddr) is 89.133.164.82.

When I manually instruct the device to renew this address, the following is logged:

Mar/01/2023 23:56:12 dhcp,debug,state debug: dhcp-client on vlan1000-wan entering <renewing...> state
Mar/01/2023 23:56:12 dhcp,debug,packet debug: dhcp-client on vlan1000-wan sending request with id 3593833787 to 80.244.108.182
Mar/01/2023 23:56:12 dhcp,debug,packet debug:     ciaddr = xxx
Mar/01/2023 23:56:12 dhcp,debug,packet debug:     chaddr = DC:2C:6E:48:95:18
Mar/01/2023 23:56:12 dhcp,debug,packet debug:     Host-Name = "xxx"
Mar/01/2023 23:56:12 dhcp,debug,packet debug:     Msg-Type = request
Mar/01/2023 23:56:12 dhcp,debug,packet debug:     Parameter-List = Subnet-Mask,Classless-Route,Router,Static-Route,Domain-Server,NTP-Server,CAPWAP-Server,Vendor-Specific
Mar/01/2023 23:56:12 dhcp,debug,packet debug:     Client-Id = 01-DC-2C-6E-48-95-18
Mar/01/2023 23:56:14 dhcp,debug,packet debug: dhcp-client on vlan1000-wan sending request with id 3593833787 to 80.244.108.182
Mar/01/2023 23:56:14 dhcp,debug,packet debug:     secs = 2
Mar/01/2023 23:56:14 dhcp,debug,packet debug:     ciaddr = xxx
Mar/01/2023 23:56:14 dhcp,debug,packet debug:     chaddr = DC:2C:6E:48:95:18
Mar/01/2023 23:56:14 dhcp,debug,packet debug:     Host-Name = "xxx"
Mar/01/2023 23:56:14 dhcp,debug,packet debug:     Msg-Type = request
Mar/01/2023 23:56:14 dhcp,debug,packet debug:     Parameter-List = Subnet-Mask,Classless-Route,Router,Static-Route,Domain-Server,NTP-Server,CAPWAP-Server,Vendor-Specific
Mar/01/2023 23:56:14 dhcp,debug,packet debug:     Client-Id = 01-DC-2C-6E-48-95-18
Mar/01/2023 23:56:18 dhcp,debug,state debug: dhcp-client on vlan1000-wan entering <rebinding...> state
Mar/01/2023 23:56:18 dhcp,debug,packet debug: dhcp-client on vlan1000-wan sending request with id 3593833787 to 255.255.255.255
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     flags = broadcast
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     ciaddr = xxx
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     chaddr = DC:2C:6E:48:95:18
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     Host-Name = "xxx"
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     Msg-Type = request
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     Parameter-List = Subnet-Mask,Classless-Route,Router,Static-Route,Domain-Server,NTP-Server,CAPWAP-Server,Vendor-Specific
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     Client-Id = 01-DC-2C-6E-48-95-18
Mar/01/2023 23:56:18 dhcp,debug,packet debug: dhcp-client on vlan1000-wan received ack with id 3593833787 from 89.133.164.82
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     hops = 2
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     flags = broadcast
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     ciaddr = xxx
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     yiaddr = xxx
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     siaddr = 80.244.108.182
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     giaddr = 89.133.164.82
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     chaddr = DC:2C:6E:48:95:18
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     Subnet-Mask = 255.255.255.0
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     Unknown(2) = 00-00-0E-10
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     Router = 178.48.233.254
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     Unknown(4) = 50-F4-6C-B6
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     Domain-Server = 80.244.99.37,80.244.99.36
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     Domain-Name = "chello.hu"
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     Address-Time = 86400
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     Msg-Type = ack
Mar/01/2023 23:56:18 dhcp,debug,packet debug:     Server-Id = 80.244.1,08.182
Mar/01/2023 23:56:18 dhcp,debug,state debug: dhcp-client on vlan1000-wan entering <bound> state

Clearly, the wrong unicast address 80.244.108.182 is tried two times, then the device reverts to broadcast, which succeeds.

Now, this may seem only a cosmetic problem, because it only delays acquiring the address by approximately 5 seconds. What makes the problem MUCH worse, is that when an automatic renewal is done at 0.5 * lease time, 0.75 * lease time etc., ONLY unicast is attempted (to the wrong address,) unsuccessfully of course, and broadcast is only attempted after the lease time has fully elapsed and the IP address is lost. This means that a device acquiring an address via DHCP loses its IP address for 5-10 seconds every lease-time interval. This is a big problem.

I would suggest to implement the fix as per the changelog, and also to attempt broadcast even on automatic renewals.

Best regards.

(P.S. New to forum, and previously posted in wrong place.)

cyayon · Thu Mar 02, 2023 11:23 am

Hi,
The gpon sfp module FS GPON-ONU-34-20BI is correctly detected and seems to work properly on CRS-305 with ROS 7.8.

pcunite · Thu Mar 02, 2023 3:08 pm

Why don't you take a 7.x and then just BUGFIX that version to finally release a LTS? Why every time just add a bunch of new features without fixing the previous issues? I don't think that is a productive way to build software. I love MT, I am also a trainer and diffuse Mikrotik's verb everywhere ... but it begins to become a difficult way to use them since I am no longer sure of the stability of the units ...

I operated a software firm for a while, so I have some, however little, experience with shipping software. You are indeed correct that super massive firmware releases make products unstable. A change log with 50 items means broken software every time. MikroTik has been around a while. They were developing and shipping before modern programming disciplines became mainstream.

That's understandable. But it will be difficult for them to make the internal culture change to accommodate a stability track (aka long term). It has to start at the top. It will need to be a C level decision. But change is hard. Much easier to throw a bunch of stuff at the wall to see what sticks vs. testing regressions. I think testing their type of product is really hard and why the slow down of a LTS version would be very helpful.

si458 · Thu Mar 02, 2023 4:34 pm

i see the same issue as others with missing write sector
not visible in winbox app or winbox mobile app
but its visible via command line
hAP ac2 - RBD52G-5HacD2HnD - 7.8

Screenshot 2023-03-02 142818.png

uCZBpmK6pwoZg7LR · Thu Mar 02, 2023 4:54 pm

Plase fix VPRN route reflector

what is wrong with that?

mikrotik transmit self instead of learned NEXT_HOP value and ignore propagate setting for vrf route. Due to it VPRN completely broken

qbic · Thu Mar 02, 2023 9:43 pm

Flashed RB4011, after improper shutdown router didn't booted correctly and was very hot after one hour.
I've rebooted and it started properly.

On the note, I've set CPU frequency to AUTO (as warning was stating that 1400 is wrong).

I do not want to speculate as I do not have equipment to check - seems that auto freq is not working properly all the time/during boot?

manojlovicl · Thu Mar 02, 2023 10:36 pm

- CHR freezes after 2 hours with 180+ OVPN connections - unresponsive also in console
- OVPN connections are duplicating (it happened before but now it happens sooner)
- OVPN server and client change cipher from null to aes 128 gcm
- it somehow changed the path for my container from disk2 to slot1-par1 - but container does not start any more... :(

BrianHiggins · Fri Mar 03, 2023 1:54 am

I too am dying waiting for a LT release of v7. I had been waiting for bug fixes for webfig and branding maker for well over 2 years that had stopped me from updating because they never made it into a long term release, that's still stick at v6.48.6. I was recently forced to adopt a mix of v6.49.7 and v7.7 due to not being able to wait for the fixed to make it into a v6 LT release and also needing to support some of the new CCR2116 and CCR2004 routers, so v7...

This means that for the first time since the introduction of the Long Term branch of the OS back in 2015 that I've installed a Stable release anywhere, and it's now deployed to every device I manage (which btw is measured in thousands). NONE of these new features matter to me, I have no need for Wireguard, WAVE2, ROSE, or Containers, and I don't care about USB support, but I do need a rock solid reliable OS that runs PPPoE (client and server) and doesn't break SFP modules that previously worked. Routing protocols matter (it's a router!), firewall matters, and tunnels matter. Beyond that I'd be thrilled if everything else was added through separate packages like in the old days. I understand why people want and use these other packages, and I have no complaint against them being developed and supported, but I can't even disable wireguard, yet I'd rather it didn't even exist on my devices so that I can run my devices as lean and clean as possible without unnecessary packages that aren't going to be utilized and may or may not introduce stability bugs or vulnerabilities in the platform. Lastly, I REALLY don't want to have important updates and core functionality bug fixes delayed or unnecessary updates released because of extraneous features that simply don't apply to the core functionality of routing and firewalling.

For now I'm trying to keep a fleet of devices running reliably on the stable releases until we get a reliable LT release again. I really miss the days of testing and validating only one or two updates in a year for deployment.

@Normis & Team, PLEASE focus efforts first and foremost on making the core routing, firewalling, and tunnel capabilities of RouterOS, as well as SFP and interface compatibility and reliability and provide that in a LT release as soon as possible. It feels like you're close, but it's not quite there yet. Once any/all bugs are worked out in the core functions, the remainder of the extraneous features can be worked on in the dev and stable trees while those of us that just need our devices to route & switch can do so without fear.

nichky · Fri Mar 03, 2023 3:36 am

Hello!

Thank you for the report.
There is known issue with ibgp-rr which is not fixed yet.

Best Regards,
Olga Ļ.

Thanks for the quick response MikroTik!!

actck · Fri Mar 03, 2023 3:48 am

Why don't you take a 7.x and then just BUGFIX that version to finally release a LTS? Why every time just add a bunch of new features without fixing the previous issues? I don't think that is a productive way to build software. I love MT, I am also a trainer and diffuse Mikrotik's verb everywhere ... but it begins to become a difficult way to use them since I am no longer sure of the stability of the units ...

I operated a software firm for a while, so I have some, however little, experience with shipping software. You are indeed correct that super massive firmware releases make products unstable. A change log with 50 items means broken software every time. MikroTik has been around a while. They were developing and shipping before modern programming disciplines became mainstream.

That's understandable. But it will be difficult for them to make the internal culture change to accommodate a stability track (aka long term). It has to start at the top. It will need to be a C level decision. But change is hard. Much easier to throw a bunch of stuff at the wall to see what sticks vs. testing regressions. I think testing their type of product is really hard and why the slow down of a LTS version would be very helpful.

Don't you feel the resentment on this forum? Yes, mikrotik choose a "Understandable" way and got these all "praise".

oliviu56 · Fri Mar 03, 2023 5:08 am

With the release of versions 7.7, but also with version 7.8, the wifi signal strength dropped dramatically by approximately 15-20% compared to version 7.6, both for the 2.4 band and for the 5Ghz band. I use hap ax2. I downgraded to 7.6 every time. I mention that the tests are done from a laptop located about 3-4 m from the router. I tried to change channels and frequency without success. With version 7.6, randomly, after a few days, I noticed a total disconnection of all devices connected to the router. Every time, after restarting the router, the devices reconnected. I live in Romania.

Pl07R3K · Fri Mar 03, 2023 8:37 am

Pl07R3K please write to support@mikrotik.com ,let us know what security profile settings you have configured, and share a supout.rif file with us, made after a connection attempt.

Done, SUP-109576

Jotne · Fri Mar 03, 2023 9:13 am

I too am dying waiting for a LT release of v7.

In another thread MT did write that next version would be 7.9
I and many other would like to see a long time release, so next version should be 7.8.1 (maybe alongside with 7.9)

mkx · Fri Mar 03, 2023 9:24 am

Unlike many vocal individuals, who express their opinions on LT version of ROS v7 around here, I can fully understand why MT doesn't release LT version of v7. This forum is full of reports of bugs, missing functionality and what not. And until most of those complaints are closed, ROS v7 is under very active development. It would be a complete waste of devs' resources to try to maintain a randomly-chosen half-baked v7 release in long term. I can imagine heaps of complaints from LT v7 users about bugs and missing features that might get "frozen" in "that" LT version.

Yes, I can feel the pain of owners of v7-only devices, but I don't see a way out.

vecino · Fri Mar 03, 2023 11:45 am

OSPFv2: crypto sequence invalid spam log

ROUTE,OSPF,WARNING	SSX0123-v2 { version: 2 router-id: 10.20.30.1 } backbone-v2 { 0.0.0.0 } interface { broadcast 10.107.***.***%vlan1030 } neighbor { router-id: 10.107.**.** state: Full } crypto sequence invalid

-

OSPFv3: authentication md5 Mikrotik vs FRRouting not working

ROUTE,OSPF,WARNING	SSX0123-v3 { version: 3 router-id: 10.20.20.1 } backbone-v3 { 0.0.0.0 } interface { broadcast fe80::****:34ff:fe0a:****%ether6 } corrupted auth trailer from fe80::****:b5f7:****:f8d7%*6

Jotne · Fri Mar 03, 2023 12:09 pm

I can fully understand why MT doesn't release LT version of v7. This forum is full of reports of bugs, missing functionality and what not.

There are no reason for MT to keep working on 7.8.1, 7.8.2 etc without adding any new functionality, just fix bugs
Then at 7.8.50 they see that there are no more outstanding bug, call it LT
7.9 is for new functions.

pe1chl · Fri Mar 03, 2023 12:12 pm

I can fully understand why MT doesn't release LT version of v7. This forum is full of reports of bugs, missing functionality and what not.
There are no reason for MT to keep working on 7.8.1, 7.8.2 etc without adding any new functionality, just fix bugs

Of course the reason not do do that it that it means extra work, to backport all fixes to an older version without introducing new functions and bugs.
That requires extra developers, and they already are short on those.

actck · Fri Mar 03, 2023 12:43 pm

There are no reason for MT to keep working on 7.8.1, 7.8.2 etc without adding any new functionality, just fix bugs
Of course the reason not do do that it that it means extra work, to backport all fixes to an older version without introducing new functions and bugs.
That requires extra developers, and they already are short on those.

I think what they lack is not a developer but a core developer. So they can't fix the core routing problem but add new features over and over again.
Who cares about that features? Are you all short of a linux machine to do what ever docker stroage unbound and any others ?

Rox169 · Fri Mar 03, 2023 1:17 pm

@actck
you have 2 posts and you are such clever....I do welcome new feature, I have only few devices feom MT but I laready use QOS CAKE, ZEROTIER,WIREGUARD almost all new features introduced in v7. And it is pretty stable on my setup. I do understand it is problem for big ISP that some features are not sorted yet but they can use v6. Just install version 6 and wait for long term version 7.

Larsa · Fri Mar 03, 2023 2:37 pm

I'm all in for a "true" well tested LTS as soon as they get the BFD and the rest of the v6 stuff on board the v7 train.

hecatae · Fri Mar 03, 2023 3:07 pm

With the release of versions 7.7, but also with version 7.8, the wifi signal strength dropped dramatically by approximately 15-20% compared to version 7.6, both for the 2.4 band and for the 5Ghz band. I use hap ax2.

Can I recommend you move to the testing branch for your ax2, it'll require a little more involvement but you will be able to push issues regarding the new wifi6 devices and instead of seeing this on the stable branch, the team producing the testing releases will be aware of wifi degradation for wifi6 devices, which is affecting new products.

So as soon as the new testing release is out, test, compare to 7.6, if issues post in the testing topic, advise why you are going back to 7.6 if wifi degradation is still an issue.

spippan · Fri Mar 03, 2023 4:28 pm

I do need a rock solid reliable OS that runs PPPoE (client and server) and doesn't break SFP modules that previously worked. Routing protocols matter (it's a router!), firewall matters, and tunnels matter. Beyond that I'd be thrilled if everything else was added through separate packages like in the old days. I understand why people want and use these other packages, and I have no complaint against them being developed and supported, but I can't even disable wireguard, yet I'd rather it didn't even exist on my devices so that I can run my devices as lean and clean as possible without unnecessary packages that aren't going to be utilized and may or may not introduce stability bugs or vulnerabilities in the platform. Lastly, I REALLY don't want to have important updates and core functionality bug fixes delayed or unnecessary updates released because of extraneous features that simply don't apply to the core functionality of routing and firewalling.

@Normis & Team, PLEASE focus efforts first and foremost on making the core routing, firewalling, and tunnel capabilities of RouterOS, as well as SFP and interface compatibility and reliability and provide that in a LT release as soon as possible. It feels like you're close, but it's not quite there yet. Once any/all bugs are worked out in the core functions, the remainder of the extraneous features can be worked on in the dev and stable trees while those of us that just need our devices to route & switch can do so without fear.

SPOT ON.
i am eager to see that again like in v5 and (especially) v6 days.
no need for fancy storage additions as long as new CCRs are not capable of being used, as the name suggests, in a CORE network!!

spippan · Fri Mar 03, 2023 4:36 pm

@actck
you have 2 posts and you are such clever....I do welcome new feature, I have only few devices feom MT but I laready use QOS CAKE, ZEROTIER,WIREGUARD almost all new features introduced in v7. And it is pretty stable on my setup. I do understand it is problem for big ISP that some features are not sorted yet but they can use v6. Just install version 6 and wait for long term version 7.

your 3 mentioned features are not only almost but only introduced with v7

and "...Just install version 6 and wait..." is not suitable for recent devices. i do not know if you knew, but also some v6/v7 devices are not able to run v6 if they are shipped and FACTORY INSTALLED with v7! (i got 3 CCR2004-1G-12S+2XS which i cannot operate with v6 because of that very reason!!)
and i hope the 3 ccr1072 which i am still waiting for are able/eligible to run with v6!)

verbovet · Fri Mar 03, 2023 4:58 pm

My problem with dhcp-client was resolved by the support. It turned out that in ver. 7.8 Mikrotik fixed RFC compliance and my incorrect configuration, which had been working before for years, stopped working. The error in the configuration was that the route to the dhcp server of one of my two ISPs went through the wan of the other ISP.

oliviu56 · Fri Mar 03, 2023 5:36 pm

With the release of versions 7.7, but also with version 7.8, the wifi signal strength dropped dramatically by approximately 15-20% compared to version 7.6, both for the 2.4 band and for the 5Ghz band. I use hap ax2.
Can I recommend you move to the testing branch for your ax2, it'll require a little more involvement but you will be able to push issues regarding the new wifi6 devices and instead of seeing this on the stable branch, the team producing the testing releases will be aware of wifi degradation for wifi6 devices, which is affecting new products.

So as soon as the new testing release is out, test, compare to 7.6, if issues post in the testing topic, advise why you are going back to 7.6 if wifi degradation is still an issue.

But I'm not the first to notice these issues related to the decrease in wifi signal once with the upgrade to 7.7 and 7.8. No fix, no solution. I repeat, I don't even have advanced knowledge in this field....

HomePadington · Sat Mar 04, 2023 1:28 am

5 Ghz wi-fi interface on HAP AX2 does not work after update(

Rox169 · Sat Mar 04, 2023 2:18 am

mine 5Ghz is working on AX2 and even AX3....

raphaps · Sat Mar 04, 2023 5:45 am

The OVPN service is unstable, and it will cause a Kernel crashes after 2,3 hours of uptime.
SUP-96432

I'm having the same problem here, on an RB4011. After updating to 7.8, the system has a kernel error and restarts before completing 5 minutes of uptime. I have about 150 ovpn connections.

HomePadington · Sat Mar 04, 2023 8:06 am

mine 5Ghz is working on AX2 and even AX3....

could you send wi-fi settings for aх2 ?

Sat Mar 04, 2023 8:09 am

No offense but can you please create separate thread and continue discussion about that particular topic there ? It's likely not a problem related to this specific release.
And I see you already posted the same problem in another thread. Doesn't help either to post multiple times the same thing. Info gets spread all around then.

own3r1138 · Sat Mar 04, 2023 9:56 am

I'm having the same problem here, on an RB4011. After updating to 7.8, the system has a kernel error and restarts before completing 5 minutes of uptime. I have about 150 ovpn connections.

https://www.youtube.com/watch?v=XhI2dNzRpHY

mk47 · Sat Mar 04, 2023 2:20 pm

This update broke my containers because disk1 was automatically renamed to usb1-part1 for some reason, and then disk1 was automatically re-added, so the update corrupted all the paths.

When I try to change the container root dir, I just the error "Couldn't change Container - Can't change root directory. (6).

How do I fix the bug?

Broke my Pihole as well, so I deleted old container and this is what I did to get it back up:
1. In Container/Mounts I changed src path to point to new directories, so "disk1" to "usb1-part1"
2. In Container/Config changed "temp dir" path to something new, doesn't really matter where you point it since it is only a temp destination for downloads
3. In command line when creating containers I changed "root-dir=disk2/pihole" to "root-dir=usb1-part1/pihole"
In short you have point to new paths by changing old disk name to a new disk name...
Then just recreated container and it is back up. Luckily Pihole on my CCR2004+ is only a back up to my Pihole running on Raspberry PI, so didn't cause me too much headache. But clearly not a good idea to run containers on Mikrotiks for important services...

qbic · Sat Mar 04, 2023 6:56 pm

So it seems I was wrong. On latest firmware RB4011 starts randomly, sometimes it boots normally, sometimes it hangs. I bought serial cable ... just to see what is happening during boot.

(if you are lucky... RB4011 in netinstall shows "READY" and clicking install just shows "Sending offer..." and then nothing happens - it stays in READY state)

My recommendation is to stay away from this version if you have RB4011 rev2. I've bricked my device by upgrade. Do not upgrade internal firmware. ...I'm probably left with paperweight.

Jotne · Sat Mar 04, 2023 10:19 pm

It does the same with default config and after nestinstall? If yes, I do agree its a problem.
I do suggest that you try that before your trow it away, or give it to me.

qbic · Sat Mar 04, 2023 10:45 pm

Sadly yes. Once I've managed to do "format" and system transfer. It stays in same - "dead mode"... with some random-luck possibility of doing "netinstall" with same outcome.

I'm waiting for console cable (RS232 <-> RJ45) just to see if there is anything left to do.

damadmai · Sun Mar 05, 2023 12:18 am

and "...Just install version 6 and wait..." is not suitable for recent devices. i do not know if you knew, but also some v6/v7 devices are not able to run v6 if they are shipped and FACTORY INSTALLED with v7! (i got 3 CCR2004-1G-12S+2XS which i cannot operate with v6 because of that very reason!!)
and i hope the 3 ccr1072 which i am still waiting for are able/eligible to run with v6!)

What happens if you try to downgrade it using this procedure?
https://openwrt.org/toh/mikrotik/common ... g_routeros

tenner · Sun Mar 05, 2023 1:20 am

I upgraded CRS112-8P from v7.7 to v7.8. The router was running all ports in bridge mode (including port 1). After upgrade, port 1 was removed from bridge and was set back up as a WAN port. It also lost static IP for bridge and I had to connect via MAC address after upgrade.

mag1024 · Sun Mar 05, 2023 2:35 am

I have a number of static DNS A entries configured, and they seem to have stopped working in some contexts after upgrading from 7.7 to 7.8.
Specifically, when using DOH as the upstream resolver, the DNS response for a statically configured host entry now appears to contain multiple entries, one valid one, and 2 NXDOMAINs.
This confuses some applications (particularly Home Assistant) such that they are unable to use any hostnames statically configured on the router.

Disabling DOH, and using regular DNS as the upstream restores the functionality:

With DOH upstream (broken):

host livingcam.not.luminal.org 10.0.1.1
Using domain server:
Name: 10.0.1.1
Address: 10.0.1.1#53
Aliases:

livingcam.not.luminal.org has address 10.0.3.106
Host livingcam.not.luminal.org not found: 3(NXDOMAIN)
Host livingcam.not.luminal.org not found: 3(NXDOMAIN)

Without DOH (working):

host livingcam.not.luminal.org 10.0.1.1
Using domain server:
Name: 10.0.1.1
Address: 10.0.1.1#53
Aliases:

livingcam.not.luminal.org has address 10.0.3.106

Is this a RouterOS bug, or is this an intentional change in behavior that is uncovering some misconfiguration on the router -- and, if so, what could it be?

rplant · Sun Mar 05, 2023 10:13 am

This update broke my containers because disk1 was automatically renamed to usb1-part1 for some reason, and then disk1 was automatically re-added, so the update corrupted all the paths.

You can rename the disks (change the name of the slot)
You may need the cli to do it though.

noradtux · Sun Mar 05, 2023 12:01 pm

So it seems I was wrong. On latest firmware RB4011 starts randomly, sometimes it boots normally, sometimes it hangs. I bought serial cable ... just to see what is happening during boot.

(if you are lucky... RB4011 in netinstall shows "READY" and clicking install just shows "Sending offer..." and then nothing happens - it stays in READY state)

My recommendation is to stay away from this version if you have RB4011 rev2. I've bricked my device by upgrade. Do not upgrade internal firmware. ...I'm probably left with paperweight.

Can't confirm. My RB4011iGS+ r2 is running fine von 7.8, including firmware.

spippan · Mon Mar 06, 2023 12:08 am

So it seems I was wrong. On latest firmware RB4011 starts randomly, sometimes it boots normally, sometimes it hangs. I bought serial cable ... just to see what is happening during boot.

(if you are lucky... RB4011 in netinstall shows "READY" and clicking install just shows "Sending offer..." and then nothing happens - it stays in READY state)

My recommendation is to stay away from this version if you have RB4011 rev2. I've bricked my device by upgrade. Do not upgrade internal firmware. ...I'm probably left with paperweight.

using netinstall on windoze or on linux?
since the linux netinstall is available i only use linux version anymore and i got the same response from 2 trainers too.
maybe try that one. (caution "-r" wipes config to defaults!)
good luck

spippan · Mon Mar 06, 2023 12:10 am

and "...Just install version 6 and wait..." is not suitable for recent devices. i do not know if you knew, but also some v6/v7 devices are not able to run v6 if they are shipped and FACTORY INSTALLED with v7! (i got 3 CCR2004-1G-12S+2XS which i cannot operate with v6 because of that very reason!!)
and i hope the 3 ccr1072 which i am still waiting for are able/eligible to run with v6!)
What happens if you try to downgrade it using this procedure?
https://openwrt.org/toh/mikrotik/common ... g_routeros

well ... thanks for that, i need to try that. did not think of looking to openWRT for mikrotik firmware downgrade honestly. thanks in advance

EDIT:
this is the normal way to downgrade firmware on mikrotik. nothing special to see there.
it just does not apply the firmware. console output (rs232) states something like "no can do yada yada below factory firmware..."

ufm · Mon Mar 06, 2023 10:03 am

> zerotier - fixed routes after VRF change;

When will there be a major fix - support for architectures other than ARM/ARM64?

qbic · Mon Mar 06, 2023 11:29 am

using netinstall on windoze or on linux?
since the linux netinstall is available i only use linux version anymore and i got the same response from 2 trainers too.
maybe try that one. (caution "-r" wipes config to defaults!)
good luck

Windoze. At this stage I do not care about config, the problem is that "netinstall" is not even starting, the etherboot port is blinking for like 3-4 seconds and then there is nothing (following official procedures, It was working in the past, using intermediate eth hub and stuff, tried multiple reset button combinations without luck).

Once I've get state where reset created blink on ports (separate blink on two groups of switches) and then it once appeared. Unable to reach that state anymore.... and funny part - warranty expired month ago :)

Mon Mar 06, 2023 11:30 am

Keep pressing reset until it appears in netinstall.