v7.11rc is released!

Mon Jul 31, 2023 11:12 am

RouterOS version 7.11rc has been released on the "v7 testing" 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 the upgrade process;
3) Device has enough free storage space to download all RouterOS packages.

What's new in 7.11rc4 (2023-Aug-11 12:57):

*) bth - removed from 7.11 for "stable" release, the development will continue in "beta" 7.12;
*) ike1 - fixed Phase 1 when using aggressive exchange mode (introduced in v7.10);
*) poe-out - advertise LLDP power-mdi-long even if no power allocation was requested (introduced in v7.7);
*) sfp - fixed incorrect optical SFP temperature readings (introduced in v7.10);

What's new in 7.11rc3 (2023-Aug-09 17:41):

*) certificate - improved CRL download retry handling;
*) ipsec - fixed public key export (introduced in v7.10);
*) ipsec - fixed signature authentication using secp521r1 certificate (introduced in v7.10);
*) lte - fixed R11e-LTE, R11e-LTE6 legacy 2G/3G RAT mode selection;
*) sms - increased wait time for modem startup;
*) switch - fixed BPDU packet processing on MT7621, MT7531 with HW offloaded vlan-filtering;
*) switch - improved multicast packet forwarding on MT7621;

What's new in 7.11rc2 (2023-Aug-03 10:50):

*) certificate - fixed trust store CRL link if generated on an older version (introduced in v7.7);
*) console - improved stability when canceling console actions;
*) ike2 - fixed ECP521 DH group usage (introduced in v7.11 beta1);
*) lte - fixed R11e-LTE6 "EARFCN" reporting format (introduced in v7.11rc1);
*) ssh - fixed SSH key agreement on the client side when ed25519 used under server settings;
*) wireguard - fixed peer IPv6 "allowed-address" usage;

What's new in 7.11rc1 (2023-Jul-28 09:52):

*) bridge - fixed MAC learning on "switch-cpu" port with enabled FastPath;
*) bridge - fixed dynamic untagged VLAN management (introduced in v7.11beta5);
*) bth - added "Back To Home" VPN service for ARM, ARM64, and TILE devices;
*) container - fixed IP address in container host file;
*) ethernet - fixed forced half-duplex 10/100 Mbps link speeds on CRS312 device;
*) firewall - improved system stability when using "endpoint-independent-nat";
*) ike2 - improved SA rekeying reply process;
*) lte - added "at-chat" support for Dell DW5829 modem;
*) lte - added "at-chat" support for Fibocom L850-GL modem;
*) lte - added "at-chat" support for SIMCom 8202G modem;
*) lte - added "band" info to the "monitor" command for MBIM modems that support serving cell info reporting over MBIM;
*) lte - fixed LtAP mini default SIM slot "down" changeover to "up" after an upgrade (introduced in v7.10beta1);
*) lte - improved system stability when changing the "radio" state for MBIM modems;
*) sfp - improved Q/SFP interface stability for 98DX8208, 98DX8212, 98DX8332, 98DX3257, 98DX4310, 98DX8525, 98DX3255, 98PX1012 switches;
*) switch - fixed BPDU packet processing on MT7621, MT7531 with HW offloaded vlan-filtering;
*) switch - improved multicast packet forwarding on MT7621;

Other changes since v7.10:

*) api - disallow executing commands without required parameters;
*) bfd - fixed "actual-tx-interval" value and added "remote-min-tx" (CLI only);
*) bfd - improved system stability;
*) bluetooth - added "decode-ad" command for decoding raw Bluetooth payloads (CLI only);
*) bluetooth - added "Peripheral devices" section which displays decoded Eddystone TLM and UID, iBeacon and MikroTik Bluetooth payloads;
*) bluetooth - added new AD structure type "service-data" for Bluetooth advertisement;
*) bridge - added more STP-related logging;
*) bridge - added warning when VLAN interface list contains ports that are not bridged;
*) bridge - fixed MSTP BPDU aging;
*) bridge - fixed MSTP synchronization after link down;
*) bridge - prevent bridging the VLAN interface created on the same bridge;
*) certificate - allow to import certificate with DNS name constraint;
*) certificate - fixed PEM import;
*) certificate - removed request for "passphrase" property on import;
*) certificate - require CRL presence when using "crl-use=yes" setting;
*) certificate - restored RSA with SHA512 support;
*) conntrack - fixed "active-ipv4" property;
*) console - added ":convert" command;
*) console - added default value for "rndstr" command (16 characters from 0-9a-zA-Z);
*) console - fixed incorrect date when printing "value-list" with multiple entries;
*) console - fixed incorrect default value of ":return" command (introduced in v7.11beta2);
*) console - fixed minor typos;
*) console - fixed missing "parent" for script jobs (introduced in v7.9);
*) console - fixed missing return value for ping command in certain cases;
*) console - fixed printing interval when resizing terminal;
*) console - improved flag printing in certain menus;
*) console - improved stability and responsiveness;
*) console - improved stability when using fullscreen editor;
*) console - improved timeout for certain commands and menus;
*) console - improved VPLS "cisco-id" argument validation;
*) container - added IPv6 support for VETH interface;
*) container - added option to use overlayfs layers;
*) container - adjust the ownership of volume mounts that fall outside the container's UID range;
*) container - fixed duplicate image name;
*) defconf - do not change admin password if resetting with "keep-users=yes";
*) dhcp-server - fixed setting "bootp-lease-time=lease-time";
*) discovery - fixed "lldp-med-net-policy-vlan" (introduced in v7.8 );
*) dns - improved system stability when processing static DNS entries with specified address-list;
*) ethernet - improved interface stability for CRS312 device;
*) fetch - improved timeout detection;
*) firewall - added warning when PCC divider argument is smaller than remainder;
*) firewall - fixed mangle "mark-connection" with "passthrough=yes" rule for TCP RST packets;
*) graphing - added paging support;
*) health - added more gradual control over fans for CRS3xx, CRS5xx, CCR2xxx devices;
*) health - fixed configuration export for "/system/health/settings" menu;
*) hotspot - allow number as a first symbol in the Hotspot server DNS name;
*) ike2 - improved system stability when closing phase1;
*) ike2 - improved system stability when making configuration changes on active setup;
*) ike2 - log "reply ignored" as non-debug log message;
*) ipsec - improved IKE2 rekey process;
*) ipsec - properly check ph2 approval validity when using IKE1 exchange mode;
*) l3hw - changed minimal supported values for "neigh-discovery-interval" and "neigh-keepalive-interval" properties;
*) l3hw - fixed /32 and /128 route offloading after nexthop change;
*) l3hw - fixed incorrect source MAC usage for offloaded bonding interface;
*) l3hw - improved system responsiveness during partial offloading;
*) l3hw - improved system stability during IPv6 route offloading;
*) l3hw - improved system stability;
*) led - fixed manually configured user LED for RB2011;
*) leds - blink red system-led when LTE is not connected to the network on D53 devices;
*) leds - fixed system-led color for "GSM EGPRS" RAT on D53 devices;
*) lora - added new EUI field;
*) lora - added uplink message filtering option using NetID or JoinEUI;
*) lora - moved LoRa service to IoT package;
*) lora - properly apply configuration changes when multiple LoRa cards are used;
*) lora - updated LoRa firmware for R11e-LR8, R11e-LR9 and R11e-LR2 cards;
*) lte - added "at-chat" support for Dell DW5821e-eSIM modem;
*) lte - added extended support for Neoway N75 modem;
*) lte - fixed Dell DW5221E "at-chat" support;
*) lte - fixed NR SINR reporting for Chateau 5G;
*) lte - fixed Telit LE910C4 "at-chat" support;
*) lte - improved initial interface startup time for SXT LTE 3-7;
*) lte - only listen to DHCP packets for LTE passtrough interface in auto mode when looking for the host;
*) modem - added initial support for BG77 modem DFOTA firmware update;
*) modem - changed Quectel EC25 portmap to expose DM (diag port), DM channel=0, GPS channel=1;
*) modem - fixed missing sender's last symbol in SMS inbox if the sender is an alphabetic string;
*) mpls - improved MPLS TCP performance;
*) mqtt - added more MQTT publish configuration options;
*) mqtt - added new MQTT subscribe feature;
*) netwatch - added "src-address" property;
*) netwatch - changed "thr-tcp-conn-time" argument to time interval;
*) ovpn - do not try to use the "bridge" setting from PPP/Profile, if the OVPN server is used in IP mode (introduced in v7.10);
*) ovpn - fixed OVPN server peer-id negotiation;
*) ovpn - fixed session-timeout when using UDP mode;
*) ovpn - improved key renegotiation process;
*) ovpn - include "connect-retry 1" and "reneg-sec" parameters into the OVPN configuration export file;
*) ovpn - properly close OVPN session on the server when client gets disconnected;
*) package - treat disabled packages as enabled during upgrade;
*) poe - fixed missing PoE configuration section under specific conditions;
*) pppoe - fixed PPPoE client trying to establish connection when parent interface is inactive;
*) profile - added "container" process classifier;
*) profile - properly classify "console" related processes;
*) qos-hw - keep VLAN priority in packets that are sent from CPU;
*) quickset - correctly apply configuration when using "DHCP Server Range" property;
*) resource - fixed erroneous CPU usage values;
*) rose-storage - added "scsi-scan" command (CLI only);
*) rose-storage - added disk stats for ramdisks;
*) rose-storage - fixed RAID 0 creation;
*) rose-storage - limit striped RAID element size to smallest disk size;
*) route - added comment for BFD configuration (CLI only);
*) route - convert BFD timers from milliseconds to microseconds after upgrade;
*) routerboard - fixed "gpio-function" setting on RBM33G ("/system routerboard upgrade" required);
*) routerboard - improved RouterBOOT stability for Alpine CPUs ("/system routerboard upgrade" required);
*) routerboard - removed unnecessary serial port for netPower16P and hAP ax lite devices ("/system routerboard upgrade" required);
*) routerboot - increased etherboot bootp timeout to 40s on MIPSBE and MMIPS devices ("/system routerboard upgrade" required);
*) sfp - improved interface stability for 98DX8208, 98DX8212, 98DX8332, 98DX3257, 98DX4310, 98DX8525, 98DX3255, 98PX1012 based switches;
*) sfp - improved optical QSFP interface handling for 98DX8332, 98DX3257, 98DX4310, 98DX8525 switches;
*) sfp - reduce CPU load due to SFP interface handling for CCR2116, CCR2216, CCR2004-12S+2XS, CRS312, CRS518 devices (introduced in v7.9)
*) ssh - fixed host public key export (introduced in v7.9);
*) ssh - fixed private key import (introduced in v7.9);
*) ssh - fixed user RSA private key import;
*) switch - fixed "reset-counters" for "switch-cpu";
*) system - disallow setting a non-existing CPU core number for system IRQ;
*) system - increased maximum supported CPU core count to 512 on CHR and x86;
*) system - reduced RAM usage for SMIPS devices;
*) tftp - improved file name matching;
*) user - added "sensitive" policy requirement for SSH key and certificate export;
*) w60g - improved stability for Cube 60Pro ac and CubeSA 60Pro ac devices;
*) webfig - added option to enable wide view in item list;
*) webfig - fixed "Connect To" configuration changes for L2TP client;
*) webfig - fixed gray-out italic font for entries after enable;
*) webfig - use router time zone for date and time;
*) wifiwave2 - added "steering" parameters and menu to set up and monitor AP neighbor groups (CLI only);
*) wifiwave2 - added more information on roaming candidates to BSS transition management requests (802.11v) and neighbor report responses (802.11k);
*) wifiwave2 - added option to filter frames captured by the sniffer command (CLI only);
*) wifiwave2 - automatically add wifi interfaces to appropriate bridge VLAN when wireless clients with new VLAN IDs connect;
*) wifiwave2 - changed default behavior for handling duplicate client MAC addresses, added settings for changing it (CLI only);
*) wifiwave2 - enabled PMK caching with EAP authentication types;
*) wifiwave2 - fixed "reg-info" information for several countries;
*) wifiwave2 - fixed "security.sae-max-failure" rate not limiting authentications correctly in some cases;
*) wifiwave2 - fixed clearing CAPsMAN Common Name when disabling "lock-to-caps-man";
*) wifiwave2 - fixed interface hangs on IPQ6010-based boards (introduced in v7.9);
*) wifiwave2 - fixed multicast frame delivery (introduced in v7.11beta2);
*) wifiwave2 - fixed registration table statistics (introduced in v7.11beta4);
*) wifiwave2 - improved stability when changing interface settings;
*) wifiwave2 - improved stability when receiving malformed WPA3-PSK authentication frames;
*) wifiwave2 - make info log less verbose during client roaming (some info moved to wireless,debug log);
*) wifiwave2 - rename "reg-info" country argument from "Macedonia" to "North Macedonia";
*) wifiwave2 - use correct status code when rejecting WPA3-PSK re-association;
*) winbox - added missing status values for Ethernet and Cable Test;
*) winbox - added warning about non-running probe due to "startup-delay";
*) winbox - fixed "Storm Rate" property under "Switch/Port" menu;
*) winbox - fixed BGP affinity display;
*) winbox - fixed default "Ingress Filtering" value under "Bridge" menu;
*) winbox - improved supout.rif progress display;
*) winbox - rename "Group Master" property to "Group Authority" under "Interface/VRRP" menu;
*) wireguard - fixed peer connection using DNS name on IP change;
*) wireless - ignore EAPOL Logoff frames;
*) x86 - updated e1000 driver;

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, please send a supout file from your router to support@mikrotik.com. File must be generated while a 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.

