VMware Communities: Message List - Scripts to manage Fusion network settings

Re: Scripts to manage Fusion network settings

DaveP — Thu, 05 Nov 2009 21:46:42 GMT

I don't see why it shouldn't the only thing that needs special treatment is vnet0 bridged. Give it a go an see what happens, just copy the networking file some place first so you can revert back. The run

./vmnet-cli --configure
./vmnet-cli --stop
./vmnet-cli --start

from /Library/Application Support/VMware Fusion.

Re: Scripts to manage Fusion network settings

fusionnotfission — Thu, 05 Nov 2009 21:43:11 GMT

Dave, scripts aside, can you just tell me whether my "fix" of just deleting the contents of the 'networking' file, but leaving the file itself intact, is a good solution for those of us who only use Bridged networking, and want to totally remove the vmnet1 and 8 adapters?

Thanks again!

Re: Scripts to manage Fusion network settings

DaveP — Thu, 05 Nov 2009 18:20:37 GMT

No they were really for Donovan who wanted my last set for Fusion 2. Now I thought I had posted a test set of scripts here last week on 29th but I cannot find them! I will trawl through the posts again. Otherwise I have some scripts that can be tried out but I am running behind on the manual due to walking back into a bit work issues that have taken me away from writing.

Re: Scripts to manage Fusion network settings

barnys — Thu, 05 Nov 2009 02:27:36 GMT

Dear Dave and fans,

I have been away for a few days from the threads, and after reading most of the postings from this section, I must admit that I am confused on the current state of your scripts and Fusion 3. So here I go:

1) Can your latest scripts posted in October 30th be used in Fusion 3 already?

2) If so, what is missing or what are the DONT'S ?

Thank you!!!!!!!!

Re: Scripts to manage Fusion network settings

fusionnotfission — Wed, 04 Nov 2009 05:51:02 GMT

Thanks, but I think you went around the problem not right at it...i ended up fixing the problem by simply modifying the new networking file, not the locations file as noted earlier. The networking file is even more straightforward, and as DaveP mentions earlier, is the bee's knees now in 3.0. I basically wiped the entire contents of that small networking file away, leaving only the version info at the top of the file, and after restarting the mac, the interfaces are gone! ifconfig doesn't even mention them anymore, not down, not up, just totally gone! Woooohoooo! Fusion seems happy with this as well now, but more testing will be needed of course.

Not sure that my process was 100% the Right Way(TM) to accomplish this task, but without further clarity on the subject it seemed the best approach. I did of course take a backup of the networking file in case what I did has other bad effects somewhere in Fusion.

Otherwise, cheers!

Re: Scripts to manage Fusion network settings

rcardona2k — Wed, 04 Nov 2009 05:14:18 GMT

fusionnotfission wrote:
Excellent thread, read thru it all...everyone here is talking about modifying the IP addresses of their vmnet8 or vmnet1 interfaces....what if I just want to blow them completely away, so they don't exist anymore? I am not going to use anything but Bridged and need to get these interfaces off my MAC! I am running SL server as a host, and Open Directory doth not like extranneous interfaces...would I just want to totally delete my locations file? Hmmmm....help please?

I don't know if this will help but i was able to disable my vmnet1 and vmnet8 interfaces with:
sudo ifconfig vmnet1 down
sudo ifconfig vmnet1 delete
sudo ifconfig vmnet8 down
sudo ifconfig vmnet8 delete

where vmnet-cli --status shows:
Bridge networking on vmnet0 is running
DHCP service on vmnet1 is running
Hostonly virtual adapter on vmnet1 is disabled
DHCP service on vmnet8 is running
NAT service on vmnet8 is running
Hostonly virtual adapter on vmnet8 is disabled
Some/All of the configured services are not running

ifconfig still shows vmnet1 and vmnet8 but the interfaces are down and have no IP addresses assigned to them. You could modify boot.sh to leave those interfaces down and IP-less.

Re: Scripts to manage Fusion network settings

Sebastian1981 — Wed, 04 Nov 2009 04:27:32 GMT

Vielen Dank für Ihre E-Mail,

ich bin bis einschließlich 04.11.2009 leider nicht im Hause. In dringenden Angelegenheiten können Sie sich an Torsten Jantzik wenden.
Ihre E-Mail wurde nicht weitergeleitet. Ich werde versuchen, Ihnen so schnell wie möglich zu antworten.

Dear Sender,

Thank you for your e-mail. Unfortunately, I will be out of the office until and including 04.11.2009. During my absence, you may contact the torsten.Jantzik@MATERNA.de. In any case, I will reply to your mail as soon as possible.

Mit freundlichen Grüßen/Best Regards

i. A.
Sebastian Schenzel
Mitarbeiter Business Center Government & Applications Business Unit Information

Re: Scripts to manage Fusion network settings

fusionnotfission — Wed, 04 Nov 2009 04:24:23 GMT

Excellent thread, read thru it all...everyone here is talking about modifying the IP addresses of their vmnet8 or vmnet1 interfaces....what if I just want to blow them completely away, so they don't exist anymore? I am not going to use anything but Bridged and need to get these interfaces off my MAC! I am running SL server as a host, and Open Directory doth not like extranneous interfaces...would I just want to totally delete my locations file? Hmmmm....help please?

Re: Scripts to manage Fusion network settings

DonovanBrooke — Fri, 30 Oct 2009 15:57:00 GMT

Thanks Dave,

Makes sense.. we'll give it a whirl over the weekend.

Donovan

Re: Scripts to manage Fusion network settings

DaveP — Fri, 30 Oct 2009 09:26:32 GMT

Donovan

Here are the scripts s I left them for Fusion 2. I have decided that I will concentrate on Fusion 3 for now but wanted you to have the last version I was using. it should allow:

1. Setting host virtual NIC address directly
2. Setting vnet NAT address directly
3. Profile support

Just run the tokamak.sh script without parameters to see the options. I'll fix up any simple errors if you find them.
Dave

Re: Scripts to manage Fusion network settings

DaveP — Fri, 30 Oct 2009 08:29:04 GMT

Actually locations is now deprecated and you use the networking file. There is much more you can add to it such as modifying specific entries in DHCP and NAT configuration files. Your solution will work for now, but will be best to migrate to the newer way of doing things. Be patient I'll get there with the documentation. (To be honest as it is becoming pretty easy to do this stuff manually now and will we need the scripts longer term, but will continue to do so for now.)

Re: Scripts to manage Fusion network settings

MacUnixGuy — Fri, 30 Oct 2009 00:10:14 GMT

For those new to this thread, here are a couple of documents that should be helpful (see attached).

To configure VMware Fusion 2.x, follow the instruction in "VMware Fusion Network Settings - Part 1.pdf". (by Dave Parsons)

To configure VMware Fusion 3.x, follow the instruction in "VMware Fusion 3.x Virtual Network Configuration Instructions.pdf".

These documents give instructions on how to manually configure the IP address ranges for the VMware Fusion host-only (vmnet1) and NAT (vmnet8) virtual networks.

If this is all you need to do, then you don't need to use any of the third-party scripts mentioned in this thread. If you do, however, need to make other changes, then you need to use the scripts created by Dave Parsons that are discussed in this thread.

Re: Scripts to manage Fusion network settings

MacUnixGuy — Thu, 29 Oct 2009 23:25:08 GMT

rdgadget wrote:mgartner/MacUnixGuy,

I apologize for misleading anyone on modifying the dhcpd files. I originally worked on this based on an older thread regarding Fusion 2.0.x. It listed the necessary files that supposedly needed editing and included the files I mentioned earlier. I never tried just doing the locations file and seeing if it automatically made the other changes. This is great information! Thanks for setting me straight on this guys.

Rick

Rick, thanks for the info. That's good news. I won't worry about testing the instructions on a clean install then.

Re: Scripts to manage Fusion network settings

rdgadget — Thu, 29 Oct 2009 21:13:57 GMT

mgartner/MacUnixGuy,

