Stagnate9916

Check screenshot below. You cannot set two different "if using internet connection" on two internet connections for the two leds. They'll systematically change to the same "if using internet connection" setting on both leds. Keenetic Titan Stable Version C

I haven’t noticed any missing features so far. However, my main concern is the possibility of this client version eventually becoming deprecated from a tracker’s perspective. I installed Transmission 4 (latest) via OPKG, and it ran smoothly, so I thought: why not upgrade the stock client? I wasn’t aware of the increased resource usage it might bring. The one thing I’ve missed with the OPKG installation is the ability to restrict the client to a dedicated connection using Keenetic OS.

The Transmission daemon version 4 has been available for two years. Could you please consider upgrading the Transmission daemon? The current version (3.00) is over four years old. For reference: Transmission 3.00 Release

I think I've understood the issue. The DNS provided from the DHCP's ISP are not populated on the "internet safety" / DNS Configuration (server list) when the internet connection is not set as primary. I had to enter the IP addresses manually.

Using 4.1.0 Three connections are configured on the Kinetic : via Ethernet (provider), via Wireless ISP and a WireGuard connection (used for internet). On the default policy, the Wireguard connectivity is the default one, followed by the Ethernet and the Wireless ISP. I have created another connection priority (labelled 'direct') that only contains the Ethernet connection. I have configured my computer to use the 'direct' profile via a policy Binding. The DHCP lease offered defines the DNS server as the kinetic router itself. I have very frequent DNS resolution errors as soon as my computer is not using the Default Connection Policy. Here is an example of rejected DNS resolution. I did not have configured the "filter mode" (internet safety). ``` ❯ dig docs.keenetic.com ; <<>> DiG 9.10.6 <<>> docs.keenetic.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 22820 ;; flags: qr ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;docs.keenetic.com. IN A ;; Query time: 2010 msec ;; SERVER: 192.168.10.1#53(192.168.10.1) ;; WHEN: Sat Feb 24 13:07:14 CET 2024 ;; MSG SIZE rcvd: 46 ``` Also the 'DNS Configuration' screen has several issues to populate the DHCP-obtained from my ISP Ethernet (bouygues). What can I do to investigate ? Thanks

Hello Would it be possible to force using a dedicated VPN connection for the Torrent built-in client ? Also, the version of the current Transmission Daemon is a bit old (this is version 3.00 - aged May 2020, almost 4 years old). Thank you