New to Pfsense just a couple of quick questions
-
Hello all, I'm new to the PC as a router scene and as such have a few questions. (I have read a lot of the topics and FAQ's just to clarify.) So grab yourself a coffee and read on :)
The hardware I will be using for the Pfsense box:
MSI 694D Pro Ver2
Dual P3 @1GHz
2GB ECC SDR RAM
2 Intel pro/100+ server NIC's (on the supported list)
1 D-LINK air plus DWL-G520 wi-fi card (on the supported list)
HDD…Well thats my first question, I want to keep this router as low powered as possible so I was going to buy a CF to IDE adaptor and run a 2GB CF card.
Now from my understanding I want one with SLC chips as they are higher quality and faster. So I may get a 2GB Transcend 300x card. Is 2GB enough to run Pfsense and Squid/adzap?
I have a 20Mb cable internet connection (static IP) which will go into one of the NIC's and deal with the WAN side.
The LAN side is where I'm needing help though. I want the router running a DHCP server to hand out IP addresses to my PC, PS3, mum's pc, etc. Can I use both the second Intel NIC and the D-Link wi-fi NIC on the same subnet?
For example my PC gets an IP address of 192.168.1.2 from the LAN card, my PS3 gets an IP of 192.168.1.3 from the wi-fi card.
Last question I promise :P will this setup I'm proposing be able to handle around 200 ping requests every 15 seconds (I run dimes, basically maps the internet, low bandwidth use) and handle 200 odd crawlers (I also run MJ-12, again maps the internet but uses a lot of bandwidth)
Thanks for reading and I look forward to your responses.
-
The LAN side is where I'm needing help though. I want the router running a DHCP server to hand out IP addresses to my PC, PS3, mum's pc, etc. Can I use both the second Intel NIC and the D-Link wi-fi NIC on the same subnet?
Yes, bridge wireless NIC to LAN, add firewall rules to wireless NIC to allow DHCP traffic.
-
Ok my pfsense box is up and running great, except for one problem. It seems a partition has run out of space, here is my sys log:
Feb 6 02:06:12 last message repeated 2 times
Feb 6 02:06:29 hostapd: ath0: STA 00:18:de:02:c5:26 WPA: group key handshake completed (WPA)
Feb 6 02:06:35 kernel: pid 1090 (squid), uid 62 inumber 4041 on /var: out of inodes
Feb 6 02:06:38 kernel: pid 27698 (php), uid 0 inumber 5952 on /var: out of inodes
Feb 6 02:06:42 last message repeated 4 times
Feb 6 02:06:42 php: /diag_logs.php: [DEBUG] Lock recursion detected.
Feb 6 02:06:43 kernel: pid 27698 (php), uid 0 inumber 5952 on /var: out of inodes
Feb 6 02:07:29 hostapd: ath0: STA 00:18:de:02:c5:26 WPA: group key handshake completed (WPA)
Feb 6 02:06:47 last message repeated 4 times
Feb 6 02:09:29 last message repeated 2 times
Feb 6 02:19:30 last message repeated 10 times
Feb 6 02:29:30 last message repeated 10 times
Feb 6 02:30:18 kernel: pid 27698 (php), uid 0 inumber 5952 on /var: out of inodes
Feb 6 02:30:22 last message repeated 4 times
Feb 6 02:30:22 php: /diag_logs.php: [DEBUG] Lock recursion detected.
Feb 6 02:30:23 kernel: pid 27698 (php), uid 0 inumber 5952 on /var: out of inodes
Feb 6 02:30:27 last message repeated 4 times
Feb 6 02:30:35 kernel: pid 1090 (squid), uid 62 inumber 4041 on /var: out of inodes
Feb 6 02:31:13 kernel: pid 1090 (squid), uid 62 inumber 4041 on /var: out of inodes
Feb 6 02:31:36 kernel: pid 1090 (squid), uid 62 inumber 4041 on /var: out of inodes
Feb 6 02:32:32 kernel: pid 27698 (php), uid 0 inumber 5952 on /var: out of inodes
Feb 6 02:32:36 last message repeated 4 times
Feb 6 02:32:36 php: /diag_nanobsd.php: [DEBUG] Lock recursion detected.
Feb 6 02:32:38 kernel: pid 27698 (php), uid 0 inumber 5952 on /var: out of inodes
Feb 6 02:32:42 last message repeated 4 times
Feb 6 02:34:07 last message repeated 5 times
Feb 6 02:34:07 php: /status_rrd_graph.php: [DEBUG] Lock recursion detected.
Feb 6 02:34:08 kernel: pid 27698 (php), uid 0 inumber 5952 on /var: out of inodes
Feb 6 02:34:13 last message repeated 4 times
Feb 6 02:34:14 kernel: pid 652 (php), uid 0 inumber 5952 on /var: out of inodes
Feb 6 02:34:18 last message repeated 4 times
Feb 6 02:34:18 php: /status_rrd_graph_img.php: [DEBUG] Lock recursion detected.
Feb 6 02:34:18 last message repeated 4 times
Feb 6 02:34:19 kernel: pid 652 (php), uid 0 inumber 5952 on /var: out of inodes
Feb 6 02:34:23 last message repeated 4 times
Feb 6 02:34:25 kernel: pid 31797 (rrdtool), uid 0 inumber 3968 on /var: out of inodes
Feb 6 02:34:25 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: Opening '/tmp/system-processor.rrd-48h.png' for write: No space left on device
Feb 6 02:34:25 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: Opening '/tmp/system-processor.rrd-6m.png' for write: No space left on device
Feb 6 02:34:25 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: Opening '/tmp/system-processor.rrd-4h.png' for write: No space left on device
Feb 6 02:34:25 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: Opening '/tmp/system-processor.rrd-16h.png' for write: No space left on device
Feb 6 02:34:25 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: Opening '/tmp/system-processor.rrd-32d.png' for write: No space left on device
Feb 6 02:34:26 kernel: pid 27698 (php), uid 0 inumber 5952 on /var: out of inodes
Feb 6 02:34:29 last message repeated 3 times
Feb 6 02:34:29 php: /status_rrd_graph_img.php: [DEBUG] Lock recursion detected.
Feb 6 02:34:30 kernel: pid 27698 (php), uid 0 inumber 5952 on /var: out of inodes
Feb 6 02:34:34 last message repeated 4 times
Feb 6 02:34:35 php: /diag_logs.php: [DEBUG] Lock recursion detected.
Feb 6 02:34:35 kernel: pid 31821 (rrdtool), uid 0 inumber 3968 on /var: out of inodes
Feb 6 02:34:35 php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: Opening '/tmp/system-processor.rrd-16m.png' for write: No space left on device
Feb 6 02:34:37 kernel: pid 657 (php), uid 0 inumber 5952 on /var: out of inodesI can't access the RRD graphs, and the web interface seems slow.
I'm running the Hacom 2GB embedded install (the one with VGA support) Any ideas?
-
You have installed squid on an embedded system with 2GB CF? If so, you probably need to tinker with squid to stop it consuming all the available "hard drive" space.
2GB is plenty of space for basic pfSense but once you add a web cache (especially an untamed web cache) the available space could disappear very quickly.
(On embedded installs the CF is split into two equal sized partitions, one for backup.)
-
On embedded, /var is a memory disk, only about 30MB in size.
You must disable squid's caching if you want to run it on embedded – its useful only for access control and authentication in that context.
If you really want caching, you'll need to manually connect and configure some kind of volatile storage (e.g. external or secondary HDD) and set squid to go there. There have been other threads in the forum that discuss this, but it is unsupported.