I apologize for misleading anyone on modifying the dhcpd files. I originally worked on this based on an older thread regarding Fusion 2.0.x. It listed the necessary files that supposedly needed editing and included the files I mentioned earlier. I never tried just doing the locations file and seeing if it automatically made the other changes. This is great information! Thanks for setting me straight on this guys.

Rick

Re: Scripts to manage Fusion network settings

mgartner — Thu, 29 Oct 2009 21:03:41 GMT

I also only had to modify the locations file and restart the virtual
networks!

Am 29.10.2009 um 21:16 schrieb MacUnixGuy <communities-emailer@vmware.com

Martin Gartner,

A new message was posted in the thread "Scripts to manage Fusion
network settings":

http://communities.vmware.com/message/1403409#1403409

Author : MacUnixGuy
Profile : http://communities.vmware.com/people/MacUnixGuy
Message:

Re: Scripts to manage Fusion network settings

MacUnixGuy — Thu, 29 Oct 2009 20:16:17 GMT

rdgadget wrote:

I did some messing around with this and found there are some other files that will have to be manually edited if you're using DHCP and/or NAT. In the vmnet1 and vmnet8 directories are the dhcpd.conf files. These will have to be modified to hand out the correct range of addresses, gateway, etc. Also in vmnet8 there is a nat.conf file that will need to be edited to point to the NAT gateway. I made these changes and all appears to be working correctly. I would advise backing up the locations file as well as the dhcpd.conf and nat.con files just in case.

That's interesting. All that I had to do was shutdown the virtual networks, modify the locations file, and start the virtual networks back up. VMware automatically modified all the necessary files in the vmnet1 and vmnet8 directories when I did this. I will be running through the steps on a clean install shortly and will post the results and modify the instructions if necessary.

rdgadget wrote:

Now all I still need is the ability to add additional network interfaces to Fusion. I have a few images that require two different host only interfaces/subnets. Waiting patiently for Dave's scripts.

You don't have to wait, if you are willing to use a beta version. Dave attached a beta version of the scripts to a post earlier this morning (see previous page in thread).

Re: Scripts to manage Fusion network settings

MacUnixGuy — Thu, 29 Oct 2009 19:48:18 GMT

mgartner wrote:Don't understand why even the official support doesn't know this simple solution?

