Code: Select all

*) mpls - improved MPLS TCP performance;

What can this mean?

SNMP Routing Table error ("Error: OID not increasing:") still not fixed, which exists since version 7.9 (SUP-117934 / SUP-119410).

7.9 changelog:

Code: Select all

*) snmp - improved outputting of routes;

Unfortunately you didn't improve it, you broke it.

You can reproduce the problem by creating multiple routes with the same destination.

Code: Select all

*) webfig - added option to enable wide view in item list;

.
This is awesome, thanks a lot for that Mikrotik :) Please consider allowing the "wide view" to be set as default somehow, and not requiring to click on the icon each time. Please also consider, and i'm asking that once again, consider also giving us the option to choose between inline or 'newline' comments.

*) system - reduced RAM usage for SMIPS devices;

*) wireguard - fixed peer connection using DNS name on IP change;

*) ssh - fixed user RSA private key import;

*) bridge - added more STP-related logging;

I'm really having a hard time understanding why you needlessly install all the extra packages if you then disable them...

Classic logic error...

So I shouldn't report?

Code: Select all

*) mpls - improved MPLS TCP performance;

What can this mean?

It works better now :)

I think in general, it has to be considered to have persistent settable viewing options in webfig. There are none, so first that has to be implemented.

*) console - improved timeout for certain commands and menus;

{
  :put "$[/terminal style escape]Press any key to exit loop"; 
  :local keypress 0xFFFF;
  while (keypress=0xFFFF) do={ 
      :put "$[/terminal style none]$[:rndstr]" 
      /terminal cuu    
      :set keypress [/terminal inkey timeout=1s]
  }
}

What's new in 7.11beta2 (2023-Jun-21 14:39):

*) netwatch - added "src-address" property;

*) mqtt - added new MQTT subscribe feature;

What's new in 7.11beta2 (2023-Jun-21 14:39):

*) netwatch - added "src-address" property;

Thanks!!!!!! Finally, no more mangle rules for doing this.

Hi all, what is the correct way to have pppoe simple queues dynamically created as children of a Parent queue, and update the target list on connection and disconnection?

I was thinking about address lists or interface lists, but it seems the target ignores all of these.

Thank you

yes, but it is alpha, alpha should be older than beta....and there is no changelog so it is woth to try it?

jut to let you know...my wifi speed on AX3 is one of the worst ever

Thanks — timeout= in /terminal/inkey now works again!

there is newer alpha (development) release (with build time of 16:17:11) on mikrotik website..

you may need to check it out before reporting issues

This version includes the changes that were present in 7.11alpha127 that was shared on the forum. While some users have reported improvements with this version, the issue is not fully resolved. We are still working on it.

*) wireguard - fixed peer connection using DNS name on IP change;

Any details? What case should it fix?

*) w60g - improved stability for Cube 60Pro ac and CubeSA 60Pro ac devices;

*) w60g - improved stability for Cube 60Pro ac and CubeSA 60Pro ac devices;

The 7.11alpha I was given by support did not fix this one for me.

Worst ever, I wouldn't say. Still low 600 here.
But it looks to be noticeably slower, yes.

Might have to do some more tests with other versions tomorrow to know for sure for myself.

Speedtest from rpi4 through router to pc (primitve but hey!)
Singlethread
iperf3 -c 192.168.0.135

- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 719 MBytes 603 Mbits/sec 271 sender
[ 5] 0.00-10.00 sec 717 MBytes 601 Mbits/sec receiver


iperf3 -c 192.168.0.135 -R
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.00 sec 418 MBytes 351 Mbits/sec sender
[ 5] 0.00-10.00 sec 416 MBytes 349 Mbits/sec receiver



Multithread
iperf3 -c 192.168.0.135 -P 10 -b 1000M
[SUM] 0.00-10.00 sec 961 MBytes 806 Mbits/sec 81 sender
[SUM] 0.00-10.01 sec 946 MBytes 793 Mbits/sec receiver


iperf3 -c 192.168.0.135 -P 10 -b 1000M -R
[SUM] 0.00-10.01 sec 710 MBytes 595 Mbits/sec sender
[SUM] 0.00-10.00 sec 707 MBytes 593 Mbits/sec receiver

WiFi hAP ax2 CLI to PC btest.exe running server


tool/speed-test address=192.168.0.135
status: udp download
time-remaining: 19s
ping-min-avg-max: 1.78ms / 2.64ms / 5.14ms
jitter-min-avg-max: 3us / 409us / 2.81ms
loss: 0% (0/200)
tcp-download: 739Mbps local-cpu-load:66%
tcp-upload: 916Mbps local-cpu-load:41% remote-cpu-load:1%

Ethernet/usb test pi to pc

forward singlethread also primitive usb setup/adapter

[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.00 sec 1.07 GBytes 916 Mbits/sec sender
[ 5] 0.00-10.00 sec 1.06 GBytes 912 Mbits/sec receiver

reverse singlethread
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.00 sec 1.07 GBytes 916 Mbits/sec sender
[ 5] 0.00-10.00 sec 1.06 GBytes 912 Mbits/sec receiver

Edit: Forgive me I mixed up the last two tests, here they are in full
-----------------------------------------------------------
Server listening on 5201 (test #7)
-----------------------------------------------------------
Accepted connection from 192.168.0.8, port 45268
[ 5] local 192.168.0.135 port 5201 connected to 192.168.0.8 port 45270
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 111 MBytes 931 Mbits/sec
[ 5] 1.00-2.00 sec 112 MBytes 941 Mbits/sec
[ 5] 2.00-3.00 sec 111 MBytes 933 Mbits/sec
[ 5] 3.00-4.00 sec 107 MBytes 899 Mbits/sec
[ 5] 4.00-5.00 sec 112 MBytes 941 Mbits/sec
[ 5] 5.00-6.00 sec 108 MBytes 909 Mbits/sec
[ 5] 6.00-7.00 sec 109 MBytes 913 Mbits/sec
[ 5] 7.00-8.00 sec 111 MBytes 933 Mbits/sec
[ 5] 8.00-9.00 sec 106 MBytes 890 Mbits/sec
[ 5] 9.00-10.00 sec 103 MBytes 866 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.00 sec 1.07 GBytes 916 Mbits/sec sender
-----------------------------------------------------------
Server listening on 5201 (test #8)
-----------------------------------------------------------
Accepted connection from 192.168.0.8, port 45272
[ 5] local 192.168.0.135 port 5201 connected to 192.168.0.8 port 45274
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 112 MBytes 939 Mbits/sec
[ 5] 1.00-2.00 sec 111 MBytes 928 Mbits/sec
[ 5] 2.00-3.00 sec 112 MBytes 940 Mbits/sec
[ 5] 3.00-4.00 sec 112 MBytes 939 Mbits/sec
[ 5] 4.00-5.00 sec 112 MBytes 941 Mbits/sec
[ 5] 5.00-6.00 sec 112 MBytes 941 Mbits/sec
[ 5] 6.00-7.00 sec 112 MBytes 941 Mbits/sec
[ 5] 7.00-8.00 sec 112 MBytes 940 Mbits/sec
[ 5] 8.00-9.00 sec 112 MBytes 939 Mbits/sec
[ 5] 9.00-10.00 sec 112 MBytes 940 Mbits/sec
[ 5] 10.00-10.00 sec 325 KBytes 874 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.00 sec 1.09 GBytes 939 Mbits/sec receiver

When you test, what's the CPU usage on AX3 or AX2 ?
If one of the cores is at 100%, that's your bottleneck.

EDIT: just checked when doing iperf from PC wired to AX3, 2.5Gb trunk to RB5009-container. CPU is around 49% on RB5009, below 20% on AX3, results (as expected) around 950-960Mbps.
Towards RB5009.
Which is way more powerful then AX3.
So I am going to guess you have a bottleneck on AX3 when running that container.

can you read? all of those issues happend on 7.11beta2.....

IKE2 is broken since 7.10, can't get site to site working properly. Created SUP-117869 two months ago but issue still persists.

IKE2 is broken since 7.10, can't get site to site working properly. Created SUP-117869 two months ago but issue still persists.

Hi,

What happens to him? What is your setup?

Regards,

I have noticed that roaming mostly works fine when using WPA2 only (using capsman so roaming between APs) and doesn't work properly on devices that prefer WPA3 when using WPA2/3 mixed. However sometimes the roaming fails with SA query timeout even on WPA2 only mode. New supout attached to SUP-116463

Hi,

So we're in the same problem, it seems (SUP-120165).

I am experiencing disconnections every 30 minutes, which matches the "Lifetime" of phase 2 (proposal) even though I have "PFS Pool" set to none.

In previous versions I did not notice this behavior.

Code: Select all

IPsec-SA expired before completion of key change.

Regards,

/routing/route/print where received-from=bgp1
or
/routing/route/print where received-from bgp1

did not works, wait for hours and no prefix has displayed

thx

*) wireguard - fixed peer connection using DNS name on IP change;

Any details? What case should it fix?

@mantouboji for a client the IP address does not to be renewed until TTL expires.

So what is the TTL of your DNS registration?

WG will renew the resolve on restart of the WG peer. You can't check every so many seconds if the DNS changes brcause of Round Robin when having multiple IP addresses. Then MT could have built-in a option that enables to say it is using a dynamic DNS that only will return one IP address.

Automating that, ckeck DNS and accept different IP when connection is lost. User needs to activate that procedure.

@mantouboji for a client the IP address does not to be renewed until TTL expires.

So what is the TTL of your DNS registration?

WG will renew the resolve on restart of the WG peer. You can't check every so many seconds if the DNS changes brcause of Round Robin when having multiple IP addresses. Then MT could have built-in a option that enables to say it is using a dynamic DNS that only will return one IP address.

Automating that, ckeck DNS and accept different IP when connection is lost. User needs to activate that procedure.

TTL doesn't matter, i have hosts with 15 sec TTL and after ip changes WG never connects back even after several days unless you re-toogle it, which also requires scripts or netwatch for monitoring.

Anyway i repeat, Mikrotiks fix works and issue is solved!

Once RB4011 reboot, change to a new IP, and update domain name (xxx.dyndns.info ), the ax2 resolv the new domain name correctly, but wireguard peer still attemp to connect old IP, so must reboot AX2 to resolv it.

That's WG behaviour by design, and people solve that problem with scripts: viewtopic.php?t=166214

/routing/route/print where received-from=bgp1
or
/routing/route/print where received-from bgp1

did not works, wait for hours and no prefix has displayed

thx

That is correct. You need to use "belongs-to".
received-from is a field from RouterOS v6 that is no longer supported in any 7.x version, it would be better if it were removed from the list.
(or it should be fixed so it works again)

... and no one knows why...😭

Hi peichl, i tried /routing/route/print where belongs-to did not works either.
can u capture yours for example, maybe i did wrong

OVPN works much better!!

Hi peichl, i tried /routing/route/print where belongs-to did not works either.
can u capture yours for example, maybe i did wrong

Parameter of "belongs-to" is like "bgp-IP-1.2.3.4" when your BGP peer has address 1.2.3.4
Probably for other routing protocols it will be similar.
It can also be "static" or "connected".

@Plugpulled
At least report errors to support, or just talk on the forum?

kernel failure in previous boot
please check SUP-121322
[RouterOS 7.11beta4]kernel failure in previous boot

*) wifiwave2 - fixed interface hangs on IPQ6010-based boards (introduced in v7.9);

What meen this bug fix? What interface hangs?

What meen this bug fix? What interface hangs?

The malfunctions would cause client device disconnections and subsequent key handshake timeouts until the AP is rebooted.
This fix prevents the malfunction from occurring.

What's new in 7.11beta4 (2023-Jul-05 13:33):

*) 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;
*) bridge - added warning when VLAN interface list contains ports that are not bridged;
*) bridge - prevent bridging the VLAN interface created on the same bridge;
*) console - fixed incorrect default value of ":return" command (introduced in v7.11beta2);
*) console - improved stability and responsiveness;
*) container - fixed duplicate image name;
*) dns - improved system stability when processing static DNS entries with specified address-list;
*) 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;
*) 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;
*) lte - fixed Dell DW5221E "at-chat" support;
*) lte - only listen to DHCP packets for LTE passtrough interface in auto mode when looking for the host;
*) package - treat disabled packages as enabled during upgrade;
*) profile - added "container" process classifier;
*) profile - properly classify "console" related processes;
*) quickset - correctly apply configuration when using "DHCP Server Range" property;
*) rose-storage - added "scsi-scan" command (CLI only);
*) route - added comment for BFD configuration (CLI only);
*) route - convert BFD timers from milliseconds to microseconds after upgrade;
*) sfp - improved optical QSFP interface handling for 98DX8332, 98DX3257, 98DX4310, 98DX8525 switches;
*) wifiwave2 - fixed "reg-info" information for several countries;
*) wifiwave2 - fixed interface hangs on IPQ6010-based boards (introduced in v7.9);
*) wifiwave2 - rename "reg-info" country argument from "Macedonia" to "North Macedonia";
*) winbox - fixed "Storm Rate" property under "Switch/Port" menu;
*) winbox - fixed BGP affinity display;
*) wireless - ignore EAPOL Logoff frames;
*) x86 - updated e1000 driver;

