<?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 - IPv6+Bridged+Wireless</title>
    <link>http://communities.vmware.com/community/vmtn/desktop/fusion?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Fri, 22 May 2009 05:41:06 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-05-22T05:41:06Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: IPv6+Bridged+Wireless</title>
      <link>http://communities.vmware.com/message/1259298?tstart=0#1259298</link>
      <description>This appears to still be broken in the latest version of Fusion. Kind of annoying to have to plug into the wall to use IPv6 from a guest.</description>
      <pubDate>Fri, 22 May 2009 05:41:06 GMT</pubDate>
      <author>BobVeznat</author>
      <guid>http://communities.vmware.com/message/1259298?tstart=0#1259298</guid>
      <dc:date>2009-05-22T05:41:06Z</dc:date>
      <clearspace:dateToText>6 months, 5 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: IPv6+Bridged+Wireless</title>
      <link>http://communities.vmware.com/message/1106346?tstart=0#1106346</link>
      <description>Sorry, I can't say. VMware policy is to not comment on unannounced products, features, or timelines.</description>
      <pubDate>Sun, 23 Nov 2008 05:25:59 GMT</pubDate>
      <author>etung</author>
      <guid>http://communities.vmware.com/message/1106346?tstart=0#1106346</guid>
      <dc:date>2008-11-23T05:25:59Z</dc:date>
      <clearspace:dateToText>1 year, 14 hours ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: IPv6+Bridged+Wireless</title>
      <link>http://communities.vmware.com/message/1106303?tstart=0#1106303</link>
      <description>&lt;br /&gt;
With the ramp up in IPv6 deployment, can we get an update for this bug? Cloud computing environments running VMWare really require this to be working.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Andrew</description>
      <pubDate>Sun, 23 Nov 2008 04:55:06 GMT</pubDate>
      <author>andrew101</author>
      <guid>http://communities.vmware.com/message/1106303?tstart=0#1106303</guid>
      <dc:date>2008-11-23T04:55:06Z</dc:date>
      <clearspace:dateToText>1 year, 14 hours ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Re: IPv6+Bridged+Wireless</title>
      <link>http://communities.vmware.com/message/935079?tstart=0#935079</link>
      <description>&lt;div class="jive-quote"&gt;1. Is this a general restriction of the VMWARE wireless bridge implementation and will be the same across all products using IPv6 ie. Workstation, Player, Server, Fusion etc...&lt;br /&gt;
or is this problem specific to Fusion?&lt;/div&gt;
&lt;br /&gt;
It's general.&lt;br /&gt;
&lt;br /&gt;
&lt;div class="jive-quote"&gt;2. Where in the release notes is this documented?&lt;/div&gt;
&lt;br /&gt;
I don't think it is, but also wouldn't expect it to be - we can't document every single combination.&lt;br /&gt;
&lt;br /&gt;
&lt;div class="jive-quote"&gt;3. Is there an open bug report against this?&lt;/div&gt;
&lt;br /&gt;
Yes, 26078.</description>
      <pubDate>Mon, 05 May 2008 18:48:28 GMT</pubDate>
      <author>etung</author>
      <guid>http://communities.vmware.com/message/935079?tstart=0#935079</guid>
      <dc:date>2008-05-05T18:48:28Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Re: IPv6+Bridged+Wireless</title>
      <link>http://communities.vmware.com/message/935038?tstart=0#935038</link>
      <description>Can someone tell me &lt;br /&gt;
1. Is this a general restriction of the VMWARE wireless bridge implementation and will be the same across all products using IPv6 ie. Workstation, Player, Server, Fusion etc...&lt;br /&gt;
or is this problem specific to Fusion?&lt;br /&gt;
2. Where in the release notes is this documented?&lt;br /&gt;
3. Is there an open bug report against this?&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
&lt;br /&gt;
Adrian</description>
      <pubDate>Mon, 05 May 2008 18:06:07 GMT</pubDate>
      <author>adrianm</author>
      <guid>http://communities.vmware.com/message/935038?tstart=0#935038</guid>
      <dc:date>2008-05-05T18:06:07Z</dc:date>
      <clearspace:dateToText>1 year, 6 months ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Re: IPv6+Bridged+Wireless</title>
      <link>http://communities.vmware.com/message/917526?tstart=0#917526</link>
      <description>&lt;div class="jive-quote"&gt;Will this be resolved in the future?&lt;/div&gt;
