Error about defconf generation process is just an outcome of many possible reasons. Simply “hey, there was some kind of error”. As you can see in changelogs, defconf is updated quite often. This error only says “there was something wrong here”. It is not a single issue. Quite often also it is possible to get such an error, for example, on 1/100 specific model devices simply because loading the system took a longer time, etc. We are looking into this and trying to figure out what kind of issue (or issues) it is this time. As always - proper way how to report bugs is through support@mikrotik.com. This is a user forum where simply MikroTik employees also like to be present.
Rextended please stop posting with such confidence if you are not sure what you are talking about. “Is the same error on RouterOS source code” is wrong.
The “error while running customized default configuration script” did not occur on next reboot… So not opening an issue for now.
Is it even defconf? In @eworm case, it sounds like it was after a version upgrade…not the /system/default-configuration. Maybe it’s crossfig (or whatever does config upgrade) since that only happen once too… If that’s case, then the error message is kinda lousy (e.g. it’s not the “default”, but “current” config, that failed to upgrade).
That’s my understanding of the issue, yes. But as we do not have the crossfig script code we can not verify…
But adding one note here… My wifi interface do not have default names, I renamed all of them. Perhaps that’s a problem?
[eworm@MikroTik] > /interface/wifi/print proplist=name,default-name where default-name
Flags: M - MASTER; B - BOUND; R - RUNNING
Columns: NAME, DEFAULT-NAME
# NAME DEFAULT-NAME
6 MB wl2-intern wifi1
15 MBR wl5-intern wifi2
Code like this should always work with the default-name property…
I’ve not renamed mine just to let you know, Also I’ve not seen a repeat of the error after rebooting mine either.
Thanks for your thoughts Strods.
Hopefully, we have managed to reproduce the same problem with “defconf” generation for AX routers. It is a cosmetic, harmless issue that can occur randomly on any upgrade/downgrade, package installation/removal. We will try to fix it in upcoming RouterOS releases. The error has nothing to do with 7.13 (if you see it on AX router).
Why are these newer builds no longer being posted to https://t.me/mikrotik_build (Telegram) and https://twitter.com/mikrotik_build (Twitter)? I am subscribed to notifications there so I get alerted the moment a new release occurs, but have received no notifications for a few weeks now (several builds)… Please fix..! 
I the new version of capsman, how do we connect a datapath to a vlan in a bridge? I get the following error and its documented, but I don seem to get any traffic trough by adding wifi interface a a bridge port or using the interface list option.
;;; client was disconnected because could not assign VLAN, maximum VLAN count for interface was reached
/interface wifi channel
add disabled=no name=channel1
/interface wifi datapath
add bridge=bridge disabled=no name=datapath1 vlan-id=22
/interface wifi configuration
add channel=channel1 country=Sweden datapath=datapath1 datapath.bridge=bridge .interface-list=datapath-home disabled=no mode=ap name=cfg1 ssid=test
/interface wifi cap
set enabled=yes
/interface wifi capsman
set enabled=yes interfaces=vlan0025 package-path=/firmware require-peer-certificate=no upgrade-policy=require-same-version
/interface wifi provisioning
add action=create-dynamic-enabled disabled=no master-configuration=cfg1 name-format=%I-%r
Thanks for the update Strods.
Please keep it comming like you are guys. 7.13RC3 for my hAP ax2 is blazing… on fire.
Thanks Team it’s getting their!
Tests over WiFi to prove it should anybody wish to take a look.
Name : WiFi
Description : Intel(R) Wi-Fi 6E AX210 160MHz
GUID :
Physical address : a0:80
Interface type : Primary
State : connected
SSID : 02
BSSID : 18:fd
Network type : Infrastructure
Radio type : 802.11ax
Authentication : WPA2-Personal
Cipher : CCMP
Connection mode : Auto Connect
Band : 5 GHz
Channel : 36
Receive rate (Mbps) : 1201
Transmit rate (Mbps) : 1201
Signal : 87%
Profile : 02
Flags: A - AUTHORIZED
Columns: INTERFACE, SSID, MAC-ADDRESS, UPTIME, SIGNAL
# INTERFACE SSID MAC-ADDRESS UPTIME SIGNAL
0 A wifi2 01 C0:4A:XX:XX:XX:XX 22h4m55s -52
1 A wifi1 02 A0:80:XX:XX:XX:XX 22h4m51s -46
2 A wifi1 02 84:2A:XX:XX:XX:XX 22h4m43s -55
3 A cap-wifi2 01 60:6B:XX:XX:XX:XX 21h37m18s -66
4 A wifi2 01 1C:56:XX:XX:XX:XX 17h8m35s -38
5 A cap-wifi1 01 AE:6B:XX:XX:XX:XX 16h57m54s -49
6 A cap-wifi1 01 6C:A1:XX:XX:XX:XX 16h26m14s -58
7 A wifi1 02 7E:40:XX:XX:XX:XX 2h7m48s -53
status: done
time-remaining: 0s
ping-min-avg-max: 1.73ms / 2.20ms / 3.11ms
jitter-min-avg-max: 1us / 165us / 844us
loss: 0% (0/200)
tcp-download: 907Mbps local-cpu-load:86%
tcp-upload: 923Mbps local-cpu-load:40% remote-cpu-load:0%
status: udp download
time-remaining: 18s
ping-min-avg-max: 1.73ms / 2.22ms / 3.13ms
jitter-min-avg-max: 2us / 156us / 857us
loss: 0% (0/200)
tcp-download: 923Mbps local-cpu-load:85%
tcp-upload: 895Mbps local-cpu-load:42% remote-cpu-load:0%
status: udp download
time-remaining: 17s
ping-min-avg-max: 1.78ms / 2.24ms / 3.31ms
jitter-min-avg-max: 1us / 146us / 1.07ms
loss: 0% (0/200)
tcp-download: 874Mbps local-cpu-load:82%
tcp-upload: 919Mbps local-cpu-load:41% remote-cpu-load:0%
My traceroute [v0.95]
Holy-moly (172.28.106.170) -> pingbox1.thinkbroadband.com (80.249.99.164) 2023-12-08T11:28:34+0000
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Drop Rcv Avg Gmean Jttr Javg Jmax Jint
1. 172.28.96.1 0 52 0.4 0.4 0.0 0.1 0.2 0.6
2. 192.168.0.254 0 52 2.5 2.5 0.3 0.2 0.6 3.0
3. (waiting for reply)
4. 80.3.67.129 0 52 12.3 11.8 0.2 2.8 30.7 48.7
5. (waiting for reply)
6. 62.254.42.174 6 46 15.4 15.1 0.3 2.9 18.9 45.0
7. (waiting for reply)
8. 84.116.136.98 0 52 14.9 14.7 3.4 1.9 19.9 29.5
9. 129.250.66.101 0 52 15.6 15.3 4.7 2.8 17.2 42.7
10. 129.250.3.214 1 50 17.3 16.6 0.7 4.6 25.3 76.7
11. 129.250.3.251 0 52 16.2 15.7 15.8 3.8 25.8 50.4
12. 192.80.16.146 0 51 15.5 15.3 2.1 2.0 10.5 36.7
13. 80.249.97.72 0 51 15.9 15.7 1.8 2.4 15.3 50.2
14. 80.249.97.90 0 51 15.5 15.4 1.0 1.5 8.9 18.4
15. 80.249.99.164 0 51 15.6 15.6 2.0 1.1 5.8 15.1
====== WAVEFORM.COM BUFFERBLOAT TEST RESULTS======
Test Version,1.0.8
Test
Unix
====== RESULTS SUMMARY ======
Bufferbloat Grade,A+
====== RESULTS SUMMARY ======
Mean Unloaded Latency (ms),17.3
Increase In Mean Latency During Download Test (ms),2.83
Increase In Mean During Upload Test (ms),0
Download speed (Mbps),242.979
Upload speed (Mbps),24.113
====== LATENCY TEST DETAIL ======
Unloaded - Median Latency (ms),15.96
Unloaded - 95th %ile Latency (ms),25.54
Unloaded - Mean Latency (ms),17.3
During Download - Median Latency (ms),18.73
During Download - 95th %ile Latency (ms),34.57
During Download - Mean Latency (ms),20.13
During Upload - Median Latency (ms),15.11
During Upload - 95th %ile Latency (ms),20.59
During Upload - Mean Latency (ms),15.65
===== BUFFERBLOAT IMPACT ======
Web Browsing,PASS,PASS
Audio Calls,PASS,PASS
4K Video Streaming,PASS,PASS
Video Conferencing,PASS,PASS
Low Latency Gaming,PASS,PASS
What kind of test is it?
BufferBloat test is for testing of Quality of Service - clients (or connections), that are trying to eat all the bandwidth of specific resource, shouldn’t harm latency of other clients (or connections).
This is even normal daily use scenario, because if someone is downloading 12GB big OS upgrade, then it shouldn’t harm quality of meetings (or gaming) for other people.
Hi,
Would like to note that the bug with non-working mangle mark routing rules with VxLAN described by esipoko in April and by me in December is still in place as of 7.13rc3. Wish it could be fixed in 7.13 stable. SUP-136716
Is this about an AC with new drivers? I’ve same behaviour, but only by using a WAP AC and wifi-qcom-ac. The AX2 is working right.
Any reported wireguard problems?
ROS 7.13rc3 Wireguard stop working after 2-3 or 4 hours, need to reboot router to work again. Disable wg tunnel or peer do not help.
CCR2116, WireGuard isn’t working, replaced it with ZeroTier, in details:
- delete and re-add the peer may solve the problem but once you disconnect you can’t connect back.
- It shows 94bytes received, ‘Handshake did not complete after 5 seconds’
- Same behavior on iPhone, iPad, Windows and MacOS
- This problem is only on connecting remotely on ‘WAN’, while if the device is present on LAN WireGuard works flawlessly connection get established/handshake without any problem.
- Tried to downgrade and netinstall, and that did not fix the problem.
I can’t rule out human error 100% (?misconfiguration), and for this reason I’m asking for any known or reported bugs.
No problem with wireguard here, working well without issues.
Wondering if you have issues with the roaming functionality… Do you have any suspicious or unexpected addresses in actual-endpoint-address?