<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: IPv6</title>
	<atom:link href="http://blog.firetech.nu/comp/ipv6/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.firetech.nu/comp/ipv6/</link>
	<description>The Public Mind of Yet Another Computer Geek</description>
	<pubDate>Sun, 05 Feb 2012 07:39:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: firetech</title>
		<link>http://blog.firetech.nu/comp/ipv6/#comment-1556</link>
		<dc:creator>firetech</dc:creator>
		<pubDate>Wed, 27 May 2009 06:16:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.firetech.nu/?p=52#comment-1556</guid>
		<description>So THAT's how it's working!
I wondered when the traffic back to me was converted, and got a little confused there. Thanks for the heads up! :)

I also saw you posted your comment from an IPv6 address, the IPv6 Internet has a few hosts anyway. :)</description>
		<content:encoded><![CDATA[<p>So THAT&#8217;s how it&#8217;s working!<br />
I wondered when the traffic back to me was converted, and got a little confused there. Thanks for the heads up! :)</p>
<p>I also saw you posted your comment from an IPv6 address, the IPv6 Internet has a few hosts anyway. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://blog.firetech.nu/comp/ipv6/#comment-1555</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Wed, 27 May 2009 03:31:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.firetech.nu/?p=52#comment-1555</guid>
		<description>"It turned out that traffic from those sites, unlike all the other ones I tested, were sent as IPv4 packets directly to me and not coming in through the tunnel interface."

The problem you encountered is that not all 6to4 packets arrive with a source address of 192.88.99.1.  6to4 uses anycast in both directions: 192.88.99.0/24 for v4-&#62;v6, and 2002::/16 for v6-&#62;v4.  So, it's mostly unpredictable which v6-&#62;v4 gateway your return packets will come through.  Some of them set their source address to 192.88.99.1, but some use a "real" IPv4 address, and that difference will confuse your IPv4 firewall.

Your solution is correct, though.</description>
		<content:encoded><![CDATA[<p>&#8220;It turned out that traffic from those sites, unlike all the other ones I tested, were sent as IPv4 packets directly to me and not coming in through the tunnel interface.&#8221;</p>
<p>The problem you encountered is that not all 6to4 packets arrive with a source address of 192.88.99.1.  6to4 uses anycast in both directions: 192.88.99.0/24 for v4-&gt;v6, and 2002::/16 for v6-&gt;v4.  So, it&#8217;s mostly unpredictable which v6-&gt;v4 gateway your return packets will come through.  Some of them set their source address to 192.88.99.1, but some use a &#8220;real&#8221; IPv4 address, and that difference will confuse your IPv4 firewall.</p>
<p>Your solution is correct, though.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

