Suggestion - Add Persistence/Startup to NIC Fix

[SdoggaMan]

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

No (this issue will likely be closed automatically)

📜 What is the name of the script you are using?

Intel e1000e NIC Offloading Fix

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/nic-offloading-fix.sh)"

⚙️ What settings are you using?

• Default Settings
• Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

Virtual Environment 8.4.16

📝 Provide a clear and concise description of the issue.

Hi all! Not strictly a script fault, but suggestion/reccomendation (hence 'no' to Verbose mode as this is not necessarily a bug, but a general issue.)

The Intel e1000e fix works flawlessly and is very much appreciated, however, if the system goes offline (I have had a few power failures recently, for example) it seems to need to be run again. Suggestion is to add a form of persistence or run-at-startup service so that it persists through system shutdown(s). I would love to suggest how, but I am totally out of my depth in that area still!

🔄 Steps to reproduce the issue.

Run the script (the system will remain online and the fix will prevent the server from going inaccessible, as intended)

Restart the system in any way that shuts down the host.

Boot and wait for the system to hang on the e1000e NIC.

Hard power cycle to resolve, boot, and run the script, and the system will run flawlessly until it is next rebooted.

❌ Paste the full error output (if available).

N/A

🖼️ Additional context (optional).

I hope this is helpful and raised in the right place - my sincere apologies if I've missed something. More than happy to help test and troubleshoot if anyone needs it!

[MickLesk]

@rcastley Do you have any idea about this? Could you perhaps take a look at it in the next few days or weeks? Thx

[rcastley]

@SdoggaMan Could you kindly try something for me please?

Can you edit /etc/systemd/system/disable-nic-offload-eno1.service and change it from:

[Unit]
Description=Disable NIC offloading for Intel e1000e interface eno1
After=network.target

[Service]
Type=oneshot
# Disable all offloading features for Intel e1000e
ExecStart=/sbin/ethtool -K eno1 gso off gro off tso off tx off rx off rxvlan off txvlan off sg off
RemainAfterExit=true

[Install]
WantedBy=multi-user.target

to:

[Unit]
Description=Disable NIC offloading for Intel e1000e interface eno1
After=network-online.target
Wants=network-online.target
[Service]
Type=oneshot
# 5 sec delay to allow for the nic to come up
ExecStartPre=/bin/sleep 5
# Disable all offloading features for Intel e1000e
ExecStart=/sbin/ethtool -K eno1 gso off gro off tso off tx off rx off rxvlan off txvlan off sg off
RemainAfterExit=true

[Install]
WantedBy=multi-user.target

This, basically, delays implementing the fix and allowing for the NIC to come up. If this works for you, then I can create a PR and get the script updated.

[SdoggaMan]

Hiya! For sure! I've got an on-site day today at work so bear with me for a little bit and I'll plug this in on the weekend (will have to learn how to do that 😅) - do you want me to reboot the system so that the fix isn't applied first, and see what happens, or plug this in as-it-is and leave it that way?

Thanks for jumping on this so quickly as well, both!

[rcastley]

@SdoggaMan if you could apply the proposed change to your host and reboot and see if your host remains online.

FYI, my Intel NUC has been rebooted many times and I have never had to apply the script again, so I am hoping that your NIC is just a lazy one that we just need to wait for.