Do you have "Block private networks" or "Block bogon networks" set on your WAN interface?

There is no documentation for this.  Read the builder scripts source code and if this is not an option consider purchasing a reseller agreement from https://portal.pfsense.org/index.php/reseller-subscription

pfSense 1.2.3 only supports PPPoE on WAN. The 2.0 beta can do as many PPPoE interfaces as you like. If you must use 1.2.3, you can put some kind of small NAT device in between pfSense and the modem, or if you have a modem/router, see if it can handle the PPPoE login portion (often called a half-bridge).

You can use tcpdump on the physical interface which will grab the information you need.  If you want, you can easily capture this data in binary format and then feed it to an instance of Wireshark running on a separate machine for extra prettiness.

Old (overblown) news, there is already at least one other thread on the matter.

Thanks for your help. I will try this tomorrow and will post the result.

You can check the inode usage from the shell with "df -i" You might also want to have a look at this thread I started for a similar issue: http://forum.pfsense.org/index.php/topic,26626.0.html

IIRC others have solve similar problems with a cronjob "/sbin/dhclient vr1"

From the physical console, reset the password.

Really simple introductory would be the Head First Networking (an O'Reilley) Then maybe CBT Nuggets Jeremy Ciaora CCNA ICND1 (video lectures, very good and entertaining, not dry!)

I (and quite a few other people) have had real problems with those Realtek NICs. Nasty st-st-stuu-uu-uuttering action if you get my meaning. AS someone else said  "They give new meaning to the term 'low end' " Everyone recommends the Intel 1000's and so do I.

well that is weird.  it sure sounds like the dhcp server is not running.  what does DHCP look like on the Status page?  If you try and fail to get an IP and set one manually, try looking at the firewall system logs to see if any error messages shed light.

I am not sure if mortified is the correct word but basically I did not Auto fill from NAT and my firewall rule was pointing to incorrect IP address ….. It works like a charm when it is set correctly !! ;D

Routing between the three LANs will happen automatically if this router is the gateway for each network. You can setup those firewall rules you describe with minimal effort. The other actions would be handled by the load balancing tutorial, with maybe the exception of FTP. If you need to use the FTP proxy, the interface for the FTP traffic must be WAN. The FTP proxy in 1.2.x isn't really compatible with Multi-WAN.