Messages

Sorry for making confusion. What I wrote is not 100% accurate for i226.

But in general eeupdate64e is easier to use since it does not require configuration file.

But going back to i226 - my workflow is following:

1 - to determine inventory I use Linux version of nvmupdate64e (from Intel driver pack)

2 - to flash i226 NVM I use Linux version of eeupdate64e. Please see this link:

CSG150 i226 NIC NVM update instructions

There in step 5 you will find instruction. Direct link to download Linux version of eeupdate64e is here:

CSG150_NVM_225.tar.gz

For me this has been working reliably.

Unfortunately EFI version of eeupdate64e compatible with i226 is not publicly available.

I find EFI version on NVM tool easier to use. Simply grab eeupdate64e.efi form Intel driver pack, boot into EFI shell and run command like:

Code Select Expand

eeupdate64e.efi /nic=1 /d=FXVL_125C_V_1MB_2.32.bin
You only specify nic number and name of NVM file to flash. No need to worry about configuration file.

I have ASRock NUC BOX-255H with i226V and i226LM. I'm on 2.22 with BIOS that disables ASPM for both of them. i226V works rock solid. i226LM stops forwarding traffic every few days. Can i update i226LM NVM using file for i226V? I don't care about "LM" management features. This happens on Proxmox 9 where I have 2xOPNsense VMs.

Hi, bug report created. In description I put link to this thread.

Hi, I have a strange problem with blocking YouTube and I'm not sure if this is Sensei bug or configuration issue.

I run OPNsense as Proxmox VM. There are 2 vtnet interfaces and 5 VLAN-s. On LAN side there are 4 VLAN on top of vtnet0.

Engine is 1.8.2
App and Rules 1.8.21040109

Sensei is configured "Routed Mode (L3 Mode, Reporting + Blocking) with native netmap driver" and protected interface is "Unassigned vtnet0". In policy configuration App Controls I selected to block all entries with YouTube in name and additionaly "Quic UDP". In such configuration all 4 VLAN-s running on vtnet0 should be protected. The problem is that YouTube is not blocked. When I go to Dashboard and check Session Details I see connections as Blocked but Byes In/Out indicate that traffic is not blocked and indeed YouYube is working.

When I changed protected interface to individual VLAN-s then YouTube is blocked as intended.

So to the questions:
1 - What is correct Protected interface selection in case VLAN-s are in use?
2 - Is behavior that I observe due to missconfiguration or shall I open support ticket to get this fixed.

Thank you,
Krzysztof