Please gato and mouse take your time quibbles to another thread LOL. I think MT gets the picture …half baked time solution creates more work then it solves, they need to go back to the drawing board.
Nope, even disabling WPA3-PSK and Disable PMKID did not help - wlan devices unable to connect and obtain IP from DHCP (using vlans). Still the same issue…
well, maybe it is too early for joy, but looks like WireGuard IPv6 spoke&hub finally working on mmips
it was known problem that only last enabled WG peer will route properly IPv6, others will be lost, but now …wooow
For some unknown reason for me I expect to see ros v8.0 after v7.9 .. I was excited since from what I see BFD will be available in ros v8.0 .. now I’m disappointed .. no v8.0 no BFD
note: I hope everyone understand this is a ironic joke .. however my disappointment for missing BDF is not
note2: however I appreciate the hap ax lite ipsec hw offload , thank you!
.
This forced inline comments on the webfig really discourages the use of comments(which is bad!), as expanding the column to see the comments forces you to scroll horizontally. It might be a good one for big monitors people, but for laptop guys, like me, this is a TERRIBLE change.
. Please revert or, at least, have it configurable!
I tried to update my Adguard container by first stopping/deleting it, and then running the commands below. The first time I ran the commands it just said “extracting” forever, until it stopped both the container I tried to update and the other one that was running. When I rebooted the Adguard container was gone, and when I try to add it back I get this:
[admin@MikroTik] > /container/config/set registry-url=https://registry-1.docker.io tmpdir=usb1-part1/pull
[admin@MikroTik] > /container/add remote-image=adguard/adguardhome:latest interface=veth-adguard envlist=envs_adgu
ardhome root-dir=usb1-part1/containers/adguardhome mounts=adguardhome_data,adguardhome_conf,adguardhome_work workd
ir=/opt/adguardhome/work
failure: could not add
The other container, that I did nothing to, won’t start now either.
The only thing I can find in my configuration of 7.10b5 is QOS simple queues Upstream isn’t working as expected. But even better news, switching over to FQ_Codel is working very well. WiFi in general seems a lot more stable.