Messages

When it is identified and shown like in your output, the tunable IMHO does work. Now check the other end and cabling.

You have identical speed on both ends?

Good morning Patrick. I got it figured out. My assumption was when one plugs an sfp into an opnsense box,the unassigned interface would light up green but it wasn't in my case so I was thinking it wasn't working. Once I assigned which in my case was ix1, things started working.

Just sharing for awareness:

I recently purchased a Qotom Q20331G9-S10 CPU Atom C3758R - (4 SFP+ Version) - No RAM, No Storage.

I then installed:

• RAM -- Kingston KF432S20IBK2/64 -- 64GB (2x32GB).
  
• NVME -- SK hynix Gold P31 2TB

Serial console issues aside, the VGA installation went off without a hitch.

I had it up and running on the Intel i226s almost immediately.

The Intel X553 was a bit of a different matter.  It refused to recognize any of the SFP+ modules (SR or DAC) I installed, so after a bit of research I found that the Intel driver itself was refusing the use of the "unapproved" SFP+ modules.

There is a sysctl that allows you to bypass this behavior.

So, within /boot/loader.conf.local I set the following:

hw.ix.unsupported_sfp=1

... after that and a quick reboot. I could get the modules to recognize and autoconfig up at 10Gb.

For connectivity to my switches I am currently using this DAC Cable:
10Gtek SFP+ DAC Twinax Cable, Passive, Compatible with Intel XDACBL2M, 2 Meter(6.5ft)

Hope that helps anyone looking to get this device working in their own environment.


Edit:

To have the system boot after power-loss, you can set that behavior within the bios here:

--> IntelRCSetup --> South Bridge Chipset Configuration --> State after G3 --> (Change to desired behavior)

I don't have that /boot/loader.conf.local
I have /boot/loader.conf but within it there is no mention of
hw.ix.unsupported_sfp. Do I add it there and set it to 1 ?

This config modification can be achieved using tunables. System>settings>tunables

System > Settings > Tunables.

Add it as a new variable and reboot.

Thank you Patrick. This tunable didn't help get my sfp+ module loaded under interfaces. I can see it identified in opnsense by running ifconfig -v under ix1 like so

Code Select Expand

@OPNsense:~ $ ifconfig -v ix1
ix1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=4803828<VLAN_MTU,JUMBO_MTU,WOL_UCAST,WOL_MCAST,WOL_MAGIC,HWSTATS,MEXTPG>
        ether 20:7c:14:f5:45:69
        media: Ethernet autoselect
        status: no carrier
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        drivername: ix1
        plugged: SFP/SFP+/SFP28 10G Base-LR (SC)
        vendor: E.C.I. NETWORKS PN: ENXGSFPPOMACV2 SN: SC25447837828 DATE: 2025-02-10
        module temperature: 21.84 C voltage: 3.24 Volts
        lane 1: RX power: 0.00 mW (-40.00 dBm) TX bias: 0.00 mA but when I go check under interfaces>>>overview ix1 is red and not green.
boot/loader.conf

Code Select Expand

# dynamically generated tunables settings follow
debug.kassert.warn_only="1"
dev.netmap.admode="2"
dev.netmap.buf_num="1000000"
hw.ibrs_disable="0"
hw.ix.unsupported_sfp="1"
hw.ixl.enable_head_writeback="0"

There might also be tunables like this they can coerce the Intel chip to cooperate with the modules:

hw.ix.unsupported_sfp
Force Intel driver to use unsupported SFP+ modules. Def: 0             
boot-time
Set the value to: 1

Where could I find this settings?

Just sharing for awareness:

I recently purchased a Qotom Q20331G9-S10 CPU Atom C3758R - (4 SFP+ Version) - No RAM, No Storage.

I then installed:

• RAM -- Kingston KF432S20IBK2/64 -- 64GB (2x32GB).
  
• NVME -- SK hynix Gold P31 2TB

Serial console issues aside, the VGA installation went off without a hitch.

I had it up and running on the Intel i226s almost immediately.

The Intel X553 was a bit of a different matter.  It refused to recognize any of the SFP+ modules (SR or DAC) I installed, so after a bit of research I found that the Intel driver itself was refusing the use of the "unapproved" SFP+ modules.

There is a sysctl that allows you to bypass this behavior.

So, within /boot/loader.conf.local I set the following:

hw.ix.unsupported_sfp=1

... after that and a quick reboot. I could get the modules to recognize and autoconfig up at 10Gb.

For connectivity to my switches I am currently using this DAC Cable:
10Gtek SFP+ DAC Twinax Cable, Passive, Compatible with Intel XDACBL2M, 2 Meter(6.5ft)

Hope that helps anyone looking to get this device working in their own environment.


Edit:

To have the system boot after power-loss, you can set that behavior within the bios here:

--> IntelRCSetup --> South Bridge Chipset Configuration --> State after G3 --> (Change to desired behavior)

I don't have that /boot/loader.conf.local
I have /boot/loader.conf but within it there is no mention of
hw.ix.unsupported_sfp. Do I add it there and set it to 1 ?

Hoping in bugs fixed that are not raised in the bug tracker for coordination? Not 100% a good plan. :)

🥲 that's fair haha.
Bug tracker in github?

Regular view: On hover:

Data in the /api/diagnostics/system/systemTemperature feed looks ok:

Code Select Expand

[
    {
        "device": "hw.acpi.thermal.tz0.temperature",
        "device_seq": "0",
        "temperature": "48.1",
        "type_translated": "Zone",
        "type": "zone"
    }
]
Tested in latest Chrome and Firefox

I am having the same bug. How can I confirm using /api/diagnostics/system/systemTemperature

I am drawing a blank here and would like some help. How do I remove nextcloud or disable it? I keep unchecking the enable button but there is no save button to make it stick.

Bonjour, personnellement je sais pas la réponse mais je pense que tu auras plus de succès si tu traduis votre question en anglais parce que la majorité ici parle l'anglais.

Thank you @NW4fun for making this post and @franco for the quick fix. I was puzzled as well since I uninstalled zenarmor before upgrade. I always have a feeling that it breaks upgrades

Hi Wstemb,

Thank you for your valuable analysis and feedback. Your feedback has been forwarded to the dev team.
Thank you for your co-operation.

Nothing has been fixed since. Still getting error 200

Code Select Expand

Connection Error
There was an issue on our end. Sorry about that.

Zenarmor 1.18.2

I was about to make a thread about his also. The latest wazuh-agent I have in my system 4.7.5 while the other agents on my other systems are updated to 4.9

Same here. Upgrade went smooth with no errors or gremlins. I LOVE LOVE the snapshot feature and the peace of mind it provides during the upgrade process.
I really only have like 2 or 3 plugins installed besides the default opnsense firmware which makes it a lot less likely to act up during upgrades I think.

How?

Hey everyone. Hope you all having a great day!
Is there anyway to decipher the crash reports for non-tech savvy that might get in their instance of opnsense?
Can one post the report on chatgpt for example to know what the error is ?

Thank you!