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?

Make sure you have installed pfSense to the HDD and that you are not booting from the CD/ISO.

thanks for the info. fixed the VMXNET 3 and PPTP is working BUT TRAFIC SAHPER ALTQ is not recognizing my network adapters…. how can i fix it ? i'm using pfsense 2.1 with esxi 5.5 thanks in advance [image: Capture.jpg]

Dude look at your traceroute Tracing route to cnn-56m.gslb.vgtf.ney [157.166.249.11] over a maximum of 30 hops: 1      <1 ms <1 ms <1 ms 192.168.1.1 2      *          *        *        Request time out 3      *          *        192.168.1.1    reports: Destination host unreachable. 3      *          *        192.168.1.1    reports: Destination host unreachable. You must have gateway set to itself on your lan?  Lan interface should NEVER have a gateway set on the interface.  If you have downstream networks that you need to access via your lan interface, then you would create a gateway and route to these networks.. But you would NOT assign the gateway to the lan interface directly on the interface settings. This makes pfsense think its a WAN sort of interface, and could enable NAT, etc.  All kinds of BAD things happen if you do this and yeah not going to work. You hit pfsense 192.168.1.1 – but then hop 3 192.168.1.1 says sorry can not talk to that host.  This is clearly not right and points to you having a gateway set on the interface to me.

I have found the erorr/ I am not able to configure my pfsbox with my lease-line internet!

hi jimp, I need help on clearing out the WAN configuration in my web GUI. I can no longer access the GUI page itself. It is not that I dont know my log in credential but the webGUI doesnt load at all. I don.t know why. I already tried to disconnect th WAN connection from the router but still i cant access the GUI page via LAN IP. This problem started when I decided to configure the pfbox WAN interface as static. When I saved the configuration, there I can no longer launch and access the GUI page.

I see. Thanks alot jimp! I never thought I had to select freebsd-64.

It's a relief knowing that its not really an attack. l'll post the dhcp logs.

Thanks for your answer. It's work fine. Now for testing purpose but I want to move for production. I have this problem to resolve. I have only a not good wifi connection and I want to subscribe a second wifi connection to create a load balancing and a fault tolerance. If is possible a want to create a binding connection but I read that is no possible with pfsense actually.

@kijianshi – Yeah I did already actually I am trying the fresh installation from 203 and/or 2.1 but am having a "cp downt suport long mode" error. Dont know what to do. I have created a new thread for the error.

And what network does pfsense get on its wan inteface?  Lets say it was 192.168.1.0/24 and you are using 192.168.1.0/24 on pfsense lan – then yeah that is not going to work.. You need to use a different network on the pfsense lan then pfsense has on its wan.