Hi @Commander - I think you'll be quite happy with your choice. I have been running pfSense on this exact system for about two years now without any major issues -- this little box offers great performance. Let me know if you have any further questions regarding configuration or performance tweaking once you have got things setup. Hope this helps.
Hi @imthenachoman -
I'm sure you'll get a lot of different suggestions, but here's one possibility - I put something similar together recently (although it was not for pfSense):
CPU - Intel i3-8100:
Motherboard - ASUS Prime H310I-PLUS CSM:
NIC - Intel i340-T4
This includes a pretty speedy (high clock speed) quad core CPU and mini-ITX board combined with a fairly recent Intel quad port NIC. This should have no problem passing 1Gbit (though not over OpenVPN). Of course don't have to use this particular case, was just an example of what's out there for mini-ITX.
Hope this helps.
@stephenw10 Agreed. Plan is to install pfSense just to get a feel for the OS/experience. My networking knowledge is not great so if I can't figure it out then I want to know before I buy a new LAN card. I've seen some videos online with screenshots and those screenshots had many terms I don't know so I'm a little worried. Just created the USB installer so I'll see how it goes.
@ac0hen said in Zotac CI323 Installation - Controller Failures:
bsdlabel -B -r -w ada0s1 auto" command, it stops at 77% (every time). Then a "ahcich1" Timeout on slot 21 port 0" and "(ada0:ahcich1:0:0:0): CAM status: Command timeout
With that same error?
The port placement and LCD look like a Lanner box in which case I would expect the SDEC driver to work. That's connected via the parallel port.
However almost all Checkpoints other stuff is Portwell/Caswell. That's not the EZIO LCD though.
But yeah it will only run the now obsolete 2.3.5.
I have made FreeBSD 12 package.
I dont consider it my work - I have just packed it in one archive. It is stable for me on 12.0 p3 more than
"sed -i -e 's/TAILQ_FOREACH/CK_STAILQ_FOREACH/g' if_re.c"
I have been using this system for a couple years now with a symmetric 1Gbit fiber connection and it is definitely capable of passing gigabit speeds even with IDS/IPS enabled (in my case I run Snort). Here a couple more suggestions:
Networking tweaks - put these four lines below in your loader.conf.local file (if you're using the SFP+ ports replace igb with ix):
I'd also recommend disabling flow control and energy efficient ethernet, unless you have a specific need/use for them.
Another good thread with tuning tips:
Finally, if you disable Suricata temporarily, do you get full speed with a client behind pfSense, or does it not make a difference?
Hope this helps.
@stephenw10 said in pfsense on rasppery PI:
You can do that with Radius accounting in pfSense but it's quite a complex setup. It also doesn't scale well to a large number of users if you have individual accounts in Freeradius. The GUI is not setup for that. Better to use a separate Radius server if you need that.
It would not run well on an SG-1000, if you go that route it should be installed on larger hardware.
So I managed to solve this with a BIOS update in the end. Part of the update process was clearing the CMOS so I had to change a bunch of settings back. The only setting I know was different that I chose to leave default this time was the ACPI HPET Table option. Previously it was enabled, now it's disabled. I don't really see how this would affect performance to the extent I was seeing, so I suspect it was something in the BIOS updates that solved the issue. Also MSI interrupts are definitely slower than MSI-X, they took me down to 50mbit.
For the next sod that goes googling this, the Motherboard was an ASRock N68-S3 UCC. Initial BIOS version was 1.4, updated to 1.6. I'm now running all defaults except that I've restricted my queues to 1 per NIC with the following in /boot/loader.conf.local
I'm doing this because I have a dual core CPU and 4 NICs, so I'm trying to reduce the amount of context switching. It may work fine as a default, but after the nightmare of getting it to this point I'm just going to leave it be.
@johnminaa said in 4g modem info:
I will also recommend Huawei E398 LTE USB Modem.
I never owned, used or recommended it. Personally I would recommend Huawei E3372H as a replacement. Fortunately some people already posted here some receipts on using it in the different modes.
@mats thanks for the reply and please forgive the long delay in responding.
Thanks for the advice regarding the electrical side. Have a APC UPS powering the cable modem. The coax feeding the cable modem is run thru a surge suppressor . The pfSense box is powered by a separate APC UPS. Anything else I should consider?
Ah, interesting. I have seen that with an incompatible SFP module but never with just the connection like that. But yes in that case simply removing the module and rebooting was not sufficient to clear the state in the NIC. It had to be completely powered down to see the correct module again.
Then any relatively cheap i3 like the 4130 will work. That will give you a faster CPU with hyperthreading and AES-NI.
I think someone fitted one earlier in this thread. (edit: several people in fact)
Ok, you will need to change it's mode. For example:
It would be better to permanently switch it which might be possible from it's interface in Windows or Mac.
Otherwise if you can switch it to device ID 1C05 it should be detected:
If you boot an image that does not use a serial console by default you won't see anything unless you have the VGA header hooked up.
The XTM5 does not have a UEFI bios. It you try to boot an image that requires UEFI it won't boot.
Are you trying to boot USB? Do you know the pfSense installed boots USB, you've made the required BIOS changes?
You might have more luck with a Broadcom NIC and patched FreeBSD driver:
I have no way of testing that myself....
I have some updated info.
I created a new vlan on the cisco switch and setup two etherchannels. One for the pfsense wan and one for the modem and put them both on the that vlan. basically a "WAN" bridge between the two devices I also added a gig port to the new vlan as well. This way I can test speeds between the modem and/or pfsense WAN side. My test computer picked up a public ip on the WAN vlan and ran some iperf tests for ingress and egress to an inside client. That produced 970Mbps both ways with no dupes or other problems in the packet capture. So I feel this rules out any issues with my inside network and pfsense.
Running a speed test across the etherchannel to the cable modem from a 1Gb connection I was able to reproduce the exact same issue I had with low throughput. I even used new cables and tested them with my fluke to be sure. So it seems like this is an issue with modem+lacp or firmware. If it was a modem firmware problem I'm SOL anyways. I'm little burned out on it right now so I'll come back in a few days and keep working at it. I have Mikrotik a could try, maybe a windows computer with a LAGG directly connected to the modem.
so I fixed this. I plugged the modem into a win box, connected to the serial port then
this enters the modem into the download mode disabling the drives altogether. (AT+ZCDRUN=8 did NOT work for me)
this is being saved in the nvram.
plugged it back in, worked right away !
ugen0.2: <ZTE,Incorporated T-Mobile Rocket 4G> at usbus0
u3g0 on uhub0
u3g0: <ZTE,Incorporated T-Mobile Rocket 4G, class 0/0, rev 2.00/0.00, addr 30> on usbus0
u3g0: Found 3 ports.
Thank you both of you for your advices.
Actually this server has either broadcom or intel NIC
I concluded the study by recommending choosing the one with Intel NIC.
I hope there will be no problem during the installation and the configuration.
@stephenw10 100% agree. That is literally the predicament I am in. For now, I VLAN to a PC who has a top of the line CPU in it (overkill really) which would probably do gigabit OpenVPN, but given my internet connection is 100/40, the box above seems like it will be perfect for the cupboard.
Sadly not at least on the 1u version. The only fan was a cpu blower designed to pull from the cpu and motherboard and push the heat out which you can clock down but still noisey. I did buy some 1u silent Gelid fans as supermicro are always generous with connecting fans but still did not work well. The other issue is the very noisy (although labelled as silent) 1u PSU.
I've been on the periphery with pfsense for a while now so did not know that "aes-ni must have compatibility" was pushed back. I went out last year and dropped £200 on one of the fanless and silent qotom boxed. ALthough am very happy with it as against running a vm.