<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Unable to set static IP addresses on guests using non-bridged NICs in VMware Fusion Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Unable-to-set-static-IP-addresses-on-guests-using-non-bridged/m-p/2993223#M185156</link>
    <description>&lt;P&gt;That seems to work.&amp;nbsp; The one caveat is that it seems like you may need to quit and restart Fusion.&lt;/P&gt;&lt;P&gt;It would be nice if there were a way to set this through the regular UI.&lt;/P&gt;</description>
    <pubDate>Sun, 29 Oct 2023 08:36:01 GMT</pubDate>
    <dc:creator>ToddDTaft</dc:creator>
    <dc:date>2023-10-29T08:36:01Z</dc:date>
    <item>
      <title>Unable to set static IP addresses on guests using non-bridged NICs</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Unable-to-set-static-IP-addresses-on-guests-using-non-bridged/m-p/2993135#M185130</link>
      <description>&lt;P&gt;I've got Fusion 13.5 Pro on a laptop, and I'm trying to prototype a process that will configure and install several client guest machines.&lt;/P&gt;&lt;P&gt;As part of the process, it will be important the the different VM guests can reliably talk to each other, and these machines need node-to-node IP communication.&lt;/P&gt;&lt;P&gt;The problem is that I can't see any was using Fusion 13.5 on Ventura or newer to reserve "specified" IP addresses for a specific guest NIC if I use either sharing/natting or private networks.&lt;/P&gt;&lt;P&gt;So, how do I configure the system so that it can reserve IP addresses (as well as other aspects of the DHCP protocol, such as specifying default routes, lease times, etc.)???&lt;/P&gt;&lt;P&gt;This question seems to be a popular one; however none of the answers that I have found have been up to date to work.&lt;/P&gt;&lt;P&gt;Current OS is 13.6.1 but considering major version upgrade soon.&lt;/P&gt;</description>
      <pubDate>Sat, 28 Oct 2023 10:08:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Unable-to-set-static-IP-addresses-on-guests-using-non-bridged/m-p/2993135#M185130</guid>
      <dc:creator>ToddDTaft</dc:creator>
      <dc:date>2023-10-28T10:08:06Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to set static IP addresses on guests using non-bridged NICs</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Unable-to-set-static-IP-addresses-on-guests-using-non-bridged/m-p/2993168#M185139</link>
      <description>&lt;P&gt;There's not a facility in the Fusion GUI to do reserve DHCP addresses for specific VMs.&lt;/P&gt;&lt;P&gt;I've done this in the past, but it involved manually editing the dhcpd.conf for the NAT networking segment found in /Library/Preferences/VMware Fusion/vmnet8 (for the default NAT network, other vmnet directories are for either the default host-only or custom host-only networks). If I remember correctly, the VMware dhcpd is based on an older version of ISC dhcpd so using its settings to recognize hosts on a particular MAC address should work.&lt;/P&gt;&lt;P&gt;Note that if the user reconfigures the networking, the dhcpd.conf files get overwritten, and the changes will need to be manually applied again..&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 28 Oct 2023 15:54:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Unable-to-set-static-IP-addresses-on-guests-using-non-bridged/m-p/2993168#M185139</guid>
      <dc:creator>Technogeezer</dc:creator>
      <dc:date>2023-10-28T15:54:42Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to set static IP addresses on guests using non-bridged NICs</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Unable-to-set-static-IP-addresses-on-guests-using-non-bridged/m-p/2993208#M185152</link>
      <description>&lt;P&gt;That is similar to the method mentioned in an old VMWare KB article (&lt;A href="https://kb.vmware.com/s/article/1026510" target="_self"&gt;1026510&lt;/A&gt;); however that article does not indicate the solution is valid for VMWare Fusion 12 or later.&amp;nbsp; There are a variety of postings on this site and others mentioning the problem, including at least one with a response by a VMWare employee indicating that VMWare was required by Apple to discontinue use of the independent virtual DHCP server in macOS 11 (Big Sur) and later.&amp;nbsp; Unfortunately, I never saw an officially endorsed procedure for newer combinations of VMWare and macOS.&amp;nbsp; The unofficial suggestions that I saw from a few years ago (when Big Sur was new) refer to changing files that I don't have on my system, so I suspect that Apple changed something (again) after Big Sur.&lt;/P&gt;</description>
      <pubDate>Sun, 29 Oct 2023 01:04:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Unable-to-set-static-IP-addresses-on-guests-using-non-bridged/m-p/2993208#M185152</guid>
      <dc:creator>ToddDTaft</dc:creator>
      <dc:date>2023-10-29T01:04:01Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to set static IP addresses on guests using non-bridged NICs</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Unable-to-set-static-IP-addresses-on-guests-using-non-bridged/m-p/2993210#M185153</link>
      <description>&lt;P&gt;The &amp;nbsp;use of VMware's &amp;nbsp;DHCP server was discontinued briefly for Big Sur so yes, those files did not exist. And since they used Apple's implementation inobody could figure out a way to modify it to hard-wire addresses.&lt;/P&gt;&lt;P&gt;VMware did re-introduce use of their own DHCP server in Fusion 12 (not sure which release, but I know it was present in 12.2.x) when it discovered it was running on Monterey and later.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I just tried this in Fusion 13.5 running on Sonoma for a VM that was configured for NAT networking. I changed the vmnet8/dhcpd.conf below the "DO NOT MODIFY" section to hard wire the IP address for the MAC address of the VM and added the following &amp;nbsp;(my NAT segment is 172.26.101.0/24) :&lt;/P&gt;&lt;PRE&gt;&lt;SPAN&gt;host myhost {&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;/SPAN&gt;hardware ethernet xx:xx:xx:xx:xx;xx;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;/SPAN&gt;fixed-address 172.16.101.xx;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&lt;SPAN&gt;My VM picked up the hard-wired address, and not one from the DHCP range.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 29 Oct 2023 01:51:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Unable-to-set-static-IP-addresses-on-guests-using-non-bridged/m-p/2993210#M185153</guid>
      <dc:creator>Technogeezer</dc:creator>
      <dc:date>2023-10-29T01:51:50Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to set static IP addresses on guests using non-bridged NICs</title>
      <link>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Unable-to-set-static-IP-addresses-on-guests-using-non-bridged/m-p/2993223#M185156</link>
      <description>&lt;P&gt;That seems to work.&amp;nbsp; The one caveat is that it seems like you may need to quit and restart Fusion.&lt;/P&gt;&lt;P&gt;It would be nice if there were a way to set this through the regular UI.&lt;/P&gt;</description>
      <pubDate>Sun, 29 Oct 2023 08:36:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Fusion-Discussions/Unable-to-set-static-IP-addresses-on-guests-using-non-bridged/m-p/2993223#M185156</guid>
      <dc:creator>ToddDTaft</dc:creator>
      <dc:date>2023-10-29T08:36:01Z</dc:date>
    </item>
  </channel>
</rss>