Agreed. It should have been documented as part of the new release (it may have been, but I sure couldn't find it). I thought about calling support also, but figured it was not one of the common questions that they would have the answer to.

Dave, thanks again for your quick response and help with this. Enjoy your vacation !

Re: Scripts to manage Fusion network settings

rdgadget — Thu, 29 Oct 2009 19:45:36 GMT

Re: Scripts to manage Fusion network settings

MacUnixGuy — Thu, 29 Oct 2009 19:28:40 GMT

Dave, thanks for your help providing the manual configuration info. This is EXACTLY what I needed to know for now, but I will look forward to the other features in your script in the future.

Martin, thanks for your observation about NOT renaming the locations file.

For others who haven't been following this thread and need to hard-code the vmnet1 and vmnet8 virtual network IP address ranges for VMware Fusion 3.x, I documented the steps that I took based on previous posts in this thread.

See the attached file, "VMware 3.x Virtual Network Configuration Instructions.pdf".

Re: Scripts to manage Fusion network settings

mgartner — Thu, 29 Oct 2009 10:20:25 GMT

Don't understand why even the official support doesn't know this simple solution?

Re: Scripts to manage Fusion network settings

DaveP — Thu, 29 Oct 2009 10:11:36 GMT

Great. There is way more you can now do but as I said on holiday in Portugal and need the break. The sun is out and the sea looks good, so I'm outta here for awhile.

Re: Scripts to manage Fusion network settings

mgartner — Thu, 29 Oct 2009 10:04:21 GMT

Hey cool this worked like Dave told:

sudo ./vmnet-apps.sh --stop
change the IP values to the needed ones in file "locations"
sudo ./vmnet-apps.sh --start

check if IP values are correctly set: ifconfig -a

Thanks alot Dave! You made my day and saved my life!

Martin

Re: Scripts to manage Fusion network settings

mgartner — Thu, 29 Oct 2009 09:56:14 GMT

Additional information: coudn't rename locations file to networking as there is allready an executable file called networking...

Re: Scripts to manage Fusion network settings

mgartner — Thu, 29 Oct 2009 09:53:12 GMT

Hello Dave,

thank you very much for your effort! Don't know exactly which locations file you need: the original one which is created from installation routine of VMWare Fusion 3 or my modified one with the needed IP addresses. So i have attached both: locations.modified and locations.original

Martin G.

Re: Scripts to manage Fusion network settings

DaveP — Thu, 29 Oct 2009 09:28:37 GMT

Guys I as I stated I am currently on vacation and was trying not to get distracted. The VMware support staff unfortunately are wrong to a certain extent, the Perl script has gone but has been replaced with a command line program. Firstly try renaming "locations" file to "networking" then run vmnet-apps.sh --stop and then --start. Need sudo or root. As a one off until I return next week, if Martin posts his locations file I will modify it to the new style.

Attached is a beta of the scripts for Fusion 3 only. Unzip and run tokamak.sh to see the options. There is no documentation yet and I will be off the net more than on it. Note it is also not tested with release of Fusion 3 due to bandwidth limits oin 3G card, so could not download. You will need to reapply settings as I haven't built any migration options.

Dave

Re: Scripts to manage Fusion network settings

mgartner — Thu, 29 Oct 2009 06:54:27 GMT

As an additional information:

I had contact with the official VMWare support and the guy there told me I still could use the vmware-config-net.pl script to manually configure the network settings in VMWare Fusion 3! So I copied over the file to the new location (Library/Application Support/VMWare) only to find out there are also other necessary files missing to configure the vmnet adapters!
I reported this back to VMWare support and the guy told me he will pass this information to the development team.

So still no solution!
Seems that I have to go back to V2.06 :-((

Re: Scripts to manage Fusion network settings

DonovanBrooke — Thu, 29 Oct 2009 00:48:37 GMT

Thanks,

Yes, I've read the virtues of 3x.

MacUnixGuy wrote:| |
I was using the 2.0.6 beta version (build 196839) previously, but I haven't seen an announcement that an official 2.0.6 version was released. I may have missed it.

No you didn't miss it. That's the build number, but it's not a beta build and it works fine on SL (though yes, 3 has more fixes/features).

http://downloads.vmware.com/d/details/fusion_2_0_6/JUBiZCVkamJAQGU=

Donovan

Re: Scripts to manage Fusion network settings

MacUnixGuy — Thu, 29 Oct 2009 00:14:32 GMT

if you upgraded for SL support, what support do you get for Snow Leopard that isn't in 2.0.6?

I was using the 2.0.6 beta version (build 196839) previously, but I haven't seen an announcement that an official 2.0.6 version was released. I may have missed it.

Here is a link to the list of 50+ new features that VMware advertises as new to version 3.x:

http://communities.vmware.com/docs/DOC-10957

Of these features, the main ones that I was upgrading for were:

Official Snow Leopard support (non-beta)
Full 64-bit support (better performance, full 64-bit host and client support)
Full Windows 7 support
DirectX 9.0c support

Since using the 3.x version I have also discovered several handy configuration settings and features that I wasn't expecting:

Much better handling of full-screen mode, with several new features for this mode, which I am now using daily
Much better support for multiple displays
Significantly cleaned up UI
Copy/paste improvements
Built-in software updater (goodby to the 2.x method of downloading/installing a full product image for every single minor point release)
Remote VNC control of clients without installing any software in the client - VERY COOL !

This is a great product, and VMware should be very proud of it. The only problem that I have found so far is that it shipped (at least as far as I can tell) without the network configuration script that was included in the 2.x version.

I'll hold out for another few days, hoping to find some instructions for manual configuration of vmnet1 and vmnet8, and revert back to the 2.0.6 beta release if can't find instructions.

Re: Scripts to manage Fusion network settings

DonovanBrooke — Wed, 28 Oct 2009 22:36:53 GMT

MacUnixGuy wrote:

I have recently upgraded from VMware Fusion 2.x to 3.x to get Snow Leopard support.

Hello, MacUnixGuy,

just for clarification..

if you upgraded for SL support, what support do you get for Snow Leopard that isn't in 2.0.6?

Donovan

Re: Scripts to manage Fusion network settings

MacUnixGuy — Wed, 28 Oct 2009 22:28:40 GMT

Dave, I have the same question as mgartner.

I have recently upgraded from VMware Fusion 2.x to 3.x to get Snow Leopard support.

I need to configure vmnet1 and vmnet8 to have specific ip addresses. I don't need a script for this, just instructions to do it manually.

I followed your excellent document (VMware Fusion Network Settings – Part 1) to get 2.x working, but I can't do that for the 3.x release, since the 3.x release no longer contains the vmware-config-net.pl script, from what I can see.

To answer your question, the 3.x documentation (even without scripts) is much more important for me, since there is already documentation to get 2.x configured manually, but nothing for 3.x yet. There are several other guys who I work with who have upgraded or are in the process of upgrading to the 3.x release who will have exactly the same problem as me in the next few days if there is not a workaround (even a manual one) for this. So put our votes down for this.

Thanks for your efforts on this product. It's obvious that you have put a lot of work into this.

Re: Scripts to manage Fusion network settings

mgartner — Wed, 28 Oct 2009 12:11:00 GMT

Hello Dave,

could you please give me a hint how to configure the vmnet adapters without your script in Fusion 3? The problem is the vmware-config-net.pl script (and other files) is missing in the new VMWare version and I need the reconfiguration urgently.

Thanks in advance,
Martin Gartner

Re: Scripts to manage Fusion network settings

DaveP — Tue, 27 Oct 2009 18:07:20 GMT

I know! Work has been a roller-coaster for the last 3 years my company ALG Software bought by Business Objects, then Business Objects bought by SAP. Each time new challenges to manage the office I am responsible for, and not enough time to hack code or be in the forums. I am using this vacation to make sure I get this ready, but there has to be time for food, drink, swimming and sun. I will definitely try an be more active once I get this done.

Re: Scripts to manage Fusion network settings

DonovanBrooke — Tue, 27 Oct 2009 17:49:12 GMT

Well, I for one would sure appreciate the 2.x version.

Thanks,

Donovan

Re: Scripts to manage Fusion network settings

WoodyZ — Tue, 27 Oct 2009 17:06:59 GMT

First of all I have to say thanks Dave for all your hard work on this and to VMware for allowing you to use some of their code to do it and Pat and Nithin for supplying you what you need. VM@Work Tokamak is an essential tool since VMware still hasn't provided a Virtual Networks Manager under Fusion in the same vein as what Workstation has and I know it made it much easier for me as I moved between Client Sites when I was using Fusion and my MacBook Pro as my primary Notebook but have put that all on the back burner and my primary Notebook is back to Dell, Windows and VMware Workstation. That said I'd do what's easiest for you to accomplish what you want to with this knowing that your efforts are truly appreciated and we'll gladly take what you have to offer when you have it even tho it seems that either you're working to much or on vacation to get it done

Re: Scripts to manage Fusion network settings

DaveP — Tue, 27 Oct 2009 16:27:27 GMT

Thanks for everyone's interest in this. Yes there is a new version coming, initially as a beta next week. Unfortunately I can't get hold of the release version of Fusion 3 as I am on holiday with only limited bandwidth. I have completed the coding and need to write some new documentation to describe both the new networking capabilities within Fusion 3's configuration system, plus a few new features in the scripts. For example setting host IP address to a user defined number, profiles and a few other things. The initial release won't deal with all the new possibilities in Fusion 3, but will certainly allow you to do what you currently do with Fusion 2, and I intend to write about manual changes that can now be very easily made to the configuration files. (Thanks to Pat and Nithin from VMware for providing me with the information to do this.)

One question, I have also implemented some of this for Fusion 2. What interest is there in also releasing it for Fusion 2 users? Would you prefer I get Fusion 3 support out the door, or a package that can work for 2 & 3?

Dave

Re: Scripts to manage Fusion network settings

mgartner — Tue, 27 Oct 2009 13:29:20 GMT

I would also be very interested in getting a solution to configure the network in Fusion 3!
Thanks in advance for your effort!

Regards,
Martin Gartner

Re: Scripts to manage Fusion network settings

sirozha — Tue, 27 Oct 2009 13:09:39 GMT

Dave,

Fusion 3 has just been released. Could you let us know more about what Fusion 3 has added with respect to VM network settings (which obviously lacked a lot of functionality in Fusion 2). What is the status of your scripts for Fusion 3?

Thanks!

Re: Scripts to manage Fusion network settings

BenBruhl — Sat, 17 Oct 2009 14:12:31 GMT

Thanks again Dave! You continue to make this product usable for those of us that need more from Fusion than a Windows game machine or Office suite host.

I am looking forward to seeing what the new changes support.

Re: Scripts to manage Fusion network settings

DaveP — Sat, 17 Oct 2009 10:55:05 GMT

Hi

I am working a lot on the scripts at the moment. The Fusion 2 stuff is nearly complete, and working hard with one of the Fusion engineers on an update for Fusion 3. (There are some nice changes in Fusion3 which I will reveal post release!) Work has gotten in the way a bit, with overseas travel, but fingers crossed for end of October.

Dave

Re: Scripts to manage Fusion network settings

DonovanBrooke — Fri, 16 Oct 2009 22:49:35 GMT

Hi Dave,

I just found your recent posts here (so sorry if you find my posts in a couple other threads!) .

I will be watching with great interest to see if you can attain something solid for 2.0.6 and Snow Leopard.

Cheers,

Donovan

Re: Scripts to manage Fusion network settings

DaveP — Tue, 29 Sep 2009 07:19:43 GMT

Hi

Do NOT use them with Fusion 3 RC or betas. VMware have changed how some things work in 3. I am working with a VMware engineer to build something for Fusion 3, but it is early (2) days. I am delaying releasing new scripts until I have version for 2.0 & 3.0 with comparable facilities.

Dave

Re: Scripts to manage Fusion network settings

barnys — Mon, 28 Sep 2009 23:41:11 GMT

Hi Dave, how is it going? did you have a chance to see my post? any progress in your scripts? Hope you can bless us again pretty soon.

Thanks,

Re: Scripts to manage Fusion network settings

barnys — Thu, 10 Sep 2009 00:32:32 GMT

Hi Dave,

I presume that you were just informing of your progress, but you haven't released any updates yet, right?

My biggest focus is on item 2 of your list. Up until the beta 1 of the new version (Version e.x.p (169060)) your scripts worked flawlessly. However with the release from today (build 184177) running your scripts renders the VMs unusable. As soon as you run -–uninstall fromyour scripts, then the vmmon starts and so the VMs, but you loose all the vnets defined

I have a strong motivation to use the latest Fusion build because it has experimental 64-bit support for both the host and guests, but Fusion is practically uselessto me without the faculty of defining more vnets and bridging ad-hoc.

Do you care to comment about this Dave? Will you be updating your wonderful solution to run in the latest build?

Thanks in advance, and also many thanks for your continuous effort to put this out for us.

Barny

Re: Scripts to manage Fusion network settings

DaveP — Fri, 04 Sep 2009 07:31:15 GMT

Update 2 - 04/09/09

1. Snow Leopard installed and will test with Fusion 2.0.5 (Can I drop earlier versions from testing?)
2. Talking with VMware over this, but don't use on beta 2 just yet!
3. Profiles done.
4. Different addresses now possible for host vmnet and nat router.
5. Longer term objective but I think will be dependent on beta program

I may get a new beta done this weekend, but if not I am on the road next week, and may not be able to work on them.

Dave

Re: Scripts to manage Fusion network settings

DaveP — Thu, 27 Aug 2009 19:04:14 GMT

Started work on a new version of the scripts.

1. SL arrives tomorrow but will take a while to setup test system.
2. Not saying too much due to NDA but network setup seems to be changing.
3. Profiles done.
4. Still investigating.
5. Longer term objective but I think will be dependent on beta program

Also did a major edit on the Perl code to remove large chunks that are Linux specific. Makes maintenance easier for me.

Re: Scripts to manage Fusion network settings

DaveP — Thu, 20 Aug 2009 13:45:37 GMT

Thanks for the ideas.

1. Snow Leopard - will check this out when I get a copy from retail
2. Fusion beta - again will check against builds as they come out
3. Profiles - nice idea and actually something I think I can achieve fairly easily
4. Host IP addresses - as mentioned in another post I did write that code but found some problems with it. Will revisit it.
5. Possibly write a GUI. I have been itching to learn some Cocoa programming so may give this some thought. Also have Realbasic for Mac which would be a quicker option.

Re: Scripts to manage Fusion network settings

BenBruhl — Wed, 19 Aug 2009 19:29:18 GMT

I wanted to also pass along that I have been using yours scripts for the past year, including with each update of Snow Leopard and they are working fine with the new OS. I also hope to one day see VMware add these capabilities via their GUI.

Re: Scripts to manage Fusion network settings

barnys — Wed, 19 Aug 2009 16:54:47 GMT

David,

I want to second the others compliments to your hard work and awesome script. I have used extensively since your first version, and 1) I can't imagine me using Fusion without them, and 2) I can't understand why VMware hasn't included such capabilities natively, via their GUI.

Things set aside, really, THANK YOU!.

Now, down to business:

1) I have been using Snow Loepard's latest seed every time that Apple makes them available, and I can confirm that up until today 8/19, your scripts work with Snow Leopard and the very latest version of Fusion (beta), released today - Version e.x.p (184177).

2) The item that I would like to suggest as an improvement perhaps is the creation of "profiles". Imagine that you create 5,10 or 30 vmnets (like in my case), and I would like to take all of those settings and "Save As" so that I am use another set of vmnets. So there should be a "Save Profile As", and an "Apply Profile", and perhaps a "List Profiles". That is just being extra picky, but I personally can see a lot of functionality in what I do.

