<?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>rwhitby.net &#187; NSLU2-Linux</title>
	<atom:link href="http://www.rwhitby.net/blog/category/nslu2-linux/feed" rel="self" type="application/rss+xml" />
	<link>http://www.rwhitby.net</link>
	<description>The Internet Presence of Rod Whitby</description>
	<lastBuildDate>Wed, 25 Jan 2012 06:43:21 +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>Connecting a Treo650 to a Freecom DataTank 2</title>
		<link>http://www.rwhitby.net/blog/treo-650/connecting-a-treo650-to-a-freecom-datatank-2.html</link>
		<comments>http://www.rwhitby.net/blog/treo-650/connecting-a-treo650-to-a-freecom-datatank-2.html#comments</comments>
		<pubDate>Sat, 22 Mar 2008 09:36:01 +0000</pubDate>
		<dc:creator>Rod Whitby</dc:creator>
				<category><![CDATA[NSLU2-Linux]]></category>
		<category><![CDATA[Treo 650]]></category>

		<guid isPermaLink="false">http://www.rwhitby.net/blog/nslu2-linux/connecting-a-treo650-to-a-freecom-datatank-2.html</guid>
		<description><![CDATA[Install bluez2-utils from Optware Install the following kernel modules: bluetooth, hci_usb, l2cap, bnep, rfcomm, hidp Create /dev/rfcomm0 as follows: mknod /dev/rfcomm0 c 216 0 Enable routing from ppp0 to eth1 (don&#8217;t do this if you use ppp for your internet connection): /etc/init.d # diff -u routing.orig routing --- routing.orig Sat Mar 22 18:57:23 2008 +++ [...]]]></description>
			<content:encoded><![CDATA[<ol>
<li>Install bluez2-utils from Optware</li>
<li>Install the following kernel modules: bluetooth, hci_usb, l2cap, bnep, rfcomm, hidp</li>
<li>Create /dev/rfcomm0 as follows:<br />
<code>mknod /dev/rfcomm0 c 216 0</code></li>
<li> Enable routing from ppp0 to eth1 (don&#8217;t do this if you use ppp for your internet connection):<br />
<code>
<pre>
/etc/init.d # diff -u routing.orig routing
--- routing.orig        Sat Mar 22 18:57:23 2008
+++ routing     Sat Mar 22 15:14:29 2008
@@ -37,6 +37,7 @@

        # lo &#038; eth0 always accepted (also if WAN port IP not set)
        /sbin/iptables -A INPUT -i $INIF -j ACCEPT
+       /sbin/iptables -A INPUT -i ppp0 -j ACCEPT
        /sbin/iptables -A INPUT -i lo -j ACCEPT

        # get IP address from WAN port
@@ -150,6 +151,7 @@
          /sbin/iptables -A FORWARD -j TCPMSS -o $EXIF --clamp-mss-to-pmtu -p tcp --tcp-flags SYN,RST SYN
        fi
        /sbin/iptables -A FORWARD -i $EXIF -o $INIF -m state --state ESTABLISHED,RELATED -j ACCEPT
+       /sbin/iptables -A FORWARD -i $EXIF -o ppp0 -m state --state ESTABLISHED,RELATED -j ACCEPT

        grep -q ^proxy_server=checked /etc/master.conf
@@ -163,6 +165,7 @@
          fi
        else
          /sbin/iptables -A FORWARD -s $SUBNET -i $INIF -j ACCEPT
+         /sbin/iptables -A FORWARD -s $SUBNET -i ppp0 -j ACCEPT
        fi

        # port forwarding
</pre>
<p></code></p>
<li>Edit /etc/ppp/options as follows:<br />
<code><br />
noauth<br />
crtscts<br />
lock<br />
local<br />
proxyarp<br />
ktune<br />
192.168.1.XX:192.168.1.YY<br />
ms-dns 192.168.1.ZZ<br />
</code><br />
(edit the last two lines to suit your network topology, the first IP address<br />
is your gateway device, the second IP address will be assigned to the client,<br />
and the third IP address is your DNS server)</li>
<li>Add the following line to /etc/dnsmasq.conf:<br />
<code>interface=eth0,ppp0</code></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.rwhitby.net/blog/treo-650/connecting-a-treo650-to-a-freecom-datatank-2.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Five new NSLU2 firmware releases in five days</title>
		<link>http://www.rwhitby.net/blog/nslu2-linux/five-new-nslu2-firmware-releases-in-five-days.html</link>
		<comments>http://www.rwhitby.net/blog/nslu2-linux/five-new-nslu2-firmware-releases-in-five-days.html#comments</comments>
		<pubDate>Mon, 31 Dec 2007 02:58:16 +0000</pubDate>
		<dc:creator>Rod Whitby</dc:creator>
				<category><![CDATA[NSLU2-Linux]]></category>
		<category><![CDATA[OpenMoko]]></category>
		<category><![CDATA[OpenWRT]]></category>

		<guid isPermaLink="false">http://www.rwhitby.net/blog/nslu2-linux/five-new-nslu2-firmware-releases-in-five-days.html</guid>
		<description><![CDATA[In the last five days, we have made five new NSLU2 firmware releases: 2007-12-31 &#8211; Unslung 6.10-beta Release 2007-12-30 &#8211; SlugOS 4.8-beta Release 2007-12-29 &#8211; OpenWrt/NSLU2 Kamikaze 7.09 Release 2007-12-28 &#8211; Angstrom/NSLU2 2007.12 Release 2007-12-27 &#8211; Debian/NSLU2 Stable 4.0r2 Release All of these new releases are available at http://www.slug-firmware.net/ See http://article.gmane.org/gmane.comp.misc.nslu2.linux/20610 for an explanation of [...]]]></description>
			<content:encoded><![CDATA[<p>In the last five days, we have made five new NSLU2 firmware releases:</p>
<p>2007-12-31 &#8211; Unslung 6.10-beta Release<br />
2007-12-30 &#8211; SlugOS 4.8-beta Release<br />
2007-12-29 &#8211; OpenWrt/NSLU2 Kamikaze 7.09 Release<br />
2007-12-28 &#8211; Angstrom/NSLU2 2007.12 Release<br />
2007-12-27 &#8211; Debian/NSLU2 Stable 4.0r2 Release</p>
<p>All of these new releases are available at</p>
<p><a href="http://www.slug-firmware.net/">http://www.slug-firmware.net/</a></p>
<p>See <a href="http://article.gmane.org/gmane.comp.misc.nslu2.linux/20610">http://article.gmane.org/gmane.comp.misc.nslu2.linux/20610</a> for<br />
an explanation of the pros and cons of each different firmware<br />
distribution, and the installable packages available for each.</p>
<p>Thanks to everyone in the NSLU2-Linux, OpenWrt, Angstrom, OpenEmbedded<br />
and Debian projects who contributed to these releases.</p>
<p>Remember, if you find any of the firmware or packages that the<br />
NLSU2-Linux project provides useful, feel free to make a donation to<br />
the project at</p>
<p><a href="http://www.nslu2-linux.org/wiki/Main/Donate">http://www.nslu2-linux.org/wiki/Main/Donate</a></p>
<p>We are currently in need of about $500 to buy a RAID controller card<br />
and some disks for our autobuild machine to support all this new<br />
firmware with up-to-date package feeds &#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rwhitby.net/blog/nslu2-linux/five-new-nslu2-firmware-releases-in-five-days.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Setting the OpenMoko timezone</title>
		<link>http://www.rwhitby.net/blog/nslu2-linux/setting-the-openmoko-timezone.html</link>
		<comments>http://www.rwhitby.net/blog/nslu2-linux/setting-the-openmoko-timezone.html#comments</comments>
		<pubDate>Sat, 01 Sep 2007 08:33:48 +0000</pubDate>
		<dc:creator>Rod Whitby</dc:creator>
				<category><![CDATA[NSLU2-Linux]]></category>
		<category><![CDATA[OpenMoko]]></category>

		<guid isPermaLink="false">http://www.rwhitby.net/blog/nslu2-linux/setting-the-openmoko-timezone.html</guid>
		<description><![CDATA[If you want to set the timezone on your phone correctly, do the following: ipkg install tzdata ipkg install your desired tzdata-* packages. &#160;For instance, I use &#8220;tzdata-australia&#8220;. Enable your desired timezone by symlinking it to &#8220;/etc/localtime&#8220;. &#160;Adjust the following example command line for your locality. ln -s /usr/share/zoneinfo/Australia/Adelaide /etc/localtime The &#8220;date&#8221; command should now [...]]]></description>
			<content:encoded><![CDATA[<p>If you want to set the timezone on your phone correctly, do the following:</p>
<ol>
<li>ipkg install <b>tzdata</b></li>
<li>ipkg install your desired <b>tzdata-<i><locality></locality></i>*</b> packages. &nbsp;For instance, I use &#8220;<b>tzdata-australia</b>&#8220;.</li>
<li>Enable your desired timezone by symlinking it to &#8220;<b>/etc/localtime</b>&#8220;. &nbsp;Adjust the following example command line for your locality.</li>
<ul>
<li>ln -s /usr/share/zoneinfo/Australia/Adelaide /etc/localtime</li>
</ul>
<li>The &#8220;date&#8221; command should now show the correct time for your timezone. &nbsp;If it is not correct, then install the &#8220;<b>ntpclient</b>&#8221; package, and use it to set your clock.</li>
</ol>
<p>Note that this technique should work on any OpenEmbedded-based Linux distribution.
<ol></ol>
]]></content:encoded>
			<wfw:commentRss>http://www.rwhitby.net/blog/nslu2-linux/setting-the-openmoko-timezone.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Replacing dropbear with openssh</title>
		<link>http://www.rwhitby.net/blog/nslu2-linux/replacing-dropbear-with-openssh.html</link>
		<comments>http://www.rwhitby.net/blog/nslu2-linux/replacing-dropbear-with-openssh.html#comments</comments>
		<pubDate>Sat, 01 Sep 2007 05:57:05 +0000</pubDate>
		<dc:creator>Rod Whitby</dc:creator>
				<category><![CDATA[NSLU2-Linux]]></category>
		<category><![CDATA[OpenMoko]]></category>

		<guid isPermaLink="false">http://www.rwhitby.net/blog/nslu2-linux/replacing-dropbear-with-openssh.html</guid>
		<description><![CDATA[I prefer to use OpenSSH rather than Dropbear on my devices.&#160; The main reason is to get sftp support (which is required by sshfs).&#160; Another reason is to get better support for agent forwarding (which is essential for bouncing from one machine to another without leaving your private keys all over the internet). To do [...]]]></description>
			<content:encoded><![CDATA[<p>I prefer to use OpenSSH rather than Dropbear on my devices.&nbsp; The main reason is to get sftp support (which is required by sshfs).&nbsp; Another reason is to get better support for agent forwarding (which is essential for bouncing from one machine to another without leaving your private keys all over the internet).</p>
<p>To do this on OpenMoko (or any other OpenEmbedded-based distribution for that matter, for instance SlugOS or Angstrom):</p>
<ol>
<li>Edit <b>/etc/init.d/dropbear</b> by replacing &#8220;<b>DROPBEAR_PORT=22</b>&#8221; with &#8220;<b>DROPBEAR_PORT=2222</b>&#8221; (or any other unused port).</li>
<li>Run &#8220;<b>ipkg install -force-depends openssh</b>&#8221; to install openssh.</li>
<li>Make sure you have set a root password before rebooting (use &#8220;<b>passwd</b>&#8221; to set it).</li>
<li>Reboot (dropbear will restart on the new port, and openssh will start on the normal ssh port).</li>
<li>Check that openssh is now serving on port 22 by logging into the device over ssh.</li>
<li>Run &#8220;<b>ipkg remove -force-depends dropbear</b>&#8221; to remove dropbear.</li>
<li>Then run &#8220;<b>ipkg install openssh-sftp</b>&#8221; to install support for the sftp protocol which sshfs uses.</li>
</ol>
<p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.rwhitby.net/blog/nslu2-linux/replacing-dropbear-with-openssh.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Connecting a Treo650 to an OpenEmbedded-based firmware distribution</title>
		<link>http://www.rwhitby.net/blog/treo-650/connecting-a-treo650-to-an-openembedded-based-firmware-distribution.html</link>
		<comments>http://www.rwhitby.net/blog/treo-650/connecting-a-treo650-to-an-openembedded-based-firmware-distribution.html#comments</comments>
		<pubDate>Sat, 11 Aug 2007 09:29:14 +0000</pubDate>
		<dc:creator>Rod Whitby</dc:creator>
				<category><![CDATA[NSLU2-Linux]]></category>
		<category><![CDATA[OpenMoko]]></category>
		<category><![CDATA[Treo 650]]></category>

		<guid isPermaLink="false">http://www.rwhitby.net/blog/nslu2-linux/connecting-a-treo650-to-an-openembedded-based-firmware-distribution.html</guid>
		<description><![CDATA[The following should work for an NSLU2 running SlugOS or Angstrom, or a device running OpenMoko. Install the required kernel modules for bluetooth ipkg install kernel-module-hci-usb kernel-module-l2cap kernel-module-rfcomm depmod -a ipkg install bluez-utils Edit /etc/default/bluetooth to enable hcid and dund. Change the pin and host settings in /etc/bluetooth/hcid.conf, and make sure that the class is [...]]]></description>
			<content:encoded><![CDATA[<p>The following should work for an NSLU2 running SlugOS or Angstrom, or a device running OpenMoko.</p>
<ul>
<li>Install the required kernel modules for bluetooth</li>
<ul>
<li>ipkg install kernel-module-hci-usb kernel-module-l2cap kernel-module-rfcomm</li>
<li>depmod -a</li>
<li>ipkg install bluez-utils</li>
</ul>
<li>Edit /etc/default/bluetooth to enable hcid and dund.</li>
<li>Change the pin and host settings in /etc/bluetooth/hcid.conf, and make sure that the class is 0x3e0100 (not the default value, which is for a PDA like a Zaurus, not a &#8220;Computer&#8221; device like the Neo which can accept and route tcp/ip network connections coming in over dund or pand on the bluetooth network)</li>
<li>Reboot and test with &#8216;hciconfig&#8217; with a bluetooth dongle plugged in.</li>
<li>Install the required kernel modules for ppp</li>
<ul>
<li>ipkg install kernel-module-ppp-async kernel-module-bsd-comp kernel-module-ppp-deflate</li>
<li>depmod -a</li>
</ul>
<ul>
<li>ipkg install ppp</li>
</ul>
<li>Edit /etc/ppp/options as follows:<br />
<code><br />
noauth<br />
crtscts<br />
lock<br />
local<br />
proxyarp<br />
ktune<br />
192.168.1.XX:192.168.1.YY<br />
ms-dns 192.168.1.ZZ<br />
</code><br />
(edit the last two lines to suit your network topology, the first IP address<br />
is your gateway device, the second IP address will be assigned to the client,<br />
and the third IP address is your DNS server)</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.rwhitby.net/blog/treo-650/connecting-a-treo650-to-an-openembedded-based-firmware-distribution.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MokoSlug Custom Firmware for the NSLU2</title>
		<link>http://www.rwhitby.net/blog/nslu2-linux/mokoslug-idea.html</link>
		<comments>http://www.rwhitby.net/blog/nslu2-linux/mokoslug-idea.html#comments</comments>
		<pubDate>Thu, 25 Jan 2007 23:27:05 +0000</pubDate>
		<dc:creator>Rod Whitby</dc:creator>
				<category><![CDATA[NSLU2-Linux]]></category>
		<category><![CDATA[OpenMoko]]></category>

		<guid isPermaLink="false">http://www.rwhitby.net/blog/nslu2-linux/mokoslug-idea.html</guid>
		<description><![CDATA[The NSLU2 is a good low-cost companion server for the Neo 1973 (the initial hardware platform for OpenMoko). It has one 10/100 ethernet port, two USB 2.0 ports, and easily supports connectivity with the Neo via Bluetooth (using a low-cost USB Bluetooth dongle). I am creating a MokoSlug firmware distribution for the NSLU2 for this [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://www.nslu2-linux.org">NSLU2</a> is a good low-cost companion server for the Neo 1973 (the initial hardware platform for <a href="http://www.openmoko.com">OpenMoko</a>).  It has one 10/100 ethernet port, two USB 2.0 ports, and easily supports connectivity with the Neo via Bluetooth (using a low-cost <a href="http://www.newegg.com/Product/Product.asp?Item=N82E16833124143">USB Bluetooth dongle</a>).</p>
<p>I am creating a MokoSlug firmware distribution for the NSLU2 for this purpose.  It will be based on the <a href="http://www.angstrom-distribution.org">Angstrom distribution</a>, which is built using the <a href="http://www.openembedded.org">OpenEmbedded build system</a> (the same build system which is used for the OpenMoko software).</p>
<p>Like the <a href="http://www.nslu2-linux.org/wiki/SlugOS/HomePage">SlugOS firmware distribution for the NSLU2</a>, it will initially run from internal flash but will allow you to boot from an external USB disk or flash key if you need more storage for installation of additional <a href="http://ipkg.nslu2-linux.org/feeds/slugos-bag/cross/unstable/">software packages</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rwhitby.net/blog/nslu2-linux/mokoslug-idea.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

