If it failed to boot the 24.03 BE it should have rolled back to the 23.09.1 BE. And it would show and alert when you next logged in. I would also have expected it to have marked the other BE as bad.

It's possible you accidentally selected a different BE on the reboot screen.

I would select the 24.03 BE to boot again and check at the console while it reboots if you can.

Steve

Congratulations on your efforts.

I went a different route to eliminate any USB and virtualization delays/errors.

https://github.com/elvisimprsntr/pfsense-ntp-gps

@Gertjan
Maybe not but .....

@tiago-fgm
I have successfully killed the watchdog. I am still having issues with reboots after the installation. I can only assume it has something to do with UEFI, partition format, or something along those lines.

Here is what I used to disable the timer:

i2cset -y 1 0x24 0x00 0x00 i2cset -y 1 0x24 0x01 0x00

I am happy to collaborate here if you start working on it.

@michmoor Hello, sorry for late reply. No limiter configured on this.

Yes, upgrade to 23.09.1 then you will see 24.03 available.

No downgrading is not supported. You won't see earlier branches available. However if you are running ZFS you will see a new boot environment created at upgrade and you can always roll back to the old one.

Yes you can put pfSense directly connected to an upstream router.

Ideally I would want to see: Modem --- pfSense --- switch ---- < devices >
I.e. only one router and that's pfSense. Doing so avoids double NAT. However that may not be possible depending on what you're using your upstream router for.

The LED next to the black diamond will flash at different rates to show the status. Slow flash indicates an update is available. See:

https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/io-ports.html#led-patterns

Steve

@Brieto said in SG-1100 not appearing in device manager:

https://prolificusa.com/product/pl2303gl-8-pin-usb-uart-bridge-controller/

Yeah, that should be the one.
And I also just found out that, as from W10, the cable, when the USB (PC) side is inserted, it should auto install :

78b84060-f976-48ce-b587-51f5ba7c87e0-image.png

If nothing helps - from here, then : cable ko ?

It's in the 2.7.2 repo so:

pkg-static install realtek-re-kmod

Then:

echo 'if_re_load="YES"' >> /boot/loader.conf.local echo 'if_re_name="/boot/modules/if_re.ko"' >> /boot/loader.conf.local

Then reboot and check the boot logs show the 1.98 driver:

re0: <Realtek PCIe GbE Family Controller> port 0x1000-0x10ff mem 0xf7a00000-0xf7a00fff,0xf7900000-0xf7903fff irq 16 at device 0.0 on pci1 re0: Using Memory Mapping! re0: Using 1 MSI-X message re0: ASPM disabled re0: version:1.98.00_3 re0: Ethernet address: 00:0d:b9:38:30:10

@schugk said in Intel BE200:

Intel BE200

Nope. There isn't even support for 802.11ac yet. .be is a way off.

@SubSeven hahah - yeah some people go to extremes.. While sure devices can be vampires and suck a little juice while "off" its normally like 1 w or sub 1 watt even. The convenience of having it on instant or close to instant when you want to use it is well worth such cost to me.

TV for example go into sort of standby mode when you turn them off.. but when you want it back on it only takes a few seconds.. But if for example you remove power completely, like power outage or pull the plug, etc - it can take quite a bit longer to boot up.

Same with computer.. I leave mine on, the monitors go into standby, but pc I just am such a random user - I might be on it at any time of the day, 2am if I wake up for some reason, etc.. And just too many issues of coming out of standby for me.. Might work 9 out of 10 times, but that 10th time can be so frustrating.. I will pay the few bucks a year for convenience. The monitors are really what are the juice suckers when the pc is just idle, etc.

Porchlight - I replaced mine with a LED light - same sort of brightness but way less power use. I only turn mine on when people are going to come over or something, or someone is at the door. And if I forget its on, timer that turns it off at midnight anyway. Pretty much every light in my house is LED now..

Yeah the kill-a-watt meters are great!!

But yeah look on your bill to see what your actual cost per kwh works out too, including delivery, etc.. Just for example see how many kwh you used, then divide that by the bill amount.. Then do some math at how much such devices cost you over a year.

You will prob be surprised..

Mmm, I would have though it would have been a much bigger impact if it was really reporting good packets as bad.

Unfortunately I have no 100G gear to test with. 😉

@keyser Thank you very much for your detailed insights... I really appreciate the information that you've provided. It makes sense.

No worries, glad to help. 😁

Anything logged?

Of the 2 options I have on this box it's supposed to be the "better" one. It has MSI-X and dual tx/rx queues to the 82583V's MSI and single tx/rx queue. 🤷

Also, I definitely had the em.5/WAN em.4/LAN setup in the past and it would miss packets over time, but this time it's all good. 🤷

Only I've reconfigured this so many times and it's never worked as well as it finally is. Computers man, what the hell.

@stephenw10 sorted as most recent upside, most old down.

Anyway luckily it isn't happened again.

I'd expect 8125 NICs to work fine. Support for those is in 1.98.

I don't know if this is uncouth to say here, but the new line of Protectli boxes with the N5105 cpu seem to be quite capable and reasonably priced. $230 for a 2 port model and $280 for 4 ports.