Dave,

I'm very interested in testing and using the scripts you've updated and/or put together for Fusion network adapter management, as I have some specific needs for a couple of moderately complex networked VMs. (Most specifically, I'm working on a tiny NAT firewall VM that will allow the aggregation of multiple outbound Internet connections, ala Wifi+EV-DO or Wired+Wifi). Your whitepaper is great, and has gotten me started down the path, though having network management scripts akin to the Linux scripts would be delightful. I'll PM you with my contact details, and look forward to assisting with your testing.

Cheers,
-Taylor

At first blush, optimal will be: two bridged adapters (ex. one to en0, other to en1 or ppp0) and a single host-only adapter, through which my Host OS will then NAT back through the VM, which will be aggregating and pseudo-load-balancing between the two distinct network connections. Make any sense? The overhead of host/guest/network configuration convolution may outweigh the benefits, but I can't know until I try...

This is still as-of-yet completely untested, though I have no reason to believe the configuration can't work, even if it requires minor manual tweaks prior to each boot...

Happy to help, and thanks for your contributions thus far!

-Taylor

Is there a way to modify the physical/MAC address for a guests network?

-urgh .. answered my own question seconds after I asked it. My vmx file

Dave,

I'm very happy to see that someone else has gone through the effort I was thinking I'd have to do myself. I would LOVE to try this out as I have a real need for product demos for my company's solutions to have multiple vmnet networks. Specifically, I need just about all of vmnet1-9, though any VM only needs 3-4 interfaces. So have you finalized the scripts and part 2 yet? I would be interested in testing.

DaveP-

I was having problems with getting my Host-Only network interface to work after installing 1.1rc under Leopard. (Running W2k3 Server and XP guests.)

Following your Step 1 - Reset Fusion Settings solved my problem.

Thanks!

Ott

How is the network set up for the virtual machine? Virtual Machine > Network > one of the options is selected: NAT, Bridged, Host-only, Disconnect ...

If it's NAT or Bridged, it should work...

On your Windows V, start > run > type "cmd" for prompt (without the "") and you get command prompt, and in that (again without the "" in teh commands)

"ipconfig" to get your network info. If the ip address is odd, "ipconfig /release" and then "ipconfig /renew" to get a new address. This usually gets the machine connect to the network. If that would still fail, what type of network connection have you set (above NAT, Bridged etc), and what kind of IP addresses do you get with ipconfig?