i beleive you might find this is an mtu issue with vmware on vlan interfaces have had it happen to our selves as well
On Fri, 2007-03-09 at 19:16 +0100, Joseph Favia Jr. wrote: > Hi, > > This worked fine when I was using a switch with no VLAN configuration , > but as soon as we defined VLANs on the switch, it seems that the PFSense > machine has lost contact with all other machines, both virtual and > physical. Are the VLANs defined at the switch level transparent to the > virtual interfaces of the PFSENSE virtual machine? I mean I simply > define 4 interfaces on my virtual machine (although I only have one > physical interface) as if there were no VLANs. It should be VMWare who > does the mapping between my virtual interfaces and my VLANs, right? At > the VMWare level I've defined a virtual switch and the virtual networks > with a VLAN tag, which is also used on the Cisco switch. Other virtual > machines are working fine with the VLANs, but not my PFSENSE VMs... > > Any ideas? > > thanks > > Joe > > > Scott Ullrich wrote: > > If you are trying to setup a CARP cluster using pfSense + ESX, please > > see the following VMWARE thread: > > > > http://www.vmware.com/community/thread.jspa?messageID=576885 > > > > In a nutshell, you need to enable promiscuous mode on each of the > > connected vswitch's. > > > > Hope this helps someone in the future, it just helped me!! > > > > Scott > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