epkulse · Mon Jul 31, 2023 11:32 am

Does it contain the fixes made in 7.11 Beta 7?

Mon Jul 31, 2023 11:42 am

Yes, the RC release contains all the fixes that you have ever seen in v7.11. Now upcoming v7.11 releases will be only RC releases with cherry-picked fixes for major issues or regressions introduced in 7.11. All other fixes will be added only in v7.12beta. When RC will become stable (better than 7.10 and without any known regressions), then 7.11 stable will be built as a copy from the last 7.11rc.

epkulse · Mon Jul 31, 2023 2:12 pm

Perfect. Thanks!

blacksnow · Mon Jul 31, 2023 2:45 pm

Looks like from v7.11beta7 to v7.11rc you can no longer re-order firewall rules in webfig. Re-ordering on other screens (routing rules) works though. I'm runnning it on firefox so looking for confirmation that it isn't a browser specific issue.

Edit: Seems to only be happening on my CCR2216.

Mon Jul 31, 2023 3:36 pm

Are you sure that your firewall rules list is ordered by column "#"? It is not allowed to move rules if the list is not sorted by ID.

blacksnow · Mon Jul 31, 2023 3:41 pm

Ahh, that was all it took. No issue here, just user error. Sorting and re-ordering works as expected! Thanks!

BillyVan · Mon Jul 31, 2023 4:36 pm

i thing from 7.7 and newer versions
no red color of unreachable routes
do you have any plan to fix it or no?
thank you

3Καταγραφή.jpg

biomesh · Mon Jul 31, 2023 6:01 pm

Finally had a chance to rebuild my nextdns container and the ipv6 support (in my case dual stack) for veth interfaces is working perfectly.

fischerdouglas · Mon Jul 31, 2023 6:15 pm

Off Topic to v7 announcements but is related to avoid misunderstandings.

Please adjust the download page on the CHR part.
As it is now(yet), end users can understand that 6.49.7 is still the latest stable to CHR...
It brings some noise to convince some Network operators to use the correct recommended version.

RouterOS_CHR_6.49.7_not-as-stable_please.png

mantouboji · Mon Jul 31, 2023 7:18 pm

How long to wait for the fix of letsencrypt with ipv6 only domain name?

Grant · Mon Jul 31, 2023 9:51 pm

Hi
rc1
Cloudflare-dns.com DOH certificate no longer works.
I deleted it and imported it again, but it didn't help.

DoH server connection error: SSL: ssl: CRL not found (6)
DoH server connection error: SSL: ssl: CRL not found (6) [ignoring repeated messages]

gigabyte091 · Mon Jul 31, 2023 10:00 pm

After update to 7.11rc I started to get famous SA Query timeout every couple of minutes:

 18:05:13 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 18:05:15 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 18:05:15 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:05:15 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:08:25 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 18:08:28 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 18:08:28 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:08:28 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:11:19 wireless,info 00:C3:0A:B7:ED:1C@cap-wifi3 disconnected, SA Query timeout, signal strength -49
 18:11:20 wireless,info 00:C3:0A:B7:ED:1C@cap-wifi4 connected, signal strength -56
 18:11:38 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 18:11:40 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -39
 18:11:41 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:11:41 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:14:51 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 18:14:53 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -42
 18:14:53 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:14:53 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:18:03 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 18:18:06 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 18:18:06 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:18:06 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:21:16 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 18:21:18 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 18:21:18 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:21:19 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:24:28 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 18:24:31 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 18:24:31 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:24:31 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:27:41 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 18:27:44 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 18:27:44 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:27:44 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:30:54 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 18:30:56 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 18:30:56 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:30:56 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:34:07 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -39
 18:34:09 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 18:34:09 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:34:09 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:37:19 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 18:37:22 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 18:37:22 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:37:22 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:40:31 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -39
 18:40:34 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 18:40:34 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:40:34 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:43:44 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -39
 18:43:46 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 18:43:46 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:43:46 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:46:56 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 18:46:59 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 18:46:59 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:46:59 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:50:09 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 18:50:12 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 18:50:12 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:50:12 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:53:22 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 18:53:24 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 18:53:24 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:53:24 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:56:34 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 18:56:37 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -42
 18:56:37 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:56:37 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:59:47 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 18:59:49 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 18:59:49 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:59:50 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 18:59:55 system,info,account user admin logged in from 10.10.88.20 via winbox
 19:03:00 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 19:03:02 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 19:03:02 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:03:02 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:04:28 system,info,account user admin logged out from 10.10.88.20 via winbox
 19:06:12 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 19:06:15 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 19:06:15 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:06:15 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:06:57 system,info,account user admin logged in from 10.10.88.20 via winbox
 19:09:25 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 19:09:27 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 19:09:27 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:09:27 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:09:57 system,info,account user admin logged out from 10.10.88.20 via winbox
 19:10:02 system,info,account user admin logged in from 10.10.88.20 via winbox
 19:12:37 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 19:12:40 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 19:12:40 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:12:40 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:13:50 system,info,account user admin logged out from 10.10.88.20 via winbox
 19:15:50 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -39
 19:15:52 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 19:15:53 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:15:53 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:15:53 wireless,info 00:C3:0A:B7:ED:1C@cap-wifi4 disconnected, SA Query timeout, signal strength -53
 19:15:58 wireless,info 00:C3:0A:B7:ED:1C@cap-wifi3 connected, signal strength -31
 19:19:03 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 19:19:05 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -42
 19:19:05 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:19:06 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:22:15 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 19:22:17 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -42
 19:22:18 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:22:18 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:25:28 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 19:25:30 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -42
 19:25:30 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:25:30 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:28:40 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 19:28:43 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 19:28:43 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:28:43 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:31:53 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 19:31:55 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 19:31:55 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:31:56 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:35:06 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 19:35:08 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 19:35:08 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:35:08 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:38:18 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 19:38:21 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 19:38:21 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:38:21 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:41:31 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 19:41:33 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 19:41:33 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:41:33 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:44:43 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 19:44:46 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 19:44:46 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:44:46 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:47:56 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 19:47:58 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 19:47:58 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:47:59 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:48:25 dhcp,info dhcp_VLAN88 deassigned 10.10.88.220 for 18:FD:74:CE:E6:83 MikroTik
 19:48:25 dhcp,info dhcp_VLAN88 assigned 10.10.88.220 for 18:FD:74:CE:E6:83 MikroTik
 19:51:09 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 19:51:11 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 19:51:11 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:51:11 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:54:21 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -39
 19:54:24 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 19:54:24 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:54:24 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:54:57 wireless,info A4:55:90:89:31:A2@cap-wifi3 disconnected, connection lost, signal strength -39
 19:57:34 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 19:57:36 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -42
 19:57:36 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 19:57:36 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:00:46 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -39
 20:00:49 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 20:00:49 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:00:49 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:01:04 wireless,info A4:55:90:89:31:A2@cap-wifi3 connected, signal strength -33
 20:03:59 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -39
 20:04:01 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 20:04:02 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:04:02 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:07:12 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 20:07:14 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 20:07:14 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:07:14 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:07:24 wireless,info A4:55:90:89:31:A2@cap-wifi3 disconnected, connection lost, signal strength -42
 20:10:24 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 20:10:27 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 20:10:27 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:10:27 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:13:37 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 20:13:39 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 20:13:39 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:13:40 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:16:50 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -42
 20:16:52 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 20:16:52 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:16:52 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:20:02 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 20:20:05 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -39
 20:20:05 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:20:05 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:23:15 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 20:23:17 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 20:23:17 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:23:17 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:26:27 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 20:26:30 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 20:26:30 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:26:30 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:29:40 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 20:29:42 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 20:29:42 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:29:43 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:32:53 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 20:32:55 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 20:32:55 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:32:55 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:36:05 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 20:36:08 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 20:36:08 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:36:08 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:39:18 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 20:39:20 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 20:39:20 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:39:20 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:42:03 wireless,info A4:55:90:89:31:A2@cap-wifi3 connected, signal strength -35
 20:42:30 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 20:42:33 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 20:42:33 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:42:33 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:42:37 wireless,info A4:55:90:89:31:A2@cap-wifi3 disconnected, connection lost, signal strength -39
 20:45:43 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 20:45:45 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 20:45:46 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:45:46 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:48:21 wireless,info A4:55:90:89:31:A2@cap-wifi3 connected, signal strength -31
 20:48:56 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -40
 20:48:58 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -40
 20:48:58 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:48:58 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:52:08 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 20:52:11 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 20:52:11 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:52:11 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:53:55 wireless,info 70:32:17:E3:AF:80@cap-wifi3 connected, signal strength -35
 20:54:08 system,info,account user admin logged in from 10.10.88.9 via winbox
 20:55:21 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 disconnected, SA Query timeout, signal strength -41
 20:55:23 wireless,info 18:A7:F1:79:D1:4B@cap-wifi5 connected, signal strength -41
 20:55:23 dhcp,info dhcp_VLAN30 deassigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0
 20:55:24 dhcp,info dhcp_VLAN30 assigned 10.10.30.3 for 18:A7:F1:79:D1:4B uplus-haier-ac-d14b-v0

Device in question is air conditioner, I didn't had any problems until update.

moep · Mon Jul 31, 2023 10:07 pm

Sadly the IPSec problem mentioned here viewtopic.php?t=197095&start=300#p1014852 is still present in this version.

own3r1138 · Mon Jul 31, 2023 10:41 pm

Sadly the IPSec problem mentioned here viewtopic.php?t=197095&start=300#p1014852 is still present in this version.

My home setup suffers from the same issue. It also doesn't work with SSTP, which is sad.

Tue Aug 01, 2023 8:08 am

After update to 7.11rc I started to get famous SA Query timeout every couple of minutes
Device in question is air conditioner, I didn't had any problems until update.

SA Query is a procedure for checking if a client device can be reached (and still has the agreed-on encryption key). SA Query timeouts are expected, when a client device attempts to connect to an AP after losing its previous connection due to signal fade (or some other conditions where it did not or could not inform the AP that it is disconnecting).
The AC in you logs appears to be switching back and forth between cap-wifi3 and cap-wifi5 without informing the AP that it's disconnecting before attempting a new connection. This might be because it is losing reception of the AP. Or it could be that it cannot reach some network resource it expected to reach and so it tries switching APs in a not-so-graceful way.
Which version did you upgrade from?

Tue Aug 01, 2023 8:25 am

Please create and send a supout.rif file to support@mikrotik.com

Hi
rc1
Cloudflare-dns.com DOH certificate no longer works.
I deleted it and imported it again, but it didn't help.
Code: Select all
DoH server connection error: SSL: ssl: CRL not found (6)
DoH server connection error: SSL: ssl: CRL not found (6) [ignoring repeated messages]

gigabyte091 · Tue Aug 01, 2023 9:06 am

SA Query is a procedure for checking if a client device can be reached (and still has the agreed-on encryption key). SA Query timeouts are expected, when a client device attempts to connect to an AP after losing its previous connection due to signal fade (or some other conditions where it did not or could not inform the AP that it is disconnecting).
The AC in you logs appears to be switching back and forth between cap-wifi3 and cap-wifi5 without informing the AP that it's disconnecting before attempting a new connection. This might be because it is losing reception of the AP. Or it could be that it cannot reach some network resource it expected to reach and so it tries switching APs in a not-so-graceful way.
Which version did you upgrade from?

If you look carefully this particular device is connected only to cap-wifi5 (IoT network) and upstair AP don't broadcast that network, only downstairs AP does, other devices that you can see here are my laptop and my wife's phone, and this AC is in the same room as my donwstairs AP and both are ofcourse stationary and from the signal you can see that they are close.

I upgraded from 7.11beta5 to 7.11rc1

Tue Aug 01, 2023 9:14 am

Gigabyte, FToms is pointing out that your LOGS show this. So please check what is really happening.

Tue Aug 01, 2023 9:26 am

Gigabyte, FToms is pointing out that your LOGS show this. So please check what is really happening.

Not really my problem but ...
I'm not sure where you see that ?
Those logs, looking at MAC 18:A7:F1:79:D1:4B, only show connection with wifi5. Nothing else.
That corresponds with the situation as explained by gigabyte.

There is only 1 entry for wifi3 or wifi4 with SA message but that's for MAC 00:C3:0A:B7:ED:1C. Irrelevant for this case, I think ?

But it could be the device itself which is causing this.

gigabyte091 · Tue Aug 01, 2023 9:31 am

Gigabyte, FToms is pointing out that your LOGS show this. So please check what is really happening.
Not really my problem but ...
I'm not sure where you see that ?
Those logs, looking at MAC 18:A7:F1:79:D1:4B, only show connection with wifi5. Nothing else.
That corresponds with the situation as explained by gigabyte.

There is only 1 entry for wifi3 or wifi4 but that's for MAC 00:C3:0A:B7:ED:1C. Irrelevant for this case, I think ?

Exactly, only few entries are for that mac address, all other entries are for 18:A7:F1:79:D1:4B, and this continued thought the night for this client.

nichky · Tue Aug 01, 2023 9:52 am

*) bth - added "Back To Home" VPN service for ARM, ARM64, and TILE devices;

where can we see that?

nichky · Tue Aug 01, 2023 9:53 am

oh sorry , all good

Ullinator · Tue Aug 01, 2023 9:54 am

*) bth - added "Back To Home" VPN service for ARM, ARM64, and TILE devices;

where can we see that?

look at IP->Cloud->BTH VPN

