network configuration interface, gui feature request.

[pixelfairy]

Still evaluating between parallels and vmware

one issue i noticed is network configuration. only a share and host only network are presented. the command line tool to make more networks is easy enough. but, i cant find a way to disable dhcp on these added networks so that the guests can provide their own dhcp services. why not just add the other networks to the configuration gui?

 

[strells]

Did you not notice bridged networking? This does exactly what you are asking for: the virtual network interface is completely independent from the physical interface, but can get its address through a physical interface.

Steve

 

[pixelfairy]

yes, i did notice that. my goal is to test virtualization clusters and thin clients from a macbook. this means pxe booting and dhcp have to work without needing external interfaces.

tried making an empty bridge on the host with ifconfig, but that network did not seem to pass traffic at all (||s warned that it wouldnt, but i tried just to check). same result with thunderbolt bridge and en2.

bridging to a virtualbox network seemed to pass traffic, but still could not pxe boot.

bridging to a virtual network created by fusion(vmware) worked just fine. fusion itself had screen corruption on the thin client doing the same thing, but ||s displayed correctly.

i understand ||s has some issue with pxe booting on non physical (i guess vmware counts as physical) networks. maybe thats the real problem?