I would definitely use the 6100 there. You might well end up with packages or traffic shaping on the firewall and the additional CPU cores will probably be required. Steve

Sure PM me.

Yes it looks like some data was inadvertently carried over from the 6100 there. Thanks for pointing it out, we are reviewing and updating pages now. And for clarity, yes, the 4100 has a single m.2 slot that intended for storage only. Steve

@steveits Thank you, I was able to get the latest firmware from Netgate and install it with little difficulty. Back up and running.

Yes, I agree. ~1Gbps routing/NAT/filtering with pfBlocker and Snort/Suricata is definitely a 6100, at least. Steve

@stephenw10 Thanks! I will give it a try then :)

Yep, got a TAC lite free software subscription, asked for the 22.01 pfsense+ firmware on a ticket and had it in less than 30 minutes! The memstick reinstall fixed the issue. Brilliant! Thanks NETGATE!!!

Do you have an expansion card in the 1541? Which one? If you have the 4x1G card then you will have 6 igb interfaces in the 1541 and the config will just import without having to reassign anything. You'll simple have to move the cables across in the correct locations: https://docs.netgate.com/pfsense/en/latest/solutions/xg-1541/io-ports.html#optional-quad-port-expansion-cards Steve

@lonewolf007 said in Netgate Appliance - Intel: install pfsense+ (think it only works on Netgate's only appliance? See here : Migrate from pfSense CE software to Netgate pfSense Plus software! IMHO : get an TAC for a device and install + on it.

@rcoleman-netgate Running the force-update has done the trick. The SG-1100 is now running 22.01 using ZFS. Thankyou.

Thank you. Seems to be losing 1-2 sec per hour.

You got 2 Cores and 4GB Ram to...

@mkeenan I had a similar OS message recently. The shortest/safest path may well be to open a free ticket at go.netgate.com and have them send you the firmware, and install it via USB stick. I have gotten past odd warnings before but this time it borked and I had to recover manually. If you've installed a package from the current repo onto an old version that may try to install dependencies from the later version. Otherwise see https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html, maybe set to "previous version" and install that first, and work your way up. 2.4.4 is pretty old. I think I started with 2.4.2 on the one that had to be reinstalled. IIRC it worked to get to 21.02 but then even though it offered 21.05 it "installed" 22.01 and was left half upgraded with the wrong OS. HTH,

Hi folks, The problem was indeed a cable plugged into wrong switch port. The funny fact is that that mistake was actually done in January, but only now things started to break. Anyways... thanks everyone for assisting me. Best regards,

@jlpoole At least it's not VLAN0 tagged like it is on that AT&T connections (IIRC). Glad you were able to get your connection up!

Thanks for the suggestions everyone. I reached out to support and they helped me convert my old config. I think I'd be able to do it myself with this xml as a guide going forward.

Yeah, it certainly can be updated. Try running at the command line: pkg-static -d update That should show you errors indicating why it can't check for upgrades. Steve

Yeah, loader.conf.local is only added at install by the installer. So if you never had it in the first place it would never have been added. When you install 2.6 clean does it install and boot as expected? I assume it does as UFS? Does it as ZFS if you comment out the i915 lines before rebooting after the install? What you're hitting appears to be something unrelated to that issue. Steve

@stephenw10 i will take the m.2 to work and see if i can get the screw lose. the hight of the m.2 standoff seems not standard do you think you can find one that might fit? and i have only seen m.2 standoffs with a built in screw and not one that can get screwed into. @rcoleman-netgate i will try and get it loose tomorrow at work i have taken out the m.2 standoff as i stated to Steptemw10 above. will post again tomorrow if it is sucessful. but it would be good to know what kind of standoffs you guys use so we can get the same or close to same :)

@johnpoz Thanks, after doing a full power cycle as suggested in that thread, the upgrade worked.