Tue Aug 01, 2023 10:01 am

Back To Home is here, Android and iPhone apps make it easier than winbox:
viewtopic.php?t=198231

Tue Aug 01, 2023 10:09 am

If you look carefully this particular device is connected only to cap-wifi5 (IoT network)

Right, my bad. That MAC is in fact only connecting to cap-wifi5.
One thing I am noticing on a second look is that the delay between a connection and disconnection appears to be almost exactly 190 seconds every time. Does that perhaps correspond to DHCP leases renewal?
7.11rc1 does not include any wifiwave2 related changes since 7.11beta5, but perhaps the bridge changes break something in the VLAN handling.
Please open a support ticket regarding this.

gigabyte091 · Tue Aug 01, 2023 10:35 am

One thing I am noticing on a second look is that the delay between a connection and disconnection appears to be almost exactly 190 seconds every time. Does that perhaps correspond to DHCP leases renewal?

I have DHCP lease renewal time set do 1 day. I will send supout and logs to support today.

Kanzler · Tue Aug 01, 2023 11:08 am

I have an SA Query timeout error when the device switches between wifi1 and wifi2 interfaces (hAP ac3). It appeared in 7.11 beta2, it was not present in 7.10.2.

03:16:11 wireless,info F2:C3:26:B2:60:1C@wifi2 disconnected, SA Query timeout, signal strength -73
03:16:11 wireless,info F2:C3:26:B2:60:1C@wifi1 connected, signal strength -58
03:31:17 wireless,info F2:C3:26:B2:60:1C@wifi1 disconnected, SA Query timeout, signal strength -56
03:31:18 wireless,info F2:C3:26:B2:60:1C@wifi2 connected, signal strength -83
04:15:10 wireless,info F2:C3:26:B2:60:1C@wifi2 disconnected, SA Query timeout, signal strength -76
04:15:11 wireless,info F2:C3:26:B2:60:1C@wifi1 connected, signal strength -53
04:33:04 wireless,info F2:C3:26:B2:60:1C@wifi1 disconnected, SA Query timeout, signal strength -52
04:33:04 wireless,info F2:C3:26:B2:60:1C@wifi2 connected, signal strength -82
04:35:53 wireless,info F2:C3:26:B2:60:1C@wifi2 disconnected, SA Query timeout, signal strength -75
04:35:53 wireless,info F2:C3:26:B2:60:1C@wifi1 connected, signal strength -57
04:39:32 wireless,info F2:C3:26:B2:60:1C@wifi1 disconnected, SA Query timeout, signal strength -51
04:39:32 wireless,info F2:C3:26:B2:60:1C@wifi2 connected, signal strength -84
04:40:14 wireless,info F2:C3:26:B2:60:1C@wifi2 disconnected, SA Query timeout, signal strength -79
04:40:15 wireless,info F2:C3:26:B2:60:1C@wifi1 connected, signal strength -57
04:49:48 wireless,info F2:C3:26:B2:60:1C@wifi1 disconnected, SA Query timeout, signal strength -52
04:49:49 wireless,info F2:C3:26:B2:60:1C@wifi2 connected, signal strength -85
04:50:29 wireless,info F2:C3:26:B2:60:1C@wifi2 disconnected, SA Query timeout, signal strength -78
04:50:29 wireless,info F2:C3:26:B2:60:1C@wifi1 connected, signal strength -59
05:08:10 wireless,info F2:C3:26:B2:60:1C@wifi1 disconnected, SA Query timeout, signal strength -52
05:08:10 wireless,info F2:C3:26:B2:60:1C@wifi2 connected, signal strength -83
05:33:13 wireless,info F2:C3:26:B2:60:1C@wifi2 disconnected, SA Query timeout, signal strength -75
05:33:14 wireless,info F2:C3:26:B2:60:1C@wifi1 connected, signal strength -65
06:03:52 wireless,info F2:C3:26:B2:60:1C@wifi1 disconnected, SA Query timeout, signal strength -55
06:03:52 wireless,info F2:C3:26:B2:60:1C@wifi2 connected, signal strength -82
06:23:22 wireless,info F2:C3:26:B2:60:1C@wifi2 disconnected, SA Query timeout, signal strength -80
06:23:23 wireless,info F2:C3:26:B2:60:1C@wifi1 connected, signal strength -54
06:33:38 wireless,info F2:C3:26:B2:60:1C@wifi1 disconnected, SA Query timeout, signal strength -56
06:33:38 wireless,info F2:C3:26:B2:60:1C@wifi2 connected, signal strength -81
06:37:02 wireless,info F2:C3:26:B2:60:1C@wifi2 disconnected, SA Query timeout, signal strength -74
06:37:03 wireless,info F2:C3:26:B2:60:1C@wifi1 connected, signal strength -63
06:52:54 wireless,info F2:C3:26:B2:60:1C@wifi1 disconnected, SA Query timeout, signal strength -56
06:52:54 wireless,info F2:C3:26:B2:60:1C@wifi2 connected, signal strength -83
06:59:36 wireless,info F2:C3:26:B2:60:1C@wifi2 disconnected, SA Query timeout, signal strength -75
06:59:37 wireless,info F2:C3:26:B2:60:1C@wifi1 connected, signal strength -67
07:24:58 wireless,info F2:C3:26:B2:60:1C@wifi1 disconnected, SA Query timeout, signal strength -59
07:24:59 wireless,info F2:C3:26:B2:60:1C@wifi2 connected, signal strength -80

Tue Aug 01, 2023 11:12 am

It's an informative message and does not mean something is wrong, like explained above

Tue Aug 01, 2023 11:25 am

I have an SA Query timeout error when the device switches between wifi1 and wifi2 interfaces (hAP ac3). It appeared in 7.11 beta2, it was not present in 7.10.2.

This is to be expected if a client device, which supports management frame protection, attempts a new connection without properly terminating the previous one.
Previously in such situations, the old connection was unconditionally dropped.
With RouterOS 7.11, by default, the new connection attempt is only allowed if SA Query procedure for the old connection times out. This is to make it harder for malicious, yet authorized, users, to cause various problems to other users by spoofing their MAC addresses ('MacStealer' attack). If you like, you can alter this behaviour, by tuning the security.connect-priority parameter, see https://help.mikrotik.com/docs/display/ ... Properties

JasonPugh · Tue Aug 01, 2023 11:27 am

Hi
v7.11 rc1 has also broken Cloudflare (1.1.1.1) DoH certificate for me - I get a CRL error in the logfile and DNS resolution remains broken until I disable DoH certificate verification.
While troubleshooting, I'd also note that I cannot import CRLs, so wondering whether CRL file validation is the bit that is broken?

Regards,
Jason

Kanzler · Tue Aug 01, 2023 11:42 am

Normis, FToms, thank you for the explanation.

Grant · Tue Aug 01, 2023 11:49 am

Hi
v7.11 rc1 has also broken Cloudflare (1.1.1.1) DoH certificate for me - I get a CRL error in the logfile and DNS resolution remains broken until I disable DoH certificate verification.
While troubleshooting, I'd also note that I cannot import CRLs, so wondering whether CRL file validation is the bit that is broken?

Regards,
Jason

yes, i wrote about it above

mantouboji · Wed Aug 02, 2023 5:32 am

for LetsEncrypt certificates.
If I use an IPv6 only domain name , it has only an AAAA record, without any A record, /certificate/enable-ssl-certificate dns-name=XXXX.dynv6.com failed .
If I add an IPv4 address, even not a public IP but a 192.168.x.x private IP, then certificate get success.

Wed Aug 02, 2023 8:02 am

Yes, LE does not work currently in RouterOS on an IPv6-only network. This is not implemented yet. This particular scenario is not in any way related to the v7.11rc release.

mantouboji · Wed Aug 02, 2023 8:25 am

Yes, LE does not work currently in RouterOS on an IPv6-only network. This is not implemented yet. This particular scenario is not in any way related to the v7.11rc release.

But it real works at 7.8 and old versions.

Jotne · Wed Aug 02, 2023 8:34 am

IP Cloud is missing from Winbox (3.39) on my OVA(x86) (7.11Rc1) Router. It show up on terminal, and in Winbox on other routers lik 750Gr3. See picutre:
.

ip-cloud.png

Cha0s · Wed Aug 02, 2023 8:59 am

IP Cloud is missing from Winbox (3.39) on my OVA(x86) (7.11Rc1) Router. It show up on terminal, and in Winbox on other routers lik 750Gr3. See picutre:
.
ip-cloud.png

Try with a clean winbox session. It shows up here.

Jotne · Wed Aug 02, 2023 10:49 am

Winbox is just installed. You are on same x86 routerOS?

fischerdouglas · Wed Aug 02, 2023 12:18 pm

Thanks!

RouterOS_CHR_stable_6.49.8_thanks.png

Dish · Wed Aug 02, 2023 4:24 pm

cube60ac pro.jpg

With the Cube 60 pro ac no improvement in stability with 7.11RC...............

Ullinator · Wed Aug 02, 2023 5:22 pm

cube60ac pro.jpgWith the Cube 60 pro ac no improvement in stability with 7.11RC...............

Try to fix the "cpu is not running at default frequency" by setting it to automatic.
If that doesn´t help, export the config to a RSC file, factory default with no config the device and import the RSC file via terminal.
That fixed all my instabilities I had during the last several ROS updates ;-)
All my devices are rock-solid with all 7.11 versions (since 7.11Beta4):

hc_002.jpg

Grant · Wed Aug 02, 2023 5:53 pm

Hi
rc1
Cloudflare-dns.com DOH certificate no longer works.
I deleted it and imported it again, but it didn't help.
Code: Select all
DoH server connection error: SSL: ssl: CRL not found (6)
DoH server connection error: SSL: ssl: CRL not found (6) [ignoring repeated messages]

Support recommended disabling CLR (/certificate/settings/set crl-use=no) and it worked

Wed Aug 02, 2023 6:00 pm

Until 7.11rc1, CRL verification did not work correctly.
If use-crl is set to yes, RouterOS will check CRL for each certificate in a certificate chain, therefore, an entire certificate chain should be installed into a device - starting from Root CA, intermediate CA (if there are such), and server certificate that is used for specific service.

Dish · Wed Aug 02, 2023 6:49 pm

cube60ac pro.jpgWith the Cube 60 pro ac no improvement in stability with 7.11RC...............
Try to fix the "cpu is not running at default frequency" by setting it to automatic.
If that doesn´t help, export the config to a RSC file, factory default with no config the device and import the RSC file via terminal.
That fixed all my instabilities I had during the last several ROS updates ;-)
All my devices are rock-solid with all 7.11 versions (since 7.11Beta4):
hc_002.jpg

Thanks for the info. i will test it.

Steve

Buckeye · Wed Aug 02, 2023 9:02 pm

@strods can you comment on the switch changes in more detail? Specifically the one about BPDU and HW vlan-filtering.

Here are two threads which were related to the problem this seems to be addressing
VLAN-Trunk not working [SOLVED - incorrect BPDU filtering on hAP ax lite HW offloaded trunk ports] - this post references support ticket SUP-119824

Bridge VLAN-Filter Offload broken on hEXr3? and this post where @skyhawk claims "Initial testing suggests the issues is *not* fixed." but doesn't go into details about what testing and results led him to the "not fixed" conclusion.

Another thread that seemed to fit the behavior repored in the above two threads. RouterOS 7 Bridge VLAN/DHCP client issue after upgrade

Amm0 · Thu Aug 03, 2023 12:15 am

*) console - added ":convert" command;

":convert to=hex" doesn't work with number types. I'd expect either a string with "7F" or "007F" back from below..., instead the number arg is treated as string and ASCII codes are used:

:put [:convert to=hex 127]

Even being explicit about everything doesn't help:

:put [:convert from=raw to=hex value=[:tonum 127]] 
313237

which are the ASCII codes for 1 (\31), 2 (\32), 7 (\37)

xrobau · Thu Aug 03, 2023 12:32 am

I upgraded a RB4011iGS+5HacQ2HnD to 7.11rc1 and MTU's were no longer being applied to vlans on a bridge, they were all at 1500.

Rolling back to 7.10, the MTUs were correctly set.

https://i.imgur.com/5trw0zz.png

The /export did have the vlan set in it, and there were no errors in the logs.

xrobau · Thu Aug 03, 2023 12:53 am

I upgraded a RB4011iGS+5HacQ2HnD to 7.11rc1 and MTU's were no longer being applied to vlans on a bridge, they were all at 1500.

Rolling back to 7.10, the MTUs were correctly set.

It looks like this has been broken for a while, and I didn't notice. I have played around with it a bit, and it looks like I can change the MTU after the device has rebooted, but it's not setting them correctly on startup.

This is with 7.11b6, which I happened to have lying around.

https://i.imgur.com/Hitjrdz.png

sirbryan · Thu Aug 03, 2023 2:01 am

I upgraded a RB4011iGS+5HacQ2HnD to 7.11rc1 and MTU's were no longer being applied to vlans on a bridge, they were all at 1500.

Rolling back to 7.10, the MTUs were correctly set.
It looks like this has been broken for a while, and I didn't notice. I have played around with it a bit, and it looks like I can change the MTU after the device has rebooted, but it's not setting them correctly on startup.

This is with 7.11b6, which I happened to have lying around.

https://i.imgur.com/Hitjrdz.png

Yes, I reported this a while back. I have a script that runs that disables/enables the VLAN interfaces after booting to force the configured MTU size to take effect. Without it, my OSPF links won't start due to MTU mismatch (most of my PTP links between routers have been configured with an MTU of 2000 or more to support future tagging and tunneling techniques).