&lt;br /&gt;
Sorry, I can't say. VMware policy is to not comment on unannounced products, features, or timelines.</description>
      <pubDate>Thu, 17 Apr 2008 01:47:38 GMT</pubDate>
      <author>etung</author>
      <guid>http://communities.vmware.com/message/917526?tstart=0#917526</guid>
      <dc:date>2008-04-17T01:47:38Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Re: IPv6+Bridged+Wireless</title>
      <link>http://communities.vmware.com/message/917501?tstart=0#917501</link>
      <description>At least I know whats going on then.  Will this be resolved in the future?</description>
      <pubDate>Thu, 17 Apr 2008 01:39:02 GMT</pubDate>
      <author>slushpupie</author>
      <guid>http://communities.vmware.com/message/917501?tstart=0#917501</guid>
      <dc:date>2008-04-17T01:39:02Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Re: IPv6+Bridged+Wireless</title>
      <link>http://communities.vmware.com/message/917265?tstart=0#917265</link>
      <description>This is a known issue, IPv6 is not expected to work over a wireless bridge.</description>
      <pubDate>Wed, 16 Apr 2008 21:05:30 GMT</pubDate>
      <author>etung</author>
      <guid>http://communities.vmware.com/message/917265?tstart=0#917265</guid>
      <dc:date>2008-04-16T21:05:30Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>IPv6+Bridged+Wireless</title>
      <link>http://communities.vmware.com/message/917128?tstart=0#917128</link>
      <description>&lt;br /&gt;
So I recently set up Fusion 1.1.1 (72241) on 10.5.2 and one of the things I work with a lot is IPv6.  When the guest (linux or vista) is in bridged mode while using wireless, it recieves the router advertisements and configures an address for itself. I can ping the host, and other vmware guests, but it seems pings off network get lost. &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
For my testing, I have 3 OS's involved, though the same things happen with other OS's as guest or the remote host.&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;hostA is a linux box on the network&lt;/li&gt;
&lt;li&gt;hostB is my MacBookPro&lt;/li&gt;
&lt;li&gt;hostC is linux running as a guest in hostB&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
 All three have global ipv6 addresses.  hostA cannot ping hostC and viceversa. hostA and hostB can ping eachother;  hostB and hostC can ping eachother.  &lt;br /&gt;
&lt;p /&gt;
If I run tcpdump on each host, I can basicly isolate whats going on:&lt;br /&gt;
&lt;p /&gt;
When hostA pings hostC, hostA can see the neighbor solicitation it sends out, but nothing ever comes back.  hostC see's the neighbor solication from hostA, and sends a neighbor advertisement, but hostA never see's it.  Neither does hostB.&lt;br /&gt;
&lt;p /&gt;
When hostC pings hostA, hostC can see the neighbor solicitation it sends out, but nothing ever comes back.  hostA see's the neighbor solication from hostA, and sends a neighbor advertisement, but hostC never see's it.  Neither does hostB.&lt;br /&gt;
&lt;p /&gt;
As soon as I plug in a wired connection and shut off the wireless, everything works great.  Can anyone else verify this behavior? I know vmware in the past has had difficulty with wireless devices (due to the nature of wireless devices) so this might be a limitation, but I was not able to find anything in the documentation saying it should be. These same sort of tests running ipv4 work fine, which makes me think the vmware kernel module has some special logic on wireless adapters for handling ipv4, and just has no consideration for ipv6.</description>
      <pubDate>Wed, 16 Apr 2008 19:35:47 GMT</pubDate>
      <author>slushpupie</author>
      <guid>http://communities.vmware.com/message/917128?tstart=0#917128</guid>
      <dc:date>2008-04-16T19:35:47Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
    </item>
  </channel>
</rss>

