Recent content by namelessx

Ok, many thanks for patience and explanation. I will try and test what I can achieve. Anyways, maybe someone will stumble upon this topic and provide definite solution. That is pretty frustrating experience TBH ;)

If I run "ethtool -K eno1 tso off gso off" manually I get following changes: tcp-segmentation-offload: off tx-tcp-segmentation: off tx-tcp-ecn-segmentation: off [fixed] tx-tcp-mangleid-segmentation: off tx-tcp6-segmentation: off udp-fragmentation-offload: off...

That's just the comment :)

Strangely, when I apply post-up to both interfaces only 'tx-tcp-mangleid-segmentation: off' line changes. root@pve:~# ethtool -k eno1 Features for eno1: rx-checksumming: on tx-checksumming: on tx-checksum-ipv4: off [fixed] tx-checksum-ip-generic: on tx-checksum-ipv6...

Not here, unfortunately :( I did exactly the same as you did (just applied to eno1 instead of eno2). Even now just repeated the steps that you did and the result of diff is blank (nothing).

Thanks for explanation. Tried that now, but the result is the same :/

Ok, I misunderstood your post – my fault. I tried that once more – applied the line only to eno1 interface. auto lo iface lo inet loopback iface eno1 inet manual post-up /usr/sbin/ethtool -K $IFACE tso off gso off 2> /dev/null auto vmbr0 iface vmbr0 inet static address...

Yup, I noticed that after a while. But even after restarting the VM's and containers I did notice really strange behaviour in Home Assistant VM. Maybe that was not related to this issue or workaround, just a coincidence. Right now I rolled back because of lack of time. I will try again tomorrow...

Oh man, I just run into many problems after applying this workaround. Really, big time. I don't know what might happened but my VM's, especially the one with smart home instance (Home Assistant) got messed. I was loosing connectivity to this VM (Web UI wasn't responding or loading), I also...

Oh, ok. I don't do passthrough because couple of VM's make use of this 'real' interface. I also don't have direct access to the host. That's my only NIC and I run NUC in headless mode. Loosing connectivity would be highly problematic then ;) I guess I'll run some "stress tests" and will see how...

Thanks. Can you point me to the best way to check if this workaround resolved the issue on my setup? I've previously tried uploading/downloading large files to/from the network drive hosted on my NUC. I also tried iperf3. However, none of those tests make me 100% sure as this issue seems to...

Ok, so it worked only after I put it under both interfaces (eno1 and vmbr0). Heres the output: Features for eno1: rx-checksumming: on tx-checksumming: on tx-checksum-ipv4: off [fixed] tx-checksum-ip-generic: on tx-checksum-ipv6: off [fixed] tx-checksum-fcoe-crc...

Sorry, forgot to tell that it's output from current state, without the fix. I will try, test and report back soon.

Many thanks! I would also appreciate if you could indeed come back with your observations/experience. Thanks. Here's the output: root@pve:/sbin# ethtool -k eno1 Features for eno1: rx-checksumming: on tx-checksumming: on tx-checksum-ipv4: off [fixed] tx-checksum-ip-generic: on...

Thanks for a real quick answer! Is there any drawback from applying post-up to both interfaces? I've seen (here: https://forum.proxmox.com/threads/e1000-driver-hang.58284/post-303366) that it may not work if applied only to 'real' interface. Regarding your example. While I clearly understand...