skyhawk · Thu Aug 03, 2023 6:09 am

*) switch - fixed BPDU packet processing on MT7621, MT7531 with HW offloaded vlan-filtering;

This does not appear to be working. Hardware offloaded VLAN filtering on hEXr3 still breaks spanning tree, as documented in this forum thread.

jimint · Thu Aug 03, 2023 6:35 am

i thing from 7.7 and newer versions
no red color of unreachable routes
do you have any plan to fix it or no?
thank you
3Καταγραφή.jpg

Yes you have right about it.
Is there any solution to fix it?

kcarhc · Thu Aug 03, 2023 7:26 am

What's new in 7.11beta4 (2023-Jul-05 13:33):
*) dns - improved system stability when processing static DNS entries with specified address-list;

This bug has reappeared in 7.11rc1 on the RB5009 device, but it has not occurred on CHR.

Please check SUP-119380, and the supout.rif file has been uploaded.

here is the image.

RB5009_7.11rc1.png

Thu Aug 03, 2023 8:05 am

":convert to=hex" doesn't work with number types. I'd expect either a string with "7F" or "007F" back from below..., instead the number arg is treated as string and ASCII codes are used:

put the value in quotes
convert “lala” from=raw to=hex

ID · Thu Aug 03, 2023 3:37 pm

Put decimal to hex function as well to reduce confusion. Decimal 127 output must be 7F not 313237.

Dish · Thu Aug 03, 2023 4:01 pm

Try to fix the "cpu is not running at default frequency" by setting it to automatic.
If that doesn´t help, export the config to a RSC file, factory default with no config the device and import the RSC file via terminal.
That fixed all my instabilities I had during the last several ROS updates ;-)
All my devices are rock-solid with all 7.11 versions (since 7.11Beta4):
hc_002.jpg
Thanks for the info. i will test it.

Steve

Unfortunately, the error also occurs with the setting to default cpu frequency..............
The error only occurs in heavy rain with a failure of the 60 ghz link.

WinBox v7.11rc1 on Cube 60Pro ac (arm).jpg

Amm0 · Fri Aug 04, 2023 3:56 am

Put decimal to hex function as well to reduce confusion. Decimal 127 output must be 7F not 313237.

Yup. If someone had time for =rot13.... num to hex seems pretty reasonable...

Basically, :convert to=hex should be type aware. At least for input arg is typeof=num... Right now :convert only deals with strings.

So if input is a string, then yeah "127" becoming "313237" makes sense...

:convert "127" to=hex # "313237"

but... if the input is "num" (decimal) then 7F is what you SHOULD get with this:

:convert 127 to=hex # should return "7F"... BUT assumes str + ASCII instead...

Arguable, perhaps not high priority, but ip and ipv6 are types, and have hex represented:

:convert 1.1.1.1 to=hex # should return "01010101" since arg :typeof = ip not "312e312e312e31"
:convert 2021:: to=hex # should return "202100000000000000000000"

Kaldek · Fri Aug 04, 2023 6:06 am

wifiwave2 - automatically add wifi interfaces to appropriate bridge VLAN when wireless clients with new VLAN IDs connect;

Is this the fix for WiFi slave interfaces adding themselves to the appropriate VLAN? I didn't see this happen when I updated my APs and my RB5009 (CAPsMAN Wifiwave2) to 7.11.

On the regular old CAPsMAN and non-ax devices, the slave interfaces - in my case on VLAN 10 - automatically add themselves to the bridge VLAN (as tagged no less) as soon as the CAPsMAN provisioning is done.

nichky · Fri Aug 04, 2023 6:34 am

@MikroTik

is there any chance on WG to add :

Last link Down Time
Last link Up Time
Uptime
Link Downs

Fri Aug 04, 2023 7:52 am

The Wireguard interface is always in a "running" state. You can connect multiple peers to the same interface. There is no easy way to determine if the interface should be up or down.

Most likely you are looking for the Wireguard peers parameter "last-handshake".

Fri Aug 04, 2023 7:56 am

Put decimal to hex function as well to reduce confusion. Decimal 127 output must be 7F not 313237.
Yup. If someone had time for =rot13.... num to hex seems pretty reasonable...

Basically, :convert to=hex should be type aware. At least for input arg is typeof=num... Right now :convert only deals with strings.

So if input is a string, then yeah "127" becoming "313237" makes sense...
:convert "127" to=hex # "313237"
but... if the input is "num" (decimal) then 7F is what you SHOULD get with this:
:convert 127 to=hex # should return "7F"... BUT assumes str + ASCII instead...

Arguable, perhaps not high priority, but ip and ipv6 are types, and have hex represented:
:convert 1.1.1.1 to=hex # should return "01010101" since arg :typeof = ip not "312e312e312e31"
:convert 2021:: to=hex # should return "202100000000000000000000"

Here is a quote from our manual - "Converts specified value from one format to another. By default uses an automatically parsed value if the "from" format is not specified (for example, "001" becomes "1", "10.1" becomes "10.0.0.1", etc.)"

You can easily see which value will be actually be used with a simple test like this:

{
:local a 001
:put $a
:put [:typeof $a]
}

{
:local a 1.0
:put $a
:put [:typeof $a]
}

This will be the type and value of the input argument if you do not specify the "from" parameter. However, since "convert" does not support the "num" format at the moment, it will use the from value as "raw".

nichky · Fri Aug 04, 2023 7:58 am

The Wireguard interface is always in a "running" state. You can connect multiple peers to the same interface. There is no easy way to determine if the interface should be up or down.

Most likely you are looking for the Wireguard peers parameter "last-handshake".

last-handshake is not the right place to check the uptime.

What u are saying completely make sense

Ullinator · Fri Aug 04, 2023 9:27 am

wifiwave2 - automatically add wifi interfaces to appropriate bridge VLAN when wireless clients with new VLAN IDs connect;
Is this the fix for WiFi slave interfaces adding themselves to the appropriate VLAN? I didn't see this happen when I updated my APs and my RB5009 (CAPsMAN Wifiwave2) to 7.11.

On the regular old CAPsMAN and non-ax devices, the slave interfaces - in my case on VLAN 10 - automatically add themselves to the bridge VLAN (as tagged no less) as soon as the CAPsMAN provisioning is done.

I had the same problem, because it´s a little bit tricky.
You have to configure the "Slave Datapath" in the CAP menu on the CAP itself:

hc_012.jpg

Additionally you need to configure the physical wifi interfaces on the CAP as managed by capsman:

hc_013.jpg

The result for me is exactly what you also want, dynamically added "virtual" wifi interfaces added to the local bridge on the CAP with the correct VLAN ID:

hc_010.jpg

Erbit · Fri Aug 04, 2023 9:48 am

Hi.

*) lte - added "at-chat" support for Fibocom L850-GL modem;

I have Fibocom L850-GL (MBIM) in MiniPCI-e slot on RBM33G. In previous RoS, each AT command ended with a message

failure: Modem unsupported!

Currently (RoS 7.11.rc1) every AT command ends with:

failure: AT channel not responding

Do I have something misconfigured or is it a RoS bug?

Fri Aug 04, 2023 11:13 am

What's new in 7.11rc2 (2023-Aug-03 10:50):

*) certificate - fixed trust store CRL link if generated on an older version (introduced in v7.7);
*) console - improved stability when canceling console actions;
*) ike2 - fixed ECP521 DH group usage (introduced in v7.11 beta1);
*) lte - fixed R11e-LTE6 "EARFCN" reporting format (introduced in v7.11rc1);
*) ssh - fixed SSH key agreement on the client side when ed25519 used under server settings;
*) wireguard - fixed peer IPv6 "allowed-address" usage;

Znevna · Fri Aug 04, 2023 1:28 pm

What's new in 7.11rc2 (2023-Aug-03 10:50):

*) wireguard - fixed peer IPv6 "allowed-address" usage;

Is it fixed-fixed now for all platforms? You've been fixing it since February 2022.

mantouboji · Fri Aug 04, 2023 3:13 pm

What's new in 7.11rc2 (2023-Aug-03 10:50):

*) ssh - fixed SSH key agreement when using ed25519 under server settings;

What means?

Amm0 · Fri Aug 04, 2023 9:22 pm

However, since "convert" does not support the "num" format at the moment, it will use the from value as "raw".

Yeah the num type to/from hex is common one that does come up sometimes, so be good to see that at some point.

As feedback,
- the "raw" type is confusing "at the moment" — it really seems to mean a string with unknown encoding. Maybe that's right, just think "raw" means an unknown type also, not an unknown encoding. Maybe to=raw shouldn't even be valid, dunno...
- ":convert from=raw to=raw" always converts to a string type, even if the input was num/ip/ipv6/etc and to=raw – guess I was expecting that to be noop (no conversion applied) and return the input as the output.
e.g. in the extreme,

:convert from=raw to=raw 1.1

IMO should be returned as an "ip" typeof with value of 1.0.0.1. Right now, it's a string "1.0.0.1".

And, fair enough...while extremely subtle... ":convert 001 to=hex" = "31" does illustrate what happens... just disagree what should happen. ;)

npeca75 · Fri Aug 04, 2023 11:28 pm

What's new in 7.11rc2 (2023-Aug-03 10:50):

*) wireguard - fixed peer IPv6 "allowed-address" usage;
Is it fixed-fixed now for all platforms? You've been fixing it since February 2022.

at least on rb5009 arm64 i could use again /112

hope that @strods will show this post to mr Oskars K. from ticketing portal [SUP-121761]
maybe ticketing stuff will be less arrogant next time
it was stated in every 7.10 ++ forum topic that WG IPv6 with non /64 allowed address will break on certain platforms
after sending 2 .rif (7.9.2 vs 7.11) mr Oskars have very negative attitude

peich1 · Sat Aug 05, 2023 2:19 am

I've finally updated from 7.7 to 7.11rc1 & rc2, and while it looks like the openvpn problems have been fixed, I'm experiencing *lots* of sfp problems.
A lot of sfp ports flapping that didn't happened neither with 7.7 nor with 6.xx versions.
And since updating to rc2, the SFP interface with my DAC (XS+DA0001) between my CRS328 and my RB5009 doesn't go up automatically anymore. I need to connect to the CRS328 and disable/enable the sfp interface after each reboot to make it work.

nichky · Sat Aug 05, 2023 4:13 am

when can we expect vrf over bgp to be fixed?

its not sending default route over it

sirbryan · Sat Aug 05, 2023 6:33 am

7.11rc2 broke iBGP for my office CCR2116 as an rr-client to my two RR's (2011's running 7.10rc4). It was working on 7.11b6 and 7.11rc1. Fortunately I had 7.11b6 saved to disk. Unfortunately there's not a way to get 7.11rc1 back from the website.

own3r1138 · Sat Aug 05, 2023 6:43 am

Unfortunately, there's no way to get 7.11rc1 back from the website.

https://download.mikrotik.com/routeros/ ... -arm64.npk

Sat Aug 05, 2023 8:02 am

We are very sorry if you felt offended in some way. However, I do not see why. You were just asked few additional questions in a polite manner which you did refuse to answer. Yes, the problem was not - wireguard does not work with any IPv6 allowed addresses. Particular addresses and specifi routers had to be used. After you declined to answer, we luckily managed to find that information and fix the issue.

Is it fixed-fixed now for all platforms? You've been fixing it since February 2022.
at least on rb5009 arm64 i could use again /112

hope that @strods will show this post to mr Oskars K. from ticketing portal [SUP-121761]
maybe ticketing stuff will be less arrogant next time
it was stated in every 7.10 ++ forum topic that WG IPv6 with non /64 allowed address will break on certain platforms
after sending 2 .rif (7.9.2 vs 7.11) mr Oskars have very negative attitude

own3r1138 · Sat Aug 05, 2023 8:30 am

@strods
Will you fix the IPsec EAP RAS authentication with EC certificates, please?
SUP-124151

npeca75 · Sat Aug 05, 2023 8:56 am

We are very sorry if you felt offended in some way.

i saw that all old beta forum topics are erased
i reported few time when v7.10 betaX started to show, that WG with IPv6 and non /64 suffix have a problem
in 7.11beta topic there was also another user with same observation, and i clearly remember that he has ticket number also

in previous posts i was clearly show configs, tracert, and errors reported by ROS when one try to use WG with non /64 on various platforms

all these post was ignored by MT staff

and then, when i had enough of ignorance, i filled the bug report with all data and RIFs to trace bug

few day of silence, then question ...
it was obvious that no one take seriously bugs reported in forum (at least 3 time, two different user) and that staff from ticketing portal is not aware of similar bug reports
so, it is annoying that we, users, help MT to debug they OS, for ex WG / IPv6, which is broken in last XX releases ( and will break again ) with different behavior on different platforms and our rewards is silence or ignorance
at least answer what i expected was: yes, we read forum posts, we are aware of problem, tnx for RIFs, will try to reproduce ...

anyway, tnx for fixing it (for now)

Sat Aug 05, 2023 10:39 am

To everyone! Please remember - this is a user forum. Report bugs to support@mikrotik.com immediately, if you are sure that the issue you have is a bug. This will get things done much faster!

Erbit · Sat Aug 05, 2023 11:38 am

To everyone! Please remember - this is a user forum. Report bugs to support@mikrotik.com immediately, if you are sure that the issue you have is a bug. This will get things done much faster!

If we are going to e-mail support, why is this topic on the forum?

My question was also left unanswered.

