<?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>Jay R. Wren - lazy dawg evarlast &#187; Networking</title>
	<atom:link href="http://jrwren.wrenfam.com/blog/category/networking/feed/" rel="self" type="application/rss+xml" />
	<link>http://jrwren.wrenfam.com/blog</link>
	<description>babblings of a computer loving fool</description>
	<lastBuildDate>Wed, 01 Feb 2012 19:08:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>OpenWRT 10.03.1-rc2 and Comcast IPv6</title>
		<link>http://jrwren.wrenfam.com/blog/2010/11/23/openwrt-10-03-1-rc2-and-comcast-ipv6-2/</link>
		<comments>http://jrwren.wrenfam.com/blog/2010/11/23/openwrt-10-03-1-rc2-and-comcast-ipv6-2/#comments</comments>
		<pubDate>Wed, 24 Nov 2010 02:41:55 +0000</pubDate>
		<dc:creator>jrwren</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[comcast]]></category>
		<category><![CDATA[ipv6]]></category>

		<guid isPermaLink="false">http://jrwren.wrenfam.com/blog/2010/11/23/openwrt-10-03-1-rc2-and-comcast-ipv6-2/</guid>
		<description><![CDATA[After documenting the IPv6 goodness for the old kamikaze release of openwrt, I wanted to play with something a little newer. I also wanted newer iptables so I could play with the tee module. Some notes: Still no 6rd support &#8230; <a href="http://jrwren.wrenfam.com/blog/2010/11/23/openwrt-10-03-1-rc2-and-comcast-ipv6-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>After documenting the IPv6 goodness for the old kamikaze release of openwrt, I wanted to play with something a little newer. I also wanted newer iptables so I could play with the tee module.</p>
<p>Some notes:</p>
<ul>
<li>Still no 6rd support on OpenWRT AFAIK </li>
<li>rc2 and rc3 are the same for the brcm-2.4 version of Openwrt 10.03.1</li>
<li>brcm4700 doesn’t work well at all with my WRT54GL. I think the open source broadcom drivers still aren’t as stable as the proprietary ones that ship with 2.4</li>
<li>nearly the same config scripts as the old kamikaze work</li>
</ul>
<p>Once you flash the router with the firmware you will need to install some extra packages.</p>
<ol>
<li>opkg update</li>
<li>opkg install ip kmod-ipv6 kmod-sit radvd </li>
<li>paste this code into a new startup script at /etc/init.d/comcast6to4     </li>
<p>#!/bin/sh /etc/rc.common</p>
<p>inetip=`ip -4 addr show dev eth0.1 | awk &#8216;/inet / {print $2}&#8217; | cut -d/ -f 1`     <br />inetipspaced=`echo $inetip | tr . &#8216; &#8216;`      <br />local6prefix=`printf 2002:%02x%02x:%02x%02x $inetipspaced`</p>
<p>start() {     <br />ip tunnel add c6to4 mode sit ttl 255 remote any local $inetip      <br />ip link set c6to4 up      <br />ip -6 addr add $local6prefix:0::1/64 dev c6to4      <br />ip -6 addr add $local6prefix:1::1/64 dev br-lan      <br />ip -6 route add 2000::/3 via ::192.88.99.1 dev c6to4      <br />sysctl -w net.ipv6.conf.all.forwarding=1 &gt; /dev/null      <br />cat &gt; /etc/radvd.conf &lt;&lt;EOF      <br />interface br-lan      <br />{      <br />AdvSendAdvert on;      <br />MinRtrAdvInterval 3;      <br />MaxRtrAdvInterval 10;      <br />prefix $local6prefix:1::/64      <br />{      <br />AdvOnLink on;      <br />AdvAutonomous on;      <br />AdvRouterAddr on;      <br />AdvValidLifetime 86400;      <br />AdvPreferredLifetime 86400;      <br />};      <br />};      <br />EOF      <br />}</p>
<p>stop() {     <br />&#160; ip tunnel del c6to4      <br />&#160; ip -6 addr del $local6prefix:1::1/64 dev br-lan      <br />}      </p>
<li>pushd /etc/rc.d ; ln –s ../init.d/comcast6to4 S42comcast6to4</li>
</ol>
<p>Then be glad you have ipv6.</p>
<p>&#160;</p>
<p>This will actually work for ANY provider which uses the standard IPv6 6to4 address of 192.88.99.1, not just Comcast.</p>
<p>Now if only Comcast would open back up their trial so I could join my work to the ipv6 network.</p>
]]></content:encoded>
			<wfw:commentRss>http://jrwren.wrenfam.com/blog/2010/11/23/openwrt-10-03-1-rc2-and-comcast-ipv6-2/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Comcast IPv6 on an old Kamikaze 8.09 Openwrt via 6to4</title>
		<link>http://jrwren.wrenfam.com/blog/2010/11/20/comcast-ipv6-on-an-old-kamikaze-8-09-openwrt-via-6to4/</link>
		<comments>http://jrwren.wrenfam.com/blog/2010/11/20/comcast-ipv6-on-an-old-kamikaze-8-09-openwrt-via-6to4/#comments</comments>
		<pubDate>Sun, 21 Nov 2010 01:46:57 +0000</pubDate>
		<dc:creator>jrwren</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[comcast]]></category>
		<category><![CDATA[ipv6]]></category>

		<guid isPermaLink="false">http://jrwren.wrenfam.com/blog/2010/11/20/comcast-ipv6-on-an-old-kamikaze-8-09-openwrt-via-6to4/</guid>
		<description><![CDATA[I’m an openwrt novice, but I know enough about linux and iptables to usually get done what I want. When Comcast announced they were trialing IPv6, I jumped at the opportunity to migration from my trusty Hurricane Electric tunnel to &#8230; <a href="http://jrwren.wrenfam.com/blog/2010/11/20/comcast-ipv6-on-an-old-kamikaze-8-09-openwrt-via-6to4/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I’m an openwrt novice, but I know enough about linux and iptables to usually get done what I want. When Comcast announced they were trialing IPv6, I jumped at the opportunity to migration from my trusty Hurricane Electric tunnel to something more direct.</p>
<p>I’m running Kamikaze 8.09.1 brcm-2.4 on my Linksys WRT54GL these instructions probably won’t work elsewhere. I’m guessing that IPv6 is a little different in a 2.6 kernel with a new iptables. If you have very new stuff you should be using 6rd instead of 6to4.</p>
<p>I’m writing this because much of the information I found out there for 6to4 on Linux didn’t work for me, or was only partly correct and I had to piece together suggestions from different sources.</p>
<p>make a script in /etc/rc.d with this content. I called mine comcast6to4</p>
<blockquote><p>inetip=`ip -4 addr show dev eth0.1 | awk &#8216;/inet / {print $2}&#8217; | cut -d/ -f 1`<br />
inetipspaced=`echo $inetip | tr . &#8216; &#8216;`<br />
local6prefix=`printf 2002:%02x%02x:%02x%02x $inetipspaced`<br />
ip tunnel add c6to4 mode sit ttl 255 remote any local $inetip<br />
ip link set c6to4 up<br />
ip -6 addr add $local6prefix:0::1/64 dev c6to4<br />
ip -6 addr add $local6prefix:1::1/64 dev br-lan<br />
ip -6 route add 2000::/3 via ::192.88.99.1 dev c6to4</p></blockquote>
<p>Make your /etc/radvd.conf look like this:</p>
<blockquote><p>interface br-lan<br />
{<br />
AdvSendAdvert on;<br />
MinRtrAdvInterval 3;<br />
MaxRtrAdvInterval 10;<br />
prefix $local6prefix:1::/64<br />
{<br />
AdvOnLink on;<br />
AdvAutonomous on;<br />
AdvRouterAddr on;<br />
AdvValidLifetime 86400;<br />
AdvPreferredLifetime 86400;<br />
};<br />
};</p></blockquote>
<p>That is it. I’m not going to explain it. Read the links below for all of that.</p>
<p>Sorry this isn&#8217;t a complete solution. You&#8217;ll have to fill in that $local6prefix in radvd.conf yourself.</p>
<p>Works Cited:</p>
<p><a title="http://www.reddit.com/r/linux/comments/dbobx/" href="http://www.reddit.com/r/linux/comments/dbobx/">http://www.reddit.com/r/linux/comments/dbobx/</a></p>
<p><a title="http://www.comcast6.net/" href="http://www.comcast6.net/">http://www.comcast6.net/</a></p>
<p><a title="http://wiki.debian.org/DebianIPv6#IPv66to4Configuration" href="http://wiki.debian.org/DebianIPv6#IPv66to4Configuration">http://wiki.debian.org/DebianIPv6#IPv66to4Configuration</a></p>
<p><a title="http://tldp.org/HOWTO/Linux+IPv6-HOWTO/configuring-ipv6to4-tunnels.html" href="http://tldp.org/HOWTO/Linux+IPv6-HOWTO/configuring-ipv6to4-tunnels.html">http://tldp.org/HOWTO/Linux+IPv6-HOWTO/configuring-ipv6to4-tunnels.html</a></p>
<p><a title="http://en.wikipedia.org/wiki/6to4" href="http://en.wikipedia.org/wiki/6to4">http://en.wikipedia.org/wiki/6to4</a></p>
<p><a title="http://www.dslreports.com/forum/r24972279-IPv6-via-6in4" href="http://www.dslreports.com/forum/r24972279-IPv6-via-6in4">http://www.dslreports.com/forum/r24972279-IPv6-via-6in4</a></p>
<p><a title="http://www.anyweb.co.nz/tutorial/v6Linux6to4" href="http://www.anyweb.co.nz/tutorial/v6Linux6to4">http://www.anyweb.co.nz/tutorial/v6Linux6to4</a></p>
]]></content:encoded>
			<wfw:commentRss>http://jrwren.wrenfam.com/blog/2010/11/20/comcast-ipv6-on-an-old-kamikaze-8-09-openwrt-via-6to4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>My Whole App is a LINQ Expression</title>
		<link>http://jrwren.wrenfam.com/blog/2010/01/10/my-whole-app-is-a-linq-expression/</link>
		<comments>http://jrwren.wrenfam.com/blog/2010/01/10/my-whole-app-is-a-linq-expression/#comments</comments>
		<pubDate>Sun, 10 Jan 2010 20:53:03 +0000</pubDate>
		<dc:creator>jrwren</dc:creator>
				<category><![CDATA[C#]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://jrwren.wrenfam.com/blog/?p=917</guid>
		<description><![CDATA[I just published an application which I consider useful over on codeplex with source hosted on launchpad. http://wlanchannelinfo.codeplex.com/ https://code.edge.launchpad.net/~evarlast/+junk/WlanChannelInfo I wrote this because Wifi in my home is very slow. Its so slow I&#8217;m tempted to run a network cable &#8230; <a href="http://jrwren.wrenfam.com/blog/2010/01/10/my-whole-app-is-a-linq-expression/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I just published an application which I consider useful over on codeplex with source hosted on launchpad.</p>
<p><a href="http://wlanchannelinfo.codeplex.com/">http://wlanchannelinfo.codeplex.com/</a></p>
<p><a href="https://code.edge.launchpad.net/~evarlast/+junk/WlanChannelInfo">https://code.edge.launchpad.net/~evarlast/+junk/WlanChannelInfo</a></p>
<p>I wrote this because Wifi in my home is very slow. Its so slow I&#8217;m tempted to run a network cable to my couch so that even when I&#8217;m couch surfing I can have fast access to my server.</p>
<p>In an effort to diagnose my slow Wifi, I tried to see if my neighbors were causing interference by running Wifi on the same or overlapping channel as me. I downloaded netstumbler; it didn&#8217;t work. I downloaded some other tool; neither did it.</p>
<p>So I wondered how hard it would be to write my own. It turns out Windows 7 added to the Wlan* api to expose all of the necessary data. After some digging I found the managedwlan project on codeplex. Now I got to play.</p>
<p>Once I figured out the api, I was able to write the entire application with pretty much one LINQ expression:</p>
<p>var client = new WlanClient();<br />
var retval =<br />
from wlanIface in client.Interfaces<br />
from bssentry in wlanIface.GetNetworkBssList()<br />
from network in wlanIface.GetAvailableNetworkList(Wlan.WlanGetAvailableNetworkFlags.IncludeAllAdhocProfiles)<br />
where InterfaceService.GetStringForSSID(network.dot11Ssid) == InterfaceService.GetStringForSSID(bssentry.dot11Ssid)<br />
select new WifiInfo<br />
{<br />
bssentry = GetStringForSSID(bssentry.dot11Ssid),<br />
channel = Wifi.FrequencyChannelMap[bssentry.chCenterFrequency],<br />
frequency = bssentry.chCenterFrequency,<br />
linqQuality = bssentry.linkQuality,<br />
strength = bssentry.rssi,<br />
signalQuality = network.wlanSignalQuality,<br />
wifitype = network.dot11BssType<br />
};</p>
<p>The result of that expression is directly databound to a WPF DataGrid and I can now view the data that I want to.</p>
<p>I really love the platform (C#+.NET) on which I work.</p>
]]></content:encoded>
			<wfw:commentRss>http://jrwren.wrenfam.com/blog/2010/01/10/my-whole-app-is-a-linq-expression/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Restoring a Desktop Image to a VMware Virtual Machine with Windows Home Server</title>
		<link>http://jrwren.wrenfam.com/blog/2009/10/09/restoring-a-desktop-image-to-a-vmware-virtual-machine-with-windows-home-server/</link>
		<comments>http://jrwren.wrenfam.com/blog/2009/10/09/restoring-a-desktop-image-to-a-vmware-virtual-machine-with-windows-home-server/#comments</comments>
		<pubDate>Sat, 10 Oct 2009 00:58:55 +0000</pubDate>
		<dc:creator>jrwren</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://jrwren.wrenfam.com/blog/2009/10/09/restoring-a-desktop-image-to-a-vmware-virtual-machine-with-windows-home-server/</guid>
		<description><![CDATA[Copy the restorecd.iso from \\homeserver\Software\Home PC Restore CD to your VMware server. Configure a new VMware virtual machine with an appropriately sized disk, a network adapter (I prefer bridged) and a CD ROM Drive pointed to said restorecd.iso from step &#8230; <a href="http://jrwren.wrenfam.com/blog/2009/10/09/restoring-a-desktop-image-to-a-vmware-virtual-machine-with-windows-home-server/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<ol>
<li>Copy the restorecd.iso from \\homeserver\Software\Home PC Restore CD to your VMware server.</li>
<li>Configure a new VMware virtual machine with an appropriately sized disk, a network adapter (I prefer bridged) and a CD ROM Drive pointed to said restorecd.iso from step 1. Do not start the VM at the last step.</li>
<li>Find the vmx file created in step 2. Add a line ethernet0.virtualDev= “e1000”.&#160; This the required trick step since Windows Home Server doesn’t have a driver for the LANCE network chip which vmware normally emulates.</li>
<li>Boot the Virtual Machine and follow the prompts.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://jrwren.wrenfam.com/blog/2009/10/09/restoring-a-desktop-image-to-a-vmware-virtual-machine-with-windows-home-server/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>nmap can open device eth15, but only if you let it</title>
		<link>http://jrwren.wrenfam.com/blog/2009/06/09/nmap-can-open-device-eth15-but-only-if-you-let-it/</link>
		<comments>http://jrwren.wrenfam.com/blog/2009/06/09/nmap-can-open-device-eth15-but-only-if-you-let-it/#comments</comments>
		<pubDate>Wed, 10 Jun 2009 00:44:00 +0000</pubDate>
		<dc:creator>jrwren</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://jrwren.wrenfam.com/blog/2009/06/09/nmap-can-open-device-eth15-but-only-if-you-let-it/</guid>
		<description><![CDATA[This is here as a note to myself to not be stupid. I’ve remembered at forgotten this at least 4 times and so that makes me stupid for not remembering. When nmap on win32 tells you that “dnet: Failed to &#8230; <a href="http://jrwren.wrenfam.com/blog/2009/06/09/nmap-can-open-device-eth15-but-only-if-you-let-it/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>This is here as a note to myself to not be stupid.</p>
<p>I’ve remembered at forgotten this at least 4 times and so that makes me stupid for not remembering.</p>
<p>When nmap on win32 tells you that “dnet: Failed to open device eth15”, it is really suggesting that you run it as administrator.</p>
<p>You need to be administrator to access the network device at this level.</p>
]]></content:encoded>
			<wfw:commentRss>http://jrwren.wrenfam.com/blog/2009/06/09/nmap-can-open-device-eth15-but-only-if-you-let-it/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

