However, the code rule we set is “forward-to=1.1.1.1 regex=(.|^)(twitter|twimg).com$”, which can only match “video.twimg.com” but not “dualstack.video.twitter.map.fastly.net”. Some may argue that this setting is correct, but if the DNS cache is cleared, then “video.twimg.com” and subsequent CNAME resolutions will use “forward-to 1.1.1.1”, creating a logical conflict.
please check
SUP-104088, dns AAAA issue
SUP-107205, dns-static CNAME not working.
SUP-107210, dns dynamic server random lost
I feel that these three issues, although different, are all related to the situation mentioned above,
and perhaps all caused by the same reason leading to DNS crash.
All 6 iPads Air with iPadOS 16.3.1 we have now keep disconnecting and reconnecting as soon as the screen turns off.
They are with the screen off and above the table, once the display is switched on, they remain connected.
# feb/17/2023 14:27:19 by RouterOS 7.8rc2
# software id = BH9H-NUQS
#
# model = C53UiG+5HPaxD2HPaxD
# serial number = HDG08XXXXXX
/interface bridge
add admin-mac=48:A9:8A:0E:18:EB auto-mac=no comment=defconf name=bridge
/interface wifiwave2
set [ find default-name=wifi1 ] channel.band=5ghz-ax .skip-dfs-channels=\
10min-cac .width=20/40/80mhz configuration.country=Italy .mode=ap .ssid=\
MikroTik disabled=no security.authentication-types=wpa2-psk \
.management-protection=disabled .wps=disable
set [ find default-name=wifi2 ] channel.band=2ghz-ax .skip-dfs-channels=\
10min-cac .width=20/40mhz configuration.country=Italy .mode=ap .ssid=\
MikroTik disabled=no security.authentication-types=wpa2-psk \
.management-protection=disabled .wps=disable
The “Interfaces/Detect Internet/Detect Internet State” problem still remains.
In Interfaces, the “Detect internet” status doesn’t work after reboot, it only works when I change and revert any of the lists in the “Detect internet” dialog.
After this manipulation, the “Detect internet” status works fine until the next reboot.
Yes, the Internet Detect issue is not solved yet. When it will be fixed, then that will be mentioned in the release notes. We are aware of a problem with Detect Internet. Please keep this topic related only to v7.8 and the issues introduced in it compared to 7.7.
Best solution would be to just remove it. It did not work out, it does not solve any issue or provide any useful function, yet it causes confusion and problems.
They should fix it. Its detection logic is fixed and kinda dumb today, that’s what’s broken. But exactly this kinda stuff ANY “user friendly” UI would need in RouterOS to make things “easier”.
e.g. If that actually worked, there be more automatic ways to use the firewall. If …/detect-internet got things to right interface-list, then “interface detect” could get things to the right interface-list (including LAN/VLANs), and the firewall can be written generically to use the interface-lists. It’s tables all the way down, but something has to kick start those tables.
Still waiting for some “ax” things, so dunno. But seems changing country has an outsized effect on things with 'ax, perhaps try “no country”? And/or, specifically select a channel to use?
try “no country”? And/or, specifically select a channel to use?
Nothing, same thing… after 5/10 minutes that the screen is off, the disconnections begin.
They do it even if I use only one wireless interface (2.4 or 5 GHz).
You are right, I should do it when nobody is there…
I have a RB5009UPr+S+IN with an SFP+ module that sometimes fails to start, and experiences 2.5G port flapping.
After upgrading to 7.8rc2, not only does port flapping still occur, but there are also negotiation issues where the port changes from 2.5G to 1G and then to 100M.
The only solution I have found is to reboot the device, which temporarily restores the 2.5G connection until the flapping starts again.
here is the image after reboot. the ether1 will back to 2.5Gbps. just reboot.
Then I found another problem after the reboot: every time I reboot, my clock is changed to Europe/Istanbul. It’s so strange, no matter how I change it, it always changes back to Europe/Istanbul after reboot. I didn’t pay attention to this issue before.
