Try setting your harddisk in PIO4 mode if you still recive this message check your RAM.

There might be an edge case where might need to change the allocated memory to kernel vs. user base. What version of pfSense is this?

You need at least 2 interfaces (WAN and LAN) but you can have as many interfaces as your hardware supports basically with multiple LANs or WANs.

You only have to follow this simple guide: Rules are applied on incoming traffic only so if you want to do outbound balancing to multiple WANs the traffic is coming in on the LAN and leaving on the WANs/OPTs. Your rules have to go to the LAN tab therefor. And also have a look at the tutorials and docs. They should get you started quickly.

Assuming you have the full install then "pkg_add -r zoneinfo" (from the command line) should do it.

Great to hear that. Good progress has been made on the traffic shaper. Now can we put together a bounty to extend captve port to be multi-wan and multiple interface?

128 MB of RAM is the minimum supported.  If you ever plan on adding any packages you'll want to add more RAM.

I'd go with rsync over SSH.  Rsync will allow you to keep the webserver updated with changes on the fileserver and as you should be using SSH to admin it anyway you're not opening up any new holes.

Oke , sensei Ullrich

Thanks a lot

Doesn't matter if it's in the GUI for me, personally.  If the support was there, I was just going to modify /etc/inc/interfaces.inc to add the lines.  No big deal.

After posting the last reply, I saw what was wrong, LAN is now on 192.168.10.1 and it all works. So much for late nights! Thanks, ~Lawrence

Either go to:  https://<pfsense-ip>/status.php#sysctl%20hw.physmem
or install the phpsysinfo package if you're not on embedded installs.</pfsense-ip>

@MTHead:

Please please PLEASE tell me you mean "switch", not "hub"!

…or just a 24/48-port bridge.  ::)

thanks for the info.
It's very helpful

i've the same problem.

1 rc4
pool.ntp.org
time zone: -5

Doum

Generally the WAN port will have a real ip and so any packets with private ip addresses will be unwanted (forged/part of attack etc) so by default all rfc1918 packets should be blocked.

I totally second what Scott wrote.

Having posted a similar statement in the past myself gave a reply in which someone suggested to pick another theme when using IE.
In  System: General Setup  use the theme: pfSense  if you have to work with IE.

Do this from a shell

fetch -o /usr/bin/telnet http://www.pfsense.com/~sullrich/extra/telnet
chmod a+rx /usr/bin/telnet