Sat Aug 05, 2023 11:50 am

Support doesn't always read user forum.
Lots of things are fixed through peer user support.
Users like you and me helping each other out.

But real bugs, need to be send to support.

rextended · Sat Aug 05, 2023 12:48 pm

If we are going to e-mail support, why is this topic on the forum?

Because 90% of problems are due to user ignorance, and often with the help of forum users they are fixed.
Then there's the 2% that users persist in reporting on the forum, instead of to support@mikrotik.com.
The remaining 8% are not problems related to any of the previous aspects.

spippan · Sat Aug 05, 2023 3:49 pm

We are very sorry if you felt offended in some way.
i saw that all old beta forum topics are erased
i reported few time when v7.10 betaX started to show, that WG with IPv6 and non /64 suffix have a problem
in 7.11beta topic there was also another user with same observation, and i clearly remember that he has ticket number also

in previous posts i was clearly show configs, tracert, and errors reported by ROS when one try to use WG with non /64 on various platforms

all these post was ignored by MT staff

and then, when i had enough of ignorance, i filled the bug report with all data and RIFs to trace bug

few day of silence, then question ...
it was obvious that no one take seriously bugs reported in forum (at least 3 time, two different user) and that staff from ticketing portal is not aware of similar bug reports
so, it is annoying that we, users, help MT to debug they OS, for ex WG / IPv6, which is broken in last XX releases ( and will break again ) with different behavior on different platforms and our rewards is silence or ignorance
at least answer what i expected was: yes, we read forum posts, we are aware of problem, tnx for RIFs, will try to reproduce ...

anyway, tnx for fixing it (for now)

to add to "strods" clarification ... you do have to understand, that support staff (not STUFF!!) mostly if at all has no time to sift through the user forum topics with A LOT of useless entries and poeple just complaining over stuff wich is BETA or RC and not stable by any means.

so show a little respect to technical support trying to cope with all the setups encountering any imaginable or unimaginable issue. thanks.

macak · Sat Aug 05, 2023 11:00 pm

I'm after update 7.11rc2 on prod ;-). Relax - It's home network so no huge risk.

Generally rc candidate - looks stable with one note:

Quick explanation about my config.
Few vlans, capsman, caps ax, two providers and TV@ separated vlan... OVPN between Mikrotiks and Android devices.
Hardware 3x CAPS AX. RB450Gx4 as main gateway.capsman/DHCP and so on. Some switches between (Mikrotiks).

After update some clients slow down over wifi. I found that on CAPSMAN under wireless -> Wireless tables are many greyed interfaces. After delete it everything back to normal (devices have max speed of Internet connection 600Mbps). All these interfaces was greyed out. Before delete I have on some devices 0.5 Mbps.

There I have one small request. In WiFi / registration tab please add CAP identity where client are connected. It help to locate ehere client connecting.

Thanks.
Maciek

Ullinator · Sat Aug 05, 2023 11:11 pm

In WiFi / registration tab please add CAP identity where client are connected.

YESSS, please!!!!! :-)

Sat Aug 05, 2023 11:12 pm

Yup, that would be very welcome !!

Erbit · Sat Aug 05, 2023 11:16 pm

If we are going to e-mail support, why is this topic on the forum?
Because 90% of problems are due to user ignorance, and often with the help of forum users they are fixed.
Then there's the 2% that users persist in reporting on the forum, instead of to support@mikrotik.com.
The remaining 8% are not problems related to any of the previous aspects.

My question was rhetorical. I don't want answers to them because I know them.

I will gladly read that I am ignorant or that I should write to the support. I will gladly read anything that will help solve my problem, perhaps resulting from ignorance. So far I haven't read anything about my previous question.

rextended · Sun Aug 06, 2023 5:23 am

Because 90% of problems are due to user ignorance, and often with the help of forum users they are fixed.
Then there's the 2% that users persist in reporting on the forum, instead of to support@mikrotik.com.
The remaining 8% are not problems related to any of the previous aspects.

My question was rhetorical. I don't want answers to them because I know them.

I will gladly read that I am ignorant or that I should write to the support. I will gladly read anything that will help solve my problem, perhaps resulting from ignorance. So far I haven't read anything about my previous question.

8%

rextended · Sun Aug 06, 2023 6:04 am

Not tested on 7.11rc2 but probably applies to this version as well:
⚠️Security Issue: Changing rights / disable / delete the users has no effect on already logged in users. [Tested on 6.48.7 and 7.10.2]
viewtopic.php?t=198410

ormandj · Sun Aug 06, 2023 5:56 pm

I've finally updated from 7.7 to 7.11rc1 & rc2, and while it looks like the openvpn problems have been fixed, I'm experiencing *lots* of sfp problems.
A lot of sfp ports flapping that didn't happened neither with 7.7 nor with 6.xx versions.
And since updating to rc2, the SFP interface with my DAC (XS+DA0001) between my CRS328 and my RB5009 doesn't go up automatically anymore. I need to connect to the CRS328 and disable/enable the sfp interface after each reboot to make it work.

I've been having this off and on with the 7.x releases. 7.9 was fine for me, 7.10.2 my Synology NAS with a ConnectX 4 card + FS SM optic has link, but DHCP/etc do not work. 7.7 was fine, I think 7.8 didn't work, etc. It's all over the map - it's become a guessing game if things will work for me with the 7.x releases and SFP+s on my CRS328. I always see notes about SFP changes in each release so I've stopped reporting the issues because every time it gets fixed, it just gets broken again. I'm going to wait for things to stabilize a bit then start reporting again if it remains broken, because right now it doesn't seem to help resolve the issue since the fixes seem to get invalidated in later releases.

skyhawk · Mon Aug 07, 2023 4:15 am

I've got a bit more information regarding this line from the changelog:

What's new in 7.11rc1 (2023-Jul-28 09:52):
*) switch - fixed BPDU packet processing on MT7621, MT7531 with HW offloaded vlan-filtering;

It seems the BPDU processing has indeed been fixed for bridges and bridge-ports in hybrid mode via `frame-types=admit-all`. If the bridge and/or ports are set for `frame-types=admit-only-VLAN-tagged` this is still broken and will cause RSTP to refuse to forward packets, unless one of the previous workarounds is employed (Disabling RSTP, setting edge=yes, or disabling Hardware Offload)

xrobau · Mon Aug 07, 2023 8:30 am

If we are going to e-mail support, why is this topic on the forum?
Then there's the 2% that users persist in reporting on the forum, instead of to support@mikrotik.com.

We are SPECIFICALLY AND DIRECTLY told to report bugs in this forum.

viewtopic.php?t=152006

Mon Aug 07, 2023 9:23 am

That topic is from 2019 when v7 was in beta. It is not beta anymore,. 4 years have passed. It is stable

uCZBpmK6pwoZg7LR · Mon Aug 07, 2023 1:19 pm

any plans to fix interface unknown in firewall for mpls vpn4 traffic ?

fischerdouglas · Mon Aug 07, 2023 4:48 pm

The OFFICIAL way is through support@mikrotik.com.
The community path is through the Forum.

Want to report a bug, both ways?
Excellent! It will enable other colleagues to identify with your situation and perhaps help to find the cause.

But...
The OFFICIAL way is through support@mikrotik.com.

You made that choice when you bought MikroTik equipment... Don't you want to do it that way?
Change the brand of equipment you are using...
But be sure to review that the vendor bug-report method you choose is forum-only.

Amm0 · Mon Aug 07, 2023 5:08 pm

Want to report a bug, both ways?
Excellent! It will enable other colleagues to identify with your situation and perhaps help to find the cause.

Yeah I kinda use these release threads to judge stability. My theory is... If you're unsure something is a bug or notice something "weird" in the release, just post. If it's critical and/or your sure it's a bug, file bug report then post...

And if you file a bug report... imagine the supout.rif is super useful to Mikrotik, so make sure to attach one.

sirbryan · Mon Aug 07, 2023 7:22 pm

(OT) I like how Ubiquiti has configured their forum software to accept private uploads on the first post of a thread. This allows both the support teams to get the files they need, as well as allowing other members of the community to see that a particular issue has been reported. Others can then pile on with similar symptoms, sharing screenshots, etc.

I also like Github's mechanisms that allow the repo admins to tag issues, such as "bug", "work-in-progress", "feature request", "user error", etc.

I imagine here that tags would be useful to sort questions or bug reports based on platform (arm, arm64, mipsbe, tile, etc.), release, or product/product family (CCR2116, CRS300), allowing both admins and other community members to sort threads based on topics they are interested in at the moment.

In particular, if an employee determines that a specific thread addresses a known bug, they could tag it as "Bug," allowing others to see that it's been reported, and provide addition supout files or screenshots of symptoms to help devs narrow the issue down. Or, mark it as "Known Issue," to help reduce the number of "me-too's" when it's already being worked on.

Simonej · Mon Aug 07, 2023 10:07 pm

@MTStaff
could you please expain

*) wifiwave2 - changed default behavior for handling duplicate client MAC addresses, added settings for changing it (CLI only);

EDIT: is security.connect-group + connect-priority ?

xrobau · Mon Aug 07, 2023 11:02 pm

That topic is from 2019 when v7 was in beta. It is not beta anymore,. 4 years have passed. It is stable

Maybe delete or unpin that post then? It's still the first one that people see.

Edit: It was unpinned! Yay!

So I tried to report the MTU issue (which is 100% breaks-routers-on-upgrade) and will now try to poke the ticket through your Jira.

rextended · Mon Aug 07, 2023 11:06 pm

That topic is from 2019 when v7 was in beta. It is not beta anymore,. 4 years have passed. It is stable
Maybe delete or unpin that post then? It's still the first one that people see.

But this is also the first line on this topic.

UPDATE: v7 is no longer in beta. Report bugs to support @ mikrotik . com please

If people are not able to read and understand what is written....

xrobau · Mon Aug 07, 2023 11:08 pm

But this is also the first line on this topic.
UPDATE: v7 is no longer in beta. Report bugs to support @ mikrotik . com please
If people are not able to read and understand what is written....

That was only just added, when it was unpinned. Don't get upset because people were doing what they were told!

rextended · Mon Aug 07, 2023 11:09 pm

That topic is from 2019 when v7 was in beta. It is not beta anymore,. 4 years have passed. It is stable

@Normis...
Is time to change the section name, is ridiculous:

RouterOS beta and rc versions
Please report all issues with RouterOS beta / rc pre-release versions.

IS time to create a section about "RouterOS 7" and leave "RouterOS beta and rc versions" just for... RouterOS beta and rc versions!!!

rextended · Mon Aug 07, 2023 11:10 pm

That was only just added, when it was unpinned. Don't get upset because people were doing what they were told!

It's not unpinned at all (now at 2023-08-07 22:11 CEST, tomorrow if is unpinned, is another thing), and if you haven't noticed it's not my fault.
viewforum.php?f=1

xrobau · Tue Aug 08, 2023 12:28 am

It's not unpinned at all (now at 2023-08-07 22:11 CEST, tomorrow if is unpinned, is another thing), and if you haven't noticed it's not my fault.
viewforum.php?f=1

Oh, I do apologise, it has NOT been unpinned. So, yeah, it really should be, like I suggested originally 8)

Look, this is silly to argue over. You expected that people had spent a lot more time on the forum than you have. We come here, see 'Report problems here, not via email', and then report problems here. We didn't know it was wrong, we were just following instructions that we thought were current!

Edit: Because I thought 'maybe I *am* crazy', I had a look on the wayback machine, and it did specifically say 'don't report v7 bugs to support, report them here'

https://web.archive.org/web/20220506060 ... cd47182e4d

rextended · Tue Aug 08, 2023 11:35 am

this is silly to argue over.

Edit: Because I thought 'maybe I *am* crazy', I had a look on the wayback machine, and it did specifically say 'don't report v7 bugs to support, report them here'

https://web.archive.org/web/20220506060 ... cd47182e4d

Can't you see that the picture is from May 6th 2022??? Not from last week...
What are you trying to prove?
That you can't interpret what you see?

rextended · Tue Aug 08, 2023 11:38 am

@Normis...
Is time to change the section name, is ridiculous:

Thanks @Normis
viewtopic.php?t=198462

kcarhc · Tue Aug 08, 2023 3:10 pm

Please review the following SUP tickets.
These issues persist in 7.11beta/rc and 7.10.x without resolution.
All of them are related to DNS problems.

SUP-121758 The functionality of matching regular expressions and subdomains in dns-to-address-list is not working properly
SUP-121988 Regarding the issue of adding comments to dns-to-address-list
SUP-123531 The rules of DNS static are not executed in sequential order

Amm0 · Tue Aug 08, 2023 3:27 pm

These sound like feature requests based on titles...

SUP-121988 Regarding the issue of adding comments to dns-to-address-list

You cannot change comments on dynamic entries, anywhere. And, address-list entries from DNS are dynamic.

SUP-123531 The rules of DNS static are not executed in sequential order

They execute in round-robin, which it's done for a while...

eworm · Tue Aug 08, 2023 3:46 pm

You cannot change comments on dynamic entries, anywhere.

That's not correct. I am pretty sure you can set a comment for dynamic DHCP leases.
https://git.eworm.de/cgit/routeros-scri ... comment.md

I have not tried anywhere else, though.

Amm0 · Tue Aug 08, 2023 3:52 pm

You cannot change comments on dynamic entries, anywhere.
That's not correct. I am pretty sure you can set a comment for dynamic DHCP leases.

Likely true, I was mainly thinking of dynamic interfaces.

