Messages

Thanks! You helped get my speeds back up to 1.1-1.2 Gbps with the pipe/queue/rule settings I was already using, but that 25.1.5_5 somehow broke, coming from 25.1.4_1.

Intel N5105, same configuration of 4x i226v ports.

You're welcome! Did you also need a separate scheduler pipe setup?

I do not need to schedule my bandwidth usage, as I have no bandwidth usage caps, only a speed limit. Though I probably have such things to look forward to considering the current political climate in the US, with regards to Net Neutrality.

Thanks! You helped get my speeds back up to 1.1-1.2 Gbps with the pipe/queue/rule settings I was already using, but that 25.1.5_5 somehow broke, coming from 25.1.4_1.

Intel N5105, same configuration of 4x i226v ports.

CPU usage rises to approximately 44% of a core for the ntopng process during the speed test, however no kernel threads register more than about 11-12% in the status line.

Speed rises to my line speed if I disable the pipes, queues, or rules. What changed about FQ_CoDel between 25.1.4 and 25.1.5, beside the new configuration system?

I am using the same configuration I had set up for 25.1.4 and 24.x before that. As of 25.1.5_5 update this morning, I can only reach approximately 50% of my line speed with the downstream set to nearly my gigabit downstream speed.

My device is a mini PC with a N5105 CPU and four dedicated Intel 2.5G ports.

Sorry. Apparently, all my DNS troubles were because systemd-resolved on Arch default enables both LLMNR and mDNS, which were slowing down DNS for practically every query.

It doesn't seem to be possible to set the common name string to a wildcard. Will it still verify if I enter a host, and the certificate has a wildcard CN that matches it? DNS over TLS doesn't seem to be working for Quad9 for me, it seems to be falling back to Recursion no matter what. Quad9's servers appear to return the CN of "*.quad9.net".