<?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>HauntedShell &#187; wireless</title>
	<atom:link href="http://hauntedshell.com/tag/wireless/feed/" rel="self" type="application/rss+xml" />
	<link>http://hauntedshell.com</link>
	<description>Just another Hauntedshell.com weblog</description>
	<lastBuildDate>Sat, 01 May 2010 20:05:47 +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>Does your RADIUS server think &quot;user&quot; = &quot;USER&quot;?</title>
		<link>http://hauntedshell.com/2009/10/20/does-your-radius-server-think-user-user/</link>
		<comments>http://hauntedshell.com/2009/10/20/does-your-radius-server-think-user-user/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 12:45:23 +0000</pubDate>
		<dc:creator>Kwame</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[freeradius]]></category>
		<category><![CDATA[radius]]></category>
		<category><![CDATA[wireless]]></category>

		<guid isPermaLink="false">http://www.hauntedshell.com/uncategorized/does-your-radius-server-think-user-user/</guid>
		<description><![CDATA[If you happen to manage a hotspot that uses Freeradius with the sql module for authentication, you might want to pay attention. The default queries used by Freeradius sql module are case-insensitive. So if user &#8220;kwame&#8221; is successfully authenticated, another user &#8220;Kwame&#8221; can also successfully autheticate. And so can &#8220;KWAME&#8221;, &#8220;kwamE&#8221;, &#8220;KwaMe&#8221; and so on [...]]]></description>
			<content:encoded><![CDATA[<p>If you happen to manage a hotspot that uses Freeradius with the sql module for authentication, you might want to pay attention. The default queries used by Freeradius sql module are case-insensitive. So if user &#8220;kwame&#8221; is successfully authenticated, another user &#8220;Kwame&#8221; can also successfully autheticate. And so can<span id="more-157"></span> &#8220;KWAME&#8221;, &#8220;kwamE&#8221;, &#8220;KwaMe&#8221; and so on for that matter. I guess you can see where I&#8217;m going with this: if any of your users should catch on to this&#8230; And to think, this hadn&#8217;t crossed my mind till a friend who runs a wireless isp pointed out some strange activity he had noticed in his logs.</p>
<p>You shouldn&#8217;t forget to make a small change to the <em>/etc/freeradius/sql/mysql/dialup.conf(or </em><em>/etc/freeradius/sql.conf</em>) file. Somewhere around line 82 lies the following:</p>
<pre>#######################################################################
        # Use these for case sensitive usernames.
#        authorize_check_query = "SELECT id, username, attribute, value, op \
#         FROM ${authcheck_table} \
#         WHERE username = BINARY '%{SQL-User-Name}' \
#         ORDER BY id"
#        authorize_reply_query = "SELECT id, username, attribute, value, op \
#         FROM ${authreply_table} \
#         WHERE username = BINARY '%{SQL-User-Name}' \
#         ORDER BY id"

        # The default queries are case insensitive. (for compatibility with
        # older versions of FreeRADIUS)
       authorize_check_query = "SELECT id, username, attribute, value, op \
          FROM ${authcheck_table} \
          WHERE username = '%{SQL-User-Name}' \
          ORDER BY id"
       authorize_reply_query = "SELECT id, username, attribute, value, op \
          FROM ${authreply_table} \
          WHERE username = '%{SQL-User-Name}' \
          ORDER BY id"
</pre>
<p>This should be:</p>
<pre>#######################################################################
        # Use these for case sensitive usernames.
        authorize_check_query = "SELECT id, username, attribute, value, op \
         FROM ${authcheck_table} \
         WHERE username = BINARY '%{SQL-User-Name}' \
         ORDER BY id"
        authorize_reply_query = "SELECT id, username, attribute, value, op \
         FROM ${authreply_table} \
         WHERE username = BINARY '%{SQL-User-Name}' \
         ORDER BY id"

        # The default queries are case insensitive. (for compatibility with
        # older versions of FreeRADIUS)
#       authorize_check_query = "SELECT id, username, attribute, value, op \
#          FROM ${authcheck_table} \
#          WHERE username = '%{SQL-User-Name}' \
#          ORDER BY id"
#       authorize_reply_query = "SELECT id, username, attribute, value, op \
#          FROM ${authreply_table} \
#          WHERE username = '%{SQL-User-Name}' \
#          ORDER BY id"
</pre>
<p>And if you apply your attributes per group instead of per user, like I do, then this:</p>
<pre>
        # Use these for case sensitive usernames.
#        group_membership_query = "SELECT groupname \
#        FROM ${usergroup_table} \
#         WHERE username = BINARY '%{SQL-User-Name}' \
#        ORDER BY priority"

       group_membership_query = "SELECT groupname \
          FROM ${usergroup_table} \
          WHERE username = '%{SQL-User-Name}' \
          ORDER BY priority"
</pre>
<p>should become:</p>
<pre>
        # Use these for case sensitive usernames.
        group_membership_query = "SELECT groupname \
        FROM ${usergroup_table} \
         WHERE username = BINARY '%{SQL-User-Name}' \
        ORDER BY priority"

#       group_membership_query = "SELECT groupname \
#          FROM ${usergroup_table} \
#          WHERE username = '%{SQL-User-Name}' \
#          ORDER BY priority"
</pre>
<p>Reload the freeradius server and your usernames should be case sensitive. Now, go and buy yourself a beer in celebration of your valiant victory against the dark forces of computer insecurity.</p>
]]></content:encoded>
			<wfw:commentRss>http://hauntedshell.com/2009/10/20/does-your-radius-server-think-user-user/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Web Interface for OpenWrt Kamikaze</title>
		<link>http://hauntedshell.com/2007/09/20/web_interface_for_openwrt_kamikaze/</link>
		<comments>http://hauntedshell.com/2007/09/20/web_interface_for_openwrt_kamikaze/#comments</comments>
		<pubDate>Thu, 20 Sep 2007 11:58:41 +0000</pubDate>
		<dc:creator>Kwame</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[kamikaze]]></category>
		<category><![CDATA[meraki]]></category>
		<category><![CDATA[openwrt]]></category>
		<category><![CDATA[router]]></category>
		<category><![CDATA[wireless]]></category>

		<guid isPermaLink="false">http://hauntedshell.com/2007/09/20/web_interface_for_openwrt_kamikaze/</guid>
		<description><![CDATA[Warning: This can brick your router. Goes without saying, I will not take responsibility for whatever havoc you wreak. You have been warned. If you use your router for internet access, tt's best to have an alternative method of getting online.  You have been warned!<br />]]></description>
			<content:encoded><![CDATA[<p>Warning: This can brick your router. Goes without saying, I will not take responsibility for whatever havoc you wreak. You have been warned. If you use your router for internet access, tt&#8217;s best to have an alternative method of getting online.  You have been warned!</p>
<p>I have a Meraki mini I&#8217;ve been playing around with. I&#8217;m running OpenWRT Kamikaze 7.06 on it and I love it. It&#8217;s very flexible piece of hardware and comes with an 8mb flash and 32mb of RAM, which is more than enough for the stuff I run on it. The only annoying thing is the lack of a web interface.<span id="more-10"></span> It&#8217;s not that I have problems with using the terminal; it&#8217;s just that, it becomes annoying to switch on my desktop just to attend to a minor detail. Or I&#8217;m downstairs in a friend&#8217;s room and just need to check if my internet connection is alive. A web interface would allow me do all that from a browser as long as I was connected to the network.<br />
Thankfuly there&#8217;s the Webif frontend by <a href="http://x-wrt.org">X-WRT </a>.  From what I&#8217;ve seen so far, it&#8217;s quite good though it&#8217;s still beta.  It does everything I want it to do so I can&#8217;t complain. </p>
<p><b>Installing</b><br />
You first need to install the haserl package, which webif depends on.Telnet or SSH into your router and enter the following:</p>
<blockquote><p>
	ipkg update
</p></blockquote>
<p>
This updates your package list</p>
<blockquote><p>
	ipkg install haserl
</p></blockquote>
<p>
Installs haserl which allows you to embed shell scripts in html.</p>
<blockquote><p>
	ipkg install http://downloads.x-wrt.org/xwrt/kamikaze/7.06/atheros-2.6/webif_latest.ipk
</p></blockquote>
<p>
Download and install webif from the x-wrt.org site since webif is not yet in the kamikaze repository</p>
<p><b>Note: the webif install will reboot your router!!<br />
</b><br />
Once the router is back up, open up a browser of your choice and enter your router&#8217;s ip address. Voila</p>
]]></content:encoded>
			<wfw:commentRss>http://hauntedshell.com/2007/09/20/web_interface_for_openwrt_kamikaze/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Cantenna Chronicles &#8211; Part 1</title>
		<link>http://hauntedshell.com/2007/09/15/cantenna_chronicles_-_part_1/</link>
		<comments>http://hauntedshell.com/2007/09/15/cantenna_chronicles_-_part_1/#comments</comments>
		<pubDate>Sat, 15 Sep 2007 19:51:23 +0000</pubDate>
		<dc:creator>Kwame</dc:creator>
				<category><![CDATA[DIY]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[cantenna]]></category>
		<category><![CDATA[homebrew]]></category>
		<category><![CDATA[wifi]]></category>
		<category><![CDATA[wireless]]></category>

		<guid isPermaLink="false">http://hauntedshell.com/2007/09/15/cantenna_chronicles_-_part_1/</guid>
		<description><![CDATA[One of the problems I have with living off campus is that of internet access.. There is a wireless hotspot I can connect to but who want's to pay for slow internet access when you can get slightly faster internet access for free. The only hitch: I live so far from c ampus, my received signal levels are just depressing.]]></description>
			<content:encoded><![CDATA[<p>One of the problems I have with living off campus is that of internet access.. There is a wireless hotspot I can connect to but who want&#8217;s to pay for slow internet access when you can get slightly faster internet access for free. The only hitch: I live so far from campus, my received signal levels are just depressing.<br />
<a href="/files/images/site_map_wifi.jpg"><img src="/files/images/site_map_wifi.jpg" alt="Location Map. Yeah, quite a distance" height="260" width="400" /></a><br />
That leaves me with three options:<br />
<span id="more-9"></span></p>
<ul>
<li>Forget about ever getting internet access ( not really much of a choice).</li>
<li>Suscribe to the commercial hotspot.</li>
<li>Find a way to improve my signal level</li>
</ul>
<p>Now the first option is like asking me not to breathe. The second is not such a bad option, I make it a point not to pay for internet access if I can get it for free (umm&#8230;. legally of course. &gt;:) ). So I guess it&#8217;s time to get out my toolkit and start voiding warranties. Now the best way to improve your wireless signal is to get a better antenna. I didn&#8217;t have much in the way of resources so I decided to opt of a &#8216;cantenna&#8217;, which basically is a waveguide antenna (if you need details, you won&#8217;t find them here. Ever heard of google?). Anyways, what I needed was a tin can, a bit of thick copper wire, an N-connector and a pigtail. Now anyone who lives in Ghana knows those last two items are virually impossible to find. So I had to improvise. I had these cables for an indoor antenna I got from a friend. One end has a magnetic base with a female SMA connector and the other end has a male SMA connector. There was also an SMA to RP-TNC connector included as well.</p>
<p align="left">
So I&#8217;ll it a try and see what happens. Updates coming soon.</p>
]]></content:encoded>
			<wfw:commentRss>http://hauntedshell.com/2007/09/15/cantenna_chronicles_-_part_1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Unbricking Linksys WRT54G v5</title>
		<link>http://hauntedshell.com/2007/09/11/unbricking_linksys_wrt54g_v5/</link>
		<comments>http://hauntedshell.com/2007/09/11/unbricking_linksys_wrt54g_v5/#comments</comments>
		<pubDate>Tue, 11 Sep 2007 02:07:28 +0000</pubDate>
		<dc:creator>Kwame</dc:creator>
				<category><![CDATA[DIY]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[linksys wrt54g]]></category>
		<category><![CDATA[unbricking]]></category>
		<category><![CDATA[wireless]]></category>

		<guid isPermaLink="false">http://hauntedshell.com/2007/09/11/unbricking_linksys_wrt54g_v5/</guid>
		<description><![CDATA[Before I begin: This <b><u>WILL</u></b> void your warranty (if you haven't done that already) and <b>might result in damage to your router</b> or <b>cause you to sustain injury</b>. You have been warned. I <u>will not</u> take any responsibility for any mishaps that may occur as a result of this post.
<p align="left">
&#160;
</p>]]></description>
			<content:encoded><![CDATA[<p align="left">Before I begin: This <strong><span style="text-decoration: underline">WILL</span></strong> void your warranty (if you haven&#8217;t done that already) and <strong>might result in damage to your router</strong> or <strong>cause you to sustain injury</strong>. You have been warned. I <span style="text-decoration: underline">will not</span> take any responsibility for any mishaps that may occur as a result of this post.</p>
<p>My Linksys WRT54G version 5 suddenly stopped working over the weekend. On powering the router, all lights powered on and stayed that way. I had previously been running DD-WRT Micro.I tried holding the reset button for 30 seconds, powering the router, holding for another 30 seconds and then usnig TFTP tool to flash the router but that did not work. My situation was desperate and I was ready for desperate measures.<span id="more-8"></span> So I used this guide : <a href="http://voidmain.is-a-geek.net/redhat/wrt54g_revival.html">http://voidmain.is-a-geek.net/redhat/wrt54g_revival.html</a> So I had to open up the router and short out pins 15-16 on the chip. The problem though was that in the pictures I saw, there were differences in the location of some of the components. So I&#8217;m posting a picture of what my board looks like just in case anyone has something similar to mine:</p>
<p><a href="http://www.hauntedshell.com/wp-content/files/images/router_board.jpg"><img title="WRT54G v5 board" src="http://www.hauntedshell.com/wp-content/files/images/router_board.jpg" border="0" alt="WRT54G v5 board" width="320" height="240" /></a></p>
<p align="left">I won&#8217;t go into the details of the process since they are already  <a href="http://voidmain.is-a-geek.net/redhat/wrt54g_revival.html">documented elsewhere</a>. All I&#8217;ll add is, funnily enough, after shorting out the pins, my router started working properly without me needed to reflash the firmware. Might work differently for you though.</p>
]]></content:encoded>
			<wfw:commentRss>http://hauntedshell.com/2007/09/11/unbricking_linksys_wrt54g_v5/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
