posts not strictly related to: v7.4beta [testing]

[Panbambaryla]

Guys,

could you, please, move your discussion regarding IPv6 SLAAC into another thread? This is one big RouterOS topic dominated now by something not strictly related…

[Znevna]

+1 minimum 3 characters

[doneware]

dup post about netwatch not available in CLI. removed. note to myself: read first, then post.

[doneware]

also something strange. I wanted to beef up the 4019’s single-chain wifi with ww2 package on a cube60 pro ac, so i installed ww2 on it - and i lost access to w60 interfaces.
presumably this is expected so, as installing/enabling ww2 disables the ‘default’ wireless package, which also has the drivers for the WiGig part… hopefully this will be a bit enhanced.

[Znevna]

Reading the description of cube60 pro ac, the 5GHz part is used as automatic backup, so they are somewhat tied to one another, I doubt that your request has any standing point.

[pe1chl]

Well, having the possibility for wireless and wireless2 to co-exist would be welcome on my 4011 too!

[WeWiNet]

Wifiwave2:
Using 802.11.r on a pair of 2G and 5G interface with same SSID on audience (set security.ft=yes),
I know see huge amount of “interface flapping” of clients being at the edge of good 5G and better 2G connection.
Before they worked well and did roam from time to time from 5G to 2.4G and back, but really not often and it would not be noticed.
Now its like 4-5 times per minutes and constant reconnects of high layer apps making it impossible to work with them.
Removing 11r, (security.ft=non) and things get stable again…

Anyhow experiencing something like this?

[WeWiNet]

Well, having the possibility for wireless and wireless2 to co-exist would be welcome on my 4011 too!

Or the option to replace the old 11n 2.4G PCIe card which is in RB4011 by a wifiwave2 compatible one.
I just checked yesterday MIkrotik web page. there is none.
Really a pitty as without that for me, the RB4011 with Wifi is a piece of useless HW ready for the bin…

[Znevna]

You can always use it without WiFi.

[pe1chl]

What I do not understand is why the addition of a new WiFi driver (which even has a new configuration command tree) means that the old driver has to be disabled.
I think RouterOS should at boot first enable wifiwave2 and have it probe for its supported hardware, and after that is finished it should enable the old wireless driver and have it find the remainder of the hardware that wifiwave2 has not picked up.
So at least I can have wifi wave2 on 5 GHz while having legacy wifi on 2 GHz (which I use only for some esp8266 gadgets so performance is not important).

[hecatae]

also something strange. I wanted to beef up the 4019’s single-chain wifi with ww2 package on a cube60 pro ac, so i installed ww2 on it - and i lost access to w60 interfaces.
presumably this is expected so, as installing/enabling ww2 disables the ‘default’ wireless package, which also has the drivers for the WiGig part… hopefully this will be a bit enhanced.

Thank you for confirming that the current ww2 package does not contain w60 drivers.

[Znevna]

Container comments don’t get saved.

[tangent]

Group Management Protocol(GMP)

Are you trying to avoid saying the “C” word? Is this CGMP by another name?

[daaf]

I have used:

 0 key="TZ" name="pihole_envs" value="Europe/Riga" 
 1 key="WEBPASSWORD" name="pihole_envs" value="mysecurepassword" 
 2 key="DNSMASQ_USER" name="pihole_envs" value="root"

Some of those changes are present in the previous beta too, what gives?
*) container - added support for running Docker ™ containers on ARM, ARM64 and x86;
*) netwatch - added support for more advanced probing;
*) wifiwave2 - added initial support for roaming (802.11r) between local AP interfaces;

Or they contain fixes over the previous implementation?
LE: ok, netwatch script on-down is fixed, the rest of the reported issues are still present (regarding netwatch).
LE2: I don’t know if containers existed in WinBox but it exists now.
This no longer works since “list” became “key” and of course the settings were not migrated to the new syntax, I had to readd them with “key”

/container/envs/add list=pihole_envs name=TZ value="Europe/Riga"
/container/envs/add list=pihole_envs name=WEBPASSWORD value="mysecurepassword"
/container/envs/add list=pihole_envs name=DNSMASQ_USER value="root"

/container/envs/print 
 0 name="TZ" key="pihole_envs" value="Europe/Riga" 
 1 name="WEBPASSWORD" key="pihole_envs" value="mysecurepassword" 
 2 name="DNSMASQ_USER" key="pihole_envs" value="root"

And using this

/container/add file=zdisk/pihole_dev_armv7.tar root-dir=zdisk/containers/pihole_dev envlist=pihole_envs hostname=pihole logging=yes interface=veth1

Makes the added container to ignore the envlist, since it starts with a random password and dnsmasq runs as “pihole” instead of root.
Meh. How was this tested, again?.. >.>
Adding comments seem to be fixed… too bad about the envlist, this is kind of unusable, again.
Veth interfaces still can’t be edited, any change to address or gateway require a reboot, or removing the interface and recreating it…

[Znevna]

Yes, but it doesn’t work, container ignores envlist.
LE: wrong, see my previous edited comment about this.

[Ovic]

*) wifiwave2 - fixed WPA3-PSK authentication incompatibility with certain vendor and model devices;
This fix is not included in the latest beta, as my Samsung A52s 5G doesn’t connect anymore on the network after upgrade. It only works with 7.3.1

[buset1974]

What’s new in 7.4beta5 (2022-Jun-27 10:39):

*) container - added support for running Docker ™ containers on ARM, ARM64 and x86;
*) dhcpv4-server - disallowed overriding message type option;
*) dhcpv4-server - log message when user option updates existing option;
*) dhcpv4-server - placed option 53 as the first one in the packet;
*) health - fixed requesting data from sensor when issuing “get” command;
*) health - fixed voltage reporting on some RBmAP-2nD devices;
*) lte - validate LTE attached IP type in MBIM mode;
*) netwatch - added support for more advanced probing;
*) poe - hide “poe-voltage” parameter on devices that do not support it;
*) route - expose all valid routes to route select filter from OSPF and RIP;
*) route-filter - fixed route select filter rules;
*) upgrade - ignore same version packages during upgrade procedure;
*) wifiwave2 - added initial support for roaming (802.11r) between local AP interfaces;
*) winbox - added “name” parameter under “Routing/BGP/Session” menu;
*) winbox - added “to-address” and “to-ports” parameters under “IPv6/Firewall/NAT” menu;
*) winbox - added support for “Routing/GMP” menu;
*) winbox - added support for “veth” interface types;
*) winbox - fixed “inactive” flag naming under “MPLS/Local Mapping” menu;
*) winbox - fixed minor typo under “Interface” stats;
*) winbox - fixed units for “reachable-time” parameter under “IPv6/ND” menu;
*) winbox - removed “TLS Host” parameter from “IP/Firewall/NAT” menu;
*) winbox - removed duplicate signal strength column under “Wireless/Registration Table” menu;

No improvement on BGP that already reported? Amazing

[DeviceLocksmith]

Container support is broken for me on arm64 after upgrade from beta4 to beta5. Mount configuration disappeared, as well as maximum ram. Cannot set maximum ram anymore, the value is not displayed in the config. Container fails to start with no error message. It was working fine in beta4.

[Znevna]

Read previous comments.

[DeviceLocksmith]

I am not using envs. It must be broken in multiple ways