<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Pete&#039;s Packet &#187; IPV6</title>
	<atom:link href="http://petespacket.com/category/routing-switching-lab/ipv6/feed/" rel="self" type="application/rss+xml" />
	<link>http://petespacket.com</link>
	<description>Limitless</description>
	<lastBuildDate>Thu, 09 Feb 2012 05:03:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='petespacket.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>Pete&#039;s Packet &#187; IPV6</title>
		<link>http://petespacket.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://petespacket.com/osd.xml" title="Pete&#039;s Packet" />
	<atom:link rel='hub' href='http://petespacket.com/?pushpress=hub'/>
		<item>
		<title>UC300 VOIP PBX</title>
		<link>http://petespacket.com/2011/03/16/uc300-voip-pbx/</link>
		<comments>http://petespacket.com/2011/03/16/uc300-voip-pbx/#comments</comments>
		<pubDate>Wed, 16 Mar 2011 21:47:12 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[BGP]]></category>
		<category><![CDATA[IPV6]]></category>
		<category><![CDATA[Service Provider]]></category>

		<guid isPermaLink="false">http://petespacket.com/2011/03/16/uc300-voip-pbx/</guid>
		<description><![CDATA[http://www.youtube.com/watch?v=1rE7oiIQ7fY&#38;feature=player_embedded Filed under: BGP, IPV6, Service Provider<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=1492&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2011/03/16/uc300-voip-pbx/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>

		<media:content url="http://img.zemanta.com/pixy.gif?x-id=2a806307-aa74-8343-b6ae-f0b71d541466" medium="image" />
	</item>
		<item>
		<title>The 5 final IPv4 blocks have now been distributed to the RIRs according to the global policy</title>
		<link>http://petespacket.com/2011/02/03/the-5-final-ipv4-blocks-have-now-been-distributed-to-the-rirs-according-to-the-global-policy/</link>
		<comments>http://petespacket.com/2011/02/03/the-5-final-ipv4-blocks-have-now-been-distributed-to-the-rirs-according-to-the-global-policy/#comments</comments>
		<pubDate>Fri, 04 Feb 2011 03:33:28 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[IPV6]]></category>

		<guid isPermaLink="false">http://usaccie.wordpress.com/2011/02/03/the-5-final-ipv4-blocks-have-now-been-distributed-to-the-rirs-according-to-the-global-policy/</guid>
		<description><![CDATA[APNIC has requested and received two IPv4 /8s (39/8 &#38; 106/8), which has in turn triggered the “last five” policy at IANA giving each Regional Internet Registry (RIR) one additional /8 and depleting the global free pool of IPv4 forever. The final five went out like this just moments ago: 102/8 &#160; AfriNIC &#160; &#160;2011-02 [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=1489&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2011/02/03/the-5-final-ipv4-blocks-have-now-been-distributed-to-the-rirs-according-to-the-global-policy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>

		<media:content url="http://img.zemanta.com/pixy.gif?x-id=3b314096-bd2f-8223-a981-202ef55d9d8f" medium="image" />
	</item>
		<item>
		<title>Multiprotocol BGP for IPv6 example</title>
		<link>http://petespacket.com/2010/04/19/multiprotocol-bgp-for-ipv6-example/</link>
		<comments>http://petespacket.com/2010/04/19/multiprotocol-bgp-for-ipv6-example/#comments</comments>
		<pubDate>Mon, 19 Apr 2010 21:51:18 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[BGP]]></category>
		<category><![CDATA[IPV6]]></category>
		<category><![CDATA[Service Provider]]></category>

		<guid isPermaLink="false">http://petespacket.com/2010/04/19/multiprotocol-bgp-for-ipv6-example/</guid>
		<description><![CDATA[Configuring an IPv6 Multiprotocol BGP Peer Group and advertising a route example. ScenarioConfigure R1 &#38; R2 for IPv6 Multiprotocol BGP using a Peer Group and advertising R1 &#38; R2&#8242;s loopbacks.Simple two router network for demonstration purposes. R1&#60;&#8212;-&#62;FR&#60;&#8212;&#8211;&#62;R2 &#160;Configurationr1 ipv6 unicast-routing interface Loopback99&#160;no ip address&#160;ipv6 address 2001:DB8:1111::1/48 interface Serial2/0&#160;ipv6 address 2001:DB8:0:CC00::1/48 router bgp 65100&#160;no bgp default [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=1421&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2010/04/19/multiprotocol-bgp-for-ipv6-example/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>

		<media:content url="http://img.zemanta.com/pixy.gif?x-id=c34351ef-2113-8cd4-93fc-d60939ba8f90" medium="image" />
	</item>
		<item>
		<title>ipv4 to ipv6</title>
		<link>http://petespacket.com/2009/07/16/ipv4-to-ipv6/</link>
		<comments>http://petespacket.com/2009/07/16/ipv4-to-ipv6/#comments</comments>
		<pubDate>Fri, 17 Jul 2009 03:42:37 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[IPV6]]></category>
		<category><![CDATA[Routing & Switching Lab]]></category>

		<guid isPermaLink="false">http://petespacket.com/?p=1038</guid>
		<description><![CDATA[Decimal 150 1 3 3 Binary 1001 0110 0000 0001 0000 0011 0000 0011 in hex, they are 16 digit groupings for hex representations, 1001=9 0110=6 so forth, The results is 9601:0303 http://blog.ru.co.za/2009/03/19/converting-ipv4-to-ipv6/ Converting from IPv4 to IPv6 is so easy, yet everyone seem to convert a IPv4 address to binary, then to IPv6. Why? [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=1038&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2009/07/16/ipv4-to-ipv6/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>
	</item>
		<item>
		<title>ipv6 cef &#8211; For Unicast RPF to work, Cisco Express Forwarding must be configured globally in the router</title>
		<link>http://petespacket.com/2009/07/08/ipv6-cef-for-unicast-rpf-to-work-cisco-express-forwarding-must-be-configured-globally-in-the-router/</link>
		<comments>http://petespacket.com/2009/07/08/ipv6-cef-for-unicast-rpf-to-work-cisco-express-forwarding-must-be-configured-globally-in-the-router/#comments</comments>
		<pubDate>Thu, 09 Jul 2009 00:21:48 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[IPV6]]></category>
		<category><![CDATA[Routing & Switching Lab]]></category>

		<guid isPermaLink="false">http://petespacket.com/?p=1009</guid>
		<description><![CDATA[The following prerequisites apply to Cisco Express Forwarding and distributed Cisco Express Forwarding for IPv6: – To forward IPv6 traffic using Cisco Express Forwarding or distributed Cisco Express Forwarding, you must configure forwarding of IPv6 unicast datagrams globally on the router by using the ipv6 unicast-routing command, and you must configure an IPv6 address on [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=1009&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2009/07/08/ipv6-cef-for-unicast-rpf-to-work-cisco-express-forwarding-must-be-configured-globally-in-the-router/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>
	</item>
		<item>
		<title>IPV6 address&#8217;</title>
		<link>http://petespacket.com/2009/06/26/ipv6-address/</link>
		<comments>http://petespacket.com/2009/06/26/ipv6-address/#comments</comments>
		<pubDate>Fri, 26 Jun 2009 14:11:50 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[IPV6]]></category>
		<category><![CDATA[Routing & Switching Lab]]></category>

		<guid isPermaLink="false">http://petespacket.com/?p=969</guid>
		<description><![CDATA[http://www.potaroo.net/ispcol/2008-08/ipv6addr.html ::1/128 local host ::FFFF:w.x.y.z IPv4 mapped address &#8211; lookup IPv4 address w.x.y.z FD00::/8 Unique Local Addresses. No registry is used for these addresses FE80::/10 Link Local Addresses No registry is used for these addresses 2001:0::/32 Teredo address a Cone NAT flag (C), the Universal (U) flag (set to 0), the Individual/Group (G) flag (set [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=969&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2009/06/26/ipv6-address/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>
	</item>
		<item>
		<title>IPV6 stateless autoconfiguration</title>
		<link>http://petespacket.com/2009/04/13/ipv6-stateless-autoconfiguration/</link>
		<comments>http://petespacket.com/2009/04/13/ipv6-stateless-autoconfiguration/#comments</comments>
		<pubDate>Tue, 14 Apr 2009 02:31:18 +0000</pubDate>
		<dc:creator>Peter Kurdziel</dc:creator>
				<category><![CDATA[IPV6]]></category>
		<category><![CDATA[Real World]]></category>

		<guid isPermaLink="false">http://petespacket.com/2009/04/13/ipv6-stateless-autoconfiguration/</guid>
		<description><![CDATA[The following is a summary of the steps a device takes when using stateless autoconfiguration: 1. Link-Local Address Generation: The device generates a link-local address. Recall that this is one of the two types of local-use IPv6 addresses. Link-local addresses have “1111 1110 10” for the first ten bits. The generated address uses those ten [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=petespacket.com&amp;blog=5091198&amp;post=724&amp;subd=usaccie&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://petespacket.com/2009/04/13/ipv6-stateless-autoconfiguration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/9f3ca338e3c74ee30f330961db548e59?s=96&#38;d=monsterid" medium="image">
			<media:title type="html">Peter Kurdziel</media:title>
		</media:content>
	</item>
	</channel>
</rss>
