[BUG] Encrypted DNS (DoH) not working on MT6000 Flint 2 - Firmware 4.8.4

Hi

Thank you for the report. We’ve reproduced the issue and identified the root cause, and will have the R&D team work on a fix.

For now, please SSH into the router and run the following commands as a temporary workaround:

cat << 'EOF' > /etc/init.d/dnscrypt-proxy
#!/bin/sh /etc/rc.common

USE_PROCD=1

# starts before dnsmasq starts
START=18
# stops before networking stops
STOP=89

PROG=/usr/sbin/dnscrypt-proxy
CONFIGFILE=/etc/dnscrypt-proxy2/dnscrypt-proxy.toml

start_service() {
    local mode=$(uci -q get gl-dns.@dns[0].mode)
    local proto=$(uci -q get gl-dns.@dns[0].proto)

    [ "$mode" = "secure" ] || exit 0
    [ "$proto" = "DoT" ] && exit 0

    /etc/init.d/dnscrypt-proxy-vpn start

    procd_open_instance
    procd_set_param group nonevpn
    procd_set_param command "$PROG" -config "$CONFIGFILE"
    procd_set_param file "$CONFIGFILE"
    procd_set_param stdout 1
    procd_set_param stderr 1
    procd_set_param respawn ${respawn_threshold:-3600} ${respawn_timeout:-5} ${respawn_retry:-5}
    procd_close_instance
}

stop_service() {
    /etc/init.d/dnscrypt-proxy-vpn stop
}
EOF

/etc/init.d/dnscrypt-proxy start
2 Likes

Thanks, it worked fine. What is the timeline for the bugfix release? Thanks it worked correctly, what is the timeframe for the bugfix release? Obviously this script no longer works once the router is restarted, you have to repeat it.

We’ve asked the R&D team to prioritize this issue. Since it isn’t particularly complex, a fix should be released soon—likely within a few days.

We’ve tested the workaround locally, and it remains effective after a reboot without needing to run the commands again, unless the device is reset or the firmware is upgraded/downgraded.

After applying the configuration, do you encounter any issues after rebooting the router? If so, please run the following commands and share the results so we can investigate further:

cat /etc/init.d/dnscrypt-proxy
ps | grep dnscrypt
netstat -tlnup | grep 5453
logread | grep dnscrypt
2 Likes

I confirm that it works after rebooting without having to repeat the first script reported I confirm that it works after a reboot without the need to repeat the first script reported, thanks and good work, we are waiting for a fix for the WiFi too

1 Like

Good morning everyone,
Unfortunately, I also need to express my disappointment. It is unacceptable that, starting from version 4.3 onward, all the updates have presented issues. We have great confidence in your products, and I kindly ask you to put more effort into the development process.
Thank you.

1 Like

The adjustment in Wi-Fi power is a regulatory compliance requirement. Please refer to our statement below:

We sincerely apologize again for the inconvenience caused.

We have asked the relevant team to conduct an internal review of this incident and improve the processes to prevent similar issues from occurring in the future.

Why did you not put this on the release notes? You just stated it was bug fixes as far as I can remember. Doesn’t sit right with me that you kept it quiet until someone highlighted the reduced WiFi power.

2 Likes

Yes, each release should have detailed release notes. We together could report this and find the error, otherwise some errors may go unnoticed between versions.