I have now reinstalled using the cnet network cards with virtualbox, I have tried using the intel's with no luck.

Then I boot up and find that I can ping out to 192.168.1.1 but i cant ping any of my other network interfaces on the network which is also on the .1 range.

I am really lost, I cant even ping my host mandriva box from PFsens virtual machine not to mention access the web interface of pfsense.

PLEASE Help, I am as you can see desperate for answers ….

Your host's driver is still involved, since it has to for Virtualbox to use the interface. Then Virtualbox is involved and finally the guest (pfSense in this case). If somebody finds an exploit in either the host or Virtualbox that can be exploited remotely then they can bypass pfSense.

It's all about risk management - you have to decide if the risk is worth the benefits. Is the extra complexity over just running IP Tables worth the features that pfSense brings, and the increase in risk?

Looks like it is working. I ended up changing the subnet to 10.0.0.x instead of 192.168.20.x.

Thanks for the help.

after the initial install

using a web browser on the local network  connect to pfsense to finish the install.
the default i/p is 192.168.1.1  ,  login  : admin,  password : pfsense.

also  from the proxmox gui, open a vnc console to check the local i/p address, enable ssh etc..

This is not a VmWare support forum…. ;)

Sorry. Pfsense related issues only.

I am also looking into something similar in order to make my rack at home more green.

You'll need a managed switch and a dedicated NIC in the host box.  VLAN your WAN to the dedicated NIC.

And yeah, security could be an issue.  Do ur homework :)

problem solved

on the wan sides in windows windows services was on

now it works normaly

only the the virtual machine does not start automatically when i reboot pc it stops in workstaion 7

I'm not sure I understand the question.
I've never run pfSense as a VM so I can't comment there but in a full install your wireless interface will be recognised automatically (as long as it's a supported device) and the wireless options will appear in the interfaces section of the gui.
If, however, you are using an external access point connected to via ethernet then why do you want to tell pfSense that it's wifi on the end? What do you hope to gain by doing so?
I would say that a WISP is a very appropriate use of pfSense.  :)
Steve

Catfish,
Here is what I do when running PFSENSE in VM Mode.
I use a dedicated NIC for the WAN and for LAN.  With that in mind. THESE ARE DEDIDICATED ADAPTERS.  I am using a managed switch, I use port 1 and port 2 form the connection from the DSL switch and that is in VLAN 1.  In VLAN 2 I connec the rest of my computers.

You can assign additional adapters up to 16 in 5.6 FP1.  That gives you alot of options.  Depending on the type of switches you have access to you can do alot really cool stuff with it.
RC

so I bought the pfSense book and it has one paragraph about how ACPI can only cause trouble with pfSense and it told how to disable it.

So I did…just for the heck of it.

Excellent! Changing the NICs in the VM to e1000 made all the difference.

I had considered this before but I couldn't change the existing NIC. Not knowing ESXi very well it took me a while to realize I had to add a new NIC in order to have the choice.

I've attached a new screenshot of the graphs during testing to compare for the curious.

Oh, and I'm not sure about the kernel not being SMP. In my system logs it says the following:

kernel: sullrich@FreeBSD_7.2_pfSense_1.2.3_snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.7

pfsenseLowCPU.PNG
pfsenseLowCPU.PNG_thumb

Yes. If you put everything behind a virtual firewall the only MAC they see is the firewall's.

You could still use VirtualBox for that, though why would you want to? There isn't much benefit to running nanobsd inside of a VM.

It doesn't output to VGA, so there is no console output beyond where you saw it "hang"

You can setup a virtual serial port in VirtualBox using a named pipe, and then connect to that pipe with PuTTY. I do that with my development NanoBSD VMs in VMware.

Couldn't you create yourself a backdoor? Like a private VPN just in case you do and make sure you make the rule to access the vpn one of the first rules. Or modify the kernel of the xen server to give you a backdoor on boot similar to this article. http://www.debian-administration.org/articles/579