$ mcelog --no-dmi --ascii --file mce.log Hardware event. This is not a software error. CPU 0 BANK 3 MISC 0 ADDR 0 MCG status: STATUS fe00000000800400 MCGSTATUS 0 APICID 0 SOCKETID 0 You have a hardware problem.

Thanks for the follow up. Easily done. Steve

Thank you very much for the help and advice

@picasso566 said in NIC not recognized pfSense 2.4.4/Intel PRO/1000 Pt Dual: I live in Tokyo and my Japanese is terrible. I bet it's better than mine!

I successfully installed pfSense on 2 DELL R320 servers this weekend to replace my WatchGuard XTM 525 (primary) and XTM 810 (backup) pfSense appliances. Now I'm ready for the next version of pfSense (2.5) that supports AES-NI.

You can do the ping if you ssh to your router, its not really much use unless your using ping to see if a device is back up after a reboot. −A Audible. Output a bell (ASCII 0x07) character when no packet is received before the next packet is transmitted. To cater for round-trip times that are longer than the interval between transmissions, further missing packets cause a bell only if the maximum number of unreceived packets has increased. −a Audible. Include a bell (ASCII 0x07) character in the output when any packet is received. This option is ignored if other format options are present.

Yes, the supplied injector would be easiest. Then using a PoE switch. Using a NIC that can supply PoE is not something I've ever actually seen myself. It would be interesting but almost certainly far more expensive. Steve

Hi! I know this is kind of an old topic but... :-) First, Thank you SO SO SO MUCH for the FreeNas Tipp ;) Saved me hours recompiling the kernel (never done that on FreeBSD). Is anyone running LACP with these cards? I currently have pretty bad performance issues, ~1-2G throughput with a 2 link 802.1ad Cheers, Matthias

xlameee… Can you please answer my questions about the LC version for the Dell R320.

Probably better to ask if FreeBSD 11.2 does. More chance someone might have tested that and posted it somewhere Googleable. Steve

X553 is the NIC used in the C3000 SoC so yes. And they are 1Gb in the SG-5100: https://store.netgate.com/SG-5100.aspx Steve

Hi @dajones13 , Not sure what our budget or connection speed is, but in terms of of your requirements I can recommend this: https://www.supermicro.com/products/system/1u/5018/SYS-5018D-FN8T.cfm Have been using this system (added SSD and 16GB RAM) with a symmetric gigabit fiber connection for about 1.5 years now without issues. Very capable little box with room for growth. If you need more horsepower, check out this newer model: https://www.supermicro.com/products/system/1U/5019/SYS-5019D-FN8TP.cfm Hope this helps.

Ok, with only one config index it will need to be changed in Linux. That does assume CradlePoint haven't changed it in some way. Steve

@killpilot , thanks for the follow-up. After giving it a lot of thought, I also decided against virtualizing pfSense. I decided it would would be better to run something this critical on dedicated hardware. I ended up going with a different solution (Fortigate) as I wanted something pretty robust with good support. So far it's working well.

Of those, I'd probably go with the i3 if 2 gbe is sufficient. It'll have VPN performance roughly on par with the xeon, and faster than the c3558. If you want to spend $750, the https://www.wiredzone.com/supermicro-servers-compact-embedded-processor-sys-e100-9s-e-10028141 should outperform the d-2123it for this application.

OK, but once you've done that you can boot from USB, change the console settings etc. It will be far easier to boot other things with all the BIOS options available. Steve

It helps a lot! Finally a proper answer :) Thank you very much! Best, Nick

Hi Steve, it seems like this motherboard and pfSense ain’t friends at all, acpi issues all over the place... I tried to turn it off in loader.conf but then it just doesn’t boot. I’m going to replace this board with a different one and give it a go. Thanks C

Here are the results before and during the speedtest: Before: 11 root 155 ki31 0K 64K CPU0 0 154:42 98.58% [idle{idle: cpu0}] 11 root 155 ki31 0K 64K CPU3 3 154:30 98.41% [idle{idle: cpu3}] 11 root 155 ki31 0K 64K CPU1 1 154:18 97.95% [idle{idle: cpu1}] 11 root 155 ki31 0K 64K RUN 2 154:51 97.35% [idle{idle: cpu2}] 340 root 32 0 98776K 38364K accept 1 0:02 1.36% php-fpm: pool nginx (php-fpm){php-fpm} 19 root -16 - 0K 16K pftm 0 0:57 0.60% [pf purge] 71606 root 20 0 7812K 4000K CPU2 2 0:00 0.12% top -aSH During: 12 root -72 - 0K 544K WAIT 1 2:17 98.74% [intr{swi1: netisr 0}] 11 root 155 ki31 0K 64K CPU3 3 157:05 76.71% [idle{idle: cpu3}] 11 root 155 ki31 0K 64K RUN 2 157:33 69.36% [idle{idle: cpu2}] 11 root 155 ki31 0K 64K RUN 0 157:20 63.68% [idle{idle: cpu0}] 12 root -72 - 0K 544K WAIT 0 0:38 26.18% [intr{swi1: netisr 1}] 12 root -92 - 0K 544K WAIT 0 0:43 24.11% [intr{irq260: igb0:que 0}] 12 root -72 - 0K 544K WAIT 3 0:32 15.26% [intr{swi1: netisr 2}] 12 root -92 - 0K 544K WAIT 2 0:15 8.30% [intr{irq264: igb1:que 0}] 12 root -92 - 0K 544K WAIT 3 0:13 4.80% [intr{irq265: igb1:que 1}] 11 root 155 ki31 0K 64K CPU1 1 156:40 2.67% [idle{idle: cpu1}]