Thanks!!!

Re: Scripts to manage Fusion network settings

sirozha — Wed, 19 Aug 2009 11:34:58 GMT

Dave,

Thanks for you work. I have been using your scripts for almost a year now, and I would not have been able to use VMWare on the Mac platform without them. If the functionality of your scripts break down in Snow Leopard, I think this is what you should concentrate on at this point because Snow Leopard is going to be out within a month, and everyone would want to upgrade right away, especially because it is going to be so inexpensive to upgrade.

Thanks!

Re: Scripts to manage Fusion network settings

DaveP — Mon, 17 Aug 2009 13:58:16 GMT

Ben, I did have some code to do this, but found issues with Fusion when running it. I will go back and take a look at the code again, if I can find it!

Re: Scripts to manage Fusion network settings

BenBruhl — Mon, 17 Aug 2009 13:45:31 GMT

First of all, thanks for all you hard work on the scripts. I could not do my job with Fusion without these scripts. Great job.
If you could find a way to assign an IP to the OS X host when setting up the IPs and sub net, it would be nice. Currently, the OS X host takes all the XXX.XXX.XXX.1 address, which some of my other VMs need to use. In order to get the OS X host off that IP address, I have to run "ifconfig down/up" to reassign the host to use a different IP, like XXX.XXX.XXX.20
Does that make sense?

Re: Scripts to manage Fusion network settings

WoodyZ — Mon, 17 Aug 2009 00:35:08 GMT

Dave I do not have any special requests although I want to say thank you for the time, energy and effort you have put into VM@Work Tokamak as it has made Fusion a more usable product, especially for those of us that are used to the Manage Virtual Networks GUI in Workstation for Windows and had tried switching to a Mac.

Re: Scripts to manage Fusion network settings

DaveP — Sun, 16 Aug 2009 20:50:44 GMT

To all the users of these scripts. I have been away from the community nfor some time now due to work and other pressures. However I have started to revisit the code, and have a 2.1.0 version waiting in the wings. (Released a beta of it here last year.) Are there any specific features that you would like me to investigate? Remember they have to be within the bounds of what the scripts from VMware are capable of, but I am open to suggestions.

Re: Scripts to manage Fusion network settings

barnys — Thu, 23 Jul 2009 15:44:36 GMT

I does run on mine with no problems.

Just FYI - I upgraded to the last seed of snow leopard in another one of my MACs, and the scripts don't seem to run properly!

Thanks,

Re: Scripts to manage Fusion network settings

dirtybit — Mon, 29 Jun 2009 08:25:47 GMT

does anyone knows if the lastest tokamak beta does run on fusion 2.0.5 ?

it didn't get the NAT running but i'm not sure if i messed up the config.

i wasn't able to reach a host outside the NAT network. when i configure dhcp i didn't get a default gateway on the guest.

Re: Scripts to manage Fusion network settings

tdurden — Sat, 11 Apr 2009 08:53:58 GMT

Thanks I saw that advice in another post and followed it. Seems I was being a bit thick.

All working now.

Thanks for the quick response and thanks Dave for the great tool. Thanks other guy for the editor too.

Re: Scripts to manage Fusion network settings

WoodyZ — Fri, 10 Apr 2009 23:28:42 GMT

tdurden wrote: What do we do if this file doesn't exist? I cant find it in finder or from the command line.

Have a look at A Beginner's Guide to VMware Fusion and Information Gathering for VMware Fusion.

Re: Scripts to manage Fusion network settings

tdurden — Fri, 10 Apr 2009 22:38:37 GMT

Hi, Thanks for the scripts. These make a huge difference. One question though. You say in the instructions that I will need to edit the VMX file held in the “vmwarevm” package.

What do we do if this file doesn't exist? I cant find it in finder or from the command line.

Can you post the command line of what you mean to do here?

Thanks

Re: Scripts to manage Fusion network settings

sirozha — Sun, 15 Feb 2009 17:06:37 GMT

The latest beta works fine with Fusion 2.0.2 as well; all of my settings were kept when I upgraded to 2.0.2.

Re: Scripts to manage Fusion network settings

Technogeezer — Sun, 15 Feb 2009 01:56:22 GMT

I can't speak for the Tokamak beta release, but the released 2.0 scripts seem to be working fine for me with Fusion 2.0.2.

Might bode well for the beta version working with 2.0.2 as well.

Re: Scripts to manage Fusion network settings

kcrandallAThytrustDOTcom — Thu, 12 Feb 2009 21:39:44 GMT

As always, thank you. Good luck with your release!

Re: Scripts to manage Fusion network settings

DaveP — Thu, 12 Feb 2009 19:19:58 GMT

I will be coming back to this soon. Been away from the forums and this due to work pressures. The software I work on is now about to be released so will have some time available to look at features.

Re: Scripts to manage Fusion network settings

kcrandallAThytrustDOTcom — Thu, 12 Feb 2009 19:04:11 GMT

I've been a happy user of the Tokamak scripts since their inception. Thanks, Dan, for all your hard work!

I have been using 210b1 with no issues on Fusion 2.0.1. Now that 2.0.2 is out, are we going to see a new beta?

Re: Scripts to manage Fusion network settings

WoodyZ — Thu, 29 Jan 2009 21:21:39 GMT

Also I want to clarify what I said by "and no you cannot have multiple "ethernet1." assigned" as I meant that literally however you can have up to 10 virtual Ethernet cards defined per Virtual Machine.

Re: Scripts to manage Fusion network settings

walts — Thu, 29 Jan 2009 21:07:24 GMT

Thanks.

I get that "ethernetn." is just an arbitrary (sequential) numbering and had no correspondence with either the hardware "enx" or the virtual "vmnety" designations.

That makes sense.

Walt

Re: Scripts to manage Fusion network settings

WoodyZ — Thu, 29 Jan 2009 20:16:38 GMT

ethernet1.<rest of parameter.> = <value> is just an example. Increment the numeric portion of "ethernet1." as necessary and no you cannot have multiple "ethernet1." assigned.

Re: Scripts to manage Fusion network settings

walts — Thu, 29 Jan 2009 20:01:16 GMT

Dave,

I've downloaded and installed the Tokamak scripts to use to add 2 new virtual Ethernet adapters. In the docs you talk about modifying the VMX file, and in searching for more information I found your excellent paper, "VMware Fusion Network Settings - Part 1". In reading it, it looks like the information I'm looking for is in Part 2 and I can't find that anywhere!

Specifically, in the Tokamak docs you say that after adding vmnet3, you should add a line to the VMX file

ethernet1.present = "TRUE"

ethernet1.connectionType = "custom"

ethertnet1.vmnet = "VMnet3"

...but it looks as though ethernet1 is already defined in my VMX file; currently it appears to be a NAT interface.

Does "Ethernet1" here refer to the Mac device "en1"? What happens if this is multiply defined?

I don't want to blindly go about making changes without understanding what I'm doing, but I can't seem to find the documentation. Please help.

Walt

Re: Scripts to manage Fusion network settings

DaveP — Fri, 23 Jan 2009 08:03:04 GMT

It is the default behaviour of all the VMware scripts and programs to generate it in this way. I didn't change it as for most folks it seemed OK. Your suggestion to hack the actual configuration files after running them through the scripts is probably the best way for now. I may get back to them to add in an even more advanced option but work is too demanding at the moment. (For any SAP folks reading this I'm in the middle of Solutions Validation!)

Re: Scripts to manage Fusion network settings

Technogeezer — Fri, 23 Jan 2009 02:54:33 GMT

Unfortunately this behavior appears to be inherent to the design of the Tokamak scripts (and the VMware code it was based on).

The Tokamak scripts calculate the host address by using the subnet mask to strip out the host portion of the IP address you've provided, and then adding 1 to that.

For most subnets (e.g. class C or /24), this results in the host being on the .1 address in the subnet. For more "estoteric" subnet configurations, here's an example:

You input 10.100.0.150 as the host IP, with a subnet mask of 255.255.255.128. The first address of the subnet is 10.100.0.128, and the host would calculated as 10.100.0.129.

You might be able to get around this by editing the generated /Library/Application Support/VMware Fusion/locations (making changes to the last VNET_x_HOSTONLY_HOSTADDR for the vmnet that you want, and making sure it doesn't collide with the DHCP ranges for that vmnet (/Library/Application Support/VMware Fusion/vmnetx/dhcpd.conf)

Re: Scripts to manage Fusion network settings

sirozha — Fri, 23 Jan 2009 02:28:30 GMT

I have experienced the same issue with vmnets always assuming the .1 address.

Re: Scripts to manage Fusion network settings

skullshot — Thu, 22 Jan 2009 13:42:06 GMT

only issue i have had with any of this so far is that it doesnt take the specified ip i put in for my new vmnet.

eg. i created a new vmnet2 with the 2.1 script. no nat, no dhcp. and when it asked ip for the host i put 10.100.0.254 with /24 subnet but when the script finishes i have vmnet with address of .1 instead of .254

Re: Scripts to manage Fusion network settings

WoodyZ — Thu, 15 Jan 2009 03:26:44 GMT

rickf101 wrote: Well, I had previously downloaded the latest (tokamak210b1.zip) which doesn't have the PDF in it. I just downloaded 200 and I see the PDF. It does answer my question.

I only mentioned the .pdf because it was there however the document that I provided the link to originally has the same directions and if you had read the "4.0 Modify Guest VMX File" section in Advanced Networking Configuration - Tokamak Networking Scripts for VMware Fusion it says the same thing as the .pdf. Don't feel to bad you're not the first person that didn't get it either and probably not the last.

Re: Scripts to manage Fusion network settings

rickf101 — Thu, 15 Jan 2009 03:00:14 GMT

Well, I had previously downloaded the latest (tokamak210b1.zip) which doesn't have the PDF in it. I just downloaded 200 and I see the PDF. It does answer my question.

Thanks!

Re: Scripts to manage Fusion network settings

WoodyZ — Thu, 15 Jan 2009 02:32:24 GMT

rickf101 wrote: I appreciate your response but this still is not answering my question. While I'm new to Mac OS-X, I've been a Unix kernel developer dating back to Unix System V Release 2 (circa 1988).

I want to bridge en0 to vmnet0, en1 to vmnet2 (step A), and then connect the guest's ethernet0 to vmnet0 and ethernet1 to vmnet2 (step B).

With that much experience one would think you'd read the entire document and the answer you seek is in that document much less the "VM@Work Tokamak.pdf" file that is in the tokamak200.zip file.

Suggest you reread it and specifically the "4.0 Modify Guest VMX File" section.

Re: Scripts to manage Fusion network settings

rickf101 — Thu, 15 Jan 2009 02:01:47 GMT

I appreciate your response but this still is not answering my question. While I'm new to Mac OS-X, I've been a Unix kernel developer dating back to Unix System V Release 2 (circa 1988).

I have looked at the script output and I see that you can associate different physical interfaces with different vmnet's. My question is how do you tie a specific vmnet to a virtual interface for a given guest? In the guest's VMX file, I see ethernet0.connectionType = "bridged". I don't see any way to specify WHICH bridge.

I want to bridge en0 to vmnet0, en1 to vmnet2 (step A), and then connect the guest's ethernet0 to vmnet0 and ethernet1 to vmnet2 (step B).

I see how to do step A, I don't see how to do step B.

Re: Scripts to manage Fusion network settings

WoodyZ — Thu, 15 Jan 2009 01:30:38 GMT

There is a very good reason why this is for advanced users. If you just run the script it should be obvious.

As an example when I run the script here is the first part of the output...

macbookpro:tokamak200 WKZ$ sudo ./tokamak.sh --modify
You have already setup networking.

Would you like to skip networking setup and keep your old settings as they are? 
(yes/no) [yes] n

Do you want networking for your virtual machines? (yes/no/help) [yes] y

Would you prefer to modify your existing networking configuration using the 
wizard or the editor? (wizard/editor/help) [wizard] w

Configuring a bridged network for vmnet0.

Your computer has multiple ethernet network interfaces available: en0, en1, en2,
en3. Which one do you want to bridge to vmnet0? [en0]

The select the ethernet network interface you want.

Re: Scripts to manage Fusion network settings

rickf101 — Thu, 15 Jan 2009 00:49:03 GMT

Yes, I did look at that document. It talks about "Changing the physical interface used for bridged connections" but it doesn't discuss how to set up bridged connections to two physical interfaces simultaneously.

Re: Scripts to manage Fusion network settings

WoodyZ — Wed, 14 Jan 2009 23:16:42 GMT

rickf101 wrote: Will your scripts allow me to create an additional vmnet (say vmnet2) which is bridged to en1 while keeping vmnet0 bridged to en0? If so, what glue is necessary in the guest vmx file to tie a virtual network adapter to this second bridge?

Yes it will however have a look at the Document DaveP did on this for directions: Advanced Networking Configuration - Tokamak Networking Scripts for VMware Fusion

Re: Scripts to manage Fusion network settings

rickf101 — Wed, 14 Jan 2009 22:50:44 GMT

Dave,

Will your scripts allow me to create an additional vmnet (say vmnet2) which is bridged to en1 while keeping vmnet0 bridged to en0? If so, what glue is necessary in the guest vmx file to tie a virtual network adapter to this second bridge?

Thanks,

Rick

Re: Scripts to manage Fusion network settings

tramahound — Tue, 30 Dec 2008 16:12:47 GMT

I was only sent a snippet from the Ciscoworks ASA log file, but according to our network admin traffic going to my vmnet1 interface was being logged there for denials every second! All it shows is the ip address of other computers along with "Inbound TCP connection denied from 10.33.4.x/7307 to 192.168.79.1/139 flags SYN on interface inside"
I had an SMB share running before, but even after turning it off and removing it the connection attempts still came in. It wasn't until actually disabling the entire interface that they stopped.
according to my netstat -r results my default route is set correctly on both my host and guest on en0.

Re: Scripts to manage Fusion network settings

sirozha — Wed, 24 Dec 2008 19:08:24 GMT

You should be able to disable both vmnet1 and vmnet8, using David's script. However, I am not sure what the original problem is. You Mac cannot "advertise" anything to the network because it is not running a routing protocol. Additionally, firewalls normally don't run routing protocols either, so they usually cannot receive any routing updates. Depending on your topology, you may have your Mac's default gateway pointing to the inside interface of the firewall. When you Mac needs to send a packet to another network, it would first ARP for your default gateway's Mac address, and your Firewall would respond with its MAC address (if the firewall is the default gateway). When the firewall needs to send something to the Mac, it would ARP for the Mac's IP address. If you your guest OS is connected to your host (Mac) via the "bridged" connection, then your guest OS's virtual network interface will respond to the ARP request with its virtual MAC (different from Mac) address. In this case, any host on the network can talk directly to your guest OS. If, on the other hand, your guest OS is connected to the network via the "NAT" connection, then your Mac is tasked with translating the IP address assigned to the virtual network interface of your guest OS into the IP address assigned to the physical network interface on the Mac itself; therefore, the MAC address used in the ARP replies will be the Mac's physical nework interface's MAC address. In the case of the "NAT" connection of your guest OS, the IP subnet configured on vmnet8 will not be visible to any physical network device besides your Mac.

So, please find out what exactly the firewall logs are showing and report it here so that we can try to help you.

If you want to turn your vmnet interfaces off temporarily, use the following commands:

sudo ifconfig vmnet1 down

sudo ifconfig vmnet8 down

If you guest OS is bridged to your Mac's physical network interface, then bringing down vmnet1 and vmnet8 should not affect the traffic to your guest OS.

In order to bring vmnet1 and vmnet8 back up, use the following commands:

sudo ifconfig vmnet1 up

sudo ifconfig vmnet8 up

Also, you may want to use the netstat -r command on your Mac to see out of which nework interface the default route (0.0.0.0) is pointing -- it should be pointing out of one of your Mac's physical interfaces (usually en0 - ethernet; or en1 - Airport). On the other hand, in your guest OS (if it's Windows), you can go to the command prompt and issue the same command: netstat -r. In the "bridged" mode, the 0.0.0.0 route should have the gateway's IP address to be the default gateway on your LAN (the same one that your Mac has as its default gateway -- this may be the inside interface of your firewall). If your guest OS is in the "NAT" mode, the gateway on the 0.0.0.0 route should be the IP address configured on vmnet8 on your Mac. You can see what that address is if you issue the ifconfig command on your Mac. If you switch between the "bridged' mode and the "NAT" in VMWare Fusion, you would have to reacquire the IP address on your guest OS (Windows), by using the following commands:

ipconfig /release

ipconfig /renew

Re: Scripts to manage Fusion network settings

tramahound — Wed, 24 Dec 2008 16:48:42 GMT

I don't know if this is off topic, but I thought this would be the best place to pose the question. In the documentation it states;

Do NOT remove the vmnet0, vmnet1
and vmnet8 adapters. Doing so will cause the VMware daemons for
networking to fail. It is OK to change the IP addresses.

I'm having an issue at work where the virtual interfaces (VMNET1 & 8) are causing traffic and logging issues on our cisco firewall which is turning up the heat for me from my Mac hating boss. It seems that the 192.168.x.x addresses are being advertised which causes traffic on our network for such things as CIFS and SMB. To try and get around this I installed NoobProof and denied those protocols and more. This appeased my boss, but not for long. Now he's working on cleaning up our junked up cisco firewall logs and found that a lot of machines on my subnet are trying to connect to my machine's 192.168.x.x address on vmnet8 which is NAT right? I don't know why this would be and how to stop it but I turned to the command 'sudo killall vmnet-netifup' to get rid of both vmnet1 and 8. I assume they will respawn once I reboot, but for now it bought me some time. I was looking into using the scripts mentioned here in order to further neuter my Fusion install and make my boss happy, but was worried about the implications of doing so based on the above comment. Is my killall command actually removing them or just disabling them? And is it even possible using these scripts to disable them each and every time I reboot?

Any and all help would be appreciated since I would really prefer using my 8 core Mac Pro over a dinky HP desktop at work!

Re: Scripts to manage Fusion network settings

sirozha — Fri, 05 Dec 2008 16:52:39 GMT

Dave,

Thanks for your work! I have tried the tokamak210b1 beta script you posted the other day, and I got it working. I did run into a few issues, though.

1. When I ran sudo ./tokamak.sh --uninstall, using the 2.0 version of your script, for some reason, I could no longer see vmnet1 or vmnet8 when issuing ifconfig. I then ran the 2.10b1 script, using the sudo ./tokamak --install command, but the virtual interfaces were still not listed by the ifcondfig command. So, I had to uninstall VMWare Fusion and then reinstall it.

2. Once I reinstalled VMWare fusion and installed tokamak210b1, I I ran sudo ./tokamak.sh --modify However, on the first run of the srcipt with the modify option it reported an error and quit. I then re-ran it with the --modify option, and it worked on the second attempt. You may want to look at this because this happens every time after a fresh installation of tokamak210b1.

3. I noticed that when you first install tokamak210b1, the script reports that the DHCP server is "not running" on vmnet1 and "disalbed" on vmnet8. Additionally, NAT "is not running" on vmnet8. I believe this behavior is incorrect because by default vmnett1 is a hostonly virtual network with DHCP enabled, and vmnet8 is a NAT virtual network, in which both DHCP and NAT should be enabled and running. However, when I ran sudo ./tokamak.sh --modify and enabled DHCP on vmnet8, the script showed that both DHCP and NAT are enabled on vment8. So, the only thing that needs to be fixed is that VMWare's defaults should be honored, in my opinion.

MB:tokamak210b1 sirozha$ sudo ./tokamak.sh --install
Password:
VM@Work Tokamak 2.1.0: Installer started
VM@Work Tokamak 2.1.0: Stop daemons and kexts
VM@Work Tokamak 2.1.0: Create backup folders
VM@Work Tokamak 2.1.0: Save original files
VM@Work Tokamak 2.1.0: Set boot script
VM@Work Tokamak 2.1.0: Display settings
The following virtual networks have been defined:

. vmnet1 is a host-only network on private subnet 192.168.208.0.
. vmnet8 is a NAT network on private subnet 192.168.102.0.

VM@Work Tokamak 2.1.0: Extended network scripting - Dave Parsons
Host-only/NAT networking on vmnet1 using 192.168.208.1/255.255.255.0 is not running
DHCP server on vmnet1 is not running
NAT networking on vmnet1 is disabled
Host-only/NAT networking on vmnet8 using 192.168.102.1/255.255.255.0 is not running
DHCP server on vmnet8 is disabled
NAT networking on vmnet8 is not running
VM@Work Tokamak 2.1.0: Installer completed

The above results are with the full version (not trial) of VMWare Fusion 2.0.1 and tokamak210b1. There's an option now to disable DHCP on the hostonly and nat vmnets when you run the script with the --modify option. I chose not to use DHCP on vmnet1 when I ran ./tokamak.sh --modify, and the script reported that DHCP is disabled on vmnet1. I have not verified if it is in fact disabled.

4. The task that I have at hand is to run a Cisco Unified Communications Manager (CUCM) 6.1 under VMWare Fusion. Sometimes, I need the environment to be hostonly (when I am not connected to any network). Other times, if I am on a wireless network, I need the environment to be bridged to the Airport inteface on my Mac, which is en1. Another requirement is that the IP range in both of these environments should remain the same (namely, 192.168.200.0 255.255.255.0), which is needed in order for the CUCM to keep the same IP address and default gateway regardless of which environment it currently is (+bridged+ or +hostonly+).