/routing/route/print where received-from or /routing/route/print where belongs-to broken, please fix it.

Hi,

I have issue with speed detection of LAN on AX2.



Once is detected speed 1G and once 100M with the same device.

Hi,

I have issue with speed detection of LAN on AX2.

Once is detected speed 1G and once 100M with the same device.

Once is detected speed 1G and once 100M with the same device.

Is it a known quirk, that wifi3-wifi6 CAPSMAN controlled slave interfaces disappear and then re-appear on enrolled APs with different reference names?

# cAP WiFi bridge port configuration in datapath settings, not /bridge/port menu
/interface/wifiwave2/datapath add name=bridged bridge=bridge interface
/interface/wifiwave2 set [find] datapath=bridged
/interface/wifiwave2/cap cap set slaves-datapath=bridged

# schedhuled script to reconfigure bridge VLANs if any include unused interface IDs
/global taggedVLANIDs {52;53;666;667}
/global untaggedVLANIDs {1}
/global wifis [/int wifi find where bound]
/global wifiNames ""
:foreach wifi in=$wifis do={
    /global wifiName [/int wifi get $wifi name]
    /set wifiNames ($wifiNames . "," . $wifiName)
}
/global PortList ("ether1,bridge" . $wifiNames)
/global VLANsWithDefunctIDs [/int bridge vlan find where tagged~"\\*" or untagged~"\\*"]
:foreach defunctVLAN in=$VLANsWithDefunctIDs do={
    :foreach VLANID in=$taggedVLANIDs do={
        if ([/int/bridge/vlan get $defunctVLAN vlan-id]=$VLANID) do={
                /int/bridge/vlan set $defunctVLAN tagged=$PortList
        }
    }
    :foreach VLANID in=$untaggedVLANIDs do={
        if ([/int/bridge/vlan get $defunctVLAN vlan-id]=$VLANID) do={
                /int/bridge/vlan set $defunctVLAN untagged=$PortList
        }
    }
}

