Just solved the issue. Turned out to be bound to virtio drivers.
Setting the NICs to e1000 solved the issue.
Lost some settings in the switch, like NAT rules (but not their firewall rule) and DHCP scope, etc. While other settings remained intact.

I was able to get it working by using virtual guest tagging basically I'm using the 802.1q driver inside of Pfsense. Also by doing this I basically removed the vswitch from the picture. However, this weekend I plan on trying to make it work via virtual switch tagging.

Download the iso from one of the mirrors of pfsense official site for example this one http://pfsense.foofus.com:81/downloads/pfSense-LiveCD-2.1-RELEASE-i386.iso.gz

Create a new virtual machine and give it the extracted iso as the installer disc , customize hardware and add 2 NICs

the installation is dead-simple , take a look at youtube http://goo.gl/EWKMQK

Here is the solution i followed…

http://serverfault.com/questions/353223/recommended-way-to-setup-a-secure-esxi-environment-with-a-publicly-accessible-ra/353242#353242

I followed steps 1-5

Here is how to configure openvp

Youtube Video

@biggsy:

Did you enable promiscuous mode on the vSwitch and permit forged transmits and MAC address changes?

I haven't had the need to do it but I think that's what's needed.

Please suggest me how to permit forged transmits and MAC address.

Input 3072 to that blank.

My memory usage has decreased from 90% to 88%, so my settings are working.  It maxed at 90% before purging cache.

90% utilization is good enough for me.

Because you have more ram than me, you may later need to adjust up or down slightly on the HDD cache.  Keep an eye on it.

I have resolve the issue.

What happened is that, due to imperfection yet of technology, I had to totally detach the livecd, although it has been released already after the first installation. Had my PC reset and boom! It fixed it's own.

I have run 2.1 all through its development and after final in esxi 5.0 and 5.1 and never any issues.  Now even on 5.5 without one problem related to it being a VM.

I have not updated anything from the default for time settings.. My esxi host runs ntp server that syncs to internet - and all my vms and physical use it to sync time.

I don't believe the vmtools you have installed even work Open-VM-Tools-8.8.1, use the 8.7 version.

^ dude read the freaking thread!! before you post and make yourself look - too late ;)

pfSense 2.1 RELEASE under Hyper-V 2008R2

setting

http://knowledge.zomers.eu/pfsense/Pages/Install-pfSense-on-Windows-2008-Hyper-V-server.aspx

ifconfig de0 down
ifconfig de0 up
ifconfig de1 down
ifconfig de1 up
dhclient de0

script
/usr/local/etc/rc.d/interfaces.sh

executed at boot, but does not work, we have to start it manually …

after obtain

....
DHCPACK from (Gateway provider)
bound to XX.XX.XX.XX (issued ip) -- renewal in 300 seconds

every 5 min. is updated by DHCP from the ISP connection and falls off to re-launch /usr/local/etc/rc.d/interfaces.sh

how to overcome it or remove renewal in 300 seconds?

thank's a lot

Interesting idea gi-minni

Have you also looked at VMware NSX?

what do you think your solution would bring to the table over integrating the router/firewall directly into the Hypervisor level?

maybe you could also look at using pfSense + the vmware API for layer 3+ features from pfSense and turn pfSense into a awesome competitor for the juniper and arista networks gear.

most of the NSX is based on Nicira's Open vSwitch so here's hoping for compatibility :)

Don't assign the same subnet for each nic.  Configure a BRIDGE in your interfaces section.  That bridge should give you in the end, ONE interface to assign an IP to.  That is how you would manage the box.

Yes, I presently have any to any passing all.

first hello to all :-)
i'am new here.

ok, i have an working pfsense as router/firewall and a debian installation as client on virtual box.
both NICs are configured with static addresses in pfsense (lan and wan and just ip4 network).

setup values:
first ethernet adapter is the NAT (select him as first NIC).
second ethernet adapter is Host-Only (allow access for vms and host).

pfsense config (i didn't use dhcp and configured both nics with static ips)

wan config: ip is 10.0.2.15/16, gateway 10.0.2.2, dns 10.0.2.3 and 192.168.*.1 (my physical router outside virtualbox u have to choose your router ip etc…)

lan config: ips is 192.168.1.1/24

and it workes fine.

a nice day for all
mahadev

The host in question has some 256GB, I asked one of the VM admins to to set me up a test machine to use and this is what I got  ;D  once I have spent some time working out the configuration I will be looking to reduce the memory and storage.  I might be looking to see at least 8/10GB as we have a requirement for keeping web access logs

Hi,

I haven't much time to simulate the lesson on the wiki but I have printed for my keep. I have attached the expanded storage, then erased the previous saved cached files.

This are my observation:

In just the whole day it filled my storage up to 85%. This is the status 4 hrs ago. Now I checked and it became 83%, I don't know what it means. But it seems to me it auto grows as it fills the storage. I have allocated 100G as you advice and put a cache cap of 40G. So I'm still observing.

Anyway, I have 2 another question as attached.

Image 1 refers to the WAN traffic but I'm not really sure how to interpret it. Also with image 2, the LAN traffic. How to interpret those data?

WAN.jpg
WAN.jpg_thumb
LAN.jpg
LAN.jpg_thumb

I read the chapter 6 of the VirtualBox Manual and played with the different network configuation. I found that in Internal Networking, my Linux VM would report "The Network Connection has been disconnected". In Host-Only, the connexion does establish itself in the VM but the web is not accessible and the Host (Windows) lose the connexion too. Maybe there is a conflict between the Bridge and the Host-Only network adapter.

From the documentation of VirtualBox :
"Internal Networking is similar to bridged networking in that the VM can directly communicate with the outside world. However, the "outside world" is limited to other VMs on the same host which connect to the same internal network."

Since my pfSense VM does access the internet, does the rule still apply?
smcclos - You say you did a setup like this, how did you proceed exactly?

Thank in advance.