By default, vmnet1 is bridged to en0, which is the Gigabit Ethernet NIC on my Mac. I was able to change the bridge that vmnet1 uses to en1 (Airport), using your script. However, what I noticed is that if I switch the virtual machine running the CUCM from hostonly to bridged (using Fusion's GUI), I can ping hosts on the network as well as my Mac's Airport IP address from the CUCM. If I switch the virtual machine's interface from bridged to hostonly (using Fusion's GUI), I cannot ping interface vmnet1 on my Mac. I tried to turn the Airport card off in Mac OS and even use sudo ifconfig en1 down, but I still couldn't ping interface vmnet1 from the CUCM. This seems to result from the Mac's routing table not being updated correctly when switching the environment from bridged to hostonly using Fusion's GUI, and may very well be a bug in Fusion. This becomes obvious when you issue the netstat -r command after you switch from bridged to hostonly in Fusion's GUI. The routing table fails to use interface vmnet1 for the route to 192.168.200.0/24. What I had to do is to issue sudo ifconfig vmnet1 down followed by sudo ifconfig vmnet1 up. Only after that my hostonly environment starts working again, and the routing table reflects the fact that packets to 192.168.200.0/24 are routed via interface vmnet1.

Even though I am not planning to run Windows under VMWare Fusion, I would like to understand how VMWare users are expected to install Windows on their Macs and be able to bridge to WiFi interfaces without resorting to Dave's tokamak script. Obviously, users of VMWare products for Windows and Linux don't have this problem because the ability to change the bridge to any physical interface is already in the GUI of those products.

5. When troubleshooting connectivity, pinging the Host's virtual interfaces (+vmnetX+) from the VMWare Guest OS's interface doesn't work if the Mac OS' firewall is enabled and the stealth mode is on. To fix the connectivity, the stealth mde should be turned off or the firewall should be disabled altogether. This appears to be a shortcoming of the Mac OS' GUI firewall. Apple should have provided an option to disable the stealth mode for the hosts located on the same subnet but to keep the stealth mode for all other hosts in the GUI of the firewall. I don't know if other types of TCP/IP connections (besides ICMP) are allowed in the inbound direction to the virtual interfaces (+vmnetX+ interfaces) when the stealth mode is enabled -- I have not yet tested this scenario.

So, the following issues still need fixing:

a. VMWare DHCP server and NAT defaults for vmnet1 and vmnet8 should be honored when tokamak is first installed, in my opinion.

b. A fix needs to be implemented for the first run of tokamak.sh --modify to prevent it from quiting with an error message.

c. It seems that at the end of the session when tokamak is used with the --modify option, the script prompts to enter yes or no as the response to whether or not the user wants to continue editing the settings. However, the script only accepts y or n. It does not accept yes or no.

d. It would be nice to get the ability to assign custom IP addresses to interfaces vmnetX instead of having to stick to .1 in the fourth octet of the IP address assigned to the Mac's virtual interface created by VMWare. When I tried to assign 192.168.200.100 to interface vmnet1, using tokamak 210b1, even though the script didn't complain, the IP address assigned to vmnet1 was 192.168.200.1

e. Consider the possibility of bypassing the Mac OS' firewall in the hostonly environment because there's no reason for the firewall to protect a virtual interface from the guest OS if there's no bridging going on to the physical interface, and hence, there's no external threat. I don't know if this is something that could be done at the tokamak level of if this is something that VMWare should consider implementing in their next release of VMWare Fusion.

Re: Scripts to manage Fusion network settings

WoodyZ — Wed, 03 Dec 2008 20:32:26 GMT

sirozha wrote: One thing, though. How do I uninstall the previous version of the script?

If you read the documentation it will tell you!

Advanced Networking Configuration - Tokamak Networking Scripts for VMware Fusion

Also in the VM@Work Tokamak.pdf file that is in the tokamak200.zip you downloaded.

Re: Scripts to manage Fusion network settings

sirozha — Wed, 03 Dec 2008 20:17:40 GMT

Dave,

I just came back from the holidays, so I will try your beta script within the next few days. One thing, though. How do I uninstall the previous version of the script?

Thanks!

Re: Scripts to manage Fusion network settings

DaveP — Mon, 01 Dec 2008 19:19:37 GMT

If anyone wants to try it I have uploaded a beta of 2.1.0. Now you can specify DHCP use for both hostonly and nat virtual interfaces. I haven't yet worked out whether this is a good or bad things and how it impacts guests, so if you are interested try it and let me konw how it goes. I'll then write up some scenarios and publish.

NOTE:
Before installing please ensure that you:

1. Uninstall any previous version as locations database has changed slightly
2. VMware is not running when you do this

Dave

Re: Scripts to manage Fusion network settings

DaveP — Wed, 26 Nov 2008 19:09:46 GMT

I need to alter both the tokamak-config-net.pl and tokamak-boot.sh scripts to allow DHCP to be selected separately. I am now working on the code and hopefully will have a new version available sometime over the weekend. Hope that helps you out.

Re: Scripts to manage Fusion network settings

sirozha — Wed, 26 Nov 2008 00:10:53 GMT

Dave,

I am attaching both of my locations files; the first one is from the tokamak directory, and the second one if from the /Library/Application Support/VMWare Fusion/

Of course I can wait for these scripts. Thanks for doing this.

By the way, have you tried Parallels Desktop 4.0 yet? I heard it beats VMWare Fusion 2.0 on speed. There's a review on informatin week:

http://www.informationweek.com/news/personal_tech/reviews/showArticle.jhtml?articleID=212100002&pgno=4&queryText=&isPrev=

What I am interested in is how Parallels Desktop 4.0 handles the tasks of changing ip addresses on virtual networks and DHCP issues on host-only and NATed networks.

Re: Scripts to manage Fusion network settings

DaveP — Tue, 25 Nov 2008 19:34:13 GMT

Hi

I've used both Parallels and VMware products on all three platforms, Windows, Linux and Mac OS X and have to say VMware beats Parallels every time for stability and speed for the sorts of things I do. As for the scripts, I will have another look at them. Maybe the underlying issues have gone away in the DHCP and NAT daemons. There are other ways to tailor the system, by directly editing the boot.sh script, and even hard coding values in there. However, I would like to see if there is something I can do in the scripts to make them more useful.

So to summarize your requirements:

1. Create additional VMnets
2. Tailor IP and subnet masks
3. Decide on DHCP and NAT for each interface - which is currently the problem

I'll also look at the one liner patch above for the tokamak-boot.sh BASH script. Hope we can get everything sorted out.

Dave

Update: OK by manually entering the following commands I was able to get what you wanted:

./vmnet-dhcpd -cf "/Library/Application Support/VMware Fusion/vmnet8/dhcpd.conf" -lf /var/db/vmware/vmnet-dhcpd-vmnet8.leases -pf /var/run/vmnet-dhcpd-vmnet8.pid vmnet8
./vmnet-natd -c "/Library/Application Support/VMware Fusion/vmnet8/nat.conf" -m "/Library/Application Support/VMware Fusion/vmnet8/nat.mac" -d /var/run/vmnet-natd-vmnet8.pid vmnet8
./vmnet-netifup -d /var/run/vmnet-netif-vmnet8.pid vmnet8 vmnet8
ifconfig vmnet8 inet 172.16.8.1 netmask 255.255.255.0
./vmnet-netifup -d /var/run/vmnet-netif-vmnet1.pid vmnet1 vmnet1
ifconfig vmnet1 inet 172.16.1.1 netmask 255.255.255.0

This gives the following output:

VM@Work Tokamak 2.0.0: Extended network scripting - Dave Parsons
Host-only/NAT networking on vmnet1 using 172.16.1.1/255.255.255.0 is running
DHCP server on vmnet1 is not running
Host-only/NAT networking on vmnet8 using 172.16.8.1/255.255.255.0 is running
DHCP server on vmnet8 is running
NAT networking on vmnet8 is running

Now to see how to code this into the scripts. It may well be as simple as the one line fix, but will check it out over the next day or so. Hopefully you can wait a day?

Re: Scripts to manage Fusion network settings

sirozha — Tue, 25 Nov 2008 19:12:44 GMT

Dave,

Thanks for your response. I will post the files you requested from home tonight.

The version of Mac OS is 10.5.5 (the latest version with all the updates).

The version of VMWare Fusion is the latest trial available on the VMWare site.

