<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Source IP weirdities with irssi and IPv6</title>
	<atom:link href="http://jeremy.visser.name/2010/01/28/source-ip-weirdities-with-irssi-and-ipv6/feed/" rel="self" type="application/rss+xml" />
	<link>https://jeremy.visser.name/2010/01/28/source-ip-weirdities-with-irssi-and-ipv6/</link>
	<description></description>
	<lastBuildDate>Thu, 29 Jul 2010 04:10:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Jeremy</title>
		<link>https://jeremy.visser.name/2010/01/28/source-ip-weirdities-with-irssi-and-ipv6/comment-page-1/#comment-5312</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Sun, 31 Jan 2010 02:17:10 +0000</pubDate>
		<guid isPermaLink="false">http://jeremy.visser.name/?p=1359#comment-5312</guid>
		<description>I think I&#039;ve found the source of the problem. In &lt;code&gt;/etc/hosts&lt;/code&gt;, there is an entry for glenstorm that resolves to &lt;code&gt;127.0.0.1&lt;/code&gt; and &lt;code&gt;::1&lt;/code&gt;.

If I remove the &lt;code&gt;::1&lt;/code&gt; entry (so glenstorm can only resolve to &lt;code&gt;127.0.0.1&lt;/code&gt;, not &lt;code&gt;::1&lt;/code&gt;), then irssi connects fine.

But this is not a &quot;solution&quot; per se, because I still want it resolvable to &lt;code&gt;::1&lt;/code&gt;.</description>
		<content:encoded><![CDATA[<p>I think I&#8217;ve found the source of the problem. In <code>/etc/hosts</code>, there is an entry for glenstorm that resolves to <code>127.0.0.1</code> and <code>::1</code>.</p>
<p>If I remove the <code>::1</code> entry (so glenstorm can only resolve to <code>127.0.0.1</code>, not <code>::1</code>), then irssi connects fine.</p>
<p>But this is not a &#8220;solution&#8221; per se, because I still want it resolvable to <code>::1</code>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy</title>
		<link>https://jeremy.visser.name/2010/01/28/source-ip-weirdities-with-irssi-and-ipv6/comment-page-1/#comment-5284</link>
		<dc:creator>Jeremy</dc:creator>
		<pubDate>Fri, 29 Jan 2010 09:56:19 +0000</pubDate>
		<guid isPermaLink="false">http://jeremy.visser.name/?p=1359#comment-5284</guid>
		<description>Yeah, this is through Internode&#039;s native IPv6.

My routing table is pretty normal:

&lt;blockquote&gt;&lt;pre&gt;::/0                           ::                         U    1024 0     0 ppp0
::/0                           ::                         !n   -1  1   720 lo&lt;/pre&gt;&lt;/blockquote&gt;

I do take special care to set &lt;code&gt;net.ipv6.conf.all.forwarding&lt;/code&gt; to &lt;code&gt;1&lt;/code&gt; &lt;em&gt;before&lt;/em&gt; I bring up the &lt;code&gt;ppp0&lt;/code&gt;, so that I don’t get the RA that stuffs my routing tables. So yeah, my &lt;code&gt;::/0&lt;/code&gt; route is a device-only route like it should be.

I thought this was more related to the fact that there are no global IPv6 addresses on the &lt;code&gt;ppp0&lt;/code&gt; interface. (My /60 subnet is routed to me via &lt;code&gt;ppp0&lt;/code&gt;, but its endpoint in the form of the first &lt;code&gt;/64&lt;/code&gt; is on the &lt;code&gt;br0&lt;/code&gt; interface.) However, if I add the same IP onto &lt;code&gt;ppp0&lt;/code&gt; (&lt;code&gt;ifconfig ppp0 add 2001:44b8:7df3:b970::14/128&lt;/code&gt;), it’s still no-go.</description>
		<content:encoded><![CDATA[<p>Yeah, this is through Internode&#8217;s native IPv6.</p>
<p>My routing table is pretty normal:</p>
<blockquote><pre>::/0                           ::                         U    1024 0     0 ppp0
::/0                           ::                         !n   -1  1   720 lo</pre>
</blockquote>
<p>I do take special care to set <code>net.ipv6.conf.all.forwarding</code> to <code>1</code> <em>before</em> I bring up the <code>ppp0</code>, so that I don’t get the RA that stuffs my routing tables. So yeah, my <code>::/0</code> route is a device-only route like it should be.</p>
<p>I thought this was more related to the fact that there are no global IPv6 addresses on the <code>ppp0</code> interface. (My /60 subnet is routed to me via <code>ppp0</code>, but its endpoint in the form of the first <code>/64</code> is on the <code>br0</code> interface.) However, if I add the same IP onto <code>ppp0</code> (<code>ifconfig ppp0 add 2001:44b8:7df3:b970::14/128</code>), it’s still no-go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas K</title>
		<link>https://jeremy.visser.name/2010/01/28/source-ip-weirdities-with-irssi-and-ipv6/comment-page-1/#comment-5277</link>
		<dc:creator>Thomas K</dc:creator>
		<pubDate>Fri, 29 Jan 2010 05:03:39 +0000</pubDate>
		<guid isPermaLink="false">http://jeremy.visser.name/?p=1359#comment-5277</guid>
		<description>Curious... I have all of the above working through node&#039;s ipv6 trial service (I assume you&#039;re using something like that)

What do you get from &quot;&lt;code&gt;/sbin/route --inet6&lt;/code&gt;&quot;?

Though the router&#039;s ipv6 address is on my eth0, because the next-hop router is through ppp0 I&#039;ve found that I need to do &quot;&lt;code&gt;/sbin/route --inet6 add default dev ppp0&lt;/code&gt;&quot; for connections originating on the router to work.

With that done, the three relevant lines for ::/0 destinations for me are, top-to-bottom:

&lt;blockquote&gt;&lt;pre&gt;::/0                           ::                         U    1   0     0 ppp0
::/0                           ::                         !n   -1  158414305 lo
::/0                           ::                         !n   -1  158414305 lo&lt;/pre&gt;&lt;/blockquote&gt;

Does that help?</description>
		<content:encoded><![CDATA[<p>Curious&#8230; I have all of the above working through node&#8217;s ipv6 trial service (I assume you&#8217;re using something like that)</p>
<p>What do you get from &#8220;<code>/sbin/route --inet6</code>&#8220;?</p>
<p>Though the router&#8217;s ipv6 address is on my eth0, because the next-hop router is through ppp0 I&#8217;ve found that I need to do &#8220;<code>/sbin/route --inet6 add default dev ppp0</code>&#8221; for connections originating on the router to work.</p>
<p>With that done, the three relevant lines for ::/0 destinations for me are, top-to-bottom:</p>
<blockquote><pre>::/0                           ::                         U    1   0     0 ppp0
::/0                           ::                         !n   -1  158414305 lo
::/0                           ::                         !n   -1  158414305 lo</pre>
</blockquote>
<p>Does that help?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
