This is the working one… <widgets><sequence>system_information-container:col1:show,gateways-container:col1:show,pfBlocker-container:col1:show,interfaces-container:col1:show,log-container:col1:close,captive_portal_status-container:col1:close,carp_status-container:col1:close,cpu_graphs-container:col1:close,gmirror_status-container:col1:close,installed_packages-container:col1:show,interface_statistics-container:col1:close,ipsec-container:col2:close,load_balancer_status-container:col2:close,picture-container:col2:close,rss-container:col2:close,services_status-container:col2:show,openvpn-container:col2:none,wake_on_lan-container:col2:none,snort_alerts-container:col2:show,traffic_graphs-container:col2:show</sequence> <traffic_graphs-config>WAN_graph-config:show,LAN_graph-config:show,DMZ_graph-config:show,MAIL_graph-config:show,WEB_graph-config:show,FORUM_graph-config:show,refreshInterval=1</traffic_graphs-config> <filterlogentries>20</filterlogentries></widgets> This is the one screwing me! <widgets><sequence>system_information-container:col1:show,gateways-container:col1:show,interfaces-container:col1:show,captive_portal_status-container:col1:close,carp_status-container:col1:close,cpu_graphs-container:col1:close,gmirror_status-container:col1:close,installed_packages-container:col1:show,interface_statistics-container:col1:show,ipsec-container:col2:close,load_balancer_status-container:col2:close,log-container:col2:close,picture-container:col2:close,rss-container:col2:close,services_status-container:col2:show,snort_alerts-container:col2:show,traffic_graphs-container:col2:show,openvpn-container:col2:none,wake_on_lan-container:col2:none</sequence> <traffic_graphs-config>WAN_graph-config:show,LAN_graph-config:show,refreshInterval=1</traffic_graphs-config></widgets>

I have disabled it.. its actually got two 3.5" floppy's listed…  I even plugged one in just  to see if I could get by the lockup.. I will take a double look tho.. thanks..

What do you see in the Proxy Filter logs?

It's the extra security… My view is that, if security is so much of a concern, it may be better not to virtualize pfSense at all.  As you may have seen on those "other sites", opinions about virtualizing pfSense (or any firewall) vary a lot. I suggest you try it without the pass-through.

BSD: gzip -dc whatever.img.gz | dd of=/dev/adX or gzip -dc whatever.img.gz | dd of=/dev/adX obs=64k Mac: gzcat whatever.img.gz | dd of=/dev/diskX (Make sure diskX is not mounted and has no mounted slices first) Linux: gunzip -c whatever.img.gz | dd of=/dev/hdX Windows: Use Win32 Disk Imager or Physdiskwrite/PhysGUI, make sure to remove existing partitions in Disk Manager to be sure it's getting a clean write. It should "Just Work" in terms of booting. If it was written correctly, it's up to the BIOS from there. And the USB key can play a part in it. For example, my Soekris net6501 will boot on less than half of my USB sticks, due to quirks in its BIOS when dealing with older sticks.

I have solved my problem by following this article: http://mikepowells.net/tag/pfsense/ Basically, I purchased a CF Micro Drive that allowed me to install the full version on pfsense. I don't know how long the Micro Drive will last so I am building a custom box to replace the ALIX boards. I am using an ITX board with dual NICs and an additions PCI slot for a DMZ if needed. The total cost is $348 which I don't think is to bad. Thanks for all the input. Todd

Personally, I would not bother bridging multiple ethernet ports on my pfSense just to get a few ports in the same LAN subnet. You will probably end up with more LAN devices to connect (WiFi access point, NAS, cabled computers…) than you have ports in your pfSense box anyway, and will have to have a switch anyhow. It is easiest to connect a switch to the single LAN port on the pfSense, and connect everything else to the switch. Then further down the track, if you want to have a separate guest network etc, you can easily use a spare ethernet port on your pfSense to make a separate subnet for guests and so on.

yup i have disable DHCP on dd-wrt and on the advanced routing tab i set it on router (default gateway) on pfsense GUI the WAN connection and the LAN is up

The NTP issue has been discussed in other threads already, complete with a fix.

I have using an Asus M2N32SLI Deluxe with pfSense 2.0.1 AMD64  without any problem…. The 2 "nfe" onboard Gigabit Ethernet adapters was detected without any problem

It's specific to your hardware. Something in your BIOS or Motherboard, to be specific. The 64-bit installer works fine on every bit of hardware, real or virtual, that we've thrown it at. That said, there's not much compelling people to use 64-bit unless they have (and really need) more than 4GB of RAM.

there are more checks there in 2.1

Golden! Indeed the gateway is working but somehow always offline in Status Gateway tab. I assume uplink provider blocks out pings. But after disable state killing, it works for the time being until I fixed the gateway check. Thank you very much for your time, make much more sense now! Really like PFsense.

So it works, you just don't see an entry for it in services? It runs, you can access it, and it shows installed, just no services entry? That's really just a cosmetic thing and doesn't actually mean it isn't doing everything it should be, provided that it's actually running and gathering data. Uninstalling the package and installing it again should fix that. Or try pressing the "xml" button at the end of the row for ntop's package and see if that brings it back.

@wallabybob: Glad you got it working. @CGTroll: Now I'm stuck on VLAN setup. I suggest you start a new topic for that and give a lot more detail. @CGTroll: know of a good tutorial on this subject? :) I have found Wikipedia is often a good place to start looking for more information about a particular topic. You could also look at the pfSense documentation pages at http://doc.pfsensense.org for more specific pfSense information. Will do! Thanks! :)

I've just come across your posting and would like to recommend following, hopefully helpful, links: http://forum.pfsense.org/index.php/topic,53401.msg285331.html#msg285331 http://www.freebsd.org/doc/en/books/handbook/serialconsole-setup.html Peter

False alarm - I removed and replaced the rule that allowed me to ssh from the outside (limited to my networks!) and it works like it used to.

Boot the pfSense CD, then wipe the drives completely from the shell. dd if=/dev/zero of=/dev/ad0 BS=1M dd if=/dev/zero of=/dev/ad1 BS=1M Substitute the actual drive devices for ad0/ad1 (e.g. if they are SATA they could be ad4/ad6, etc), do "ls -l /dev/ad*" to see the drives if they are ATA/SATA, /dev/da* if they are SCSI