thanks guys will give it a bash and see how I get on !

So after a bit more research, it looks like ESXi is responsible for determining which PCI bus # a given device gets added to…and there seems to be no specific way to configure it from ESXi-land.

FreeBSD (and pfSense) are behaving as designed, so no fault there.

It looks like what I would have to do is:

Develop a manual script to create a mapping of interface names and roles (e.g. "external", "intrasite", etc., arbitrary definitions) to MAC addresses (similar to /etc/network/interfaces in Linux);

Run the script once I've got a configuration ready for production;

Develop an rc script that runs at each boot that a) checks to see that the mapping is as originally set; b) renames interfaces if their PCI bus order changes (and reapplies any other configurations as needed); and c) calls the "Assign Interfaces" function if all of the MACs have changed; and

Make all this scripting something that can be transitioned to other *BSD-based systems (for example, the next upgrade of pfSense).

This, of course, in my Copious Spare TimeTM.

So, not an issue with pfSense or FreeBSD per se…but one that I'll have to work out how to handle from within FreeBSD in order to ensure a consistent configuration template that I don't have to re-work for each potential instance.

Biggsy: thank you for your input on the issue; you stimulated much research and learning.

--
Troy

I've encountered a fatal trap 12 with a pfsense kernel running under xen.

You need to provide the trace information (at the db> prompt, just type "trace" and hit enter), to see what was on the call stack at the time it trapped the fatal error.

That will tell you which function threw the error, and be the first step to finding a solution.  Here's the thread for my fatal trap 12 - different circumstances and thus likely a different problem, but it has an example of the debug trace.

https://forum.pfsense.org/index.php/topic,69546.0.html

1. Please post your ipconfig and ifconfig maybe edit out your WAN?

2. Can you ping anything else on the LAN from pFsense?

3. Are you really sure that your are on the same virtual network?

Thanks alot!

Here's another problem.

While waiting for a reply on my previous issue, I turned off my box alread. Just now, when I am abot to implement your solution, ran the vbox (as pfs nanobsd is running in vbox) and the pfs can't obtain connection from bridged WAN. I bridged it to the laptops broadcom wireless. Nevertheless, I unchecked the box, based on your solution, restarte the vbox, and the console no longer show any WAN, it just shows WAM > em0 > (blank)

did I missed something?

my laptop is connected via wifi.

@akshay:

Hi all ,

I am new to "Pfsense" i have read and truing to install on hyper-v guest with legacy network card but its not working its always gives same error "no link-up detected". i cant understand can any one help me on this.

Also can Pfsense able to block HTTPS websites with wildcard like [ / , . ].

Use image from this https://forum.pfsense.org/index.php/topic,56565.msg364122.html#msg364122 post
Up and running well with syntetic network. Not legacy.

Check this out maybe:
http://timita.org/wordpress/2011/07/29/protect-your-windows-laptop-with-pfsense-and-virtualbox-part-1-preamble/

so keep your WAN of pfsense bridged to the NIC that is connected to your ISP

but then create an internal vSwitch that is bonded to your secondary NIC

then point your LAN interface of pfsense to that vSwitch

then also point your webserver VM to that same internal vSwitch

and that will put your server "under" or "behind" the virtual firewall as well as other devices on your physical network if you plug that secondary NIC into your internal physical switch

VLAN 4095 in ESXi is "All VLANs" tagged.

Cheers nice one! Appreciate your response! As always! Maybe one day ill be good as you. I slept on it and woke with a brain wave that worked. It was actually my Layer 2 switch causing the issues with vlans. The Default Vlan "1" all ports were not configured. So i just set the Vmware nics in untagged in 1 vlan and bingo! Job done

If anyone gets stuck give me a shout! I got there in the end! I recommend sleep! and then go back to it.

check and set the right DEFAULT GATEWAY, this caused often to me after set up the right GW, networking was running, mostly wrong bridge configuration.

route show

or

netstat -r

are your friends

regards
ren22

Okay, thanks again! Thread solved.

That is where the update check text goes, so it's possible it is failing to pull the update check page from our servers properly. If it works on the primary and not the secondary, there must be something different in their network settings that prevents one from getting out.

I have a how to in my signature for Xen 4.3. I will try to adapt it for XenServer and see how it goes.

any time frame for citrix xenserver pv support? as I can find vyatta router is the only one is xen aware.
I did some testing beween pv nic drivers and can see big difference.  vyatta shows 700mb upload/download with pv nic drivers compare to hvm pfsense 100mb upload/download. when pfsense start supporting free xenserver platoform you will get more customers.
also you may rise donation for this feature and I am sure you will get certain amounts.

I don't think vmware accounts for such a setup.  You can clearly assign more than 1 physical nic to a vswitch.. But they would be used in teaming/failover/etc. sort of situation.  I don't think you can just use them like physical ports on a switch and connect specific hosts that are on the same network.

Let me do a little digging and play with my setup, I am currently running esxi 5.5 as well and have multiple physical nics on the host I can play with.

edit:  So a read of this
http://www.vmware.com/files/pdf/virtual_networking_concepts.pdf

I really don't see how you can do what your after - the connection of physical nics to a vswitch is not meant to be like ports on a normal switch.  They are used for teaming or load balancing or failover.

you might be able to setup a load balance and then use route based on ip hash, both source and destination IP..  But I think your going to run into problems.

What you could do is create 4 vswitches, with each switch connected to a physical nic and then in pfsense with 4 vnics 1 each connected to each switch and then bridge these vnics in pfsense.. But don't think would be a great performer?