Not a problem, I can drive there tomorrow. Better to test on this one than units I have in other cities.

An update to 1.2.3 or just updating your bogons list should do it. You should be running 1.2.3 anyhow. I don't recall if this is on 1.2.2, but on 1.2.3 you can do this: /etc/rc.update_bogons.sh now And that should refresh the bogons list.

@bobbob2: And what we'd like to achieve is: Both LANs have Internet Access. In pfSense you three interfaces will initially be called LAN, WAN and OPT1. LAN will default to allow internet access. You can add firewall rules for OPTx interfaces to allow internet access. Neither LAN can see each other. Add firewall rule to the LAN interfaces to block access from OPT1, add firewall rules to OPT1 interface to block access from LAN. Custom NAT / Firewall rules per LAN       - LAN1 is to be highly secure, filtered web access, minimal open ports etc       - LAN2 is to less secure although still protected by the usual Firewall gumph. Custom firewall rules per interface is definitely possible. Not sure what you mean by "custom NAT". LAN1 & LAN2 need different outbound public IP's (e.g. LAN1 has x.x.x.146 and LAN2 and x.x.x.147) I don't know if this is possible. Have you read through some of the tutorials linked to be http://doc.pfsense.org/index.php/Tutorials or any of the documentation linked to by http://doc.pfsense.org/index.php/Main_Page?

You probably have a hardware problem, possibly faulty memory.

Now that helped :)

Unless you are very lucky and have an ISP that can bond circuits for you.  Very pricy :(

i dont see the point in 2 wifi adapters on the same system.  N doesnt offer N ONLY just like G doesnt ONLY do G.  an N adapter will offer both

Satellite yes, at least from what I've seen that's always just an Ethernet connection. Dial up, not yet. 2.0 has the ability to do dial up, it's an active work in progress at the moment.

I wonder how this will end with IPv6 and RFC4193 if there are already confusions with /8, /12, /16 subnets. Where will this end with /48 ~ /64 subnets? :D

There is no (easy) way to manage these from the command line. These are not held in a particular file, but they are part of the main config.xml file. You may be able to edit that file and add them in, but it isn't something you'd want to regularly. There are a few other ways to configure things from the CLI, but they are not optimal. You can use the (included) text browser links to view the web interface (links http://localhost), you could learn the PHP functions to add them via the PHP Developer shell, or you could write a program that adds them on your own. You may be able to accomplish some of the same things by adding items to a pf table from the CLI, but you'd have to look for existing tables to use (e.g. sshlockout)

@nfsiv: the problem is, from outside i can not ping these 4 ip address, and inside i can not ping outside, even i ping from my pfsense. Did you create any firewall rules on the WAN, allowing ICMP to these IPs? How did you test to "ping outside"?

Don't do what you just described. Each VIP needs it's own VHID. Just put another VHID for each VIP. This doesn't affect the functionality. The password isn't used for your setup. This is if you want hardware-failover between multiple pfSenses.

I doubt its a dsl modem problem. I have had a Smoothwall firewall and that modem since 2001. @jimp: Is there another port on the back of your DSL router that you can try? No. There is only a single Lan and single Wan connection. I intend to get another dsl connection and wanted a firewall that was better suited for dual wan connections. The only problem I have had with the smoothwall is after about 6 months, it starts to block outbound connections its not supposed to. For instance, I cannot connect the PS3 to the playstation network anymore. Another example, is my daughters WOW, it worked fine for months, and now it will not connect through the smoothwall. If I were to reinstall the smoothwall, then everything would be fine, but I am tired of having to reinstall it every 6 months or so and spend the hours reconfiguring all the firewall rules.  I have two boxes with smoothwall on it so when one is down, I can use the last one until the new one is ready. I need to have a backup one ready to bring online because I host several websites and services. That is another reason I am looking for a more robust and secure firewall. Those websites are prone to attack by spammers because they are used to supply evidence to registrars, LE and ISP's to get sites and IP's shut down.

Store your pages in /conf/ <somewhere>as long as they are not too large, then add a shellcmd to the config to copy them over to the proper place if they do not yet exist (or on every boot just to be safe)</somewhere>

The book covers all that and more http://www.amazon.com/gp/product/0979034280?ie=UTF8&tag=pfsense-20&linkCode=as2&camp=1789&creative=9325&creativeASIN=0979034280

Well, port that pfsense was plugged into need to be in trunk mode. From there it was a matter of taking it step by step. Initially we couldnt get any subnet to communicate with the pfsense box. We had to actually add the subnets to the lan interface. Once we could get vlans to communicate with pfsense it was just a matter of figuring out NAT. NOTE: Automatic NAT does not work/would not work in our situation. Has to manually do it.         1:1 NAT also would not work had to stick with NAT port forwarding. Things are good now, internally geting out we have noticed a 50% increase in speeds.