Dennis Wood
Senior Member
It's been some time since posting here, but I'd figure I'd post an updated build to compliment the "Confessions of a PfSense newbie" sticky: http://www.snbforums.com/threads/confessions-of-a-pfsense-newbie.5379/
The build in 2011 used 29 watts, the 2016 Qotom version uses only 10 watts (max of 13) measured with an EM100 with RAM and SSD onboard, running under load.
We've been using pfsense for some time now, and found the 5 yr old mini-itx build routers max'd out at 2GB of ram, creating some swap file issues running several instances of Snort. PfSense has been rock solid in our two locations now for 5 years. It was time for some updated hardware. We run several boxes, and require 4 network ports. These were quite inexpensive, easy to configure and work perfectly with pfsense 2.3. We're running a pretty full package compliment including Snort, Squid, Squidgard, Lightsquid, NUT, ClamAV, OPENVPN etc., so the RAM and SSD space was needed. The PfSense boxes manage all of our DHCP, static reservations, DNS and autoproxy config files as well. We run dual WAN in both locations, so the boxes keep busy with load balancing, traffic limiters and guest WIFI access as well as the packages themselves.
The build was very easy this time..just plugged in the RAM and mSATA drive:
QOTOM-Q190G4 - J1900 Quad core 4 LAN 1080P Industrial computer
Intel Celeron Processor J1900(Quad-Core 2M Cache,2 GHz, up to 2.41 GHz)
NO RAM.NO SSD,NO WIFI (NO OS)
Support Windows /Linux (Can not support windows xp)
4 LAN+VGA+2 usb 2.0
Network Card:4*LAN Intel WG82583 10/100/1000M Ethernet
$159
Kingston Technology 8GB 1600MHz DDR3L (PC3-12800) 1.35V Non-ECC CL11 SODIMM Intel Laptop Memory KVR16LS11/8
$30
Samsung 850 EVO - 120GB - mSATA Internal SSD (MZ-M5E120BW)
$68
The Qotom units have zero documentation in the box, but it's pretty simple to configure them. Four screws on the bottom of the case exposes the SODIMM slot, the mSATA slot, and provided SATA/power cables in case you have a SATA SSD kicking around. The case bottom plate hosts an integrated SSD mount. These are very small boxes, with no fan or moving parts at all. They are about perfect for pfsense.
I enabled TRIM on the Samsung SSD as follows. Below is compiled from several other posters on the pfsense forum so thanks to those who posted.
1. booted pfSense from USB stick and installed pfSense to SSD
2. Used Putty to connect to the box, fired up the shell and obtained ufsid by showing the fstab file:
[2.2.4-RELEASE][root@pfSense.localdomain]/root: cat /etc/fstab
# Device Mountpoint FStype Options Dump Pass#
/dev/ufsid/576dca6e13175d08 / ufs rw 1 1
3. booted pfSense from USB stick into single-user mode
4. at the # prompt, the following was issued:
/sbin/tunefs -t enable /dev/ufsid/576dca6e13175d08 (your ufsid will be different!
/sbin/reboot
5. booted pfSense from SSD. Again using putty, ran this command from shell to see if TRIM was enabled.
/sbin/tunefs -p /
In terms of the hardware swap, it was suprisingly simple. I did our work install in the 30 minutes during lunch. I had previously updated the two 2011 vintage boxes over to 2.3.1-RELEASE-p5 (amd64), then backed up the configuration. The Qotoms got a fresh 2.3.1 install using USB. Restoring the old config (a lot of time invested there!) onto the new boxes was super simple. The pfsense web gui prompts you to reassign your network ports (as it detects the mismatch), it reboots, installs packages and all good. The upgrade was surprisingly simply. I only had to copy my proxy.pac, wpad.dat and proxy.pa config files (make sure you keep a copy!) over to the new install and it was done.
The PfSense crew deserves a lot of respect in terms of making this so simple. It would be pretty amazing if PC machine replacements went this well.
The pics below are pretty much self explanatory
Cheers,
Dennis.
The build in 2011 used 29 watts, the 2016 Qotom version uses only 10 watts (max of 13) measured with an EM100 with RAM and SSD onboard, running under load.
We've been using pfsense for some time now, and found the 5 yr old mini-itx build routers max'd out at 2GB of ram, creating some swap file issues running several instances of Snort. PfSense has been rock solid in our two locations now for 5 years. It was time for some updated hardware. We run several boxes, and require 4 network ports. These were quite inexpensive, easy to configure and work perfectly with pfsense 2.3. We're running a pretty full package compliment including Snort, Squid, Squidgard, Lightsquid, NUT, ClamAV, OPENVPN etc., so the RAM and SSD space was needed. The PfSense boxes manage all of our DHCP, static reservations, DNS and autoproxy config files as well. We run dual WAN in both locations, so the boxes keep busy with load balancing, traffic limiters and guest WIFI access as well as the packages themselves.
The build was very easy this time..just plugged in the RAM and mSATA drive:
QOTOM-Q190G4 - J1900 Quad core 4 LAN 1080P Industrial computer
Intel Celeron Processor J1900(Quad-Core 2M Cache,2 GHz, up to 2.41 GHz)
NO RAM.NO SSD,NO WIFI (NO OS)
Support Windows /Linux (Can not support windows xp)
4 LAN+VGA+2 usb 2.0
Network Card:4*LAN Intel WG82583 10/100/1000M Ethernet
$159
Kingston Technology 8GB 1600MHz DDR3L (PC3-12800) 1.35V Non-ECC CL11 SODIMM Intel Laptop Memory KVR16LS11/8
$30
Samsung 850 EVO - 120GB - mSATA Internal SSD (MZ-M5E120BW)
$68
The Qotom units have zero documentation in the box, but it's pretty simple to configure them. Four screws on the bottom of the case exposes the SODIMM slot, the mSATA slot, and provided SATA/power cables in case you have a SATA SSD kicking around. The case bottom plate hosts an integrated SSD mount. These are very small boxes, with no fan or moving parts at all. They are about perfect for pfsense.
I enabled TRIM on the Samsung SSD as follows. Below is compiled from several other posters on the pfsense forum so thanks to those who posted.
1. booted pfSense from USB stick and installed pfSense to SSD
2. Used Putty to connect to the box, fired up the shell and obtained ufsid by showing the fstab file:
[2.2.4-RELEASE][root@pfSense.localdomain]/root: cat /etc/fstab
# Device Mountpoint FStype Options Dump Pass#
/dev/ufsid/576dca6e13175d08 / ufs rw 1 1
3. booted pfSense from USB stick into single-user mode
4. at the # prompt, the following was issued:
/sbin/tunefs -t enable /dev/ufsid/576dca6e13175d08 (your ufsid will be different!
/sbin/reboot
5. booted pfSense from SSD. Again using putty, ran this command from shell to see if TRIM was enabled.
/sbin/tunefs -p /
In terms of the hardware swap, it was suprisingly simple. I did our work install in the 30 minutes during lunch. I had previously updated the two 2011 vintage boxes over to 2.3.1-RELEASE-p5 (amd64), then backed up the configuration. The Qotoms got a fresh 2.3.1 install using USB. Restoring the old config (a lot of time invested there!) onto the new boxes was super simple. The pfsense web gui prompts you to reassign your network ports (as it detects the mismatch), it reboots, installs packages and all good. The upgrade was surprisingly simply. I only had to copy my proxy.pac, wpad.dat and proxy.pa config files (make sure you keep a copy!) over to the new install and it was done.
The PfSense crew deserves a lot of respect in terms of making this so simple. It would be pretty amazing if PC machine replacements went this well.
The pics below are pretty much self explanatory
Cheers,
Dennis.
Last edited: