VMware Communities: Message List - How to modify Fusion network settings whitepaper

Re: How to modify Fusion network settings whitepaper

rdgadget — Tue, 17 Nov 2009 01:36:39 GMT

Check out this previous thread:
http://communities.vmware.com/thread/108167?start=120&tstart=0

DaveP posted tools for Fusion 3.0, post #127

Rick

Re: How to modify Fusion network settings whitepaper

mkennetha — Mon, 16 Nov 2009 22:31:17 GMT

Anybody figure out how to modify settings and add interfaces on VMware Fusion 3 yet? There doesn't seem to be a vmware-config-net.pl anymore.

Re: How to modify Fusion network settings whitepaper

etung — Fri, 19 Jun 2009 23:10:59 GMT

Check if the Windows firewall is on.

Re: How to modify Fusion network settings whitepaper

nayatronix — Fri, 19 Jun 2009 23:02:38 GMT

Hi,

Wondering if you can help.

1. I need to connect two virtual interfaces on a single VM back-to-back, similar to a crossover connection between two physical ports.

2. I also have 802.1q running on 2 VMs but I am unable to ping between the VM vlans . The ethernet port on the switch that the MAC (apple) connects to is a trunk port and the VM mac addresses show up in the mac-table on the switch in the relevant vlans.

Any ideas?

Thanks.

Re: How to modify Fusion network settings whitepaper

langtv — Wed, 20 May 2009 17:25:19 GMT

Hi Dave,

I've installed VMware Fussion on Mac OS X, on the virtual machine I use Windows XP. I've also configured networking hot machine like VMware Fusion Network Setting - Part 1. Now I want to use host-only in Virtual Machine to connect between Mac and Windows.

In the Windows, an IP address is assigned automatically, and it also set IP Address like file ./vmnet1/dhcp,conf. However, from Mac cannot ping to Windows.

I don't know how to correct. Please help me

Lang

Re: How to modify Fusion network settings whitepaper

Silica V — Tue, 10 Jun 2008 14:22:44 GMT

Thanks for the "Fusion network settings whitepaper" document.

Regards,

Silica V.

Re: How to modify Fusion network settings whitepaper

WoodyZ — Tue, 10 Jun 2008 13:51:50 GMT

Have a look at: A Beginner's Guide to VMware Fusion

Re: How to modify Fusion network settings whitepaper

allesmit — Tue, 10 Jun 2008 13:49:58 GMT

Sorry to be slow but where can I find the VMX files on the Mac?

Re: How to modify Fusion network settings whitepaper

whistl — Mon, 28 Apr 2008 20:23:54 GMT

Many thanks DaveP! That solved my immediate problem with getting Windows running on the corporate lan (en1) while leaving my test VMs running on the lab lan (en0).

Re: How to modify Fusion network settings whitepaper

DaveP — Mon, 19 Nov 2007 20:58:54 GMT

All

The scripts are no available in this thread http://communities.vmware.com/post!reply.jspa?threadID=108167.

Dave

Re: How to modify Fusion network settings whitepaper

etung — Fri, 09 Nov 2007 14:04:21 GMT

In addition to aetm's suggestions, you might try reinstalling Fusion - certain upgrade paths to Leopard result in the networking stack not working.

Re: How to modify Fusion network settings whitepaper

aetm — Fri, 09 Nov 2007 11:46:34 GMT

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?

Re: How to modify Fusion network settings whitepaper

DoctorDave — Fri, 09 Nov 2007 08:09:51 GMT

I am a relative novice at networking. My problem is this: under Tiger, Fusion with Windows XP Pro ran fine and I could access the internet. Now with Leopard, I cannot see the internet in Windows although it runs fine on the Mac side. Any suggestions?

Hardware: Mac Pro 8 core, 9G RAM. I access the internet via Airport 802.11n, and my external access to the internet is via cable.

I would appreciate any advice or suggestion.

Thanks again!

Re: How to modify Fusion network settings whitepaper

chrisott — Wed, 07 Nov 2007 20:08:07 GMT

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

Re: How to modify Fusion network settings whitepaper

DaveP — Sat, 03 Nov 2007 07:46:48 GMT

I had released them but have no found dependency in the way Fusion needs to have the networks defined. I will be re-releasing in a couple of days after 2 weeks of tryng to fathom out the porblem. The URL to watch is here: http://communities.vmware.com/message/773816

Re: How to modify Fusion network settings whitepaper

HeraldMage — Sat, 03 Nov 2007 01:59:24 GMT

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.

Re: How to modify Fusion network settings whitepaper

DaveP — Thu, 01 Nov 2007 15:29:09 GMT

Only within certain limits see here http://pubs.vmware.com/ws6_ace2/ws/ws_net_advanced_mac_address.html and other Workstation forum posts.

Re: How to modify Fusion network settings whitepaper

dracobyte — Thu, 01 Nov 2007 01:46:41 GMT

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

Re: How to modify Fusion network settings whitepaper

DaveP — Wed, 03 Oct 2007 07:35:01 GMT

To all who had asked about Part 2, it is on its way! Well actually I have written scripts that will allow modification of all the network settings for Fusion. If you are aware of the Linux Workstation way of doing things then this works the same way. I am going to have a small group of testers try it out, and then publish, hopefully next week. I would like to thank Pat Lee and VMware for allwoing me to re-distribute some VMware code with this.

Dave

Re: How to modify Fusion network settings whitepaper

DaveP — Thu, 20 Sep 2007 07:29:50 GMT

Glad it worked for you. I am waiting for VMware to check something out for me. Once that is done I will post test scripts.

Re: How to modify Fusion network settings whitepaper

darkwillow98 — Wed, 19 Sep 2007 20:35:27 GMT

Thank you SO much for your work on this Dave.

I needed to setup two separate bridges vmnets on two NICS and had got as far as tweaking the boot.sh mostly the way you had. I had forgotten the vmx file for the actual host. You porvided the missing piece for me.

Now I have the first NIC, en0, set to handle the host-only, NAT, and bridge for that portion, and the second NIC en1, set to handle bridging on the other NIC which is statically set and wired to a different subnet.

If you need help testing, I can assist.

Re: How to modify Fusion network settings whitepaper

taylorbanks — Tue, 18 Sep 2007 18:27:13 GMT

together. Out of interest how many virtual interfaces
do you need and of what sort?

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...

Thanks for offering to help.

Dave

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

-Taylor

Re: How to modify Fusion network settings whitepaper

DaveP — Tue, 18 Sep 2007 17:26:01 GMT

I just finished the Bash script and seems to be working on my Mac. I have a deadline this week for work, so will be next week when release, also so I have some time to put some preliminary documentation together. Out of interest how many virtual interfaces do you need and of what sort?

Thanks for offering to help.

Dave

Re: How to modify Fusion network settings whitepaper

taylorbanks — Tue, 18 Sep 2007 17:06:06 GMT

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

Re: How to modify Fusion network settings whitepaper

DaveP — Sun, 16 Sep 2007 18:18:46 GMT

quick update. I now have a modified vmware-config-net.pl script that adds back the same capabilities as in the Linux version of the script. For example, add/remove networks, change bridged, IP addresses etc. This seems to work well, but I now need to modify the boot.sh script that actually is used to start up and run the various parts of the virtual network.

Sorry it is taking longer than expected but work has been pretty busy recently, and I have a major release of software to deliver for Business Objects, and RTM is next Friday.

If anyone is prepared to test then please let me know.

Dave

Re: How to modify Fusion network settings whitepaper

DaveP — Wed, 12 Sep 2007 07:56:53 GMT

I also have a web site which I am going to be updating with this information. I don't mind you using it but would appreciate that it is correctly attributed to my paper which is copyrighted. If you want to discuss more then either PM or email me,

Cheers

Dave

Re: How to modify Fusion network settings whitepaper

DaveP — Wed, 12 Sep 2007 07:55:12 GMT

Hi

Give me a couple of days and I'll PM you with them. I haven't quite finished the Bash script for starting the services. There is nodocumentation on this, that was what I was writing as well.

Dave

Re: How to modify Fusion network settings whitepaper

vdanen — Tue, 11 Sep 2007 22:06:24 GMT

Dave, I think your whitepaper is fantastic, and I'm working on a wiki page with some information on various tweaks and tips and whatnot for Fusion.

I don't want to take your work verbatim, but I'd like to know if I can base some of what I'm writing on your observations and your white-paper (although I'll probably end up dummying it up a bit so that there isn't as much technical stuff... more of a "howto" than a full understanding type thing).

Would you mind terribly if I did so? I've already got some tips on there about xorg.conf and modprobe.conf settings, so I've been concentrating so far on the Linux guests, but I'd like to flesh out the page to cover as many troubleshooting/tweaking tips as possible.

Re: How to modify Fusion network settings whitepaper

QuiLoxx — Tue, 11 Sep 2007 18:57:41 GMT

Thank you for the reply!

if you can provide those scripts, I would greatly appreciate it... Otherwise, if you can point me to the right documentation to discuss how to do this manually - I would also appreciate it!

I have not been able to find this in the Fusion or the Workstation documentation...

Thanks!

-A

Re: How to modify Fusion network settings whitepaper

DaveP — Sun, 09 Sep 2007 12:42:08 GMT

I have a modified set of scripts which should do what you want. However, I want to check with VMware that they are happy for me to release them, as it uses parts of the VMware Workstation 6 Linux scripts. Using these scripts you can add or remove bridged, host and NAT adapters. Also I haven't written much on how to use them yet, which I would like to get done before releasing them.

Re: How to modify Fusion network settings whitepaper

QuiLoxx — Sat, 08 Sep 2007 20:46:51 GMT

If you come up with how to create another NAT interface - please post that as well...

What I really need - is another virtual network - like VMNet8 where my MAC can communicate with 2 VMs, and both VMs can communicate with each other as well. Getting out to the rest of the world is a secondary concern - so NAT is not truly required.

Thanks for posting all that you have!

-Aaron

Re: How to modify Fusion network settings whitepaper

DaveP — Tue, 28 Aug 2007 08:15:58 GMT

Here's the first quick update on adding a new bridged adapter and configuring the VMX file. Assumes that you have en0 and en1 adapters and that we will be using vmnet2 for 2nd bridged adapter. Please note if you are not comfortable editing bash scripts then best leave well alone. Please read the whitepaper first so you know where the files are located.

1. Edit boot.sh to add the following lines into the main procedure. Goto line 591 which should look like this:

[code]
# vmnet-bridge puts itself in background (daemon mode)
# Bridge to host network interface 'en0'.
#"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 en0
# Bridge to the primary host network interface (which can change over time).
"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 ''
;;

--stop)
logger -s -t "VMware Fusion 51348" "Shutting down VMware Fusion: "

# First attempt to synchronously kill the daemons this script had launched.
vmware_stop_pidfile /var/run/vmnet-bridge-vmnet0.pid || true
vmware_stop_pidfile /var/run/vmnet-dhcpd-vmnet1.pid || true
vmware_stop_pidfile /var/run/vmnet-dhcpd-vmnet8.pid || true
vmware_stop_pidfile /var/run/vmnet-natd-vmnet8.pid || true
vmware_stop_pidfile /var/run/vmnet-netif-vmnet1.pid || true
vmware_stop_pidfile /var/run/vmnet-netif-vmnet8.pid || true
[/code]
You need to comment out line 595 and then add the lines shown below so that it matches the second code block.

[code]
# vmnet-bridge puts itself in background (daemon mode)
# Bridge to host network interface 'en0'.
#"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 en0
# Bridge to the primary host network interface (which can change over time).
#"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 ''
"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 en0
"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet2.pid vmnet2 en1
;;

--stop)
logger -s -t "VMware Fusion 51348" "Shutting down VMware Fusion: "

# First attempt to synchronously kill the daemons this script had launched.
vmware_stop_pidfile /var/run/vmnet-bridge-vmnet0.pid || true
vmware_stop_pidfile /var/run/vmnet-bridge-vmnet2.pid || true
vmware_stop_pidfile /var/run/vmnet-dhcpd-vmnet1.pid || true
vmware_stop_pidfile /var/run/vmnet-dhcpd-vmnet8.pid || true
vmware_stop_pidfile /var/run/vmnet-natd-vmnet8.pid || true
vmware_stop_pidfile /var/run/vmnet-netif-vmnet1.pid || true
vmware_stop_pidfile /var/run/vmnet-netif-vmnet8.pid || true
[/code]
The difference is shown in the diff patch below:

[code]--- boot.sh.bk! 2007-08-27 18:51:41.000000000 +0100
+++ boot.sh 2007-08-28 14:40:47.000000000 +0100
@@ -592,7 +592,9 @@ case "$1" in
# Bridge to host network interface 'en0'.
#"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 en0
# Bridge to the primary host network interface (which can change over time).
- "$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 ''
+ #"$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 ''
+ "$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet0.pid vmnet0 en0
+ "$LIBDIR/vmnet-bridge" -d /var/run/vmnet-bridge-vmnet2.pid vmnet2 en2
;;

