Transparent mode on ESXi using VLAN's - Page 2

sky-knight · 07-10-2009, 01:52 PM

All you need is the promiscuous mode. The others aren't needed.

EagleTG · 07-15-2009, 08:12 AM

I've also got the whole "test environment" Untangle behind pfSense working completely within a VM environment. Same routine, add a vSwitch between the Untangle's "external" NIC (with a made-up static address, gateway set to pfSense's made-up address) and the pfSense "internal" NIC (with another made-up static address), set that vSwitch to promiscuous, and you're golden.

For mine, true external network is 10.10.x.x, the made-up IP Addressing on the new vSwitch between Untangle and pfSense is 192.168.123.x (Untangle is .2, pfSense is .1). Client VM's on the actual internal vSwitch (not the new one between Untangle and pfSense) are using a static 10.10.x.x address, as I still can't get DHCP to pass... But that's my environment, normally DHCP could be served by something that actually resides on the internal LAN (mine comes from the gateway router on the 10.10.x.x network).

For my testing, this works perfectly.

sky-knight · 07-15-2009, 08:55 AM

Yeah I don't think UT has a DHCP relay...

EagleTG · 07-16-2009, 06:49 AM

Quote:

Originally Posted by sky-knight

Yeah I don't think UT has a DHCP relay...

I don't think it calls it out like pfSense does, but in a transparent bridge you can get DHCP from the other side of it. I'm doing it in my production environment (test user group) right now. Seems to work, but doesn't give 100% confidence in having a separate menu item specifically calling it out. Probably for simplicity's sake.

I haven't messed with it any more, and probably won't until Friday night or the weekend. I'll post back if I can get the DHCP relaying working properly.

Thanks again everyone.

07-10-2009, 01:52 PM	#11 (permalink)
sky-knight Join Date: Apr 2008 Location: Phoenix, AZ URLs submitted: 7 Posts: 8,106	All you need is the promiscuous mode. The others aren't needed. __________________ Intouch Technology Rob Sandling, BS:SWE, MCP Office: 480-272-9889 rob@intouchtechllc.com

07-15-2009, 08:55 AM	#13 (permalink)
sky-knight Join Date: Apr 2008 Location: Phoenix, AZ URLs submitted: 7 Posts: 8,106	Yeah I don't think UT has a DHCP relay... __________________ Intouch Technology Rob Sandling, BS:SWE, MCP Office: 480-272-9889 rob@intouchtechllc.com

07-15-2009, 08:12 AM	#12 (permalink)
EagleTG Untanglit Join Date: Jun 2009 Location: Pennsylvania Posts: 23	I've also got the whole "test environment" Untangle behind pfSense working completely within a VM environment. Same routine, add a vSwitch between the Untangle's "external" NIC (with a made-up static address, gateway set to pfSense's made-up address) and the pfSense "internal" NIC (with another made-up static address), set that vSwitch to promiscuous, and you're golden. For mine, true external network is 10.10.x.x, the made-up IP Addressing on the new vSwitch between Untangle and pfSense is 192.168.123.x (Untangle is .2, pfSense is .1). Client VM's on the actual internal vSwitch (not the new one between Untangle and pfSense) are using a static 10.10.x.x address, as I still can't get DHCP to pass... But that's my environment, normally DHCP could be served by something that actually resides on the internal LAN (mine comes from the gateway router on the 10.10.x.x network). For my testing, this works perfectly.