They seem perfectly sufficient in the testing I have done. It does not run especially hot. See: https://docs.netgate.com/pfsense/en/latest/solutions/sg-5100/m-2-sata-installation.html Steve

It's DDR4 2400MT/s non-ECC, 4GB, 8GB, or 16GB SODIMMs. Steve

Yeah that's not likely to be Unbound. It's exhausting the RAM and swap space (if you have an SSD) so something is using far more than expected. Try running top -aSH at the command line to see what is using it if this is still an issue. Steve

I had exactly the same problem today, with my sg-3100. Luckly, I also had a backup config and a 2.4.4 p2 firmware in a pendrive. Installed, upgraded, restored, download blacklist from squid/pfblocker, restored my keytab file to squid folder, and everything is working perfectly again. I will perform the reboots from now on with the F option, to force fsck.

register and open a ticket at https://go.netgate.com they will assist you

Ok I messed up some DNS settings. All better now.

I understand, thanks for your fast reply .

Glad you have your XG-7100 back on track. -Rico

@vladanpopovic said in locked out - reset not working - SG3100: address i get is not 192.168.1.X but something like 169.254.29.154 with a subnet 255.255.0.0 - I have no idea where this address comes from. The DHCP client running on your device (PC, Phone, laptop, whatever) will auto-assign itself an 169.254.0.0/16 after a certain time-out : when no DHCP is answering its request for an IP/DNS/Gateway..

Yeah moved, sure didn't belong in the TNSR section.

That is odd. Are there no other log messages around the time of the reboot? Anything from before the reboot? Since you can somewhat predict the occurrence, could you leave a system connected to the console port logging the output from there to see what happens? It may have some better info. From the general symptoms it sounds like a power/environmental issue somehow, perhaps it's enough to trip the 5100 but not a UPS, though at least for me, my 5100s don't seem to be phased by small power blips even without a UPS. If you leave the console connected and there is nothing logged before the reboot, then it would almost have to be power or hardware. A hardware issue would almost certainly be more random/less predictable, though.

ix0-ix3 should be assigned but not enabled by default. igb1 is LAN by default and that's where you be given an IP address via DHCP. https://docs.netgate.com/pfsense/en/latest/solutions/sg-5100/io-ports.html Steve

You would need to re-assign the WAN to ix0. By default it uses lagg0.4090 to connect to the Eth1 port via the internal switch. So Interfaces > Assign. Change the dropdown on WAN to ix0. Either remove OPT1 or assign that as some other port and save. Steve

Yeah that's crazy and seems completely unnecessary. No such code should be required to create a pps driver should you go that route. Steve

@kiokoman As mentioned above, on the SG-4860-1U that I have, there is no contact surface to clean - the eMMC is directly soldered to the PCB. Aside from trying to resolder it, there isn't much to do, and at that point it's too big a risk vs. the mSATA and ignoring kernel messages. I could probably change the config to avoid mounting da0 in the first place if it gets that frequent/irritating.

Hey thx KOM! BlazeStar, thanks for the heads up. I’ll get our partner manager to update our listing. And, thx for the order. We will get it out tomorrow morning. Bill

I wouldn't think so.. As long they both support the fiber type your going to use.

Yeah with the switch configured like that the OPT port is just a second switch interface on the LAN which is what you want. The OPT interface becomes irrelevant you could disable it and unassign it. In the Interfaces > LAN settings set the 'Switch port' field either to port 0 (always connected) or to not monitor a port. It is monitoring the LAN port status so when you unplug it it marks the interface as down. Steve

@Kleinmann I couldn’t get it to work with any cable so I opened a support ticket. They replaced my hardware at only the cost it took me to ship it to them in Texas.