<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - bridged mode network ip routing question</title>
    <link>http://communities.vmware.com/community/vmtn/desktop/fusion?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Wed, 23 Jan 2008 07:19:38 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-01-23T07:19:38Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: bridged mode network ip routing question</title>
      <link>http://communities.vmware.com/message/845968?tstart=0#845968</link>
      <description>Editing boot.sh worked like a charm...thanks!</description>
      <pubDate>Wed, 23 Jan 2008 07:19:38 GMT</pubDate>
      <author>halcyonic</author>
      <guid>http://communities.vmware.com/message/845968?tstart=0#845968</guid>
      <dc:date>2008-01-23T07:19:38Z</dc:date>
      <clearspace:dateToText>1 year, 10 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: bridged mode network ip routing question</title>
      <link>http://communities.vmware.com/message/845262?tstart=0#845262</link>
      <description>By default, Fusion uses whichever interface OS X tells it is the primary one. You can tell it to always use the same interface by editing /Library/Application Support/VMware Fusion/boot.sh, or by using &lt;a class="jive-link-thread" href="http://communities.vmware.com/thread/97712"&gt;How to modify Fusion network settings whitepaper&lt;/a&gt; (instructions for manual configuration) or &lt;a class="jive-link-thread" href="http://communities.vmware.com/thread/108167"&gt;Scripts to manage Fusion network settings&lt;/a&gt; (script to do the configuration for you).</description>
      <pubDate>Tue, 22 Jan 2008 14:28:13 GMT</pubDate>
      <author>etung</author>
      <guid>http://communities.vmware.com/message/845262?tstart=0#845262</guid>
      <dc:date>2008-01-22T14:28:13Z</dc:date>
      <clearspace:dateToText>1 year, 10 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: bridged mode network ip routing question</title>
      <link>http://communities.vmware.com/message/845241?tstart=0#845241</link>
      <description>Change the priority of the network interface in Mac OS and see.</description>
      <pubDate>Tue, 22 Jan 2008 14:21:30 GMT</pubDate>
      <author>Silica V</author>
      <guid>http://communities.vmware.com/message/845241?tstart=0#845241</guid>
      <dc:date>2008-01-22T14:21:30Z</dc:date>
      <clearspace:dateToText>1 year, 10 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>bridged mode network ip routing question</title>
      <link>http://communities.vmware.com/message/845040?tstart=0#845040</link>
      <description>I'm running a virtual machine under Fusion (1.1) in bridged mode on my macbook pro running Leopard.  I connect to the internet through my wireless connection.  I need to connect to a server via the wired connection.  The wired connection is on the 192.168.2.x subnet, and the wireless connection is on the 192.168.1.x subnet.&lt;br /&gt;
&lt;br /&gt;
Here's the question: I have an application that needs to communicate with the server on the 192.168.2.x subnet (at 192.168.2.2, specifically).  If I turn off the wireless connection, it works fine.  However, when I turn on the wireless connection, it stops working (and when I look at network traces, all the packets start going out on the wireless interface).&lt;br /&gt;
&lt;br /&gt;
I'm confused as to why this is happening as when I run "route get 192.168.2.2", the interface it reports for the route is the wired interface (which is where the packets &lt;u&gt;should&lt;/u&gt; be going but aren't).  Does Fusion automatically send out VM packets on whatever interface it thinks is connected to the internet?  Is there a way to control routing of packets originating from the VM?&lt;br /&gt;
&lt;br /&gt;
Any help is appreciated.&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
Nick</description>
      <pubDate>Tue, 22 Jan 2008 07:34:42 GMT</pubDate>
      <author>halcyonic</author>
      <guid>http://communities.vmware.com/message/845040?tstart=0#845040</guid>
      <dc:date>2008-01-22T07:34:42Z</dc:date>
      <clearspace:dateToText>1 year, 10 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
  </channel>
</rss>

