@anthonysawah: Hey everybody! I'm looking to setup pfsense on a virtual machine on my laptop… Can I do that with workstation? Yes, though you may not get great performance. Your laptop may not support any virtualisation pass-through features. @anthonysawah: I also already do have a home router thats connected to the modem. Can I still use pfsense without directly connecting to the modem? Yes, though you will be double NATing. It's better to have a public IP on the pfSense WAN interface if you can. Steve

Hi Pete and Steve, Thanks for your replies.  I will give DiffProbe a gander when I have a chance.  Thanks for the tip about that.  I've also mentioned it to my buddy who is much better educated on networking. We will let you know if it tells us anything. Unfortunately, I spent the better part of last weekend trying to get a StrongVPN client working.  So far, no luck.  Had to do a complete factory reset at one point, started over and tried all the various tutorials in the forum as well as links to other directions.  I'll post in the existing thread on that topic.  If you guys may be of help, I'd appreciate the input. @ Steve, I was able to get Amahi working.  I successfully turned off DHCP server on the pfSense box and gave that job to the Amahi box. Thanks again guys for sharing the wisdom! DW

No. It should only go back to the configure interfaces screen at the console if it can't find a valid config.xml file. That can happen if the config file is lost for some reason or if it contains a reference to a NIC that is no longer in the system. It also happens if you boot from the install media instead of the HD. Steve

Like I say I went for the V120 for that exact reason. If your WAN interface is a PPPoE connection and you're seeing the green arrow it must be doing something. Check the PPP logs. Steve

@CandSNetworking: OK… I have some 4GB cards on the way.  If I may re-ask the question, would my previously mentioned upgrade procedure work? or... would it be easier to migrate the existing image to the new card using the supposedly non supported image migration to larger card method? I would hope that since I'm already on 2.1 that I could simply just put 2.1.3 on the new cards and then boot to them and restore my config.  I can reinstall the few custom packages like BlinkLED by hand... no worries there.  Had to install it to begin with. Any additional advice is greatly appreciated. Sky Migrating to a larger card is easy.  Just install to the new 4GB card as you originally did to the 512MB and then restore your config.xml.

So it dropped you at the mountroot> prompt? Give it the correct location for root and then edit the fstab accordingly. Steve

Thanks for all the help.

I hit the same problem when booting on a Geode system with 512M ram. I was able to select option 2 on boot to disable APC to get it to finish booting. I have this weird problem though where I can't access the webconfigurator after restarting it and even after reboots…... :'(

I have a Cisco PIX of some model or other, I forget which, think it's about 3 or 4 rack units tall to which I added a hard drive, a new MB, a couple gig of RAM, a P4, a couple gig NICs (and a fiber gig NIC as well), a new PS that supported the extra power connectors the P4 needs, and an extra fan or two. So it looked like a PIX until you took off the case or connected to the console and saw it was pfSense. I never actually put it into use, as I wanted to button it up a bit neater inside, but just never got around to it. Mostly did it just to do it. It makes for a fairly nice pfSense box, but I just bought a WatchGuard XTM5 (running pfSense of course) that I'll be putting into place when we move to the new house just because it's a bit more powerful and looks a lot prettier. And it only takes up 1u which is nice when you're using a small wall rack.

Yes, it would.  ;) They are normally listed in the man page of whatever is generating them as either loader variables or sysctls. Many are tough to find though especially if it's something in the kernel for example. Steve

Hmm, yes, I'm pretty sure you need AHCI for trim to work correctly.  :-\ Steve

I'm just thinking loud. You can use a script that checks if the anti-lockout rule exists or not and add it manually if not and run this script every hour or day using cron package

You're doing the right procedure, and that's how I've installed to mine and it works OK. Make sure your terminal program properly supports the methods the installer is using to draw the menu. PuTTY should work, as should most any *nix/MAC terminal. Hyperterminal may not.

any one can help please  :(

I'm happy to take the credit - when you do all the work…... ;)

And nevermind…I forgot my helmet and crayons yesterday!

The extra 4 NICs are more like a layer 3 switch than a quad NIC card. As such it will be veery difficult to control them from pfSense. It might theoretically be possible if you were able to determine how Watchguard's OS talks to the card but it would be hard. The card appears as a networking device in pciconf and that initially makes you think it's a network card of some sort that might be recognisable by a standard FreeBSD driver given the correct PCI IDs however there isn't a NIC chip on the card that we might reasonably talk to. If we were able to talk to the card how is the Rapidstream chip controlled? If we're very lucky it might be via telnet or some simple protocol but it might just as likely be directly via the PCI slot using completely proprietary coding. Looking in the Watchguard firmware might reveal some clues but it's likely all the stuff to talk to the card will be binary blobs. Steve

I install pfSense on Dell R210's all the time - usually have to disable the onboard Broadcom NICs during install and then re-enable them after I've added the following lines to the /boot/loader.conf.local file kern.ipc.nmbclusters="131072" hw.bce.tso_enable="0" hw.pci.enable_msix="0" -ct