https://github.com/cat-milk/Anime-Girls-Holding-Programming-Books

Is she gay or European?

And I ran a speedtest on the OpenWRT router itself to compare against. There, the upload speed also varies greatly between 35-55MBit/s, but that’s just classic cable fuckery (and still more than twice as much as OPNsense achieved in the beginning)

Yeah… well spent… not that I could just have, you know, used the ISP router and spend my time on other things ^^

I would rather not introduce any more complexity into the routing than needed. I just hope my current setup allows the networking gear to automatically adjust itself for best performance (which it now does).

iperf3 between OPNsense and OpenWRT reached 900Mbit/s, so there was no bottleneck for all kinds of traffic. It only plummeted to 15Mbit/s when there were a lot of small packets to be transmitted. When I ran a speedtest on OPNsense itself, the CPU would hit 100% and I would see 50000+ Interrupts. Because OPNsense and consequently Proxmox were both connected to a 10Gbit/s Switch Port, OPNsense just flooded the OPNsense with as much traffic as possible and without buffering on the switch OPNsense was just drowning in packets. Instead of discarding all packets OpenWRT can’t handle, I think it’s a way more elegant solution to use Flow Control to throttle the transmission to what the router is capable of. I have a hard time believing that this would affect any other traffic (especially on my LAN), because the 10GbE NIC has 8 Queues which should handle different flows and TX/RX pause packets should only throttle the affected flows. Matter of fact, I just tested and I can still hit consecutive 770Mb/s transfer from my client to my NAS while running a speedtest on the OPNsense (TrueNAS is running on the same Proxmox host as OPNsense). And when disabling flow control all together, I only hit about 750Mb/s transfer speed… So I will stick with my current configuration, as it results in reliable, 0 packet loss transmissions with maximum speeds.

Yeah, two whole days of work 😅 The alternative would have been to install a dedicated 1GbE NIC in the servers again. The tunables and proxmox settings probably don’t do anything now but maybe in the future when I finally get FTTH. I read a lot about OPNsense performance optimization and these tweaks shouldn’t hurt anything, so might as well apply them for good measure.

Yep, I moved away from having multiple 1GbE NICs to a single 10GbE NIC and creating the network virtually using VLANs and SDNs. This freed up some PCI-E slots and cables, but also spawned a new boss

Yep, still on cable… vodafone to be exact. I should get FTTH this year, but also then only 1000 down/500 up for almost double the price (and it’s Telekom, so cloudflare services are unusable).

But the Problem I was facing was unique to the 10GbE Adapter. I used a 1GbE adapter before for years, without this issue.

Just set up DynDNS an host rustdesk on docker. It requires two docker containers, exchanging secret keys and opening firewall ports

I use it for just two things, triggering a download with a docker tool over a webhook call I use in a userscript and calling a webhook of a media server on local file changes

What’s wrong with Proton?!