check this:

The "Realtek PCIe GBE Family Controller" NIC can be configured to not strip the vlan tags, by going to the Adapter Settings and setting "Priority & VLAN" to "Priority & VLAN disabled"

Do you have virtual switch in hyper-v?

You have to assign static address in virtualPfSense, within same network, your LAN is configured.

pfSense
192.168.1.1

Hyper-v
192.168.1.2

pfSenseVirtual
192.168.1.3

If you want more specifig answer you have to describe you network more specific (vlans etc).

t1.micro isn't going to happen, Amazon won't let it.

May be you should try virtio drivers instead of sr-iov?

Thank you very much.  Just after I posted this, I found instructions telling me to run
setenv PACKAGESITE ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/amd64/packages-8.3-release/Latest/

at which point I followed the instructions on the original instructions and everything installed.  Thank you very much for the answer!

/random when i rebooted, I'd told vmware to conenct my VMXNET3 adaptors, and to NOT connect my E1000 adaptors - instead it connected the E1000, so I shut down, removed the E1000's, and booted back up with JUST the vmxnet3's connected and it worked.  in case anyone else tries to do what I did and hedge their bets by having both adaptor types installed at the same time :)

I've been using a few hundreds at a time.
Managing/creating these was the biggest task.
In the end i created an excelsheet in openoffice, exported it to csv, parsed it with a shellscript and generated the parts of the config i needed.
After that i didn't bother with the GUI anymore because it wasn't really useable anymore, but always edited the config directly.
But then, this was on a quilte old version. Not sure how the GUI behaves today in such a setup.

@KOM:

As a workaround, you could create a second larger vdk and then using cloning utility to copy the logical sectors from your old disk to the new disk.  I haven't tried it, but it may be an easier solution if you happen to have a copy of Acronis (or equivalent) laying around.

"problem" is only that it must support UFS filesystems…
For instance www.gparted.org ISO image has no such support (it can only copy/move but no resize and in my case he also didn't recognize the created partition table by pfSense) ;)

=> therefore my suggestion for this option.

Myself I have tested the mentioned solution in my first post successfully.
It's only a "nice to have" as common task for all pfSense users.

not by itself, but can be implemented in some way.
Thanks for your support. I will try to gather the informations for a bugreport.

Yeah I don't think so - when would that rule even be used.  Why would clients talk to their gateway to talk to devices on their own segment?  That rule would never see any packets.

ok, i will install it, in the future i will check in this forum if there are some news, ok?

Tnx kom and BBcan177, it was a pleasure

Regards

Alex

The equipment I'm using as stated above is a Proliant DL360 G4p.  the highest ESXi version is can run is 4.1u3.

I seem to recall that can be worked around by disabling checksum offloading (System > Advanced, Networking tab)

Hoping for beta in a few weeks, release maybe by September if we can swing it.

"vmxnet on 8.3 just doesn't work with jumbo frames"

Looks to be working to me - what driver did you test with?  I don't really see a need for jumbo in my home network.  It would just complicate the connections and not all devices support them.  I could always segment out even more and put my non jumbo on their own segment, etc.  Seems kind of pointless for what I am doing.

As you can see from thread I was able to ping at the full mtu - but be happy to do some other testing to validate its working.

@cmb:

A jail isn't viable for a full-blown OS. Our kernel isn't the same as FreeBSD's. It's not very practical to run our kernel on a stock FreeBSD. Bhyve is a vastly better solution than jails for what you're looking to do.

Except Bhyve doesn't support early Nehalem's implementation of EPT (also on some Atom processors) and has a low priority for a fix. (I did try Bhyve with various workarounds, but couldn't get it to stop kernel panicking even before I did anything with it.)

Don't use the Realtek NICs in XenServer guests, they're known to do that. Switch to e1000 and that should go away.

Ah, I remember months ago there was debate about whether or not to base 2.2 on FreeBSD 10 or stick with 9.  I didn't know that 10 was settled.  Still, it will take some time for 2.2 to be released.