v7.8 [stable] is released!

[depth0cert]

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:

r2:

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


Please, fix it.

[dksoft]

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]

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 - http://forum.mikrotik.com/t/ospf-v3-does-not-work-in-7-7/163595/1
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]

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]

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]

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]

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]

ospf v3 still not working in 7.8

http://forum.mikrotik.com/t/ospf-v3-does-not-work-in-7-7/163595/1

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?

[antonsb]

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

Thanks we will check this

@dksoft

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]

I’ve this problem since v7.7 → https://forum.mikrotik.com/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]

I’ve this problem since v7.7 → https://forum.mikrotik.com/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]

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

I’ve this problem since v7.7 → v7.7 [stable] is released! - Announcements - MikroTik community forum.
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]

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]

Hello,

@ToTheCLI

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]

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]

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

http://forum.mikrotik.com/t/v7-8-stable-is-released/164757/1

[Pl07R3K]

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

[nonolk]

@saimens

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

http://forum.mikrotik.com/t/v7-8-stable-is-released/164757/1

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.

[emilst]

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]

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