<?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 - VMWare Fusion and vlans interfaces</title>
    <link>http://communities.vmware.com/community/vmtn/desktop/fusion?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Wed, 24 Jun 2009 00:08:31 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-06-24T00:08:31Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: VMWare Fusion and vlans interfaces</title>
      <link>http://communities.vmware.com/message/1293202?tstart=0#1293202</link>
      <description>hi jnsmith,&lt;br /&gt;
I am presuming that you want to bridge to a VLAN interface created on the host. We don't support bridging to VLANs on Fusion, although we are considering adding this feature if there strong use case for it. Pls. watch out for Beta2.&lt;br /&gt;
&lt;br /&gt;
thanks!</description>
      <pubDate>Wed, 24 Jun 2009 00:08:31 GMT</pubDate>
      <author>nithinr</author>
      <guid>http://communities.vmware.com/message/1293202?tstart=0#1293202</guid>
      <dc:date>2009-06-24T00:08:31Z</dc:date>
      <clearspace:dateToText>5 months, 3 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: VMWare Fusion and vlans interfaces</title>
      <link>http://communities.vmware.com/message/1292765?tstart=0#1292765</link>
      <description>Hello, &lt;br /&gt;
&lt;br /&gt;
1. I need to connect two virtual interfaces on a single VM&lt;br /&gt;
back-to-back, similar to a crossover connection between two physical&lt;br /&gt;
ports. &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
2. I also have 802.1q running on 2 VMs but I am unable to ping between&lt;br /&gt;
the VM vlans . The ethernet port on the switch that the MAC (apple)&lt;br /&gt;
connects to is a trunk port and the VM mac addresses show up in the&lt;br /&gt;
mac-table on the switch in the relevant vlans. &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
Any ideas?&lt;br /&gt;
&lt;p /&gt;
Thanks.</description>
      <pubDate>Tue, 23 Jun 2009 17:10:36 GMT</pubDate>
      <author>nayatronix</author>
      <guid>http://communities.vmware.com/message/1292765?tstart=0#1292765</guid>
      <dc:date>2009-06-23T17:10:36Z</dc:date>
      <clearspace:dateToText>5 months, 4 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: VMWare Fusion and vlans interfaces</title>
      <link>http://communities.vmware.com/message/821327?tstart=0#821327</link>
      <description>There are details on Fusion's networking internal in Dave's excellent whitepaper: &lt;a href="http://communities.vmware.com/thread/97712" class="jive-link-thread"&gt;How to modify Fusion network settings whitepaper&lt;/a&gt;</description>
      <pubDate>Mon, 17 Dec 2007 18:41:58 GMT</pubDate>
      <author>rcardona2k</author>
      <guid>http://communities.vmware.com/message/821327?tstart=0#821327</guid>
      <dc:date>2007-12-17T18:41:58Z</dc:date>
      <clearspace:dateToText>1 year, 11 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: VMWare Fusion and vlans interfaces</title>
      <link>http://communities.vmware.com/message/821198?tstart=0#821198</link>
      <description>&lt;div class="jive-quote"&gt;&lt;span class="jive-quote-header"&gt;MandarMS wrote:&lt;/span&gt;&lt;br /&gt;
&lt;p /&gt;
Are you looking for the How to force Fusion to use a specific interface? &lt;br /&gt;
&lt;p /&gt;
&lt;span style="font-family:Verdana"&gt;&lt;span style="font-size:10pt"&gt;Refer this KB Article # 1001875 to change network connection mapping in VMware Fusion&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;a class="jive-link-external" href="http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;#38;docType=kc&amp;#38;externalId=1001875"&gt;http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;#38;docType=kc&amp;#38;externalId=1001875&lt;/a&gt;&lt;/div&gt;
&lt;p /&gt;
This no longer seems to work with Fusion 1.1.  I re-edited the boot.sh file after the upgrade and I can no longer force the VM to a specific interface.&lt;br /&gt;
&lt;br /&gt;
Anyone have it working?</description>
      <pubDate>Mon, 17 Dec 2007 16:15:26 GMT</pubDate>
      <author>jayc67</author>
      <guid>http://communities.vmware.com/message/821198?tstart=0#821198</guid>
      <dc:date>2007-12-17T16:15:26Z</dc:date>
      <clearspace:dateToText>1 year, 11 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: VMWare Fusion and vlans interfaces</title>
      <link>http://communities.vmware.com/message/821189?tstart=0#821189</link>
      <description>&lt;br /&gt;
Are you looking for the How to force Fusion to use a specific interface? &lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-family:Verdana"&gt;&lt;span style="font-size:10pt"&gt;Refer this KB Article # 1001875 to change network connection mapping in VMware Fusion&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;#38;docType=kc&amp;#38;externalId=1001875"&gt;http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;#38;docType=kc&amp;#38;externalId=1001875&lt;/a&gt;</description>
      <pubDate>Mon, 17 Dec 2007 15:50:52 GMT</pubDate>
      <author>MandarMS</author>
      <guid>http://communities.vmware.com/message/821189?tstart=0#821189</guid>
      <dc:date>2007-12-17T15:50:52Z</dc:date>
      <clearspace:dateToText>1 year, 11 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>VMWare Fusion and vlans interfaces</title>
      <link>http://communities.vmware.com/message/820071?tstart=0#820071</link>
      <description>Hello,&lt;br /&gt;
&lt;br /&gt;
I am tying to get VMWare Fusion working to work with a bridged interface to a vlan tagged (802.1q) interface on Leopard.  I can get a host only and NAT but binds to the wrong interface.  Has anyone got this to work?  I am running Vmware 1.1&lt;br /&gt;
&lt;br /&gt;
Thanks.</description>
      <pubDate>Fri, 14 Dec 2007 22:17:47 GMT</pubDate>
      <author>jnsmith</author>
      <guid>http://communities.vmware.com/message/820071?tstart=0#820071</guid>
      <dc:date>2007-12-14T22:17:47Z</dc:date>
      <clearspace:dateToText>1 year, 11 months ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
  </channel>
</rss>

