@stephenw10 I was just in the process of filling out the form on the website when I got the email you had replied to my post. I'll have the ticket submitted shortly.

Yeah I think trying to diagnose this with the other other issue still present is going to be very difficult. There's s good chance they are related and it might already be fixed in 23.05.

The service watchdog is a trouble shooting tool and should be seen as such. There are some situations where you might want to enable it on a service in a more permanent way but even then it's usually to address some underlying bug. For example if you have an OpenVPN client and want it to be always up you might use the watchdog. But only because if the server side rejects the connection as unauthorized the client will exit and not retry. Most clients would never see that or if they did retrying would not help. Steve

@nevolex The 1100 has not even be slated as "end of sale" so it's successor is still the 2100, whose successor is the 4100, whose successor is the 6100, whose successor is the 8200, whose successor is the 1537, whose successor is the 1541. Also when there's an announcement to be made look for it to appear in Netgate Announcements

Yeah, you should be fine. Just reinstall 23.01 clean when you can.

Thanks @stephenw10 !

@captainron My previous offer still stands.

@stephenw10 said in IMIX benchmarks: There has been no significant change there. I haven't seen any measurable change in local testing. Thanks Stephen. Have a nice weekend!

@stephenw10 said in SG 1100 unable to check for updates: @gdarends said in SG 1100 unable to check for updates: Segmentation fault (core dumped) The first thing to try here is a full power cycle to reset the crypto chip. That means actually pulling the power plug, a reboot does not reset it. That was it! Thanks so much. Gonna start prepping to do the upgrade now.

You might be able to get a new-old-stock SG5100 which works great for 1gb PPPoE, but with 1gb ports instead of the 2.5/10 on the 6100…

@iversa None of the Netgate devices have Wireless built in and there is a wireless function in pfSense but it is not well supported by FreeBSD and you should look at any other dedicated Wireless AP option instead. As a company we do not have a specific recommendation of any particular product.

I would expect it to install and run fine but you would be missing some of the hardware support. So at least the LEDs and reset buttons would not function. That would also mean the firmware updater for BlinkBoot would not be available should there be an update. It's not something I've tried though because it's not supported. I can do if it's something you need. Steve

@stephenw10 Thank you. I'll message you my NDI shortly

It does sound like the eMMC has failed. There are some of us on 23.01 who have seen 1100 storage timeouts but they behave a bit differently than that (and I haven't seen them at all on 23.05). While it is possible in theory to run from USB, in practice it's not that viable. Running live off a thumb drive will kill the thumb drive fast, they are not made to take constant writes. Last time I tried this it didn't even make it a month. Maybe an actual SSD in a USB enclosure might have a chance but it's debatable, given the 1100's pickiness with what it will/won't boot. If you can find one that will boot from, You could go into the Marvell>> prompt and change the default bootcmd. Out of the box, it's set to bootcmd=run emmcboot to boot from eMMC. You'd need to run setenv bootcmd 'run usbboot' and then saveenv to make it boot from USB each time. But again, it's anyone's guess whether or not that would boot reliably. To get that far you'd also need to manage to get the live/installed image onto a USB drive, and not the recovery installer.

@ariban99 We are working with you on this ticket right now.

The fact you can't apply/revert those patches is not necessarily a problem. None of those patches address the error you originally posted though. That should already be fixed in 23.01 so it looks like something might have regressed that fix. https://redmine.pfsense.org/projects/pfsense/repository/1/revisions/c5c09acd9713a8e3ed3a553dc4d83daf4baf9502/diff/src/usr/local/www/services_dhcp.php

@ddbnj thanks for the info, will check the channel out as well.

@rdatla Did you apply the recommended patches in System Patches? There is specifically a patch for linker files on 3100. Or as a (the same fix) workaround run "kldxref /boot/kernel" in SSH or Diagnostics/Command Line.

Test the card in something else. Assuming it works there check the PCI IDs it's returning.