<?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: Using mod_proxy to convert a legacy IPv4 web site to IPv6</title>
	<atom:link href="http://signal.eu.org/blog/2007/10/15/using-mod_proxy-to-convert-a-legacy-ipv4-web-site-to-ipv6/feed/" rel="self" type="application/rss+xml" />
	<link>http://signal.eu.org/blog/2007/10/15/using-mod_proxy-to-convert-a-legacy-ipv4-web-site-to-ipv6/</link>
	<description>voie libre ou appel système</description>
	<pubDate>Fri, 21 Nov 2008 11:09:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Fabrice</title>
		<link>http://signal.eu.org/blog/2007/10/15/using-mod_proxy-to-convert-a-legacy-ipv4-web-site-to-ipv6/#comment-5671</link>
		<dc:creator>Fabrice</dc:creator>
		<pubDate>Tue, 27 Nov 2007 08:53:04 +0000</pubDate>
		<guid isPermaLink="false">http://signal.eu.org/blog/2007/10/15/using-mod_proxy-to-convert-a-legacy-ipv4-web-site-to-ipv6/#comment-5671</guid>
		<description>Hello,

For information, an application using the same proxy technique is online at http://www.v6proxy.com.

Fabrice.</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>For information, an application using the same proxy technique is online at <a href="http://www.v6proxy.com" rel="nofollow">http://www.v6proxy.com</a>.</p>
<p>Fabrice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pierre</title>
		<link>http://signal.eu.org/blog/2007/10/15/using-mod_proxy-to-convert-a-legacy-ipv4-web-site-to-ipv6/#comment-3873</link>
		<dc:creator>Pierre</dc:creator>
		<pubDate>Mon, 15 Oct 2007 00:00:41 +0000</pubDate>
		<guid isPermaLink="false">http://signal.eu.org/blog/2007/10/15/using-mod_proxy-to-convert-a-legacy-ipv4-web-site-to-ipv6/#comment-3873</guid>
		<description>&lt;b&gt;OB&lt;/b&gt;: You can't use simple NAT since we're talking about converting IPv4  IPv6. So you need more than NAT in any case. Doing IPv4  IPv6 "on the wire" would be a bit tough on the hardware (or even kernel, if that's what you had in mind) and I don't see this usable outside of a lab, at least because of logging requirements, not to mention virtual host handling and various other HTTP tricks we might need to pull. So application-level proxying looks like the logical answer, and that's what we're doing.</description>
		<content:encoded><![CDATA[<p><b>OB</b>: You can&#8217;t use simple NAT since we&#8217;re talking about converting IPv4  IPv6. So you need more than NAT in any case. Doing IPv4  IPv6 &#8220;on the wire&#8221; would be a bit tough on the hardware (or even kernel, if that&#8217;s what you had in mind) and I don&#8217;t see this usable outside of a lab, at least because of logging requirements, not to mention virtual host handling and various other HTTP tricks we might need to pull. So application-level proxying looks like the logical answer, and that&#8217;s what we&#8217;re doing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OB</title>
		<link>http://signal.eu.org/blog/2007/10/15/using-mod_proxy-to-convert-a-legacy-ipv4-web-site-to-ipv6/#comment-3871</link>
		<dc:creator>OB</dc:creator>
		<pubDate>Sun, 14 Oct 2007 23:49:27 +0000</pubDate>
		<guid isPermaLink="false">http://signal.eu.org/blog/2007/10/15/using-mod_proxy-to-convert-a-legacy-ipv4-web-site-to-ipv6/#comment-3871</guid>
		<description>Why not do this at the network layer level using simple NAT?</description>
		<content:encoded><![CDATA[<p>Why not do this at the network layer level using simple NAT?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
