<?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>Jannich Brendle&#039;s blog &#187; OpenWrt</title>
	<atom:link href="http://bredsaal.dk/tag/openwrt/feed" rel="self" type="application/rss+xml" />
	<link>http://bredsaal.dk</link>
	<description>My name is Jannich - I blog!</description>
	<lastBuildDate>Mon, 12 Jul 2010 10:54:52 +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>Upgrading to OpenWRT 10.03 backfire on Asus WL-500gp</title>
		<link>http://bredsaal.dk/upgrading-to-openwrt-10-03-backfire-on-asus-wl-500gp</link>
		<comments>http://bredsaal.dk/upgrading-to-openwrt-10-03-backfire-on-asus-wl-500gp#comments</comments>
		<pubDate>Thu, 10 Jun 2010 18:57:35 +0000</pubDate>
		<dc:creator>Jannich Brendle</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[happy]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[OpenWrt]]></category>

		<guid isPermaLink="false">http://bredsaal.dk/?p=973</guid>
		<description><![CDATA[I&#8217;ve just gotten a new internet connection, from TDC, which included a wireless router. That means that I can play with my Asus WL-500gp. The first step was upgrading to OpenWRT 10.03, which was really easy: cd /tmp/ wget http://downloads.openwrt.org/backfire/10.03/brcm47xx/openwrt-brcm47xx-squashfs.trx sysupgrade openwrt-brcm-2.4-squashfs.trx reboot Now it&#8217;s playtime!]]></description>
		<wfw:commentRss>http://bredsaal.dk/upgrading-to-openwrt-10-03-backfire-on-asus-wl-500gp/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OpenWrt USB automount on boot</title>
		<link>http://bredsaal.dk/openwrt-usb-automount-on-boot</link>
		<comments>http://bredsaal.dk/openwrt-usb-automount-on-boot#comments</comments>
		<pubDate>Mon, 19 Oct 2009 22:34:46 +0000</pubDate>
		<dc:creator>Jannich Brendle</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[OpenWrt]]></category>

		<guid isPermaLink="false">http://bredsaal.dk/blog/OpenWrt+USB+automount+on+boot</guid>
		<description><![CDATA[To automatically mount a harddrive partition on a OpenWrt enabled router with USB, insert this into /etc/init.d/usbmount on your router: #!/bin/sh /etc/rc.common START=80 STOP=40 start() { echo -n "Enabling swap: " swapon /dev/scsi/host0/bus0/target0/lun0/part1 echo -n "Testing USB Partition: " e2fsck -p /dev/scsi/host0/bus0/target0/lun0/part2 &#38; sleep 5 echo -n "Mounting USB drive: " mount -t ext3 -o [...]]]></description>
		<wfw:commentRss>http://bredsaal.dk/openwrt-usb-automount-on-boot/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building an OpenWrt twitter client</title>
		<link>http://bredsaal.dk/building-an-openwrt-twitter-client</link>
		<comments>http://bredsaal.dk/building-an-openwrt-twitter-client#comments</comments>
		<pubDate>Sun, 27 Sep 2009 01:02:22 +0000</pubDate>
		<dc:creator>Jannich Brendle</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[OpenWrt]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://bredsaal.dk/blog/Building+an+OpenWrt+twitter+client</guid>
		<description><![CDATA[Alright, I was looking through the referrers to my blog, and saw this search term that came from google.com &#8220;openwrt twitter client&#8221;. I have no idea why you would want a twitter client on your router, but still, I was inspired to write a simple script that would allow you to tweet from the commandline of [...]]]></description>
		<wfw:commentRss>http://bredsaal.dk/building-an-openwrt-twitter-client/feed</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Reading logfiles on OpenWrt</title>
		<link>http://bredsaal.dk/reading-logfiles-on-openwrt</link>
		<comments>http://bredsaal.dk/reading-logfiles-on-openwrt#comments</comments>
		<pubDate>Mon, 21 Sep 2009 16:25:16 +0000</pubDate>
		<dc:creator>Jannich Brendle</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[OpenWrt]]></category>

		<guid isPermaLink="false">http://bredsaal.dk/blog/Reading+logfiles+on+OpenWrt</guid>
		<description><![CDATA[If you are used to Linux systems, you know that logfiles are usually located in /var/log/ &#8211; but there is only three files in that directory on OpenWrt: root@OpenWrt:~# ls /var/log/ lastlog messages wtmp root@OpenWrt:~# cat /var/log/* Sep 21 15:56:26 OpenWrt syslog.info syslogd started: BusyBox v1.11.2 root@OpenWrt:~# So, to read the logfile from syslogd you [...]]]></description>
		<wfw:commentRss>http://bredsaal.dk/reading-logfiles-on-openwrt/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Some small iptables on OpenWrt tips</title>
		<link>http://bredsaal.dk/some-small-iptables-on-openwrt-tips</link>
		<comments>http://bredsaal.dk/some-small-iptables-on-openwrt-tips#comments</comments>
		<pubDate>Mon, 14 Sep 2009 21:51:54 +0000</pubDate>
		<dc:creator>Jannich Brendle</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[iptables]]></category>
		<category><![CDATA[OpenWrt]]></category>

		<guid isPermaLink="false">http://bredsaal.dk/blog/Some+small+iptables+on+OpenWrt+tips</guid>
		<description><![CDATA[I have noticed a lot of people have issues with iptables on openwrt, so I have gathered a few tips that I&#8217;ve used myself. All the examples should be put in the file /etc/iptables.user on your openWrt router, and you should restart iptables every time you insert a rule with this command /etc/init.d/firewall restart. Blocking [...]]]></description>
		<wfw:commentRss>http://bredsaal.dk/some-small-iptables-on-openwrt-tips/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Trust nobody (or nothing)</title>
		<link>http://bredsaal.dk/trust-nobody-or-nothing</link>
		<comments>http://bredsaal.dk/trust-nobody-or-nothing#comments</comments>
		<pubDate>Sat, 05 Sep 2009 02:59:02 +0000</pubDate>
		<dc:creator>Jannich Brendle</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[oops]]></category>
		<category><![CDATA[OpenWrt]]></category>

		<guid isPermaLink="false">http://bredsaal.dk/blog/Trust+nobody+%28or+nothing%29</guid>
		<description><![CDATA[Earlier tonight, I made a shellscript to automatically remove unused shared libraries from an openwrt router, using opkg whatdepends $libraryname &#8211; and it worked. It reported seven libraries installed but not used by any other package, so I figured that they were safe to remove. NOTHING could be further from the thruth! One of the libraries [...]]]></description>
		<wfw:commentRss>http://bredsaal.dk/trust-nobody-or-nothing/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Blocking a port range in OpenWRT using iptables</title>
		<link>http://bredsaal.dk/blocking-a-port-range-in-openwrt-using-iptables</link>
		<comments>http://bredsaal.dk/blocking-a-port-range-in-openwrt-using-iptables#comments</comments>
		<pubDate>Thu, 20 Aug 2009 23:33:32 +0000</pubDate>
		<dc:creator>Jannich Brendle</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[iptables]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[OpenWrt]]></category>

		<guid isPermaLink="false">http://bredsaal.dk/blog/Blocking+a+port+range+in+OpenWRT+using+iptables</guid>
		<description><![CDATA[Some time ago, I had to make sure that clients on my home network could not connect to any hosts on the internet, ports 6000 to 65000 (both inclusive) &#8211; since I thought it was the easier way to block bittorrent on OpenWRT. Today I needed that again, so just as a reminder to myself, [...]]]></description>
		<wfw:commentRss>http://bredsaal.dk/blocking-a-port-range-in-openwrt-using-iptables/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Controlling transmission using json-rpc in perl</title>
		<link>http://bredsaal.dk/controlling-transmission-using-json-rpc-in-perl</link>
		<comments>http://bredsaal.dk/controlling-transmission-using-json-rpc-in-perl#comments</comments>
		<pubDate>Thu, 09 Jul 2009 23:53:40 +0000</pubDate>
		<dc:creator>Jannich Brendle</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[OpenWrt]]></category>
		<category><![CDATA[perl]]></category>
		<category><![CDATA[transmission]]></category>

		<guid isPermaLink="false">http://bredsaal.dk/blog/Controlling+transmission+using+json-rpc+in+perl</guid>
		<description><![CDATA[For some time I have wanted to play with the json-rpc interface of Transmission. Today I jumped into it. I decided to make a program that would run on my local computer and should be called via cron every X minutes, and scan a directory for .torrent files. Any .torrent files found should be added [...]]]></description>
		<wfw:commentRss>http://bredsaal.dk/controlling-transmission-using-json-rpc-in-perl/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Startup script for transmission on OpenWrt.</title>
		<link>http://bredsaal.dk/startup-script-for-transmission-on-openwrt</link>
		<comments>http://bredsaal.dk/startup-script-for-transmission-on-openwrt#comments</comments>
		<pubDate>Thu, 09 Jul 2009 23:15:19 +0000</pubDate>
		<dc:creator>Jannich Brendle</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[OpenWrt]]></category>
		<category><![CDATA[transmission]]></category>

		<guid isPermaLink="false">http://bredsaal.dk/blog/Startup+script+for+transmission+on+OpenWrt.</guid>
		<description><![CDATA[I wrote a blog some time ago describing running transmission on OpenWrt. Apparently I forgot to include the startup script in the blogpost, so I am posting it here. Insert the following snippet into /etc/init.d/transmission. #!/bin/sh /etc/rc.common START=99 start(){ # Adjust as needed. username=username password=password torrentpath=/mnt/torrent transmission-daemon -b -f -p 9091 -t -u $username -v [...]]]></description>
		<wfw:commentRss>http://bredsaal.dk/startup-script-for-transmission-on-openwrt/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OpenWRT and sshfs</title>
		<link>http://bredsaal.dk/openwrt-and-sshfs</link>
		<comments>http://bredsaal.dk/openwrt-and-sshfs#comments</comments>
		<pubDate>Mon, 04 May 2009 23:32:11 +0000</pubDate>
		<dc:creator>Jannich Brendle</dc:creator>
				<category><![CDATA[howto]]></category>
		<category><![CDATA[OpenWrt]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[sshfs]]></category>

		<guid isPermaLink="false">http://bredsaal.dk/blog/OpenWRT+and+sshfs</guid>
		<description><![CDATA[This is just a short note to explain how to mount your routers filesystem via sshfs. On your router: opkg install openssh-sftp-server On your computer: sshfs root@router:/remote/directory/ /local/mountpoint/ -o sftp_server=/usr/libexec/sftp-server Easy as that. Enjoy.]]></description>
		<wfw:commentRss>http://bredsaal.dk/openwrt-and-sshfs/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
