Jump to content

Le ecureuil

Forum Members
  • Posts

    10175
  • Joined

  • Last visited

  • Days Won

    600

Everything posted by Le ecureuil

  1. opkg dns-override just releases the local resolver from the port 53 (because a user may want to bind their special service to the port 53). No, it's not a docker, just a group of subprocesses (with optional chroot). Connections to the outside are allowed by default (as, for example, for the download station). Connections from the internal network are allowed by default too (as, for example, for the web-interface server).
  2. Installing or removing a component can only be done through reboot with the reflashing of the new repacked version of the software. So it's impossible to install/remove a component without a reboot.
  3. Can you please try the cable with another gigabit device?
  4. It has already fixed, please try the new release of 4.3 from the coming friday.
  5. Вы лично DoH/3 пробовали в draft 4.2? Все хорошо работало?
  6. 1 - создаете этот интерфейс командой, вешаете на него IP-адрес, делаете его global (или нет), настраиваете маршрутизацию и firewall - вобщем все, что можно делать с интерфейсом наподобие wireguard. 2 - настраиваете IPsec site-to-site, и в нем привязываете этот интерфейс. Теперь в это соедиение идет не вообще весь трафик по политике, а только тот, что в интерфейс должен уйти. И наоборот - трафик удаленной стороны появляется не из "ниоткуда", а выходит из этого интерфейса. Также в такой конструкции можно сделать селекторы 0.0.0.0/0 (как в wireguard указывается allowed-ips 0.0.0.0/0), и дальше уже трафик полностью управляется роутингом и фаерволом.
  7. Hello. Right now it is not possible.
  8. You can run the server with opkg.
  9. The real economical demand is rather negligable.
  10. So Zero-Wait DFS is enabled, great.
  11. Don't mind about this parameter, it is only for compatibilty. All you need is to take a look on the DfsDedicatedZeroWait.
  12. There are no reasons to disable it.
  13. 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.
  14. DoQ это не просто DNS, тупо завернутый в QUIC. Там отличается механика в некоторых местах, тупые демо-proxy не подходят.
  15. 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.
  16. 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?
  17. 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.
  18. Hello. I suppose it's better to contact to the support.
  19. 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.
  20. 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.
  21. Смысла нет - ПО все равно имеет заранее определенные размеры, оно не "увидит" дополнительной памяти.
  22. 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).
  23. We have implemented the ping-based probing in the future 4.2 release.
  24. Can you please describe your TV Box? HW revision, SW version, photos maybe?
  25. We have reduced errors count and timeouts before downgrading, please check on the next 4.2 release.
×
×
  • Create New...