My network adapters send corrupted packets unless I disable RX/TX offloading with ethtool (this feature is turned on by default). Is this normal? Should I be able to do checksum and TCP session offloading?
I think the driver is up to date because I’m on the latest 6.8 kernel. Firmware, TP-Link offers none for their junk.
Is there a way I can check if it’s a driver or a firmware issue? I took a look at the driver code to TBF I’m not enough of an expert to understand how it actually talks to the device.
On this matter, I’m an ignorant myself too. Perhaps searxing with the model name and brand there’s a post somewhere that shares some insight. Hardware support on linux is great, until it isn’t ;/
True, but you gotta give Linux some slack. All of this driver work is reverse engineered. It would be so much easier if the vendor just published information about their hardware.
My network adapters send corrupted packets unless I disable RX/TX offloading with
ethtool(this feature is turned on by default). Is this normal? Should I be able to do checksum and TCP session offloading?I’d say you need to check for drivers or firmware upgrades…
I think the driver is up to date because I’m on the latest 6.8 kernel. Firmware, TP-Link offers none for their junk.
Is there a way I can check if it’s a driver or a firmware issue? I took a look at the driver code to TBF I’m not enough of an expert to understand how it actually talks to the device.
On this matter, I’m an ignorant myself too. Perhaps searxing with the model name and brand there’s a post somewhere that shares some insight. Hardware support on linux is great, until it isn’t ;/
True, but you gotta give Linux some slack. All of this driver work is reverse engineered. It would be so much easier if the vendor just published information about their hardware.
Indeed!