--stop)
@@ -600,6 +602,7 @@ case "$1" in

# First attempt to synchronously kill the daemons this script had launched.
vmware_stop_pidfile /var/run/vmnet-bridge-vmnet0.pid || true
+ vmware_stop_pidfile /var/run/vmnet-bridge-vmnet2.pid || true
vmware_stop_pidfile /var/run/vmnet-dhcpd-vmnet1.pid || true
vmware_stop_pidfile /var/run/vmnet-dhcpd-vmnet8.pid || true
vmware_stop_pidfile /var/run/vmnet-natd-vmnet8.pid || true

[/code]
2. Restart Fusion daemons with:
[code]boot.sh --restart[/code]
3. Modify your VMX file for the guest you want to use. In my example it is a Windows XP guest with ethernet0-->bridged vmnet0 and ethernet1-->bridged vmnet2. Edit the VMX file, after showing package contents on vmwarevm package.

[code]
ethernet0.connectionType = "bridged"
ethernet0.present = "TRUE"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet1.connectionType = "custom"
ethernet1.present = "TRUE"
ethernet1.vnet = "vmnet2"
ethernet1.wakeOnPcktRcv = "FALSE"
[/code]
Power on and hopefully you should have 2 bridged network adapters. Here's my output from guest:

[code]
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

Physical Address. . . . . . . . . : 00-0C-29-BA-EC-BB
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.101.0.102
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.101.0.1
DHCP Server . . . . . . . . . . . : 10.101.0.2
DNS Servers . . . . . . . . . . . : 158.43.240.4
158.43.240.3
Lease Obtained. . . . . . . . . . : Tuesday, August 28, 2007 8:38:26 AM
Lease Expires . . . . . . . . . . : Friday, August 31, 2007 8:38:26 AM

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

Physical Address. . . . . . . . . : 00-0C-29-BA-EC-C5
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.101.0.103
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.101.0.1
DHCP Server . . . . . . . . . . . : 10.101.0.2
DNS Servers . . . . . . . . . . . : 158.43.240.4
158.43.240.3
Lease Obtained. . . . . . . . . . : Tuesday, August 28, 2007 8:38:26 AM
Lease Expires . . . . . . . . . . : Friday, August 31, 2007 8:38:26 AM
[/code]
I will be working on other scenarios and of course updating the paper with this.

Cheers

Dave

Re: How to modify Fusion network settings whitepaper

HogHerder — Tue, 21 Aug 2007 19:25:50 GMT

DaveP -- great work, please send anything you can on configuring additional virtual adapters to Fusion ASAP!

Re: How to modify Fusion network settings whitepaper

InactiveX — Tue, 21 Aug 2007 13:05:53 GMT

Dave,

Thanks for this - got me out of a hole (in more ways than one).

Jason

Re: How to modify Fusion network settings whitepaper

matthite — Mon, 20 Aug 2007 17:11:41 GMT

Thanks so much! Looking forward to it.

Re: How to modify Fusion network settings whitepaper

DaveP — Mon, 20 Aug 2007 16:21:08 GMT

Thanks for the feedback. I will be starting on the next part, adding additional adapters, this week.

Re: How to modify Fusion network settings whitepaper

dan0016cb — Mon, 13 Aug 2007 04:30:21 GMT

Works on the 1.0 release. Thanks a lot for capturing this information!

Looking forward to any tips on adding more host-only vmnets.

Dan

Re: How to modify Fusion network settings whitepaper

matthite — Sun, 12 Aug 2007 18:55:42 GMT

This is great, Dave. I really appreciate it. I am looking forward to part 2! If you have any information on how to configure custom networks for networks other than vmnet1 and vmnet8, please do share.

Thanks!

-M

Re: How to modify Fusion network settings whitepaper

Pat Lee — Thu, 09 Aug 2007 12:39:08 GMT

Dave,

Thanks for your hard work, this looks great.

Pat

How to modify Fusion network settings whitepaper

DaveP — Thu, 09 Aug 2007 10:45:27 GMT

Like others in this forum, I need specific settings for the virtual networks setup on Windows and Linux version of VMware products. In Fusion the simplified installation and configuration means that rather than using the tools in the other versions of VMware, we need to take a different approach for now. Attached is a paper on changing IP address ranges for Fusion.

I will be working on other papers, and possibly new scripts to manage this, but for now I thought it would be useful to post it. Feedback & comments on this thread or via forum messaging would be appreciated, although I will be on vacation next week, with no web access.

Dave