It works, but performance is, in my experience, poor. Don't use trunking (802.3ad / LACP) and VLANs together, or inter-vlan routing slows down drastically. This appears to be a VMWare problem, not a pfSense problem. I recommend creating one virtual Ethernet device per network, and in fact mapping each virtual switch (or vlan) to a physical NIC on the host. Basically, keep the networking as simple as possible, don't get fancy like I did. -Adam Thompson athom...@athompso.net
> -----Original Message----- > From: Eugen Leitl [mailto:eu...@leitl.org] > Sent: Saturday, October 02, 2010 05:20 > To: discussion@pfsense.com > Subject: [pfSense-discussion] pfSense router/firewall in a Vmware > ESXi guest for other guests > > > A customer needs to run VMWare instances on the cheap, so naturally > I thought > about http://wiki.hetzner.de/index.php/VMware_ESXi_english > > ESXi can't route by itself though, so I thought about putting > pfSense into one VMWare guest instance, and use that for a router/ > firewall for the other guests. > > Anyone here doing that? Works well? Care to share details of > your setup? > > -- > Eugen* Leitl <a href="http://leitl.org";>leitl</a> http://leitl.org > ______________________________________________________________ > ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org > 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE > > ------------------------------------------------------------------- > -- > To unsubscribe, e-mail: discussion-unsubscr...@pfsense.com > For additional commands, e-mail: discussion-h...@pfsense.com > > Commercial support available - https://portal.pfsense.org --------------------------------------------------------------------- To unsubscribe, e-mail: discussion-unsubscr...@pfsense.com For additional commands, e-mail: discussion-h...@pfsense.com Commercial support available - https://portal.pfsense.org
