There's no need for Netgate coreboot update on your system, so it's giving you the generic error / warning.

HA! Sorry to bug you all. I spent some more time in this forum and discovered the Netgate Coreboot Upgrade package. I applied an update and that seems to have done the job. Ping times are find now. VoIP sounds good, too! regards, Cybertoy

Bit late but… The MAC of traffic from the LAN ports will by the LAN interface MAC, mvneta1. Whilst I think you could technically configure on of the switch ports as a mirror port we don't currently have any way to set the in the GUI. It is possible to configure a bridge and set a span port to mirror the bridge traffic. That does incur a performance penalty though. Steve

Derelict, Again, thank you for responding!  I've decided to forgo the bridging idea.  In my other post, I bring up some questions I have about the way to properly trunk an interface and change it's native VLAN.  Thanks!

I'm running Suricata rulesets on three different VLAN interfaces without any issues. They take about 300 MB of RAM in each process. Running Squid on top of all this is what caused an out of memory condition and hung the device until I rebooted it. It's the Little Router that Could, but not too much.

@jimp: Boot to single user mode and run "fsck -y /" a few times until it does not find anything, don't stop when it claims to be clean. It may take 3-5 times. Thanks! This got me all fixed in a hurry in the field today.  Day started out with me having a really bad attitude toward PFSense Store purchased SG-2440 equipment. I usually build my own PFsense boxes out of PC hardware for clients and they last for years without any issues other than keeping them up to date. This would have been the 4th SG-2440 that suddenly ate itself for lunch and failed.  This box has not been modified or changed lately and is on clean battery backed power.  So I wonder what might have caused this to happen suddenly. Thanks again & take care!

I do not believe Netgate/pfSense has ever shipped anything Celeron-Based. ALIX, APU, Atom D525-ish, Atom C2XXX, Xeon-D, and recent ARM is all I can recall. You might want to post a picture and check the end-of-sale products here: https://www.netgate.com/docs/

Thanks!

Thanks!  I was a few versions behind.

Adding my vote for a "newer version available" message flag in the BIOS section.

Thank you! Please let us know how the deployment goes.

Jim and dotdash, thank you both.

Jimp, just wanted to say thanks again for your help and let you know it worked flawlessly.  Crossing my fingers I can get IDS set up this weekend without doing anything stupid …

It could also just be the cable.. For gig to come up multiple things have to happen..  It could be the cable, it could be the negotiation between your media converter port and the sg3100 interface. So yes connecting a PC that you know is gig and has shown gig connection before, with a cable you know has worked with gig is a valid test. I would do that test with the media convert to your PC and also the PC to sg3100 interfaces.  Both its wan/lan interfaces and its switch ports. Do you have another gig switch, be it smart/managed or even just dumb? It could be something as stupid as if the media converter is managed that they have the interface set for set for 100 hard coded, etc.  Or there is something off with the cable. Also you sure your running the light correctly… What does pfsense web gui show for the connection speed?  When you say "connection is capped at 100 mbps up and down" So your seeing low to mid 90's - 100mbps switch/port connection is not capable of actually doing 100.. If your speed test is showing you 100, and not say 95-97 tops say then that could point to a isp cap to your speed and not the actual interface being at 100..  The front page of pfsense should show you what speed the interface is at. [image: interfacespeeds.png] [image: interfacespeeds.png_thumb]

Thanks very much, that's exactly what I was looking for!

Never mind - ended up solving my own problem - once I rebooted with the addition to the conf file - the application showed up on the Services drop down menu where I could enable and configure it - it is now up and running - no problems.