<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Rogierm&#039;s Blog &#187; ipv6</title>
	<atom:link href="http://rogierm.redbee.nl/blog/tag/ipv6/feed/" rel="self" type="application/rss+xml" />
	<link>http://rogierm.redbee.nl/blog</link>
	<description>Just another blog with technical stuff</description>
	<lastBuildDate>Mon, 28 Jun 2010 21:04:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>IPv6 subnetting</title>
		<link>http://rogierm.redbee.nl/blog/2009/08/14/ipv6-subnetting/</link>
		<comments>http://rogierm.redbee.nl/blog/2009/08/14/ipv6-subnetting/#comments</comments>
		<pubDate>Fri, 14 Aug 2009 21:15:59 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Network]]></category>
		<category><![CDATA[ipv6]]></category>

		<guid isPermaLink="false">http://rogierm.redbee.nl/blog/?p=57</guid>
		<description><![CDATA[There are couple of differences between IPv6 and IPv4 address allocation. The prefix length for an IPv6 subnet will always be /64; no more, no less. It allows you to place as many IPv6 devices as the underlying network medium allows. The 128 bit IPv6 address is automatically created from the /64 bit subnet extended [...]]]></description>
			<content:encoded><![CDATA[<p>There are couple of differences between IPv6 and IPv4 address allocation.</p>
<ul>
<li>The prefix length for an IPv6 subnet will always be /64; no more, no less. It allows you to place as many IPv6 devices as the underlying network medium allows. The 128 bit IPv6 address is automatically created from the /64 bit subnet extended with the 64 bit MAC-address of the NIC.</li>
</ul>
<p>With IPv4, prefix length varies between subnets to subnets, and it caused painful costs when renumbering subnets (for example, imagine when you renumber an IPv4 subnet from /28 to /29 or vice versa).</p>
<ul>
<li>An ordinary leaf site will always get /48 of address space. This will be sufficient for most small to medium sized networks.</li>
</ul>
<p>With IPv4, the allocation varies by the size of the site, and made it very painful when you migrated from one ISP to another, for example.</p>
]]></content:encoded>
			<wfw:commentRss>http://rogierm.redbee.nl/blog/2009/08/14/ipv6-subnetting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cisco ASA IPv6 failover not supported</title>
		<link>http://rogierm.redbee.nl/blog/2009/07/24/cisco-asa-ipv6-failover-not-supported/</link>
		<comments>http://rogierm.redbee.nl/blog/2009/07/24/cisco-asa-ipv6-failover-not-supported/#comments</comments>
		<pubDate>Fri, 24 Jul 2009 12:50:36 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Network]]></category>
		<category><![CDATA[asa]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[failover]]></category>
		<category><![CDATA[ipv6]]></category>
		<category><![CDATA[pix]]></category>

		<guid isPermaLink="false">http://rogierm.redbee.nl/blog/?p=23</guid>
		<description><![CDATA[Due to the shortage of IPv4 IP addresses, we will run out of IPv4 some day in the near future (approx. 699 days from now, http://inetcore.com/project/ipv4ec/index_en.html). To be prepared for this we are experimenting with IPv6. We got a /32 allocated by RIPE, and are currently preparing a live network to connect some services via [...]]]></description>
			<content:encoded><![CDATA[<p>Due to the shortage of IPv4 IP addresses, we will run out of IPv4 some day in the near future (approx. 699 days from now, http://inetcore.com/project/ipv4ec/index_en.html). To be prepared for this we are experimenting with IPv6. We got a /32 allocated by RIPE, and are currently preparing a live network to connect some services via native  IPv6 to the internet. While reviewing the IPv6 capabilities of the network equipment we use, I found out that Cisco ASA/Pix does not support failover when running IPv6. For details on this matter please see the following links:</p>
<ul>
<li>http://www.v4tov6.com/2009/06/cisco-asa-ipv6-failover-update.html</li>
<li>http://v4tov6.com/2008/11/cisco-asa-ipv6-failover.html</li>
<li>http://forums.cabling-design.com/cisco/Re-PIX-IPv6-Failover-bug-4167-.htm</li>
</ul>
<p>This failover support seems to be lacking for some time now, and is still missing in the latest release. I&#8217;ve notified our sales rep. at Cisco about this. Personally I think this is quite a serious issue, as failover is a essential part of building serious infrastructures. I hope Cisco will see that this feature should be implemented as soon as possible.</p>
<p>If you consider this a serious issue as well, I recommend you notify your Cisco contact. Also leave a comment, just because I&#8217;m wondering how many people think this is a problem <img src='http://rogierm.redbee.nl/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>06 april 2010: Cisco released ASA version 8.3 which solves this problem: http://www.networkworld.com/community/node/58537</p>
]]></content:encoded>
			<wfw:commentRss>http://rogierm.redbee.nl/blog/2009/07/24/cisco-asa-ipv6-failover-not-supported/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