I am still trying to decide between VMWare and Parallels. I need to run virtual machines for my VoIP lab to use Cisco voice servers as guest OSes. I will also be running VMWare Server for Linux on a stationary server, so I would rather stick with Fusion for I hear a lot of code is the same on the Linux and the Mac platforms, so the trouble shooting should be easier if I run VMWare on both my Mac and the Intel server. However, the lack of functionality to add, remove, or modify VMNets, to enable or disable the DHCP server and NAT, etc. in VMWare Fusion is holding me back from purchasing VMWare Fusion. I need to make sure that all the tasks that I need to do with my virtual machines can be accomplished in VMWare Fusion with these scripts before I purchase VMWare Fusion. So far, I have not had any need to install Windows on my Mac, and my goals are a little more demanding than just running Windows under VMWare Fusion.

I have not yet tried Paralles for the same purpose, but I have heard that Parallel's GUI has a lot more options to modify virtual networks than Fusion's GUI. I just wish VMWare would bring Fusion up to par with VMWare Workstation for Linux and for Windows.

Re: Scripts to manage Fusion network settings

DaveP — Tue, 25 Nov 2008 17:19:30 GMT

It's an issue with VMware Fusion. I should add a note to that effect. Disabling one seems to disable the other. I will do some new tests on Fusion 2.0.1, but this behavior has been seen in all releases of Fusion until now. But if you can answer the other questions we may also have a issue with the way your locations files are being built.

Re: Scripts to manage Fusion network settings

DaveP — Tue, 25 Nov 2008 15:55:36 GMT

Guys

I'll be home soon to check this out my Mac. Sorry haven't been around, but work's been busy. Before I get home can you post:

1. locations file from tokamak backup directory
2. locations file from /Library/Application Support/VMware Fusion directory
3. Version of VMware being used
4. Veriosn of Mac OS X being used

Note that tokamak.sh does not directly modify the locations file, that is done by the Perl file which is primarily VMware code (Fusion plus a touch of the Linux version).

Re: Scripts to manage Fusion network settings

sirozha — Tue, 25 Nov 2008 14:19:18 GMT

Andrew,

I found the locations file in the tokamak200/current directory, and I looked at every instance of answer VNET_1_DHCP yes

It appears that this locations file also keeps track of every time you modify a VMNet, using the tokamak.sh script.

When I run ./tokamak.sh --modify even if I don't modify anything, the last few lines of the script report that:

Host-only/NAT networking on vmnet1 using 192.168.200.1/255.255.255.0 is running
DHCP server on vment1 is not running

Host-only/NAT networking on vmnet8 using 192.168.225.1/255.255.255.0 is running
DHCP server on mnet8 is not running
NAT networking on vmnet8 is running

Even though all instances of VNET_1_DHCP in the locations file are as follows:
answer VNET_1_DHCP yes

So, why doesn't *tokamak.sh *pay any attention to *answer VNET_1_DHCP yes *?

Thanks!

Re: Scripts to manage Fusion network settings

andrewwillis — Tue, 25 Nov 2008 13:23:08 GMT

sirozha, I wasn't that clear about which locations file to edit. The tokamak.sh script keeps a copy of this file in the current directory (located in the same place as the tokamak.s script itself). When you run tokamak.sh --reapply, it copies the version stored in current to /Library/Application Support/VMware Fusion/. This is what was recreating the locations file that you saw.

-Andrew

Re: Scripts to manage Fusion network settings

Technogeezer — Tue, 25 Nov 2008 02:39:42 GMT

Yes, tokamak-boot.sh does indeed care what's in the locations file. tokamak-boot.sh, tokamak-config-net.pl, and the locations file are all interrelated:

While I'm not an expert on the VMware Workstation for Linux scripts that Tokamak was based on, I've looked at the tokamak scripts extensively. it looks to me like:

The locations file is the virtual networking configuration database.

The locations file serves as input to tokamak-config-net.pl which allows the modification of virtual network settings. This program is what gets invoked by tokamak.sh --modify. Note that any changes you make here are appended to the locations file, (which matches your observation about it looking like a log).

tokamak-config-net.pl creates the /Library/Application Support/VMware Fusion/vmnet directories, and the configuration files within them for the Fusion natd and dhcpd.

tokamak-boot.sh reads the locations file database as one of its first actions when it's invoked. Since the locations file has the information about vmnet type (bridged/hostonly/nat), the IP addresses and subnets, and whether to run the DHCP server or not, tokamak-boot.sh uses this information to start/stop the right Fusion background processes with the right options.

If you look carefully, you'll see that entries seem to get repeated in the file each time you modify the virtual network config. What I've found is that when there are multiple incarnations of a setting within the locations file, it's the last one that's meaningful.

Re: Scripts to manage Fusion network settings

sirozha — Tue, 25 Nov 2008 02:09:37 GMT

Actually, I don't think the documentation is saying that you cannot change the subnet IP addressing on VMNet1. I thought it says you should not remove VMNet1 or VMNet8. Please correct me if I am wrong.

So, my question was about what exactly the locations file does in relation to the modified tokamak-boot.sh

From what I observed, the tokamak-boot.sh script pays no attention to what is specified in the locations file. In fact, when you look at the content of the locations file, it looks more like a log of the tokamak.sh script. For example, if you run ./tokamak-sh --modify three times, the lines specific to each VMNet will be listed three times there.

I hope someone can answer this question.

Thanks.

Re: Scripts to manage Fusion network settings

WoodyZ — Mon, 24 Nov 2008 20:16:16 GMT

Have a look at: Plain Text Markup Help

Now it's screwing with me!

Message was edited by: WoodyZ

Re: Scripts to manage Fusion network settings

WoodyZ — Mon, 24 Nov 2008 20:25:10 GMT

sirozha it is suggested and recommended that you not modify the default vmets vmnet1 and vmnet8 (motley vmnet1) and rather that you add additional vmnets and configure accordingly and edit the target Virtual Machine's .vmx configuration file to support the newly created vmnet. I'm not saying you can edit vmnet1 but the documentation suggests not doing so for a good reason. Maybe you'd be better off uninstalling VM@Work Tokamak 2.0.0 to restored the default settings and then reinstall it and create a new vmnet vs modifying an existing one. Just a thought.

Re: Scripts to manage Fusion network settings

sirozha — Mon, 24 Nov 2008 19:19:19 GMT

Andrew,

I followed your instructions, and after I run ./tokamak.sh --modify, and set up the ip address on Vmnet 1 to the subnet that I need, upon exit the script is reporting:

Host-only/NAT networking on vmnet1 using 192.168.200.1/255.255.255.0 is running
DHCP server on vmnet1 is not running

This happens independantly of the locations file. In fact, I had deleted the locations file from /Library/Applications Support/VMware Fusion, and after I re-ran ./tokamak.sh --modify, the system created a new locations file. I have the following listed in the locations file:

remove_answer VNET_1_DHCP
answer VNET_1_DHCP yes

So, why do I need to edit to locations file in the first place since the script is not paying any attention to the answer VNET_1_DHCP yes line?

I noticed another thing after I made the change to the tokamak-boot.sh file per your instructions and re-ran ./tokamak.sh --modify. Tokamak is now reporting that DHCP server on vmnet8 is not running. After the locations files was recreated by the system, I did not edit it, so why is DHCP turned off on VMnet8? Since this is a NATed vmnet, DHCP is needed on it. Am I doing something wrong? If not, is it possible to control which VMNets will have DHCP disabled and which ones will continue to have it enabled?

Thanks!

Re: Scripts to manage Fusion network settings

andrewwillis — Sat, 22 Nov 2008 12:31:20 GMT

I had a similar need to be able to turn off the DHCP server on one of the NATed vnets. I made a small update to the tokamak-boot.sh script that allows for DHCP to be disabled in this situation.

The update is to line 660 (at least on version 2.0.0 of the scripts). Change that line to be:

if \[ \( "$dhcp" = 'yes' -o "$nat" = 'yes' \) -a "$dhcp" != 'no' \]; then

(You will have to remove the \ characters before the open and close square brackets. I put them in because the forum software was messing the code up without them)

Once you've done that, you can then turn off the DHCP server for one of the vnets by adding the following line to the locations file:

answer VNET_2_DHCP no
You'll need to change the number fo the vnet to you situation.