But I'm still not sure this thread is the best place to ask for status updates ... on what sound like feature requests ;)

pe1chl · Tue Aug 08, 2023 3:57 pm

(OT) I like how Ubiquiti has configured their forum software to accept private uploads on the first post of a thread. This allows both the support teams to get the files they need, as well as allowing other members of the community to see that a particular issue has been reported. Others can then pile on with similar symptoms, sharing screenshots, etc.

Well, I HATE that and I refuse to use it!
The only thing making your "private" upload private is some flag on the item in the database, and you have no insight at all in who is able to read it.
At any time they may assign outside moderators (like is happening here) which suddenly have access to your private files, and/or the forum software may be hacked and anyone may be able to download your private files.
Of course that issue more or less exists with Jira as well, but at least there we may hope/expect that they never willfully give insider access to volunteers outside the company.
Still I would prefer when stuff like uploaded supout files would get removed on closing a ticket.

sirbryan · Tue Aug 08, 2023 4:47 pm

(OT) I like how Ubiquiti has configured their forum software to accept private uploads on the first post of a thread.
Well, I HATE that and I refuse to use it!

My point is less about the means or methods, and more about the idea that the issues and feedback are exposed to both internal and external eyes in one place, in an attempt to eliminate duplicate posts and consolidate discussion about the issue(s). Certainly a more secure method of file transfer could be employed for transferring support files.

Wed Aug 09, 2023 7:54 am

MikroTik forum is for the community. It is user-to-user discussion. No bugs should be reported here, no private files should be uploaded here. Unlike some others, we have actual support with an actual ticketing system. help.mikrotik.com/servicedesk/servicedesk/

msatter · Wed Aug 09, 2023 10:35 am

There is someting like I think I found a bug and like to know if any others have the same expierence on that.

Sometimes I was just "holding it wrong" and got info to solve my "bug". The forum is a good filter for bugs, before escalating to actual reporting it as a confirmed bug to Mikrotik.

Then it always good to report back in the forum that the confirmed bug is reported to Mikrotik to avoid multiple reporting of the same bugs by many.

I see sometimes Mikrotik reporting in the forum that a bug is confirmed an is worked on.

So the forum has a function in the bug eco-system, however don't expect Mikrotik to scan constantly the forum to find reports on potential bugs. There are exceptions that Mikrotik picks up on a discussion and investigate.

Testing and RC treads have close attention of Mikrotik but the problem is that an itteration closes the previous tread an throws it out of focus. While there was a discussion, which so is killed off.

Now we have only a reference in the closing post link to the new tread. It would be nice that the opening post would also refer to the previous tread.

Wed Aug 09, 2023 10:42 am

Yes, if you are not sure if it's a bug and want somebody to do a sanity check - sure, forum is a good place. But please do not expect that MikroTik staff is monitoring all threads for possible bug reports. If you are sure it's a bug - report directly in our support system

rpingar · Wed Aug 09, 2023 11:09 am

MikroTik forum is for the community. It is user-to-user discussion. No bugs should be reported here, no private files should be uploaded here. Unlike some others, we have actual support with an actual ticketing system. help.mikrotik.com/servicedesk/servicedesk/

Normis... I have several tickets opened about pppoe crahes and bgp instability or bgp late advertisment over time.
your guys reply in months and no solution or at least analisys on all of them.
These are the tickets:
support #[SUP-123606]: CCR2216 - BGP flap session lead to router crash/reboot
support #[SUP-124445]: bgp goes in stange behavior (x86) after some seession flap
support #[SUP-120995]: BGP prefix Count broken after some days
support #[SUP-110510]: bgp ipv6 causes memory leaks and cpu consumption in 7.7 and 7.8 - ccr2216
support #[SUP-119592]: pppoe servers slow to boot and some of them are invalid
support #[SUP-115401]: ccr2216 and qsfp28 issues still persists on 7.9
support #[SUP-108462]: dst limit rule doesn't catch anything when rate is > then 10K p/s
support #[SUP-97493]: pppoe v7 issue

So I think you should improve your support dep.

pe1chl · Wed Aug 09, 2023 12:14 pm

Yes, if you are not sure if it's a bug and want somebody to do a sanity check - sure, forum is a good place. But please do not expect that MikroTik staff is monitoring all threads for possible bug reports. If you are sure it's a bug - report directly in our support system

I would not expect them to read all threads, but it would not be unreasonable to expect them monitoring the Announcements / x is released! and Feature requests (the one you started yourself) threads.

There are also a couple of "We at MikroTik consider to develop x" threads that lead off into a lot of discussion and suggestions, but no outcome.
Are you saying we should instead put that all in the support system for it to be monitored?

msatter · Wed Aug 09, 2023 12:31 pm

@pe1chl This will show all topics you started and with this it would be easy to check:

https://forum.mikrotik.com/search.php?keywords=&terms=all&author=pe1chl&sc=1&sf=firstpost&sr=topics&sk=t&sd=d&st=0&ch=300&t=0&submit=Search

Replace pe1chl by strods or normis for the topics they started

Wed Aug 09, 2023 12:39 pm

rpingar, not all issues can be reproduced easily, if you have a large and complex network, issue can be caused by many things. To fix something, we need to reliably repeat the problem. And not all issues can be fixed easily. I checked your tickets, there are long discussions with support. So you can't say there is no response.

FuscaSoftware · Wed Aug 09, 2023 12:55 pm

Hello,
I have 4 DAC-SFP+ in my Mikrotik switch which are shown with a temperature of 255C. I can set the value to disable them to 256, so they are working perfectly fine. But the fans of the whole switch are running in maximum speed. The switch is in my living room, so it is really anoying.

mikrotik_overheated_sfp_dac_2023-08_#2.png

Obviosly 255C is an error, maybe -1 in an unsigned 2^8 integer. Please don't use this value for system fans or give me the opportunity to ignore the value each module one by one.
The error occured with 7.10 and unfortunately wasn't fixed in 7.11rc yet.

Also described here:
viewtopic.php?p=1017712#p1017712

Wed Aug 09, 2023 12:58 pm

@FuscaSoftware
Best to create supout.rif and include it in support ticket.
So Mikrotik can investigate where the problem is.

pe1chl · Wed Aug 09, 2023 1:15 pm

@pe1chl This will show all topics you started and with this it would be easy to check

I don't understand what I would need to check and what you are trying to solve.
This shows how important it is to always quote the (part of) the article you are replying to.

Wed Aug 09, 2023 4:24 pm

@Buckeye, @skyhawk the next rc version will include additional fixes for correct BPDU processing on MT7621, MT7531 switches.

msatter · Wed Aug 09, 2023 4:50 pm

@pe1chl This will show all topics you started and with this it would be easy to check
I don't understand what I would need to check and what you are trying to solve.
This shows how important it is to always quote the (part of) the article you are replying to.

My reply to you was posting #116 and your posting was #115 and so a direct answer. Also I don't like to quote because then the pages becomes a mess. My nightmares exist of reading topics, where two users are the only ones active and they quote each other in full in every posting......WHY???

You wrote in post 115 about that if Mikrotik opens an topic then they should also check that topic for what is going on. The link I gave allows them to do that and most likely they already use it. Makes work easier and they have not to browse though the pages to find their own started topics back.

rextended · Wed Aug 09, 2023 5:18 pm

What I have suggest?
viewtopic.php?t=198228#p1017613

That topic is from 2019 when v7 was in beta. It is not beta anymore,. 4 years have passed. It is stable

@Normis...
Is time to change the section name, is ridiculous:
RouterOS beta and rc versions
Please report all issues with RouterOS beta / rc pre-release versions.

IS time to create a section about "RouterOS 7" and leave "RouterOS beta and rc versions" just for... RouterOS beta and rc versions!!!

rextended · Wed Aug 09, 2023 5:26 pm

The real rule in this forum is that there should be no rules.
More moderators to moderate what?
They keep allowing topics like "no internet", "help me", "question". Seriously?
Most of the posts are garbage and spam, and by spam I mean opening other topics to post the same thing for the umpteenth time.
Moderators should delete those bulls–t, and direct people to ask in the right section and for topics that have the same problem.
For example, there are dozens of posts on DDNS of various kinds, which do the same thing, one gets lost even in the search, and I believe they open up new sections.

For me at this point the whole forum should be locked, moving it to a subsection and reopening the relevant and more detailed sections from the beginning,
for example scripting, api, vlan, ipsec, certificates, wireguard, BGP, lte, lora, etc.
all more detailed subsections, instead of generic things,
and a beta/rc section all for it's own.

Even the discourse of quotations, hundreds of useless posts are produced in the search,
because the search also searches in the quoted text, making a mess that disorients.

pe1chl · Wed Aug 09, 2023 5:39 pm

You wrote in post 115 about that if Mikrotik opens an topic then they should also check that topic for what is going on. The link I gave allows them to do that and most likely they already use it. Makes work easier and they have not to browse though the pages to find their own started topics back.

The problem is not that MikroTik do not read the topics, they do. See the above reply by normis: apparently he is reading the topic.
The problem is that they ignore "possible bug reports" (and also "possible suggestions for improvement") and wait until they are reported on the support system. But as users cannot see what others report on the support system, that means double work for them.
What we need is a support system where others can also see and add information to what is being reported, like Bugzilla or Github.
That would of course not cover all support needs, but at least it would cover the reporting of plainly visible issues that multiple people do experience.

Amm0 · Wed Aug 09, 2023 5:40 pm

When the release thread commentary switches to process...that always seems to be good indicator of a release...

Only thing missing is xMIPSx support for BTH...

manojlovicl · Wed Aug 09, 2023 6:09 pm

Hi!

Something changed from beta firmware(s) (at least 7.11beta2) to RC in relation to OpenVPN - RC version has problems with more than 170 OVPN connections ...
I reverted to 7.11beta2 and everything works great.

Luka

rextended · Wed Aug 09, 2023 6:45 pm

Have you open the support ticket sending the supout.rif after and before (or better before, and after)?
If you limit yourself to writing it here on the forum and that's it,
without opening a separate topic where you give an explanation worthy of that name, and an export of your configuration,
what you write is useless.

vovan700i · Wed Aug 09, 2023 10:23 pm

Hello,
I have 4 DAC-SFP+ in my Mikrotik switch which are shown with a temperature of 255C. I can set the value to disable them to 256, so they are working perfectly fine. But the fans of the whole switch are running in maximum speed. The switch is in my living room, so it is really anoying.
mikrotik_overheated_sfp_dac_2023-08_#2.png

Obviosly 255C is an error, maybe -1 in an unsigned 2^8 integer. Please don't use this value for system fans or give me the opportunity to ignore the value each module one by one.
The error occured with 7.10 and unfortunately wasn't fixed in 7.11rc yet.

Also described here:
viewtopic.php?p=1017712#p1017712

Hi, I described it here (viewtopic.php?p=1007986#p1007986) and reported to support (SUP-122789). Sadly, no solution yet. They asked to send supout.rif by the way. I think it would be helpful if you could make another report with such a file attached if you don't mind.

Thu Aug 10, 2023 1:11 am

....
Even the discourse of quotations, hundreds of useless posts are produced in the search, because the search also searches in the quoted text, making a mess that disorients.

Good point ... It's a ROS 7.11rc2 topic ... please do not flood it with moderation complains. Should I delete or moderate your post?
That is the closest /latest topic to discuss moderation: viewtopic.php?t=197356

raphaps · Thu Aug 10, 2023 1:12 am

Hi!

Something changed from beta firmware(s) (at least 7.11beta2) to RC in relation to OpenVPN - RC version has problems with more than 170 OVPN connections ...
I reverted to 7.11beta2 and everything works great.

Luka

I had the same problem. The connections hang, the interface drops and the addresses in ip/address turn red. Openvpn port 1194 is blocked and only normalizes when I restart the router. I went back to 7.11beta2.

Thu Aug 10, 2023 12:01 pm

What's new in 7.11rc3 (2023-Aug-09 17:41):

*) certificate - improved CRL download retry handling;
*) ipsec - fixed public key export (introduced in v7.10);
*) ipsec - fixed signature authentication using secp521r1 certificate (introduced in v7.10);
*) lte - fixed R11e-LTE, R11e-LTE6 legacy 2G/3G RAT mode selection;
*) sms - increased wait time for modem startup;
*) switch - fixed BPDU packet processing on MT7621, MT7531 with HW offloaded vlan-filtering;
*) switch - improved multicast packet forwarding on MT7621;

effitall · Thu Aug 10, 2023 3:19 pm

Out of curiosity, I've had a problem (as others have had) with MLAG. The problem was introduced in 7.7, and just prior to 7.10 being released, it was finally acknowledge as a problem with a solution pending. I have not seen in the release notes where this was fixed, and even though my support tickets are "closed" the last communication was (SUP-116568):

"We have managed to reproduce the issue locally in our labs and look forward to fixing it on upcoming RouterOS versions, unfortunately, I cannot provide a release date now."

Has this been fixed yet or is it still pending? I really need this to be fixed so I can complete an installation.

Thu Aug 10, 2023 3:25 pm

Has this been fixed yet or is it still pending? I really need this to be fixed so I can complete an installation.

If it is not mentioned in the release notes, it's not yet fixed.

loloski · Thu Aug 10, 2023 4:03 pm

I think the problem here with MT they should finished one thing at a time before jumping on to another task at hand and also they should published the roadmap at least people know what to expect or not, otherwise this will be a recurring theme MT will surely delete this post anytime soon just like what they did before.

Kevo · Thu Aug 10, 2023 6:46 pm

