Recent posts

#1

General Discussion / Re: Issue migrating hardware

Last post by nero355 - Today at 02:59:55 AM

Like you I would of thought it was something to do with the interface assignments.

Could still be the case, but because of something different : Import/Restore config.xml bug that did not apply things properly to the right Interfaces :)

You could check the OPNsense Release Changes from version 26.1.2 up to 26.1.9 or so for anything related ?!

#2

26.1, 26,4 Series / Re: First time OPNsense setup ...

Last post by nero355 - Today at 02:52:19 AM

Any help is very much appreciated, let me know what information I can provide.

Read this : https://forum.opnsense.org/index.php?topic=52253.0

It basically comes down to having to do this : https://forum.opnsense.org/index.php?topic=48695.0

!!! READ FIRST !!! as much as possible about it and only proceed once you are 100% sure you know what you are going to do step by step ;)

#3

General Discussion / Re: Periodic NIC issues (?) wi...

Last post by fornax - Today at 02:07:31 AM

Thanks for confirming 2.32 is vendor approved.

"Vendor approved" is probably overstating it. I'll just say that the Protectli support rep working with me indicated that he tested the upgrade to that version and used it in his guidance to me for the procedure.

At any rate, I successfully updated:

Code Select Expand

[1] igc0: <Intel(R) Ethernet Controller I226-V> mem 0x80400000-0x804fffff,0x80600000-0x80603fff at device 0.0 on pci1                                       
[1] igc0: EEPROM V2.32-0 eTrack 0x80000422                                                                                                                         
[1] igc0: Using 1024 TX descriptors and 1024 RX descriptors                                                                                                       
[1] igc0: Using 4 RX queues 4 TX queues                                                                                                                           
[1] igc0: Using MSI-X interrupts with 5 vectors                                                                                                                   
[1] igc0: netmap queues/slots: TX 4/1024, RX 4/1024                                                                                                               
[1] igc1: <Intel(R) Ethernet Controller I226-V> mem 0x80700000-0x807fffff,0x80900000-0x80903fff at device 0.0 on pci2                                             
[1] igc1: EEPROM V2.32-0 eTrack 0x80000422                                                                                                                         
[1] igc1: Using 1024 TX descriptors and 1024 RX descriptors                                                                                                       
[1] igc1: Using 4 RX queues 4 TX queues
[1] igc1: Using MSI-X interrupts with 5 vectors
[1] igc1: netmap queues/slots: TX 4/1024, RX 4/1024
I haven't changed anything else yet. Still on the -iflib kernel, no tunables, still on coreboot. I'm going to monitor for a bit, and if/when it pops up again I'll go from there.

#4

26.1, 26,4 Series / Re: First time OPNsense setup ...

Last post by newsense - Today at 01:36:19 AM

Doubt your issue is caused by NAT.


Bridge mode is where you want to be, don't change that.

Check the logs for dhcp events. Depending on how your wan is configured there may be a temporary loss of the ip on the wan. Either that or upstream link is flaky and occasionally drops

#5

26.7 Release Candidate Series / Re: 26.7 firmware update loop

Last post by newsense - Today at 01:26:44 AM

A healthcheck wouldn't hurt.

Are you sure it is not a mirror issue? I don't see any logical path for a downgrade.

Also, 26.7.r2_3 is where you want to be now.

#6

26.7 Release Candidate Series / 26.7 firmware update loop

Last post by monkfish - Today at 01:11:43 AM

Hello,

Wanted to report a firmware update loop on my dev lab 26.7rc machines.
It appears to have installed 26.7r2 correctly but subsequent firmware checks seem to want to "downgrade" to 26.7.r1.
If I do happen to select it, its installing "something" but resulting in 26.7r2 again after reboot.
Happens regardless of which development repo I select in the firwmare settings.


100% no problem in this lab, I just wanted to flag it as its curious behaviour.

Thank you for OPNsense!

#7

General Discussion / Re: Periodic NIC issues (?) wi...

Last post by OPNenthu - Today at 12:58:32 AM

What I might expect from Protectli support is, they obtain and publish just the SHA256 hashes of the official Intel NVM's for freeBSD

Sounds like a good compromise.  Hope they can do it.

t's still a bit baffling as to why Intel simply doesnt host the NVM images for their products. Buy MU shares instead of INTC. ;)

I can understand why they differentiate this way between server and consumer/embedded parts, but yeah this situation is frustrating.  Micron also turned its back on the consumer market and now we're finding out that memory makers may have colluded to fix prices.  All of them need to face a reckoning, IMO.

#8

Hardware and Performance / Re: RISC-V port could be an id...

Last post by dgshue - Today at 12:55:37 AM

I really don't even remember why/how I got down this road... But it does work, wifi is still a little flakey and needs some work. https://github.com/dgshue/OPNsense-RISC

#9

General Discussion / Re: Periodic NIC issues (?) wi...

Last post by BrandyWine - Today at 12:35:35 AM

I am still on v2.13 myself:

... but, I left the NVM firmware as-is.  Reason being, the upstream Linux patch this is sourced from does not stipulate any particular NVM version as being required.

Yikes.

We covered this a lot in many threads.
Drivers and NVM's are basically linked. Newer drivers typically are updated to use new features in newer firmware. Driver code is also sometimes fixed for the bugs they carry.

If Intel is updating NVM then we know it's not because they needed something to keep them busy, they did updating for a reason. And there's no functional reason not to run the latest NVM code. Same goes for their driver code. For long running hardware (i225 i226 as example), newer drivers (KLM's) are almost 100% better to run than older drivers. Unfortunately for most the GENERIC kernel builds compile in that code making it very difficult to just unload the old and load in the new, which was the whole point of KLM feature. I showed how to recompile kernel w/o the igc in it, then I just loaded in whatever igc driver that I wanted as KLM.

So, full circle on this issue.

#10

General Discussion / Re: Periodic NIC issues (?) wi...

Last post by BrandyWine - Today at 12:32:37 AM

Just a note for readers, a warning.
The billy curtis NVM images are just that, they have not been officially validated as authentic Intel images.
In the other thread for i226 NVM I had only validated that one of the i226 VVM versions I obtained from another hardware vendors matched the same one on billy curtis github (SHA256 matching). The other hardware vendor is known-legit and said the NVM was from Intel. Beyond that the other NVM images I cannot validate in any way because finding them anywhere else is very difficult.

So, if your FW system is critical in any way, then I recommend you call Intel and demand a copy of NVM directly from them.
For non-critical, we can use the billy curtis downloads. Always a risk using non-official stuff, etc.

What I might expect from Protectli support is, they obtain and publish just the SHA256 hashes of the official Intel NVM's for freeBSD so that we can compare to the downloads we get from non-official sources. This way we have something pseudo-trusted, and Protectli stays compliant for not hosting the NVM images.

It's still a bit baffling as to why Intel simply doesnt host the NVM images for their products. Buy MU shares instead of INTC. ;)