<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>

<channel>
	<title>Cyconet Blog &#187; IPv6</title>
	<atom:link href="http://blog.waja.info/tag/ipv6/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.waja.info</link>
	<description>Just a place to be!</description>
	<lastBuildDate>Wed, 28 Apr 2010 08:22:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
		<item>
		<title>Our Prefix did hit the routing table</title>
		<link>http://blog.waja.info/2005/12/12/our-prefix-did-hit-the-routing-table/</link>
		<comments>http://blog.waja.info/2005/12/12/our-prefix-did-hit-the-routing-table/#comments</comments>
		<pubDate>Mon, 12 Dec 2005 09:54:16 +0000</pubDate>
		<dc:creator>cyco</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[routing]]></category>

		<guid isPermaLink="false">http://blog.waja.info/2005/12/12/our-prefix-did-hit-the-routing-table/</guid>
		<description><![CDATA[On Friday at 11:47:19 +01:00 our prefix did hit the BGP routing tables &#8230;. So AS20646 managed to fix their filters. Also the reverse delegation was set up today, so we took another step forward.]]></description>
			<content:encoded><![CDATA[<p>On Friday at 11:47:19 +01:00 our prefix did hit the BGP routing tables &#8230;. So AS20646 managed to fix their filters.<br />
Also the reverse delegation was set up today, so we took another step forward.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.waja.info/2005/12/12/our-prefix-did-hit-the-routing-table/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Searching (native) IPv6 Upstream</title>
		<link>http://blog.waja.info/2005/12/08/searching-native-ipv6-upstream/</link>
		<comments>http://blog.waja.info/2005/12/08/searching-native-ipv6-upstream/#comments</comments>
		<pubDate>Thu, 08 Dec 2005 22:29:47 +0000</pubDate>
		<dc:creator>cyco</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Networking]]></category>

		<guid isPermaLink="false">http://blog.waja.info/?p=47</guid>
		<description><![CDATA[Since we allready have IPv6 upstream through IPTunnel with AS20646 for a /40 of them (native isnt possible with our router connected to them, yet) it will only be a question of time until this uplink has fixed his filters. But the goal is to get native upstream&#8230;. at this point AS3209 comes in place. [...]]]></description>
			<content:encoded><![CDATA[<p>Since we allready have IPv6 upstream through IPTunnel with AS20646 for a /40 of them (native isnt possible with our router connected to them, yet) it will only be a question of time until this uplink has fixed his filters.<br />
But the goal is to get native upstream&#8230;. at this point AS3209 comes in place.<br />
The first request by mail was ignored. So I was searching trough our documentations (yes, we have some :-)) and found the phone number of our contact there. The guy told me, he will see what can be done.<br />
I got the callback some days later and the news wasnt like expected. The net development department stated, that this wont be in place in the next time &#8230; so far, so bad.</p>
<p>Some days later &#8230; I got the next call &#8230; they are interested into satisfied customer. He asked my to specify, what our goals are and what we need, after that it will come to a telephone conference. So I did write a friendly mail. :-)</p>
<p>Also some days later, I did remember, that on ipv6-ops mailing was a mail of one of their employee. So I decided to write him also a mail .. and what a success, this guy works in the network development department and we will have a telephone conference next week. So we will see, what comes up.. :-)</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.waja.info/2005/12/08/searching-native-ipv6-upstream/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>ipv6-first-alloc request</title>
		<link>http://blog.waja.info/2005/11/18/ipv6-first-alloc-request/</link>
		<comments>http://blog.waja.info/2005/11/18/ipv6-first-alloc-request/#comments</comments>
		<pubDate>Fri, 18 Nov 2005 21:14:02 +0000</pubDate>
		<dc:creator>cyco</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[ripe]]></category>

		<guid isPermaLink="false">http://blog.waja.info/?p=46</guid>
		<description><![CDATA[We decided, after we will reach the next billing categorie 2007 anyways (you remember, we got /18 allocated), that it will be neat to request a /32. I created a sweet address plan and got the allocation in less than 5 hours approved. :-)]]></description>
			<content:encoded><![CDATA[<p>We decided, after we will reach the next billing categorie 2007 anyways (you remember, we got /18 allocated), that it will be neat to request a /32.<br />
I created a sweet address plan and got the allocation in less than 5 hours approved. :-)</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.waja.info/2005/11/18/ipv6-first-alloc-request/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Traffic Shaping</title>
		<link>http://blog.waja.info/2004/10/19/traffic-shaping/</link>
		<comments>http://blog.waja.info/2004/10/19/traffic-shaping/#comments</comments>
		<pubDate>Tue, 19 Oct 2004 19:44:14 +0000</pubDate>
		<dc:creator>cyco</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[OpenSource]]></category>

		<guid isPermaLink="false">http://blog.waja.info/?p=34</guid>
		<description><![CDATA[Linux Advanced Routing &#038; Traffic Control HOWTO Test script for P2P Shaping ADSL traffic with linux Filtering IPv6 Traffic]]></description>
			<content:encoded><![CDATA[<p><a target="_blank" href="http://lartc.org/howto/">Linux Advanced Routing &#038; Traffic Control HOWTO</a><br />
<a target="_blank" href="http://lists.netfilter.org/pipermail/netfilter/2003-June/044718.html">Test script for P2P</a><br />
<a target="_blank" href="http://nsd.dyndns.org/shapedsl/">Shaping ADSL traffic with linux</a><br />
<a target="_blank" href="http://lartc.org/howto/lartc.adv-filter.ipv6.html">Filtering IPv6 Traffic</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.waja.info/2004/10/19/traffic-shaping/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
	</item>
		<item>
		<title>Sniffing for IPv6 Packets with tcpdump</title>
		<link>http://blog.waja.info/2004/10/19/sniffing-for-ipv6-packets-with-tcpdump/</link>
		<comments>http://blog.waja.info/2004/10/19/sniffing-for-ipv6-packets-with-tcpdump/#comments</comments>
		<pubDate>Tue, 19 Oct 2004 19:22:17 +0000</pubDate>
		<dc:creator>cyco</dc:creator>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[OpenSource]]></category>

		<guid isPermaLink="false">http://blog.waja.info/?p=42</guid>
		<description><![CDATA[# tcpdump -i eth0 -vv ip6]]></description>
			<content:encoded><![CDATA[<p class="code"># tcpdump -i eth0 -vv ip6</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.waja.info/2004/10/19/sniffing-for-ipv6-packets-with-tcpdump/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
	</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->