@Pootle:

@abiscula:

Regarding pass through, have you used any unsupported card? Have you ever tested it with a fast ethernet card?

Not sure what you mean by fast - I'm using a couple of realtek gigabit cards passed through, it's not easy to find a pci-x NIC that isn't supported in ubuntu…

I'm really interested in this setup but before replacing my processor with a vt-d one I need to make sure fast ethernet old PCI cards are supported by VmDirectPath (Pass through)

Given the IO is passed through, I don't think that the card is particularly relevant.  I'm running with pci-x cards.  You could potentially use pci cards, but the pass through capability will pass through all the pci cards (or none of them). I've never tried pci pass through - only pci-x.

Remember that the motherboard has to be IOMMU capable as well…

Working with an intel DP67BA just need to get a new processors since I did not know core i3s do not support VT-D.

Sorry then i misread someparts, (almost half of your post)
There have been some updates, when something small is broke for a day or so. after upgrade everything works well

Alternately, from the console shell, run:

pfSsh.php playback enableallowallwan

And then get in from the WAN side. Before you do anything else, setup a proper WAN rule to let you and only you into the GUI from WAN, and then remove the allow all rule that the above command added.

Are you running pfSense in a VM - if so which one?

Can you post a screenshot of the LAN rules? What packages do you have installed?

Oh, sure.  Hot snaps.  I've done that too (when upgrading my ubuntu server).  I don't bother in the pfsense case, since the firmware upgrade requires a reboot anyway, and a hot snap is a lot slower (at least given that I have 1GB RAM that it needs to snapshot), versus the cold snap which is 1-2 seconds tops.

So nobody has tried to use Virtual network adapters for PFSense?

edit
Figured it out. First, set the host adapter to manual IP of 172.16.0.1, Subnet of 255.255.255.0, gateway of 0.0.0.0. Use VMnet2, not 10 or higher. I'm not sure which of these changes made things work, but it does work.

To get sticked I think there is some work to be done by other member. I fell alone with this topic so I give up for the moment (other things to do like my wedding for example).

I think the best way is to use the appliance part of pfSense build tools, we also need a lot of patches from last kernel and xen devices (the xn network device for example that need some improvement if we need to manage VLAN inside pfSense or QOS with bandwidth tweaks).

Feel free to try and Improve the receipe, if this topic is moving on, I will do my best to continue my work.

@ciela2:

Everyone should be aware that the VMware Player installation is often missing a critical file called vmnetcfg.exe. If you don't have this file, advice about configuring your virtual interfaces won't even make sense to you–it didn't to me anyway. I found instructions for retrieving this file at the following web site:

http://superuser.com/questions/187767/why-vmware-player-3-1-1-missing-the-vmnetcfg-exe-utility-and-where-to-get-it

Thanks so much for saving me much frustration.

When you bridge, only one interface gets an IP address in the same subnet.

I had thought on 1.2.3 we had a little hack that let you put in "none" for the IP, haven't tried it in a while though. You can always put in an IP from another subnet, it doesn't matter, it shouldn't get used. So long as it's an IP in another subnet it should behave.

@Zeon:

Hey guys,
Just an update on this, after speaking with PFsense support they suggested I look at the dupelx settings on our switch where the WAN comes in. Sure enough the port was only auto-negotiating at half duplex. After setting this to forced 100mbps full-duplex and installing open-vm-tools everything is working a treat :)

Thanks for feedback!

I am using VMware Player - not workstation, maybe that's why these answers don't make sense to me. Can someone explain the connection between pfSense IP addresses, VMware IP addresses, and Host Computer IP addresses?

I'm sure I'm missing something obvious.
Thanks

as i mentioned above, i use vmware workstation first.
now i shifted to virtualbox coz it would not eat much on my host pc ram…^^

windows xp sp3 32bit
virtualbox 4.0.8
pfsense 2.0 RC3 + lusca cache

Andy,

Thanks very much for the detailed response. I've tried the chmod +x and it looks like it has worked. It still takes a while to boot pausing at "Configuring WAN interface" and at "Starting OpenNTP time client" but at least once it starts it works!

Yes, I'm pretty sure that the underlying issue is that there is limited OS support in Hyper-V. I'm no expert in this but I think that MS is using a type of virtualization that works best when there is operating system support. I've not had problems with pfSense on ESXi or VirtualBox to name two competitors, but there are reasons beyond pfSense why Hyper-V makes best sense for me.

Thanks again.

Richard

I am a home user with a 15Mb down 1Mb up plan from my ISP, so unless I misread Mbits as Kbits my reply might not be too helpful.  However I have a near identical setup to yours, W2K8R2 with PFSense & Debian Web Host running in VMWare Server, I have experienced no slowdowns in internet speeds, and local speeds appear to be the same as before.

Hi RC,

Thanks for the bump, I forgot that I posted this. What I ended up doing was trying the exact same installation on Xen 5.6, and it worked the way I expected it to.  (ie. Able to have multiple interfaces and ping out, etc.)

I suspect there was something wrong with the virtual interface or interface drivers when running on Xen 5.5.

Since I've got it working, I don't think any further troubleshooting is necessary.  Thanks for the response :)

ang -

even without the link state information, pfsense still performs without too many issues

Setup untangle in transparent mode when your doing the install.
Example of the switch setup:

vswitch0 - WAN
WAN <-> pfSense WAN

vswitch1 - Internal Router
pfSense LAN <-> untangle WAN (In transpartent mode, you give it a static IP for your LAN)

vswitch2 - LAN
untangle internal (LAN)  (No IP since its bridge to the WAN interface)

Accept promiscuous mode needs to be allowed on the interfaces with untangle. I believe both need it but its been away.

I've tried this setup on EXSi and it was really slow when untangle was put into the mix but i was running this on an Atom d510.. Been meaning to try this on a XenServer to see if it improves..