I think the problem here with MT they should finished one thing at a time before jumping on to another task at hand and also they should published the roadmap at least people know what to expect or not, otherwise this will be a recurring theme MT will surely delete this post anytime soon just like what they did before.

Many people, myself included, have had similar thoughts about Mikrotik software releases and other companies' releases as well. Of course this is a naive outlook which is not well matched with reality. If you just think about it a little while you realize it obviously makes no sense to work on one thing at a time. With a team of people you have multiple projects occurring simultaneously simply because you have multiple developers of different levels and skill sets and many things to get done.

In addition to the obvious stuff, there are less obvious factors involved. Sometimes adding additional resources to a particular task can actually slow things down. More developers working on bug x doesn't necessarily mean bug x gets fixed quicker or more correctly. It's very difficult to manage large software projects and many fail from poor management. I think MikroTik does a reasonable job overall. I'm not suggesting they couldn't do better, but I am suggesting that without direct knowledge of all their resources, planning, and management of those resources we certainly can't be expected to know better then they do how they should be allocated.

Probably the best thing we can do is put in our feature requests and bug reports as clearly and concisely as possible and just be persistent in letting them know what we need and why. The more people that do that the easier it will be for MT to figure out priorities and resolve issues. Keeping the SNR down will be helpful for everyone.

effitall · Thu Aug 10, 2023 6:49 pm

Has this been fixed yet or is it still pending? I really need this to be fixed so I can complete an installation.
If it is not mentioned in the release notes, it's not yet fixed.

Well...The problem with MLAG is directly related to bridging and spanning-tree for which there have been a number of fixes in the past couple of releases. I'm not sure if any of those posted fixes also fix the MLAG issues or not. Just checking. Would be nice if there were some sort of actual bug tracking number for the MLAG issue that I could search (like other software/equipment manufacturers).

But hey...What do I know? I just use this stuff.

loloski · Thu Aug 10, 2023 7:56 pm

as they always say, if it's not mentioned in the changelog therefore they won't fix it

pe1chl · Thu Aug 10, 2023 7:59 pm

It is quite clear that fixes go into RouterOS without mention in the changelog.
If only because some thing suddenly appear "broken" without any mentioned change in that function or anything related to it.
The changelog is only a recap of the most important changes in that version, otherwise it would be too long.
(I have proposed possible improvements of the whole changelog publication system)

pe1chl · Thu Aug 10, 2023 8:07 pm

Many people, myself included, have had similar thoughts about Mikrotik software releases and other companies' releases as well. Of course this is a naive outlook which is not well matched with reality. If you just think about it a little while you realize it obviously makes no sense to work on one thing at a time. With a team of people you have multiple projects occurring simultaneously simply because you have multiple developers of different levels and skill sets and many things to get done.

Of course we have no idea about how many people are actually working in MikroTik software development, and how specialized they are on certain areas of the system.
In total the company seems to have about 350 employees, but many of those will work on hardware development, production, shipping, accounting, support, sales, management etc.
So how many are active as developers we do not know (AFAIK there are no published figures about that).

What IS quite apparent is that there have been critical shortages in some areas, that required new hiring or re-training. E.g. the whole "routing protocols in v7" department has experienced at least a year of no progress, before it restarted a couple of months ago.
At the moment they appear to be restaffed, but still it surprises me that rather than finishing the job on the existing problems that have been caused by the routing revamp in v7, they already start on new things like IS-IS. This appears to be a single skill set.

Amm0 · Thu Aug 10, 2023 8:51 pm

At the moment they appear to be restaffed, but still it surprises me that rather than finishing the job on the existing problems that have been caused by the routing revamp in v7, they already start on new things like IS-IS.

Well, at this point, IS-IS is an unfilled row on a help page. I'd call that being on the "roadmap" ;)

But help pages also tell me:

BFD
Features not yet supported
enabling BFD for ip route gateways
[...]

skyhawk · Thu Aug 10, 2023 11:30 pm

Out of curiosity, I've had a problem (as others have had) with MLAG. The problem was introduced in 7.7, and just prior to 7.10 being released, it was finally acknowledge as a problem with a solution pending.

What hardware was this on? These fixes in 7.11rc3 have gotten my hEXr3s working the same as the rest of my 'tik gear, at least so far as vlan-filtering, bridging, and rstp are concerned.

*) switch - fixed BPDU packet processing on MT7621, MT7531 with HW offloaded vlan-filtering;
*) switch - improved multicast packet forwarding on MT7621;

pe1chl · Fri Aug 11, 2023 12:13 am

At the moment they appear to be restaffed, but still it surprises me that rather than finishing the job on the existing problems that have been caused by the routing revamp in v7, they already start on new things like IS-IS.
Well, at this point, IS-IS is an unfilled row on a help page. I'd call that being on the "roadmap" ;)

No, it is listed as "initial support" under version 7.12.
So it will start appearing (as usual with only command line support) in version 7.12beta which may appear as soon as end of this month, early next month.
And all that while BGP is not even feature complete relative to v6, and has known bugs that severely affect some people (it works kind of OK for me), and some "new features for v7" are not implemented.

peich1 · Fri Aug 11, 2023 1:09 am

I've been having this off and on with the 7.x releases. 7.9 was fine for me, 7.10.2 my Synology NAS with a ConnectX 4 card + FS SM optic has link, but DHCP/etc do not work. 7.7 was fine, I think 7.8 didn't work, etc. It's all over the map - it's become a guessing game if things will work for me with the 7.x releases and SFP+s on my CRS328. I always see notes about SFP changes in each release so I've stopped reporting the issues because every time it gets fixed, it just gets broken again. I'm going to wait for things to stabilize a bit then start reporting again if it remains broken, because right now it doesn't seem to help resolve the issue since the fixes seem to get invalidated in later releases.

I've tried different versions in the last days and it looks like it happens as you say. The behaviour changes from one version to another in my CRS328 too. I'm starting to think if this is not a mix of hardware and software issues, it's not "normal" having so many problems related with SFP and different firmware versions.

Jotne · Fri Aug 11, 2023 8:04 am

No, it is listed as "initial support" under version 7.12.

Where did you read that?

Amm0 · Fri Aug 11, 2023 8:25 am

No, it is listed as "initial support" under version 7.12.
Where did you read that?

https://help.mikrotik.com/docs/display/ ... l+Overview
And if you make sure your browser window is wide enough, and you'll see a 7.12 column...

Fri Aug 11, 2023 8:40 am

It is quite clear that fixes go into RouterOS without mention in the changelog.
If only because some thing suddenly appear "broken" without any mentioned change in that function or anything related to it.
The changelog is only a recap of the most important changes in that version, otherwise it would be too long.
(I have proposed possible improvements of the whole changelog publication system)

This is absolutely incorrect. Our changelogs do include all (without exceptions) changes in the source code that do affect already released products and features. Of course, sometimes we are working on a new feature in the background or support for a new product and that might in some way interfere and break already working configuration. Also, a lot of things on systems like RouterOS depend on timing, and by adding a code in one facility you might break something else.

Truth be told, most of the issues that are "yelled about" after an upgrade are actually caused by a reboot, changes in the network, different mood of the administrator on that particular day, etc. Forum is a great example. In most cases, when something breaks after an upgrade, there is a discussion here, but once people complain about the issue through support@mikrotik.com and we recommend downgrading software to the previous version for testing purposes - the same issue is also already there (with emphasis on "most", not "all").

Additionally, very, very often we solve some issues and we do post in the changelog what we did actually fix. Networking devices are complex systems that run different tools at the same time and communicate with each other within milliseconds. Quite often you might, for example, see many complaints that, let us say Wireguard is not working after an upgrade. However, the issue was actually DNS in the background and Wireguard could not resolve a remote-peer domain name. So in short - we do describe in the changelog what happens under the hood, not how it might look from the outside.

rextended · Fri Aug 11, 2023 10:24 am

....
Even the discourse of quotations, hundreds of useless posts are produced in the search, because the search also searches in the quoted text, making a mess that disorients.
Good point ... It's a ROS 7.11rc2 topic ... please do not flood it with moderation complains. Should I delete or moderate your post?
That is the closest /latest topic to discuss moderation: viewtopic.php?t=197356

You know I respect you, but this time you were wrong.
With all the posts that have absolutely nothing to do with this topic, you see just mine that complains about how moderators don't moderate properly?

please do not flood it with moderation complains.

I only wrote it once.

pe1chl · Fri Aug 11, 2023 11:06 am

No, it is listed as "initial support" under version 7.12.
Where did you read that?

On this page: https://help.mikrotik.com/docs/display/ ... l+Overview

pe1chl · Fri Aug 11, 2023 11:40 am

It is quite clear that fixes go into RouterOS without mention in the changelog.
If only because some thing suddenly appear "broken" without any mentioned change in that function or anything related to it.
The changelog is only a recap of the most important changes in that version, otherwise it would be too long.
(I have proposed possible improvements of the whole changelog publication system)
This is absolutely incorrect. Our changelogs do include all (without exceptions) changes in the source code that do affect already released products and features. Of course, sometimes we are working on a new feature in the background or support for a new product and that might in some way interfere and break already working configuration.

Well, that may be the official position, but e.g. take a look on the whole DNS resolver disaster earlier this year.
There were no announced DNS changes but at some point the resolver broke down. Only after that, a lot of release note mentions of things that were fixed came with the different (beta, rc and final) releases, but the rework of the DNS resolver "that should not affect the users" never were in the release notes.
When I asked about that, the reply (I think on Jira) was "yeah we made a lot of changes in the DNS code".

To be complete, it should include items like "dns) did a lot of rework and cleanup of the code, should not affect the users" but such items never appear AFAIK.

It seems that similar things happen with OpenVPN and wireguard, but I never use these features so I have no experience with it myself. But I WAS affected by the DNS trouble, that caused a lot of confusion and debugging here.

Fri Aug 11, 2023 12:03 pm

DNS changes are listed in the changelogs. You can re-read them here. You are referring to versions 7.4,7.5,7.6,7.7, 7.8, and others. There are plenty of changes listed in the changelog:
https://mikrotik.com/download/changelogs
So no, we did not hide anything there. Just described hundreds of code lines within a sentence. Of course in software development that can lead up to an unexpected issues. If they would be expected, then they would not be introduced.
Please, as stated in the first post on this topic and each and every other RouterOS release topic - keep this forum discussion strictly related to the version. In this vase, issues introduced v7.11.
Feel free to open a new topic for discussing MikroTik release notes and their structure.

Cha0s · Fri Aug 11, 2023 12:20 pm

Truth be told, most of the issues that are "yelled about" after an upgrade are actually caused by a reboot

Even if that is the case (reboot), which in my 18year experience with MikroTik, very rarely is, isn't that a bug on its own?

It's 2023, reboot should never be a solution to any problem. That's not Windows 95 that needed a reboot every time you twisted your head in the wrong way... just saying...

maigonis · Fri Aug 11, 2023 12:39 pm

Updated hap ax lite lte6 to rc3 and noticed that on lte1 interface Data class in not showing CA usage, rc2 was fine. Informative/cosmetic thing, CA is used as CA band is shown on load and can see proper 2CA speeds.

Fri Aug 11, 2023 12:42 pm

Updated hap ax lite lte6 to rc3

Q: was on your device also lte1 configured as WAN and all ether ports as LAN ?
Because for AX Lite ether1 was WAN so I was a bit surprised to see it was different for AX Lite LTE (but it does make sense like it is).

Fri Aug 11, 2023 4:08 pm

All LTE home WiFI devices have such default config. It must be like that out of box already. Chateau is the same.

Fri Aug 11, 2023 4:23 pm

OK, thanks for confirming.
As said, it makes perfect sense thinking about it.

pe1chl · Fri Aug 11, 2023 4:45 pm

Truth be told, most of the issues that are "yelled about" after an upgrade are actually caused by a reboot
Even if that is the case (reboot), which in my 18year experience with MikroTik, very rarely is, isn't that a bug on its own?

It doesn't happen often that a reboot fixes a problem, but it can happen that a reboot results in a situation that does not occur when you make a configuration step by step, which is then built in a different sequence after reboot.

Especially for those that build VPN or other tunnel interfaces that rely on other things already running, like DNS or setup of the local address of the router.

Paternot · Fri Aug 11, 2023 6:45 pm

On this page: https://help.mikrotik.com/docs/display/ ... l+Overview

By the way: is it only me, or the text for "Show from which peer route received", on the "v7.1" column is light gray over green - make it quite hard to read?

light_grey_over_green.png

Jotne · Fri Aug 11, 2023 7:20 pm

Same for me.

bpwl · Fri Aug 11, 2023 7:29 pm

hAP ac3 , upgrade from ROS 7.10.2 stable, to 7.11rc3 ...
failed
"can not install lora-7.11rc3: iot-7.11rc3 is not installed, but is required"
Installed packages: (none was upgraded)
[admin@hAPac3] /system/package> print
Flags: X - DISABLED
Columns: NAME, VERSION
# NAME VERSION
0 iot 7.10.2
1 dude 7.10.2
2 lora 7.10.2
3 tr069-client 7.10.2
4 container 7.10.2
5 user-manager 7.10.2
6 zerotier 7.10.2
7 routeros 7.10.2
8 rose-storage 7.10.2
9 X wifiwave2 7.10.2

Something to do with the following change?

*) lora - moved LoRa service to IoT package;

hAP ac3 , no Lora card, but interested in the MQTT service of IOT.

pe1chl · Fri Aug 11, 2023 7:40 pm

