Messages

Take the EEPID and REPLACES out of the cfg file, these are optional cfg parameters.

When it fails, what is the exit code?
https://edc.intel.com/content/www/us/en/design/products/ethernet/adapters-and-devices-user-guide/intel-ethernet-nvm-update-tool/#command-line-parameters

What does the inventory output say? Why is the device tagged with a Micro Star subvendor?

@and,

Please list your cfg file.

Use some PCB 2.4GHz yagi antennas, just make sure they stay pointed in proper direction. This will significantly increase range.

This one is interesting, no VSWR spec, so I ordered one just to see what it looks like on my VNA.

https://www.amazon.com/dp/B0H3ZYM661

make the OPNsense 26.7.2 version with 15.1-rc3

Dude... you know 15.1 is newer than the RC3 release for 15.1 right ?!

And again : The problem are FreeBSD 14.x to 15.x upgrades and not fresh installs of FreeBSD 15.x a.k.a. OPNsense 26.7.x :)

15.1 Release is June 16th (a lie on their site, https://www.freebsd.org/releases/)
15.1 is actually June 12th (https://download.freebsd.org/releases/amd64/15.1-RELEASE/)
RC3 is June 6th.

What's the diff?

My point is, make the OPNsense 26.7.2 version with 15.1-rc3. So when I upgrade into 26.7.2 from 26.x less than .7, I don't need to do any manual bootloader copying.

But as I noted, that URL I gave, is talking about rc3, but then goes onto say "copy in the fixed bootloader". If rc3 already has the fixed bootloader then why would I be copying it in?

I started planning with U7 Outdoor, but I have not yet found any tests on the what actual area coverage I can expect in the open field.

This thing : https://store.ui.com/us/en/category/accessories-access-point/collections/accessories-pro-ap-external-antennas/products/uma-d

Use to give you WiFi @ 300+ meters range when mounted on the UAP-AC-M instead of the standard antenna setup :)

It's not omni. If vehicles are circling the AP then directional is no good? All depends on relative geographic deployment. If 3 AP's form a triangle and all vehicles are inside the tri, then directional is great. The vehicles are still omni though.

And then I wonder, if 3 AP's are placed around, how do they reach a hub? The AP's will be bridges I suspect.

Also look at that antenna specs. Dual band. 5GHz may be faster, but 2.4GHz will go further. Also look at polarization angles, 5GHz is narrower, so although it has gain it's only gain in that beam width. If race day is misty or just high RH, 5GHz will attenuate way more than 2.4GHz.

The antenna is good, but using one that is 2.4GHz-only makes more sense to me.

It is using 15.1 release. But you need to manually update your boot loader in FreeBSD after the OS upgrade. There is no automation for that at all.

15.1-rc3 is said to have the bootloader fix in it. So I thought OPNsense 26.7.2 could use rc3, this way going from less than 26.7 you could get directly to the fixed rc3.

But it's a bit baffling, rc3 is said to be fixed, but the notes for rc3 still says you need to manually copy in a bootloader?

https://lists.freebsd.org/archives/freebsd-stable/2026-June/004124.html

15.1 RC3 includes the bootloader fix. Is the v26.7 OPNsense not using RC3 build?

ethtool --show-eee igc0
ethtool -i igc0

Code Select Expand

root@opnsense:~ # ethtool
ethtool: Command not found.

OPNsense isn't Linux.

Yeah, my bad, I do that often. I live in ubuntu for last 12mo, deep in interface settings with both wired and wireless IDS.

@fornax, it has been seen in past that auto-negotiate for 2.5gbps was an issue between certain devices that can do 2.5Gbps. If the WAN shows problem again, try:

sudo ifconfig igc1 down
sudo ifconfig igc1 media 1000baseTX
sudo ifconfig igc1 up

Then monitor.

So the WAN "died", and then you installed fresh copy of 26.7? That's not really a good troubleshooting tactic, because now the issue (if it still exists) is reset.

Is WAN router or LAN switch 2.5G capable?

Even on 15.1 (26.7), verify EEE settings and look for events.

ethtool --show-eee igc0
ethtool -i igc0
and
nohup sh -c "dmesg -aw | grep -i -E 'igc|eee|energy|lpi|sleep|wake'" > watch-energy.txt 2>&1 &

its wrapped nohup so if your ssh dies the capture keeps running, you come back in to look at the txt file, etc. Kill that pid when done.

First time for everything, I guess... yesterday I had an issue that was only resolved after bouncing the WAN interface instead of LAN like every other time. In a fit of frustration I reinstalled the OS today

And you are running latest NVM for the 226's ?

Are you building this for a specific car/team, or is this a service to all car/teams?

You said no 5GLTE, so how then do you reach utoob?

It's a racetrack, are there any local stipulations where you can increase wifi Tx power? How does Indy or NASCAR do in-car video? Wifi is cheap, but perhaps comes with it's own problems due to Tx power limits.

From my view, all the camera feeds should land in a 2x2 video mixer, one that allows you to show (choose) 1, 2, 3, or 4 video feeds at once, basically allowing you to have 4 video feeds in one HD screen (car, drone, cam1, pit), from there it connects (outputs hdmi) to a live-stream gateway that encodes direct to utoob live, same encoder gateways can live stream to multiple platforms at the same time. The encoders do usually support 5g-wifi and ethernet-wired, so some choices there.

As for multi-wan, sure, OPNsense can do that via policy-based routing. You default route based on source subnet. 10.10.10.0/24 DFG WAN1, 10.10.11.0/24 DFG WAN2, 10.10.12.0/24 DFG WAN3, etc. This also implies that you have three distinct connections or ISP's for internet access.

To do that, I would use a device that has at least 6 gig ifaces, 3 for WAN and 3 for LAN, then just match them, like LAN1-WAN1, LAN2-WAN2, LAN3-WAN3.

Having the fw in there allows you to control the data flows. Duly noted the single point of failures.

This is a good read, seems more like router tuning.
https://docs.opnsense.org/manual/interfaces_settings.html

What's the status of your fix?

How does the video get from vehicle to the livestream PC?
What's the internet link, your 5GLTE device? If everyone else is using the same cell then bandwidth could/might be impacted.

Anything streaming to a utoob channel, you can buy a small device from amzon or the like that takes in video (hdmi, composite, ntsc/pal), hardware encodes it, and then streams it to the utoob channel. So basically no work for that part, dont need a PC. Use the one that has eth port so no reliance on wifi.

Wifi for the team, you just need a wifi AP. What are they doing on the wifi (internet, other)?