Does startup still freeze on squid3-dev? On my amd64 test machines, it's starting up fine but still not working.

@plang: Thanks a lot! In order to make things clean, is it supposed to be safe to make a backup, remove manually in there everything related to ntop, and restore everything back? Maybe there is a better way to remove these menu entries? I answer my own question: I simply made a backup "without package information", followed by a restore. Works perfect, no "hack" was necessary.

More information please.  ;) What hardware are you using? What modem? What sort of connection? What subnets? Steve

Hmm, you would expect your newer bios to boot more easily.  :- Odd but at least you're up and running anyway. Steve

Hi, welcome!  :) If you're using the laptop as an AP behind your existing router it should be connected to one of the LAN ports on the router. The WAN port connects to whatever device you have for connecting to the internet, cable modem for example. The Latitude D420 appears to have been fitted with several different models of wifi hardware. pfSense has limited support for wifi hardware so it's all important. Do you know what is fitted to yours? Have you already installed pfSense? Steve

I am using the latest version and I can not find the option in the ACPI BIOS and enable AHCI. could you please help me to start to try and tell them how I was

pfSense 2.1-RELEASE (amd64) Status->Services Before squid3-devel (or squid3) installation:   https://www.evernote.com/shard/s1/sh/145ca9e5-4193-49b1-b789-ba408fa05098/d94afdc27ce3d894907cfdfec7a6c28b After squid3-devel installation:   https://www.evernote.com/shard/s1/sh/186aedb1-c24d-4ed8-911d-f4da0da0aef3/64e3cdfc6db9155e0e94d9026af16545

That did it.  :) You guys are awesome, it had to be one of those things that I would've never thought would affect anything, obviously I still have a lot to learn! Thanks gentlemen, your help is much appreciated, I'm sure I'll be back here soon…  ;D

@phil.davis: You have made a "one-armed-router" with just a WAN interface. That is fine if that is what you intended. Hi, Thanks for your advice. pfSense is complete new to me.  This is ONLY a test.  My target is to setup pfSense running on VM of VirtualBox as router for Internal network, without via ISP's router.  eth0 will be connected direct to ISP cable modem, interface being PPPOE. (It works on Host.  I have tested it) Current network: ISP -> Cable modem -> ISP Router -> PC New network: ISP -> Cable modem -> PC eth0 Host can be connected to Cable modem to access ISP with pppoeconf. Please advise; 1) Can pfSense connect ISP modem on the virtual NIC, eth1? Where can I find tutorial to setup pfSense as router for Internal Network? I found following article: How to Setup a pfSense Router http://samkear.com/pfsense/setting-up-a-pfsense-router On a system on the WAN subnet (in 192.168.0.0/24) you should be able to browse to 192.168.0.12 and login. Whether on Host browser and browser on any other VMs of the PC? There is no GUI on the console, just the text menu. Noted.  Thanks Rgds satimis

@lmontinola: @grazzianos: Hey Guys, I had the same problem and received an instruction to edit the file  /usr/local/www/status_openvpn.php, bellow the line with: require_once("shortcuts.inc"); Add this: require_once("service-utils.inc"); This worked for me. Try and report, ok? this worked with me… this also worked for me! thanks!

Oh snap… I'm on the 2.1.0 firmware. Sorry.

Done and done. It looks like I'll have a LOT of poking around to do before I swap out our Fortigate for this FB! Thank you for the assistance, you sir, are much appreciated!

Yes. Look in the virtualisation subforum: https://forum.pfsense.org/index.php/board,37.0.html Steve

Hi Team, Able to install- I reset / reconfigured LSI  raid controller mirror hdd for redundancy.. Thank you.

Please don't set a gateway on LAN or OPT interface unless you want them to act as a WAN. It will just fail. This goes for any LAN type interface.

@stephenw10: Also I know the antenna selection is working because if either are set #2 (or Default or Auto) then the range is reduced dramatically. Well yes, that's how I figured out it has no effect here because no matter what I set nothing improves or gets worse. :D

So what do you see on the dashboard? From your output above I would exepct to see, '5% of 13G'. So your problem is not that you're not seeing a value rather that the root slice is not the filling the drive? Steve

Ok, I figured out the NTP thing.  This post was helpful: https://forum.pfsense.org/index.php?topic=62099.0 I had done two things this morning, renumber the LAN IP range and upgrade from 2.0.1 to 2.1.  Guessing changing the LAN IP range has something to do with this.  I had to go to Services -> NTP then select the LAN interface and hit Save.  NTP working now.

Confirmed the problem .This is really the chipset limitation of which BTX loader is unaware. The workaround solution was to switch SATA into RAID JBOD. Thankfully the mainboard supports this.