Le ecureuil

Hello. Right now it is not possible.

You can run the server with opkg.

The real economical demand is rather negligable.

So Zero-Wait DFS is enabled, great.

Don't mind about this parameter, it is only for compatibilty. All you need is to take a look on the DfsDedicatedZeroWait.

There are no reasons to disable it.

It means, that any 5G-capable extender will use only 5G as the backhaul to the main router (it forces that the main router must be 5G-capable too). But as a repeater it will broadcast both.

DoQ это не просто DNS, тупо завернутый в QUIC. Там отличается механика в некоторых местах, тупые демо-proxy не подходят.

New models have ZW-DFS enabled on KN-1011, 1811, other AX3000 models have some kind of ZW-DFS too. Anything else, esp. on low-end devices, is unfeasible.

ZW-DFS requires dedicated RF-chain and HW RF frontend, so it can't be implemented without explicit HW assistance. Which model do you imply?

I suppose it's better to write to support and to receive guaranteed answer. If you want to proceed here at your risk: please enable interface Wireguard0 debug then save it: system configuration save and then download the self-test file at the moment when wireguard doesn't work. The file you can send to me in the direct messages.

Hello. I suppose it's better to contact to the support.

Hello. Our userspace code has nothing in common with the original Donenfeld's code. We implemented it by scratch, and of course we support reresolving in case of connection termination (or restart by the command of a user). For better experience feel free to try version 4.2.

Typically it is the bots trying to get access to your device or some small network glitches. If everything works ok that there's no reason to worry.

Смысла нет - ПО все равно имеет заранее определенные размеры, оно не "увидит" дополнительной памяти.

It's the different situation. Dyndns try to execute two http requests in parallel: via IPv4 connection, and via IPv6 connection. This logs signalise that your interface has only IPv4 connection, and it's impossible to connect via IPv6. But you can update both addresses via arguments in link: it's just a different method of updating. So please enable the interface debug to which the dyndns profile is linked via: > interface XXX debug and prove which arguments are really passed to the dyndns servers (in logs).

We have implemented the ping-based probing in the future 4.2 release.

Can you please describe your TV Box? HW revision, SW version, photos maybe?

We have reduced errors count and timeouts before downgrading, please check on the next 4.2 release.

I have made some logic for autodowngrade to HTTP/2, please try the next 4.2.

To be honest, I don't see any bootstrap issues. The bootstrap takes time, and implemented as asynchronous background process. So the bootstrap repeats attempts for several times, and it can take up to 1-2 minutes. But after that in all your self-tests the bootstraps are completed successfully. The real issue is the unavailability of QUIC, but I will fix the fallback to HTTP/2.

Does it fail unrecoverable, or just makes noisy logs and reloads, but continues to work? For bootstrap we obviously need some additional information and configuration (or at least your self-test in hidden post).

Оно работает автоматически, вводить нужно все как раньше. Сперва будет попробован http/3, потом будет fallback на http/2 и даже 1.1.

Нет, слишком много возни и усилий ради очень узкой прослойки. Работает он нормально, но поскольку dns-https находится в базовой версии, то он появится у всех, и вызовет проблемы при автообновлении из-за возросшего размера. Отдельные же компоненты придется поддерживать, и обьяснять владельцам других моделей, почему у них один, а не два. Рост бестолковой нагрузки на поддержку нам не нужен.

В итоге в выходящем 4.2 будет включено на всех устройствах с более чем 32 МБ flash - то есть на всех, кроме моделей на MT7628 и KN-3010.