Le ecureuil

Wireguard's DNS are static ones. KN adds automatic routes for dynamic configuration, e. g. DHCP or PPP or OpenVPN ones. So static route is the good solution.

Fixed in 3.8 branch.

plz provide output in cli (telnet) when high load occurs: > show threads > show processes Don't go to the web interface and don't try to download self-test. When system is thrashing due to high load generation of self-test can lead to full lockup.

It's definitely a hardware problem: maybe power is not enough, or connect is not so good. BTW, having disk and modem with pingcheck on the same hub is awful decision. You disk will perform unsafe restart on each pingcheck run and it can lead to hardware damage (or software issues).

It's hard to say, but I personally will bet on hardware issues in "usb-port/usb-cable/usb-drive" chain. Logs of disconnections are greatly welcome, so we can properly handle incorrect drive disappearing from USB bus.

Handling of two partitions having the same label was fixed and will be available in the next release.

Your logs clearly states that you have TWO partitions with the same label "TEMP". Do you really have them?

It seems that stale phantom record of damaged partition stays in memory, and prevents from mounting after fsck.

Did you try to reboot KN before inserting disk after fsck?

What does e2fsck say about it?

DoQ is under heavy development, current IETF draft doq-i04 and -i03 changed wireformat and incompatible with -i02 used in Adguard DNS (IETF QUIC v1 is incompatible with Draft-QUIC-32 also). So any solution will stop work after 2-3 month. We wait for final (or at least stable) specs. DoH + HTTP/3 is real, but only QUIC was stabilized as RFC 9000, HTTP/3 is still under review. We have no stable TLS libraries for QUIC, except GnuTLS right now. Curl's support for HTTP/3 is based on ngtcp2 + nghttp3, which has no stable releases for now also. So we wait for stable ngtcp2 for DoH+HTTP/3.

Connecting to the same L2TP server from the same subnet behind the same NAT is very difficult and not implemented right now.

You must not use this buggy crap as Minitool Partition Wizard is. Plz format with reference ext2/3/4 implementation only: e2fsprogs.

There are errors on disk, the must be fixed.

@yerebakan plz run fsck on this ext4 volume on PC.

Покажите > ip http ssl acme list > show acme

Need more info. What is your ISP connection? What speed do you expect? Screenshots of speedtest from laptop and pc would be nice.

Thanks, we are working on this.

We are working on replacing DoT implementation right now, so it pretty useless until completion. But after we will back to this. I hope it will be autofixed.

I need to investigate it further.

Interesting idea, but we need example set of settings.

In general yes, but in can be tricky enough. You set highest priority to the client wireguard connection and explicit 'connect via' interface. 'Connect via' must be set for server interface also, preferrably with the same ISP interface. Then all your wireguard clients will go to the Internet through the wg client.

Plz try version 3.7.A.11, it was implemented.

Can you please capture dns requests on Home interface via 'monitor' component on page 'Diagnostics'? Use filter "udp port 53".

Will be fixed in the next release.