v7.11.2 [stable] is released!

[patrickmkt]

I’ve lost my license key!!!

The upgrade to 7.11.1 on my CCR1036-12G-4S went well. However after rebooting for the firmware update, I got a warning that I had no license key and that my router will stop working after 24 hours.
I tried to click on update license key but it did not work.
After a third reboot however the license was back…
I’m glad that I did a monitored update as usually my router is updating automatically. I would have not caught that problem and my script would have not done a third reboot.

[rextended]

usually my router is updating automatically

It’s one of the dumbest things people can do on devices, and it applies to any software (to specify it, it was not understood) not only MikroTik …

Luckily you belong to that club, so at least the first ones who try it, end up in the bag,
while the smartest ones wait a few months before updating/upgrading with a new version.
Anyway there is always someone who tries them as soon as they come out and suffers the consequences…

[Paternot]

So the other question is why did you buy a device for the American market, and then you didn't resell it when you moved to South Africa...

That's an irrelevant and extraneous question (with all due respect). Besides for the fact that Mikrotik as a brand is generally not so popular in the US market, perhaps I did try to sell it and nobody showed

No, it is not irrelevant. In fact, it is the central point of Your problem. By FCC rules, every wireless device sold to the US market MUST have its firmware locked. It can't select wifi rules from other country. As far as I know, it is the only country doing this.

So, all the wifi products (not only Mikrotik) legally sold on the US market cannot change the wifi country. By law. They are made this way because of the FCC - go complain with them.

Do You see the problem? Your US device is locked to the USA wifi rules, because of a law passed. My Mikrotik wifi devices aren´t - because I didn't buy an US version. If You were living on the USA, there was nothing You could do about it - but the device should be sold there. THIS part is your fault.

[Amm0]

If You were living on the USA, there was nothing You could do about it

Nope. FCC is very specific and fines are stiff. A pretty good explanation, and associated rants, is here: https://news.ycombinator.com/item?id=9959088 .

[theosoft]

For me, i can’t see a differnece between 7.11. and 7.11.1. My SonOff devices are not able to connect to WLAN. reverted to 7.10.1, all devices registered again.
Update: I have seen, that the failing devices are trying to get an IP over DHCP (Discover) and after that, restarting with the new IP 0.0.0.0 !!
Maybe, there is a DHCP related issue. Will use Wireshark

[DarkNate]

After upgrading from v7.11 to v7.11.1 my hAP ax2 throws this error
“error while running customized default configuration script no such item”

[rextended]

“error while running customized default configuration script no such item”

= /interface wireless do not exist on wifiwave2

Do not worry, is the same error on defconf I report a year ago the 2022-05-04 17:10:00…
Some spam lines inside the file get-custom-defconf, never removed.
Too many lazy programmers to fix something reported dozen of times, with precise indication on how to solve…

7.5 http://forum.mikrotik.com/t/v7-5-stable-is-released/160518/96
7.6 http://forum.mikrotik.com/t/v7-6-stable-is-released/161553/54
7.9rc http://forum.mikrotik.com/t/v7-9rc-is-released/165607/1

But the MikroTik Staff (still) never gave a damn about it.

No, it’s worse than I remembered, from a search already in RouteroOS 7.2.2 I reported the problem…
7.2.2 http://forum.mikrotik.com/t/v7-2-2-stable-and-v7-2-3-stable-are-released/157734/169
7.9rc http://forum.mikrotik.com/t/v7-9rc-is-released/165607/83

(just checked and the garbage is still present on 7.11.1)

[Kentzo]

If the rules of the State change, it is not MikroTik's job to inform customers, it is assumed that they already know the law, which does not admit ignorance.

I remember reading in change logs that this-or-that regulatory domain was updated up to standards.

Sounds more likely that they pushed newer wireless driver and were in the dark about this change themselves. Which is bad.

[Guscht]

Da smol homenet was updated - no issues

[Paternot]

Nope. FCC is very specific and fines are stiff. A pretty good explanation, and associated rants, is here: https://news.ycombinator.com/item?id=9959088 .

I think You misread my post…

[ZupoLlask]

This is becoming a bumpy 7.11 release…

[spippan]

WG/ChaCha lack support för HW acceleration

which hardware has this in hw-offload?
until now i know of none

[shulfei]

After upgrade from 7.11 to 7.11.1 many my devices can not get IP from DHCP.
Tell me, please, what could be the reason?
Downgrade to 7.11 was fix this problem.

[spippan]

After upgrade from 7.11 to 7.11.1 many my devices can not get IP from DHCP.
Tell me, please, what could be the reason?
Downgrade to 7.11 was fix this problem.

more details would be good.

is the dhcp client a 7.11.1 client or is the dhcp server on 7.11.1? or both?
what was the status on the DHCP server when that happened? (at what part of the DORA sequence it gets stuck?)

[erlinden]

Tell me, please, what could be the reason?

Haven’t seen this behavior on any of my devices. Could you share your config to make sure that is ok? What MikroTik do you use? Do you have firmware upgraded as well?

/export file=anynameyoulike

Remove serial and any other private information like public IP.

[EdPa]

What’s new in 7.11.2 (2023-Aug-31 16:55):
*) dhcp - fixed DHCP server “authoritative” and “delay-threshold” settings (introduced in v7.11.1);

[shulfei]

Thanks all.
After upgrading on 7.11.2 all works.

[felted67]

Hello everyone,

well, update run well - but I got massive problems with VLAN’s and bridging.
VLAN on my main network 192.168.xxx.0/24 run fine, but the other VLANs made massive problems.

It looks like that a port delegated to a special VLAN and set to HW-offload the VLAN-tag, did not
remove the tag at all. I saw that this port (set for SECURE and ALWAYS STRIP) did not remove the tag
and all VLAN’s are visible via TORCH.

I know that a brief description of the network helps a lot, but using lots of mikrotik-devices (about >25 devices)
and 21 VLANS makes the creation of an “easy” network map nearly impossible. This is a semi-production network,
means it is not really production-critical, but used for the internal development.

Also I saw that the VLAN tags on this interface was not editable, meaning all VLAN-settings on the bridge-port
are non editable.

The used systems are RB3011, RB2011, CRS326-24G-2Splus, some CCS and CCR, and also 2x KNOT’s, 3x LORA-devices
and LTE. This is not a really homogenous network, I know, but setting all devices to 7.11.1 give this errors, described
before.

I am in doubt, if my bridge configurations are correct. Running with 7.11 gives no error and the network reacts fine.
After not able to reach some devices (also via CAPS and WLAN), it gives me the choice to roll back to 7.11.

After doing so everything is fine now. After lot of text, here are my main questions:

Doing some update to the bridges in 7.11.1 is there a need to reconfigure the bridge-configuration (RSTP,MRTP etc.) ?
What are the prequisition for using 7.11.1 with bridging along with the changes done in the update of ROS ?

I am thinking about building a virtual network to check out the update to 7.11.1 and the reaction due to my previous
bridge configuration. Working with Mikrotik-devices for about > 15 years, I suppose I am not a bloody newby at all.

Has anyone similar problems with updating to 7.11.1 ?

Thanks in advance !

All comments about my thoughts are welcome…

Greetz…Detlef

[theosoft]

YES. DHCP fix resolved my SonOff DHCP issue. All 32 WLAN clients online

[sindy]

*) bridge - prevent bridging the VLAN interface created on the same bridge;

Even after reading this a few times, I dont know what this means?

The following misconfiguration should not be possible any more:
/interface/vlan/add vlan-id=N interface=bridge name=bridge.N
/interface/bridge/port/add bridge=bridge interface=bridge.N