Temporarly you can solve with deleting all templates, reboot, and after that do this

Code: Select all

/routing bgp template
add as=65530 disabled=no name=default routing-table=main

and add back the other templates, set the default template, then set the correct template for each "connection"...

I never use the default objects, I often just disable them (or ignore them if not disableable) and create the new ones I need.

- when exporting bgp configuration, as number should always be exported also when it is 65530.

Also noticed something else in IP/Cloud:
2 tabs with BTH VPN and BTH VPN WIreguard (BTH = Back To Home).
What are those supposed to be used for??
Can't see anything in the release notes for that.

Also noticed something else in IP/Cloud:
2 tabs with BTH VPN and BTH VPN WIreguard (BTH = Back To Home).
What are those supposed to be used for??
Can't see anything in the release notes for that.

Using 7.11beta4 here and did not see nothing like you mentioned.
I must confess that I'm a bit curious to see that.

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

/interface bridge
add name=test-bridge vlan-filtering=yes
/interface bridge vlan
add bridge=test-bridge tagged=test-bridge vlan-ids=111
/interface vlan
add name=test-vlan-111 interface=test-bridge vlan-id=111
/interface bridge port
add bridge=test-bridge interface=test-vlan-111 pvid=111

You can ensure wireless interfaces are always added as bridge ports on the cAP by specifying it in the wireless datapath settings, not in the bridge port configuration.

Finally, if RADIUS CoA worked with standalone APs, it should work with CAPsMAN as well.

Also noticed something else in IP/Cloud:
2 tabs with BTH VPN and BTH VPN WIreguard (BTH = Back To Home).

How odd ... it doesn't show in RB5009, AX2, mAP, MAP Lite, Hex, ...
But it does on AX3 and AX Lite ?

Code: Select all

[-a-zA-Z0-9][-a-zA-Z0-9][-a-zA-Z0-9][-a-zA-Z0-9]+\.[a-z][a-z]+

(briefly tested the creation, did not test the tunnel since that AX3 is behind another router, so it will not work that way).

Back to Home VPN service

Only during BETA period it is limited to 802.11ax devices with wifiwave2 package.
We will expand supported device list after 7.11 release

(briefly tested the creation, did not test the tunnel since that AX3 is behind another router, so it will not work that way).

actually it will, because if router is behind NAT, connection will be going through our relay service, securely