By the way: is it only me, or the text for "Show from which peer route received", on the "v7.1" column is light gray over green - make it quite hard to read?

It is used to hide secrets :-)

Amm0 · Fri Aug 11, 2023 7:40 pm

hAP ac3 , upgrade from ROS 7.10.2 stable, to 7.11rc3 ...
failed
"can not install lora-7.11rc3: iot-7.11rc3 is not installed, but is required"
[...]
Something to do with the following change?
Code: Select all
*) lora - moved LoRa service to IoT package;
hAP ac3 , no Lora card, but interested in the MQTT service of IOT.

Well, I'm guessing you need to remove the LoRa package... but sounds like a bug.

Now MQTT has been always IoT package since it came out — but you'll be getting the new MQTT subscribe in 7.11 :)

skyhawk · Fri Aug 11, 2023 8:58 pm

hAP ac3 , upgrade from ROS 7.10.2 stable, to 7.11rc3 ...
failed
"can not install lora-7.11rc3: iot-7.11rc3 is not installed, but is required"

Something to do with the following change?
Code: Select all
*) lora - moved LoRa service to IoT package;
hAP ac3 , no Lora card, but interested in the MQTT service of IOT.

You might be able to force this through by also installing IoT package from extra-packages at the same time?
But yeah, stock-to-stock upgrades shouldn't fail, this sounds like a bug to me too... I would suggest waiting for a response from MikroTik. This might actually be worth opening a support ticket for, because this is the kind of thing that might cause a *lot* of end-user upgrades to fail.

edit: Actually, it looks like lora was an extra-package before. It's not unreasonable for a device with one or more extra-packages installed to require those extra-packages to be presented by a user doing a manual RouterOS upgrade. In this case, I'd suggest do the upgrade again, but give the router the IoT package along with the main RouterOS package.

bpwl · Fri Aug 11, 2023 10:33 pm

Already manually removed lora-7.10.2 and iot-7.10.2 . Upgrade to 7.11rc3 done and OK. Will add the new IOT again later. This time there normally is no LoRa package, as the change log it is now part of IOT. But there is a smaller LoRa one in the 7.11rc3 extra packages ZIP file.

The update logic got confused, all of LoRa service moved to IoT package ???? or only some parts ????

Anyway BTH in 7.11rc3 works fine! Very easy to set up. Excellent feature for my short-term holiday travel.

Amm0 · Fri Aug 11, 2023 10:40 pm

The update logic got confused, all of LoRa service moved to IoT package ???? or only some parts ????

Seems like in an upgrade bug. I read RN that going forward you use iot.npk for LoRa... but it should still handle if you already had lora.npk installed to upgrade...

Cha0s · Fri Aug 11, 2023 11:01 pm

On this page: https://help.mikrotik.com/docs/display/ ... l+Overview
By the way: is it only me, or the text for "Show from which peer route received", on the "v7.1" column is light gray over green - make it quite hard to read?light_grey_over_green.png

I probably depends on the monitor.

On my Dell QHD monitor and Thinkpad laptop both show the green very clearly with good contrast between gray and green.
But on my old Asus (decade+ old) monitors I can barely distinguish the gray from the green boxes.

Amm0 · Sat Aug 12, 2023 12:35 am

*) lora - moved LoRa service to IoT package;

FWIW, the help docs on "Packages" and "Lora" do not reflect this...
https://help.mikrotik.com/docs/display/ROS/Packages
https://help.mikrotik.com/docs/display/ ... Properties

vuducdong · Sat Aug 12, 2023 7:33 am

please fix the compatibility of RB4011, RB5009 (versions 7.8 to 7.11) with sfp gpon

Jotne · Sat Aug 12, 2023 10:05 am

What is the problem and have you made a support case?

Znevna · Sat Aug 12, 2023 10:56 am

It doesn't work.

bpwl · Sat Aug 12, 2023 12:51 pm

Already manually removed lora-7.10.2 and iot-7.10.2 . Upgrade to 7.11rc3 done and OK. Will add the new IOT again later. This time there normally is no LoRa package, as the change log it is now part of IOT. But there is a smaller LoRa one in the 7.11rc3 extra packages ZIP file.

The update logic got confused, all of LoRa service moved to IoT package ???? or only some parts ????

Anyway BTH in 7.11rc3 works fine! Very easy to set up. Excellent feature for my short-term holiday travel.

FYI ...

Help docs on packages are very limited

When both npk : iot & lora are copied to files ... install failed. Was is because now I used tmpfs?
When only iot copied (not tmpfs) .. OK.
Well the iot-7.11rc3 package includes LoRa (Lora comes as submenu of iot in WinBox)
The lora-7.11rc3 package brings again the same lora menu now as top menu. (is redundant? not needed)

seriquiti · Mon Aug 14, 2023 8:25 am

Anyone noticed the following issue on HEX(RB750):

As soon as I update to this version all inter vlan printing stops working with Bridge hardware offloading enabled even though hosts can ping the printer. Disabling hardware offloading fixes the issue immediatly but only for a few minutes then all VLANs just stop responding.

Updated to RC because was hoping this fixes other Bridge issues with HW offloading on but seems like this just makes everyting even worse.

Mon Aug 14, 2023 8:31 am

Best to create a separate topic with your config and explanation about network setup so others can have a look to make sure it's not config related.
Worst case you may have to file bug report with your supout.rif to support.
rc2 and rc3 contain some fixes related to Bridge HW offloading but it's always possible some use case is being missed.

seriquiti · Mon Aug 14, 2023 8:40 am

For now I have dowgraded and all is back to normal. Will do some testing with another unit I have and see if I can replicate the issue.

epkulse · Mon Aug 14, 2023 9:52 am

I have asked this question before, and I have issued a support ticket. And I know it has been answered to be related to the client behaving erroneus. Still, it is very annoying. The issue is that my Macbook intermittently looses wifi connection, sometimes only with a few minutes of connection. I manually reconnect and it works again - but disconnects again after a while. The log says:
"9C:3E:53:70:A6:22@Nere-50 disconnected, SA Query timeout, signal strength -46"

Is this "SA Query Timeout" entirely an error by the client, or is my MT HAP-AX3 (running Capsman wifiwave2) doing something not OK here. I have seen forum items explaining why this occurs - but still... Anyone else having the noted the same? Is this something Apple is causing, or does it happen also to other clients? Or is it only my Macbook?

Rox169 · Mon Aug 14, 2023 10:03 am

I had similar situation very annoying...I had teams call and suddenly my new Dell with WiFI 6 disconnected from my hap AX3 and immediately connected to the same WiFI. In log was SA Query timeout. I do not think that this is OK

Mon Aug 14, 2023 10:08 am

What's new in 7.11rc4 (2023-Aug-11 12:57):

*) bth - removed from 7.11 for "stable" release, the development will continue in "beta" 7.12;
*) ike1 - fixed Phase 1 when using aggressive exchange mode (introduced in v7.10);
*) poe-out - advertise LLDP power-mdi-long even if no power allocation was requested (introduced in v7.7);
*) sfp - fixed incorrect optical SFP temperature readings (introduced in v7.10);

epkulse · Mon Aug 14, 2023 10:21 am

I had similar situation very annoying...I had teams call and suddenly my new Dell with WiFI 6 disconnected from my hap AX3 and immediately connected to the same WiFI. In log was SA Query timeout. I do not think that this is OK

That´s why I asked again. If maybe something is not handled correctly by Mikrotik in the RC-version, to avoid lots of complaints when rolling out stable 7.11. I have not tested if possibly the same behaviour appears on 7.10.2. I use the RC as I have wifiwave2 and I believe the RC-version is more stable still...

Rox169 · Mon Aug 14, 2023 11:32 am

I like that MT is releasing so many RC version till stable. Please keep it that way and do not rush with testing.

Jotne · Mon Aug 14, 2023 12:19 pm

bth is removed. hmm

Znevna · Mon Aug 14, 2023 12:21 pm

yes yes, because if nothing else critical pops up as reproducible by support staff they'll just slap a stable tag on this rc4 and rebuild it calling it a stable release.

mkx · Mon Aug 14, 2023 12:22 pm

Obviously BTH is not release-ready yet. And probably stabilizing BTH would take longer time than MT devs would like. Specially as many users are eagerly awaiting for wifiwave2 stability ... which is IMO waaay more important than some random new feature.

eworm · Mon Aug 14, 2023 12:43 pm

I would put in another fact... Probably Mikrotik needs to scale up the infrastructure before this can be released for anybody to be used in a stable release.

Mon Aug 14, 2023 12:59 pm

We had three options - release BTH as is, delay 7.11 stable just due to the BTH or remove BTH. We did choose to remove BTH as we can not call it "stable" yet and move a step closer to 7.11 (stable) for those who do not care about BTH. We would like to call it a win-win. BTH will be back on 7.12, no worries.

Rox169 · Mon Aug 14, 2023 1:04 pm

Strods this is good aproach...when it is not stable just do not include it in stable version. BTH can wait we have Wireguard anyway...

S8T8 · Mon Aug 14, 2023 1:21 pm

Obviously BTH is not release-ready yet. And probably stabilizing BTH would take longer time than MT devs would like.

As MikroTIk fan, this move is 100% approved, BTH is a nice have but pretty sure there is a looong list of things to fix/improve!
Nice job MT, waiting for Stable.

dark77 · Mon Aug 14, 2023 1:26 pm

We had three options - release BTH as is, delay 7.11 stable just due to the BTH or remove BTH. We did choose to remove BTH as we can not call it "stable" yet and move a step closer to 7.11 (stable) for those who do not care about BTH. We would like to call it a win-win. BTH will be back on 7.12, no worries.

Nice move. I wait for Stable.
Thanks.

nescafe2002 · Mon Aug 14, 2023 5:23 pm

*) ike1 - fixed Phase 1 when using aggressive exchange mode (introduced in v7.10);

Minor detail, but I'd argue this was introduced in 7.11beta2 not 7.10 (SUP-122289). Thank you very much for thoroughly diagnosing and fixing the issue.

pe1chl · Mon Aug 14, 2023 6:05 pm

Minor detail, but I'd argue this was introduced in 7.11beta2 not 7.10 (SUP-122289). Thank you very much for thoroughly diagnosing and fixing the issue.

I have a feeling that in some cases the renewal of an IPsec ike1 association kills some other associations and triggers a renewal.
Did you observe that? It happens in "main" mode so it may not be related to this. What I observe is when a GRE/IPsec tunnel's IPsec is renewed, the L2TP/IPsec from the same remote peer is renewed at the same time. The local address is different for these.

nescafe2002 · Mon Aug 14, 2023 6:25 pm

I have a feeling that in some cases the renewal of an IPsec ike1 association kills some other associations and triggers a renewal.
Did you observe that? It happens in "main" mode so it may not be related to this. What I observe is when a GRE/IPsec tunnel's IPsec is renewed, the L2TP/IPsec from the same remote peer is renewed at the same time. The local address is different for these.

In this case, a peer with aggressive mode set would continuously trigger a rekey for *all* other peers/policies (different remote addresses).
Not sure if both issues are related. Would recommend finding a reproducible scenario and submit the case to support.

pe1chl · Mon Aug 14, 2023 6:51 pm

In this case, a peer with aggressive mode set would continuously trigger a rekey for *all* other peers/policies (different remote addresses).

Ok that is interesting, I will try to find an opportunity to upgrade the software on that router and see if it is the same issue. Thanks!

epkulse · Mon Aug 14, 2023 11:00 pm

I had similar situation very annoying...I had teams call and suddenly my new Dell with WiFI 6 disconnected from my hap AX3 and immediately connected to the same WiFI. In log was SA Query timeout. I do not think that this is OK
That´s why I asked again. If maybe something is not handled correctly by Mikrotik in the RC-version, to avoid lots of complaints when rolling out stable 7.11. I have not tested if possibly the same behaviour appears on 7.10.2. I use the RC as I have wifiwave2 and I believe the RC-version is more stable still...

Noted that if I choose 2,4 network instead of 5 G - the SA Query Timeout is gone. My 2,4G network has WPA/WPA2 only since I have old devices not supporting WPA 3. Can this be related to WPA3 security?

evbocharov · Mon Aug 14, 2023 11:34 pm

That´s why I asked again. If maybe something is not handled correctly by Mikrotik in the RC-version, to avoid lots of complaints when rolling out stable 7.11. I have not tested if possibly the same behaviour appears on 7.10.2. I use the RC as I have wifiwave2 and I believe the RC-version is more stable still...
Noted that if I choose 2,4 network instead of 5 G - the SA Query Timeout is gone. My 2,4G network has WPA/WPA2 only since I have old devices not supporting WPA 3. Can this be related to WPA3 security?

use disable-pmkid=yes

gigabyte091 · Tue Aug 15, 2023 9:38 am

What's new in 7.11rc4 (2023-Aug-11 12:57):

*) bth - removed from 7.11 for "stable" release, the development will continue in "beta" 7.12;

So are you keeping up your relay ? Or it will be offline until 7.12beta ?

epkulse · Tue Aug 15, 2023 12:07 pm

Noted that if I choose 2,4 network instead of 5 G - the SA Query Timeout is gone. My 2,4G network has WPA/WPA2 only since I have old devices not supporting WPA 3. Can this be related to WPA3 security?
use disable-pmkid=yes

I have set disable pmkid since before. And now removed WPA3. Seems more stable.

Tue Aug 15, 2023 3:24 pm

RouterOS v7.11rc4 has been promoted to 7.11 stable:
viewtopic.php?t=198641