On the 6100 it does do a config reset, vs some models it's just a hardware reset/boot.
Frustration understood. :) I suggest creating a new thread per issue so it's easier for people to notice. The forum is pretty active with several dev/admin/support folks from Netgate also, especially in this Netgate hardware forum.
Hmm, the i350 NIC is kinda surprising but there are a number of NICs that present like that. The only NICs we can ensure will work are those we sell. So if you need 4 1G ports the AOC-SGP-i4 does work.
Yup repoc was added in 23.05. In 23.01 that functionality was part of pfSense-upgrade but if it had ever seen 23.05 available it would have pulled it in.
However after running pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade the situation can be unclear since it forces the versions of those packages back to their defaults in 23.01.
In 23.01 you can still use the static repo site that is available for upgrading from 22.05. It looks like your system has at one time seen the dynamic repo packages an pulled them in and now is unable to ull the repo data from them for some reason. You should be able to force it to use the static data by removing the folder: /usr/local/etc/pfSense/pkg/repos That folder should be empty since you don't see anything listed.
However, since there is some doubt as to the status of that install, reinstalling 23.05.1 directly is also an option. That way you know there is nothing remaining from the old repo system that might cause problems later.
The biggest thing that makes me think it's something unique to that install/location is that there are a lot of 3100s running 23.05.1 and if this were common to all 23.0X installs we would be flooded with support tickets.
It almost has to be some combination of unusual things in that specific setup. Testing either of those units in a different location would confirm that.
One other thing we could try is using the debug kernel. If there is some issue it might throw some additional errors before it stops responding. I wouldn't really expect to see anything else when it stops though as it logs nothing at all currently.
I have kinda given up. After talking to two people at Netgate TAC its confirmed that this router can NO do 10gbit, and not even close. If you are going to do anything real world that include the firewall, vlans etc. it will give you 2-3 git at MOST on a good day. The hardware is just not capable of anything else. This is the numbers Netgate is giving me, but most plausible the hardware caps out at around 1.5gbit if you are running from LAN to WAN with firewall and some packet analyzing on.
I appreciate all the support I received on here, but today I ended up returning my 8200. mostly it was me misunderstanding the advertised throughput values. I somehow either had the non-Firewalled or the TNSR values in my head which became my expectations. I was achieving 5Gb/s download speed pretty consistently, but needed a beefier box in order to exceed that so I'm going to be switching back to a DIY build (probably not as much overkill as I had before though).
Hopefully we don't have a reoccurrence (although this device has had it happen twice in two weeks now) but should have console connected to the 5 known devices this seems to happen to.. all appear to have the same symptoms so hopefully capturing one will provide answers for all...
@Cabledude A summer house (even though it is TINY) is such a privilige that I cannot even begin to tell you how lucky I feel🙏
Yeah, I got the base model in both cases - and upgraded them both with a 500Gb'ish SSD because I - luckily - realized soon enough that my use of logging, pfBlockerNG, NtopNG and Syslog-NG would kill the eMMC on both boxes in short order.
I stage logs for my switch and access points on each site in Syslog-NG, filters it and transfers it with TCP to my Raspberry Pi log analyzer (Geeky - i know....😂)
The 6100 is way overkill for 1000/1000 - it is never above 20% utilization on CPU or Memory. It would require use of the 10Gbe interfaces to go higher - but at least a have that for future use now.
At the time there was no 4100 which would be the much more obvious and sufficient choice. The 3100 which was the alternative was going EOL and already suffered from not being a 64bit device (no ZFS filesystem fx.), so that was never actually in play.
@stephenw10 Thank you. I was thinking of getting RJ45 SFP+ but hearing from the forum it can get very hot and may require rebooting. I will stick with the dac solution. It is addition cost but better have cool equipment than a hot one.