{"id":248,"date":"2018-11-17T14:16:08","date_gmt":"2018-11-17T19:16:08","guid":{"rendered":"http:\/\/myblog.vindaloo.com\/?p=248"},"modified":"2018-11-17T14:19:06","modified_gmt":"2018-11-17T19:19:06","slug":"changing-vmware-fusion-network-settings","status":"publish","type":"post","link":"http:\/\/myblog.vindaloo.com\/?p=248","title":{"rendered":"Changing VMware Fusion network settings"},"content":{"rendered":"<p>For those that run VMware Fusion, the &#8220;<em>\/Library\/Preferences\/VMware Fusion&#8221;\u00a0<\/em> directory on the Mac is a wealth of information.<\/p>\n<p><code>$ cd \/Library\/Preferences\/VMware\\ Fusion\/<br \/>\n$ ls -l<br \/>\ntotal 40<br \/>\n-r--r--r--   1 root  wheel   31 Nov 17 11:01 lastLocationUsed<br \/>\n-rw-r--r--   1 root  wheel  548 May  5  2018 license-fusion-100-e3-201704<br \/>\n-rw-r--r--   1 root  wheel  689 May  5  2018 license-fusion-100-e4-201704<br \/>\n-rw-r--r--   1 root  wheel  547 Dec  6  2013 license-fusion-50-e3-201202<br \/>\n-rw-r--r--   1 root  wheel  547 Apr 10  2014 license-fusion-60-e3-201303<br \/>\n-rw-r--r--   1 root  wheel  547 Oct 31  2014 license-fusion-70-e3-201404<br \/>\n-rw-r--r--   1 root  wheel  688 Oct 25  2014 license-fusion-70-e4-201404<br \/>\n-rw-r--r--   1 root  wheel  547 Jun 23  2016 license-fusion-80-e3-201505<br \/>\n-rw-r--r--   1 root  wheel  740 Nov  3 05:54 networking<br \/>\n-rw-r--r--   1 root  wheel  740 Aug  7 20:23 networking.bak.0<br \/>\ndrwxr-xr-x  10 root  wheel  340 Nov 17 11:01 thnuclnt<br \/>\ndrwxr-xr-x   4 root  wheel  136 Dec  6  2013 vmnet1<br \/>\ndrwxr-xr-x   7 root  wheel  238 Dec  6  2013 vmnet8<br \/>\n$<\/code><\/p>\n<p>The license-fusion&#8230; files have your license keys as well as other information in them. But today, the jewel for me is the <strong>networking<\/strong> file:<\/p>\n<p><code>$ cat networking<br \/>\nVERSION=1,0<br \/>\nanswer VNET_1_DHCP yes<br \/>\nanswer VNET_1_DHCP_CFG_HASH E08B... ...D0D8<br \/>\nanswer VNET_1_HOSTONLY_NETMASK 255.255.255.0<br \/>\nanswer VNET_1_HOSTONLY_SUBNET 172.a.b.0<br \/>\nanswer VNET_1_VIRTUAL_ADAPTER yes<br \/>\nanswer VNET_8_DHCP yes<br \/>\nanswer VNET_8_DHCP_CFG_HASH 2031... ...F498<br \/>\nanswer VNET_8_HOSTONLY_NETMASK 255.255.255.0<br \/>\nanswer VNET_8_HOSTONLY_SUBNET 10.c.d.0<br \/>\nanswer VNET_8_NAT yes<br \/>\nanswer VNET_8_VIRTUAL_ADAPTER yes<br \/>\n...<br \/>\n<\/code><br \/>\nThis file defines the networks that your <em>host-only<\/em> and <em>nat<\/em> network adapters use. VMware appears smart enough to avoid network collisions e.g. using 192.168.1.0\/255 for the NAT adapter at vmnet8 when that&#8217;s also the network configured on your home router.<\/p>\n<p>According to <a href=\"https:\/\/kb.vmware.com\/s\/article\/1026510\"><em>this article (VMware login required),<\/em><\/a> simply editing this file and restarting VMware Fusion&#8217;s networking component should change the dhcp setting that your machine uses. Any skilled system or network administrator should be able to get their hands around that.<\/p>\n<p>Finally, the lines that specify DHCP hashes appear to be the mechanism that VMware uses to detect changes in the networking file. If you dig deeper, there&#8217;s a directory for vmnet1.<\/p>\n<pre><code>$ ls -l vmnet1\r\ntotal 8\r\n-rw-r--r--  1 root  wheel  1575 Nov 17 11:01 dhcpd.conf\r\n-rw-r--r--  1 root  wheel  1575 Nov 17 11:01 dhcpd.conf.bak\r\n$ cat vmnet1\/dhcpd.conf\r\n# Configuration file for ISC 2.0 vmnet-dhcpd operating on vmnet1.\r\n#\r\n# This file was automatically generated by the VMware configuration program.\r\n# See Instructions below if you want to modify it.\r\n#\r\n# We set domain-name-servers to make some DHCP clients happy\r\n# (dhclient as configured in SuSE, TurboLinux, etc.).\r\n# We also supply a domain name to make pump (Red Hat 6.x) happy.\r\n#\r\n\r\n###### VMNET DHCP Configuration. Start of \"DO NOT MODIFY SECTION\" #####\r\n# Modification Instructions: This section of the configuration file contains\r\n# information generated by the configuration program. Do not modify this\r\n# section.\r\n# You are free to modify everything else. Also, this section must start\r\n# on a new line\r\n# This file will get backed up with a different name in the same directory\r\n# if this section is edited and you try to configure DHCP again.\r\n\r\n# Written at: 11\/17\/2018 11:01:21\r\nallow unknown-clients;\r\ndefault-lease-time 1800; # default is 30 minutes\r\nmax-lease-time 7200; # default is 2 hours\r\n\r\nsubnet 172.a.b.0 netmask 255.255.255.0 {\r\nrange 172.a.b.128 172.a.b.254;\r\noption broadcast-address 172.a.b.255;\r\noption domain-name-servers 172.a.b.1;\r\noption domain-name localdomain;\r\ndefault-lease-time 1800; # default is 30 minutes\r\nmax-lease-time 7200; # default is 2 hours\r\n}\r\nhost vmnet1 {\r\nhardware ethernet 00:50:56:x:y:z;\r\nfixed-address 172.a.b.1;\r\noption domain-name-servers 0.0.0.0;\r\noption domain-name \"\";\r\n}\r\n####### VMNET DHCP Configuration. End of \"DO NOT MODIFY SECTION\" #######\r\n$<\/code><\/pre>\n<p>&nbsp;<\/p>\n<p>This is just a standard dhcpd.conf file as you would see if you ran isc-dhcpd. The interesting thing is that the hash is what you get if you do this:<br \/>\n<code>$ sed -ne '\/VMNET DHCP.*Start\/,\/VMNET DHCP.*End\/ p' vmnet1\/dhcpd.conf | shasum<br \/>\ne08b... ...d0d8  -<\/code><\/p>\n<p><i>The more you know&#8230;<\/i><\/p>\n","protected":false},"excerpt":{"rendered":"<p>For those that run VMware Fusion, the &#8220;\/Library\/Preferences\/VMware Fusion&#8221;\u00a0 directory on the Mac is a wealth of information. $ cd \/Library\/Preferences\/VMware\\ Fusion\/ $ ls -l total 40 -r&#8211;r&#8211;r&#8211; 1 root wheel 31 Nov 17 11:01 lastLocationUsed -rw-r&#8211;r&#8211; 1 root wheel 548 May 5 2018 license-fusion-100-e3-201704 -rw-r&#8211;r&#8211; 1 root wheel 689 May 5 2018 license-fusion-100-e4-201704 -rw-r&#8211;r&#8211; &hellip; <\/p>\n<p class=\"link-more\"><a href=\"http:\/\/myblog.vindaloo.com\/?p=248\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Changing VMware Fusion network settings&#8221;<\/span><\/a><\/p>\n","protected":false},"author":54,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[24],"tags":[],"class_list":["post-248","post","type-post","status-publish","format-standard","hentry","category-vmware"],"_links":{"self":[{"href":"http:\/\/myblog.vindaloo.com\/index.php?rest_route=\/wp\/v2\/posts\/248","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/myblog.vindaloo.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/myblog.vindaloo.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/myblog.vindaloo.com\/index.php?rest_route=\/wp\/v2\/users\/54"}],"replies":[{"embeddable":true,"href":"http:\/\/myblog.vindaloo.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=248"}],"version-history":[{"count":4,"href":"http:\/\/myblog.vindaloo.com\/index.php?rest_route=\/wp\/v2\/posts\/248\/revisions"}],"predecessor-version":[{"id":252,"href":"http:\/\/myblog.vindaloo.com\/index.php?rest_route=\/wp\/v2\/posts\/248\/revisions\/252"}],"wp:attachment":[{"href":"http:\/\/myblog.vindaloo.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=248"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/myblog.vindaloo.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=248"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/myblog.vindaloo.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=248"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}