RouterOS CHR version seemed to have compatibility issues with I226-V passthrough mode on Proxmox

Hello everyone:

I recently installed RouterOS (the latest version) on Proxmox VE (PVE) with a hardware setup consisting of 4x I226-V NICs and an N100 processor. For convenience and better performance, I set three of the network interfaces to PCIe passthrough mode (one as WAN and two as LAN).

Initially, after configuration, everything worked fine, and RouterOS correctly recognized the NICs. However, after a short while(About half a day or 8 hours) , the network interfaces stopped working—I could no longer access the router’s management interface, and all packets sent to the router seemed to vanish without any response.

Fortunately, I had kept a virtual interface as a fallback. Through this interface, I regained control of the router and noticed that the NICs were still present but were not responding to any packets. I then logged into the PVE management interface and observed that the system seemed to be experiencing issues—CPU usage remained consistently high at 25%. I suspect something had deadlocked one of the CPU cores. Later, I discovered that simply re-plugging the Ethernet cable temporarily resolved the issue.

I also tried enabling promiscuous mode for the NICs in PVE, but that didn’t help. Additionally, I came across some posts mentioning compatibility issues between CHR and the I226-V NICs in virtualized environments. However, no solutions were provided—only recommendations to switch to a non-virtualized installation.

For now, I’ve switched back to using PVE’s VirtIO NICs for RouterOS, and it’s working fine. But I regret not being able to use passthrough mode anymore.

I searched online and found a post describing a situation similar to mine, but it was from three years ago and might be outdated.

Before I start troubleshooting again (which would cause a longer service interruption), I wanted to ask if anyone here has encountered this issue recently and how you resolved it,thank you again for your replying.

Hi,

Think that CHR is mostly directed for virtualized interfaces and even passthroughed card seems to work it could be a coincidence.

1 Like

I have a persistent issue with machines that have that NIC and also the i219. Mine are running Proxmox server.

The logs refer to a driver hang when it occurs.

The devices are plugged into a CRS-326 switch so I have a netwatch job which pings the host, once it goes down a script sets the switch port to down and after a few seconds it will re-enable the port again and the issue is resolved at least for a while.

Issue is a bug in the Intel Driver itself that apparently is not being fixed.

The Netwatch Script:

/interface disable ether1
:delay 5
/interface enable ether1
/tool e-mail send to="me@`mydomain.eu" subject="Interface ether1 toggled" body="ether1 was disabled and re-enabled after 5 seconds."

1 Like

Thank you for your replying ,that is a raw and effective way :laughing: