@slackie Let us know how it goes. I've been sitting in the weeds watching this thread with interest. Ted

@SteveITS said in Can not update - no space left on device: the future I’d do that before upgrading Before updating, upgrading, for every device you own - PC, smart light bulb, your car, printer, Phone pad and camera : These are the universal rules : Step 1 : power it down and count to 10. Step 2 : Power it back on. Step 3 : If the device has a 'filesystem' or a massive comples operatuion system like a Phone, PC, and also pfSense : check avaible space. To understand why and what happens there isn't : try upgrading PC from Win 10 to Win 11, with less then x Gbytes left on the disk. You risk to 'break' the OS on your PC, it can't boot anymore and good luck retrieving your data. Step 4 For pfSense : Get (export) a copy of the config. Now you are ready to upgrade. These 4 steps take 5 minutes max, and it's really small investment, see it as a assurance. If you don't do these 4 steps, the risk is great you loose way more time (and your data). You could recap my ramble in 5 words : "Do not test Murphy's law".

Just following up here -- still running solid after a year plus. Have probably only rebooted a couple times over that year but no problems at all.

@preston said in Goodbye Netgate Hardware: Just lost my 4100 after about 3 years of light duty use. eMMC failure. With the amazon link shown above, you can make, after 3 years of service, a perfect 4100 MAX out of it. That's the one you wanted anyway ^^ I've a MAX, using barely 10 % of the avaible disk disk space, have backup ZFS partitions to go back to 23.09 if I have to.

@stephenw10 said in Realistic Lifespan on Netgate Hardware 5100: I've not seen a 5100 fail like that. Usually if I saw symptoms like that I would look for unexpected CPU loading. I've been experiencing long delays and hangs using the web interface. Even after the clean re-install the UI has occasional delays. Would you consider that unexpected CPU loading?

Yup some forced cooling is about the only thing you can do there. The 1100 is designed/expected to run hot though.

@patient0 Thx for pointing out - there is a lot of information .... :-)

@thanosg said in SG-1100 – Inconsistent LAN Interface Detection & WebGUI Access After Config Import: During system initialization, the device frequently fails to detect the LAN interface. What exactly are you seeing that makes you think it's not detected? The 1100 only has one NIC. The three ports are accessed via VLANs configured by default. So it's hard to see how it could ever fail to find the LAN whilst still seeing the WAN and OPT interfaces.

@itandgeneral you might need to add some heat sinks because of heat build up too …[image: 1768754068320-img_3448.jpeg]

@hsgajmer21 TAC may be able to help. Try contacting them. If not, make a new thread for further discussion.

@pdalmao Is this a brand new FSP? You can use any high-quality 12V 5-10A power supply (a “brick” type), such as MeanWell. You just need to solder, make, or buy an appropriate adapter. [image: 1768389193936-1baaf983-5844-437b-a345-453656936a71-17683891359631139037712982685383.jpg]

Hmm 50X error like that is almost always some PHP issue. Like PHP has stopped or all available PHP threads are used. There should be something logged when it starts happening though. Something beyond those logs which also just show the PHP is nor responding as expected.

@netboy said in Migrating from Netgate 2100 to 4200: Advice on Port Mapping & Integrated Switch Removal: should I bother with a software bridge to keep the "two ports per network" behavior of my 2100? Not unless you really need it, I agree. The 4200 ports are not a switch and using a real switch is better in almost every way.

Thx so much, I appreciate the input!

@crgbt said in Netgate 4200 - physical RJ45 port sensitivity: all three worked fine in my Ubiquiti equipment Gee, I wonder why...

@w0w different technology and more than twice the difference in listed performance. That’s not something I would attribute to testing methodology with out real data suggesting otherwise. Imo a much more likely explanation is Netgate were not focusing on SSD wear as a major limit to device reliability and brand reputation at that time. They are now and I would be surprised if they made the same decision in the future.