tag:blogger.com,1999:blog-71649042024-03-13T14:36:31.077+02:00Community Owned Information NetworkWelcome to the CSIR Meraka Institute's "COIN" Blogking davidhttp://www.blogger.com/profile/17101894497352927717noreply@blogger.comBlogger112125tag:blogger.com,1999:blog-7164904.post-1132657464902035852005-11-22T13:04:00.000+02:002005-11-22T13:04:24.956+02:00The Wiki is taking shape<DIV> Thanks for all the contributions so far, please feel free to move your Blog postings over to the wiki: <i><font color="#0000ff"><u><a href="http://wirelessafrica.meraka.org.za/wiki/">http://wirelessafrica.meraka.org.za/wiki/</a></u></font></i> </DIV> <DIV> </DIV> <DIV> Ciao! </DIV>Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-7164904.post-1132141273843982082005-11-16T13:41:00.000+02:002005-11-16T13:58:07.260+02:00New home for CSIR COIN Blog<DIV>The information on this Blog is currently being moved to a new home, which will hopefully allow for more interactivity and organisation. A link to the new home will be made available on <A href="http://wirelessafrica.meraka.org.za/">http://wirelessafrica.meraka.org.za/</A> when sufficiently populated. </DIV> <DIV> </DIV>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7164904.post-1129234044767143532005-10-13T21:59:00.000+02:002005-10-13T22:07:24.773+02:00Best collection of links I've seen for ad hoc networkinghttp://www.antd.nist.gov/wctg/manet/adhoclinks.htmlking davidhttp://www.blogger.com/profile/17101894497352927717noreply@blogger.com1tag:blogger.com,1999:blog-7164904.post-1129112994618425012005-10-12T12:27:00.000+02:002005-10-12T12:29:54.626+02:00wistron CM9 Altheros MiniPCI card infoWiki on the Wistron CM9<br />http://melbourne.wireless.org.au/wiki/?CM9<br /><br />Latest windows drivers<br />http://www.phoenixnetworks.net/atheros.php<br /><br />Product information<br />http://www.wneweb.com/wireless/products/cm9.htmking davidhttp://www.blogger.com/profile/17101894497352927717noreply@blogger.com1tag:blogger.com,1999:blog-7164904.post-1129014448529408932005-10-11T09:07:00.000+02:002005-10-11T09:07:28.586+02:00Engineering News Article Its amazing how a simple idea like the cantenna has grabbed the attention of the media. So far I've been interviewed on SABC Africa and by Engineering News (<a href="http://www.engineeringnews.co.za/?show=74454">Tin-can bridge to digital society</a>). One would have thought that the technical, innovative stuff we're doing with ad-hoc networking in the larger project would have more interest. I suppose that its easier to grasp the imagination with simplicity.Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-7164904.post-1128284441461873992005-10-02T22:13:00.000+02:002005-10-02T22:20:41.506+02:00Making sense of LQ ILQ and ETX in OLSRYou will see a table like this in the OLSR status screen on Freifunk<br /><br /><h2>Topology entries</h2> <table align="center" border="1" cellpadding="0" cellspacing="0" width="100%"> <tbody><tr><th>Destination IP</th><th>Last hop IP</th><th>LQ</th><th>ILQ</th><th>ETX</th></tr> <tr><td>10.51.1.13</td><td>10.51.1.10</td><td>1.00</td><td>1.00</td><td>1.00</td></tr> <tr><td>10.51.1.20</td><td>10.51.1.10</td><td>1.00</td><td>1.00</td><td>1.00</td></tr> <tr><td>10.51.1.1</td><td>10.51.1.13</td><td>0.90</td><td>1.00</td><td>1.11</td></tr> <tr><td>10.51.1.10</td><td>10.51.1.13</td><td>1.00</td><td>1.00</td><td>1.00</td></tr> <tr><td>10.51.1.12</td><td>10.51.1.13</td><td>1.00</td><td>0.90</td><td>1.11</td></tr> <tr><td>10.51.1.14</td><td>10.51.1.13</td><td>0.90</td><td>1.00</td><td>1.11</td></tr> <tr><td>10.51.1.20</td><td>10.51.1.13</td><td>1.00</td><td>1.00</td><td>1.00</td></tr> <tr><td>10.51.1.13</td><td>10.51.1.14</td><td>1.00</td><td>0.90</td><td>1.11</td></tr> <tr><td>10.51.1.1</td><td>10.51.1.20</td><td>0.90</td><td>0.75</td><td>1.49</td></tr> <tr><td>10.51.1.10</td><td>10.51.1.20</td><td>1.00</td><td>1.00</td><td>1.00</td></tr> <tr><td>10.51.1.12</td><td>10.51.1.20</td><td>1.00</td><td>1.00</td><td>1.00</td></tr> <tr><td>10.51.1.13</td><td>10.51.1.20</td><td>1.00</td><td>1.00</td><td>1.00</td></tr></tbody> </table><br /><br /><h2><span style="font-size:100%;">LQ = The percentage of packets that are succesfully sent from youself to the neighbour<br /></span></h2> ILQ = The percentage of packets that succesfully are sent from your neighbour to yourself also often called NLQ<br /><br />ETX = Expected Trasnmission count = How many trasnmission attempts are required to get packets through = 1 / (LQ*ILQ)king davidhttp://www.blogger.com/profile/17101894497352927717noreply@blogger.com2tag:blogger.com,1999:blog-7164904.post-1128197053667763842005-10-01T21:13:00.000+02:002005-10-01T22:04:13.713+02:00Getting an OpenWRT Freifunk mesh stable<span class="postbody">After a lot of tweaking OLSR running on Linksys has had no "ping down" messages for about 5 days now. Some of the tips to getting OLSR on OpenWRT stable.<br /><br />1. Lock all the nodes to 802.11B don't let it auto sense<br />2. If there are any v2.2 hardware devices, change the clock speed to 216MHz with the following commands1<br /><br /># nvram set clkfreq=216<br /># nvram commit<br /># reboot<br /><br />3. Lock the RX and TX antenna to the one you connected your external antenna too, don't use AUTO. TAKE NOTE!!! On Version 2.0 hardware Antenna A is on the left looking from the front of the linksys and and on Version 2.,2 hardware Antenna A is on the right looking from the fron of the linksys. This caught me out a few times.<br /> </span>king davidhttp://www.blogger.com/profile/17101894497352927717noreply@blogger.com1tag:blogger.com,1999:blog-7164904.post-1127116055439846542005-09-19T09:47:00.000+02:002005-09-19T10:01:26.750+02:00International Wireless Summit 2005<a href="http://www.iws2005.org/">International Wireless Summit 2005, Aalborg, Denmark</a><br/><br/>The international wireless summit has just kicked off and I have the privilege of being amongst some of the greatest think-tanks in the wireless arena.<br/><br/>The aim of the IWS is to offer a platform for establishing exchanges of information between universities, industry and science parks. The next summit will be in 2008 in Helsinki, Finland.<br/><br/>International Wireless Symposium aims to exchange research information. 450 papers to be presented on “hot topics”. <br/><br/><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://photos1.blogger.com/blogger/521/328/1600/Image%2813%291.jpg"><img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;" src="http://photos1.blogger.com/blogger/521/328/320/Image%2813%291.jpg" border="0" alt="" /></a><br/><br/>Prof. Ramjee Prasad giving introductory speech.<br/><br/>Prof. Ramjee Prasad predicts that the future of wireless comms will be based on single layer technology, not quite sure what is meant by this though.<br/><br/>“Personal Networks are going to be of major importance in future business…”<br/>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7164904.post-1126276135625502862005-09-09T16:28:00.000+02:002005-09-09T16:28:55.676+02:00Network stats on Freifunk<DIV> See: <font color="#0000ff"><u><a href="http://wiki.freifunk-leipzig.public-ip.org/index.php/LinksysNetzwerkStatisik"><i>http://wiki.freifunk-leipzig.public-ip.org/index.php/LinksysNetzwerkStatisik</i></a></u></font> for info on how to install web interface packages for network stats. </DIV> <DIV> </DIV> <DIV> p.s. hows your german? </DIV>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7164904.post-1126211731804571372005-09-08T22:31:00.000+02:002005-09-08T22:35:31.806+02:00How to stop dhcp client over-writing resolv.confFinally I found out how to do it<br /><br />Edit the /etc/dhcp3/dhclient.conf file<br />Find the line that says request<br /><br />Comment out the line that requests for domain-name, domain-name-servers and host-name<br /><br /><span style="font-size:78%;">request subnet-mask, broadcast-address, time-offset, routers,<br /># domain-name, domain-name-servers, host-name,<br /> netbios-name-servers, netbios-scope;<br /></span>king davidhttp://www.blogger.com/profile/17101894497352927717noreply@blogger.com0tag:blogger.com,1999:blog-7164904.post-1126211474007577402005-09-08T22:06:00.000+02:002005-09-08T22:31:14.013+02:00Setting up different networking scenarios on a laptopI have always wanted to write some good scripts that configure my laptop for home and work wireless/ethernet automatically in ubuntu and so I set about building up a set of scripts that I can call.<br /><br />I have four scenarios:<br />1. use laptop at home with wireless access point<br />2. use laptop at home with ethernet<br />3. use laptop at work with wireless access point<br />4. use laptop at work with ethernet<br /><br />I created two files in /etc/network: interfaces.work and interfaces.home with all the ethernet and wireless settings for home and work in this file<br /><br /><span style="font-weight: bold;">/etc/network/interfaces.home</span><br /><span style="font-size:78%;"># This file describes the network interfaces available on your system<br /># and how to activate them. For more information, see interfaces(5).<br /><br /># The loopback network interface<br />auto lo<br />iface lo inet loopback<br /><br /># The primary network interface<br />iface eth0 inet static<br />address 10.3.13.102<br />netmask 255.255.255.0<br />gateway 10.3.13.1<br /><br />#The wireless network interface<br />iface eth1 inet dhcp<br />wireless-essid pta-mesh<br />wireless-mode Ad-Hoc<br />wireless-channel 1<br />wireless-key off<br /></span><br /><span style="font-weight: bold;">/etc/network/interfaces.work</span><br /><span style="font-size:78%;"># This file describes the network interfaces available on your system<br /># and how to activate them. For more information, see interfaces(5).<br /><br /># The loopback network interface<br />auto lo<br />iface lo inet loopback<br /><br /># The primary network interface<br />iface eth0 inet dhcp<br /><br /># The wireless network interface<br />iface eth1 inet dhcp<br />wireless-essid icomtek<br />wireless_mode Managed<br />wireless-key off<br /></span><br />I also created two files with my dns and domain settings for home and work in /etc/ called resolv.home and resolv.work<br /><br /><span style="font-weight: bold;">resolv.home<br /></span><span style="font-size:78%;">search icomtek.csir.co.za elarduspark.org.za cids.org.za<br />nameserver 146.64.28.1 10.3.13.1<br /></span><span style="font-weight: bold;"><br />resolv.work<br /></span><span style="font-size:78%;">search icomtek.csir.co.za cids.org.za<br />nameserver 146.64.28.1</span><span style="font-weight: bold;"><br /><br /></span>Here are my scripts that configure my interfaces based on the above files<br /><br />1. Setup for wireless networking at home<br /><span style="font-weight: bold;">/usr/local/bin/homenet-wireless</span><br /><span style="font-size:78%;"><br />#!/bin/bash<br />echo Setting up network for home wireless network<br />sudo cp /etc/network/interfaces.home /etc/network/interfaces<br /><br />eth0_status=`ifconfig | grep eth0`<br />eth1_status=`ifconfig | grep eth1`<br /><br />if [ -n "$eth0_status" ]; then<br /> sudo ifdown eth0<br />fi<br /><br />if [ -n "$eth1_status" ]; then<br /> sudo ifdown eth1<br />fi<br /><br />sudo ifup eth1<br /><br />sudo cp /etc/resolv.home /etc/resolv.conf<br /></span><br />2. Setup for ethernet networking at home<br /><span style="font-weight: bold;">/usr/local/bin/homenet-fixed</span><br /><span style="font-size:78%;">#!/bin/bash<br />echo Setting up network for home ethernet<br />sudo cp /etc/network/interfaces.home /etc/network/interfaces<br />sudo cp /etc/resolv.home /etc/resolv.conf<br /><br />eth0_status=`ifconfig | grep eth0`<br />eth1_status=`ifconfig | grep eth1`<br /><br />if [ -n "$eth0_status" ]; then<br /> sudo ifdown eth0<br />fi<br /><br />if [ -n "$eth1_status" ]; then<br /> sudo ifdown eth1<br />fi<br /><br />sudo ifup eth0<br /></span><br />3. Setup for wireless at work<br /><span style="font-weight: bold;">/usr/local/bin/worknet-wireless</span><br /><span style="font-size:78%;">#!/bin/bash<br />echo Setting up network for work wireless network<br />sudo cp /etc/network/interfaces.work /etc/network/interfaces<br />sudo cp /etc/resolv.work /etc/resolv.conf<br /><br />eth0_status=`ifconfig | grep eth0`<br />eth1_status=`ifconfig | grep eth1`<br /><br />if [ -n "$eth0_status" ]; then<br /> sudo ifdown eth0<br />fi<br /><br />if [ -n "$eth1_status" ]; then<br /> sudo ifdown eth1<br />fi<br /><br />sudo ifup eth1<br /></span><br />4. Setup for ethernet at work<br /> <span style="font-weight: bold;">/usr/local/bin/worknet-fixed<br /></span><span style="font-size:78%;">#!/bin/bash<br />echo Setting up network for work ethernet<br />sudo cp /etc/network/interfaces.work /etc/network/interfaces<br />sudo cp /etc/resolv.work /etc/resolv.conf<br /><br />eth0_status=`ifconfig | grep eth0`<br />eth1_status=`ifconfig | grep eth1`<br /><br />if [ -n "$eth0_status" ]; then<br /> sudo ifdown eth0<br />fi<br /><br />if [ -n "$eth1_status" ]; then<br /> sudo ifdown eth1<br />fi<br /><br />sudo ifup eth0</span><span style="font-weight: bold;"><span style="font-weight: bold;"></span><br /></span>king davidhttp://www.blogger.com/profile/17101894497352927717noreply@blogger.com0tag:blogger.com,1999:blog-7164904.post-1123711892787146392005-08-11T00:10:00.000+02:002005-08-11T00:24:41.136+02:00Setting up DHCP with OLSRThere have been so many misleading postings on this - I will finally set the record straight.<br /><br />You will need to reserve a block of IP's for non OLSR wireless clients that want to connect onto the mesh network such as a laptop. Here is an example setup:<br /><br />Wireless router 1:<br />Wireless IP: 10.51.1.13<br />LAN IP: 10.3.13.1<br />Subnet for Wireless DHCP clients: 10.51.1.64/28 (This would mean that 16 machines could potentially connect to this wireless router. The IP leases will be in the range from 10.51.1.64 to 10.51.1.79)<br /><br />Wireless router 2:<br />Wireless IP: 10.51.1.14<br />LAN IP: 10.3.14.1<br />Subnet for Wireless DHCP clients : 10.51.1.80/28 (IP leases will be in the range from 10.51.1.80 to 10.51.1.93)<br /><br />To set this up On Friefunk firmware<br />Wireless Router 1:<br />OLSR:<br />OLSR DHCP: 10.51.1.64/28<br /><br />Wireless Router 2:<br />OLSR:<br />OLSR DHCP: 10.51.1.80/28<br /><br /><br />Most people gave strange values for OLSR DHCP in their postings the most common one was:<br />OLSR DHCP: 10.51.1.80/28, 255.255.255.240<br /><br />The subnet mask after the comma (255.255.255.240) is an alternative to the slash format /28. <span style="font-weight: bold;">Why does everyone have this reduntant subnet mask on their postings???</span>king davidhttp://www.blogger.com/profile/17101894497352927717noreply@blogger.com0tag:blogger.com,1999:blog-7164904.post-1123452835981786092005-08-08T00:10:00.000+02:002005-08-08T00:13:56.006+02:00good info on checking linksys hardware version<p><strong><span style="font-weight: normal;">Finally some good info about finding the version number from outside markings and using NVRAM settings - info from www.openwrt.org</span><br /><br /></strong></p> <p><strong>Linksys WRT54G</strong> </p> <ol> <li><a href="http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRT54G#head-755412fb9789c00233194d6af2dd1a283d5af434">Hardware versions</a><ol><ol><li><a href="http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRT54G#head-55c2d0f7231454a88b632665f06cc5845eb29751">Identification by S/N</a></li></ol><li><a href="http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRT54G#head-f2fe3762941f7a18cbe23d7b5283fd75a6723094">WRT54G v1.0</a></li><li><a href="http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRT54G#head-433d63ecfb29f0a1e8a47a0789e01bc433b40d8a">WRT54G v1.1</a></li><li><a href="http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRT54G#head-75560cf44b7c5c269b04485b3cedfd58090167a3">WRT54G v2.0</a></li><li><a href="http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRT54G#head-44798ba5ce79c5cacbf793fbf159324db319c90b">WRT54G v2.2</a></li><li><a href="http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRT54G#head-1284d396869c9284b2b913b8a3f6f87bd1b61651">WRT54G v3.0 & WRT54G v3.1</a></li><li><a href="http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRT54G#head-e95587330908fc975c1dfc95f82d730e8702f6f9">WRT54G v4.00</a></li></ol> </li><li><a href="http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRT54G#head-15e21881961e4d9257c9c29f04d9a60bca860487">Table summary</a></li><li><a href="http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRT54G#head-bca76ba650d7e514d474e22b0e073dc1225a83df">Hardware hacking</a></li> </ol> <h4 id="head-755412fb9789c00233194d6af2dd1a283d5af434">1. Hardware versions</h4> <p>There are currently seven versions of the WRT54G (v1.0, v1.1, v2.0, v2.2, v3.0, v3.1, v4.00). With the exception of v4.00 devices (it is currently marked as untested for White Russian RC1), the WRT54G units are supported by <a href="http://wiki.openwrt.org/OpenWrt">OpenWrt</a> 1.0 (White Russian) and later. boot_wait is off by default on these routers, so you should turn it on. The version number is found on the label on the bottom of the front part of the case below the Linksys logo. </p> <h6 id="head-55c2d0f7231454a88b632665f06cc5845eb29751">1.0.1. Identification by S/N</h6> <p>Useful for identifying shrinkwrapped units. The <strong>S/N</strong> can be found on the box, below the UPC barcode. </p> <div> <table style=""> <tbody><tr> <td colspan="2" style="text-align: center;"> <p> <img src="http://wiki.openwrt.org/wiki/classic/img/idea.png" alt="(!)" height="15" width="15" /> <strong>Please contribute to this list.</strong> <img src="http://wiki.openwrt.org/wiki/classic/img/idea.png" alt="(!)" height="15" width="15" /> </p></td> <td colspan="2" style="text-align: center;"> <p><strong>OpenWRT</strong></p></td> </tr> <tr> <td> <p><strong>Model</strong></p></td> <td> <p><strong>S/N</strong></p></td> <td> <p><strong>CVS</strong></p></td> <td> <p><strong>EXP</strong></p></td> </tr> <tr> <td colspan="1" style="text-align: left;" rowspan="2"> <p>WRT54G v1.1</p></td> <td> <p>CDF20xxxxxxx</p></td> <td colspan="1" style="text-align: center;" rowspan="2"> <p> <img src="http://wiki.openwrt.org/wiki/classic/img/checkmark.png" alt="(./)" height="15" width="20" /> </p></td> <td colspan="1" style="text-align: center;" rowspan="2"> <p> <img src="http://wiki.openwrt.org/wiki/classic/img/checkmark.png" alt="(./)" height="15" width="20" /> </p></td> </tr> <tr> <td> <p>CDF30xxxxxxx</p></td> </tr> <tr> <td> <p>WRT54G v2</p></td> <td> <p>CDF50xxxxxxx</p></td> <td style="text-align: center;"> <p> <img src="http://wiki.openwrt.org/wiki/classic/img/checkmark.png" alt="(./)" height="15" width="20" /> </p></td> <td style="text-align: center;"> <p> <img src="http://wiki.openwrt.org/wiki/classic/img/checkmark.png" alt="(./)" height="15" width="20" /> </p></td> </tr> <tr> <td> <p>WRT54G v2.2</p></td> <td> <p>CDF70xxxxxxx</p></td> <td style="text-align: center;"> <p> <img src="http://wiki.openwrt.org/wiki/classic/img/icon-error.png" alt="{X}" height="16" width="16" /> </p></td> <td style="text-align: center;"> <p> <img src="http://wiki.openwrt.org/wiki/classic/img/checkmark.png" alt="(./)" height="15" width="20" /> </p></td> </tr> <tr> <td> <p>WRT54G v3</p></td> <td> <p>CDF80xxxxxxx</p></td> <td style="text-align: center;"> <p> <img src="http://wiki.openwrt.org/wiki/classic/img/icon-error.png" alt="{X}" height="16" width="16" /> </p></td> <td style="text-align: center;"> <p> <img src="http://wiki.openwrt.org/wiki/classic/img/checkmark.png" alt="(./)" height="15" width="20" /> </p></td> </tr> <tr> <td> <p>WRT54G v3.1 (AU?)</p></td> <td> <p>CDF90xxxxxxx</p></td> <td style="text-align: center;"> <p> <img src="http://wiki.openwrt.org/wiki/classic/img/icon-error.png" alt="{X}" height="16" width="16" /> </p></td> <td style="text-align: center;"> <p> <img src="http://wiki.openwrt.org/wiki/classic/img/checkmark.png" alt="(./)" height="15" width="20" /> </p></td> </tr> </tbody></table> </div> <h5 id="head-f2fe3762941f7a18cbe23d7b5283fd75a6723094">1.1. WRT54G v1.0</h5> <p>The WRT54G v1.0 is based on the Broadcom 4710 board. It has a 125MHz CPU, 4Mb flash and 16Mb SDRAM. The wireless NIC is a mini-PCI card. The switch is an ADM6996. </p> <h5 id="head-433d63ecfb29f0a1e8a47a0789e01bc433b40d8a">1.2. WRT54G v1.1</h5> <p>The WRT54G v1.1 is based on the Broadcom 4710 board. It has a 125MHz CPU, 4Mb flash and 16Mb SDRAM. The wireless NIC is soldered to the board. The switch is an ADM6996. </p> <p>Hardware informations (nvram) : </p> <pre>boardtype=bcm94710dev<br /></pre> <h5 id="head-75560cf44b7c5c269b04485b3cedfd58090167a3">1.3. WRT54G v2.0</h5> <p>The WRT54G v2.0 is based on the Broadcom 4712 board. It has a 200MHz CPU, 4Mb flash and 16Mb SDRAM. The wireless NIC is integrated to the board. The switch is an ADM6996. </p> <p>Hardware informations (nvram) : </p> <pre>boardtype=0x0101<br />boardflags=0x0188</pre> <h5 id="head-44798ba5ce79c5cacbf793fbf159324db319c90b">1.4. WRT54G v2.2</h5> <p>The WRT54G v2.2 is based on the Broadcom 4712 board. It has a 200MHz CPU, 4Mb flash and 16Mb DDR-SDRAM. The wireless NIC is integrated to the board. The switch is a BCM5325. </p> <p>Hardware informations (nvram) : </p> <pre>boardtype=0x0708<br />boardflags=0x0118</pre> <h5 id="head-1284d396869c9284b2b913b8a3f6f87bd1b61651">1.5. WRT54G v3.0 & WRT54G v3.1</h5> <p>This unit is just like the V2.2 Except it has an extra reboot button on the left front panel behind a Cisco logo. </p> <h5 id="head-e95587330908fc975c1dfc95f82d730e8702f6f9">1.6. WRT54G v4.00</h5> <p>Please add information for this revision. </p> <p>Hardware informations (nvram) : </p> <pre>boardrev=0x10<br />boardtype=0x0708<br />boardflags2=0<br />boardflags=0x0118<br />boardnum=42</pre> <p><img src="http://wiki.openwrt.org/wiki/classic/img/alert.png" alt="/!\" height="15" width="15" /> <strong>To take the front cover off of this unit you must first remove the small screws under the rubber covers of the front feet!</strong> </p> <h4 id="head-15e21881961e4d9257c9c29f04d9a60bca860487">2. Table summary</h4> <p>how to get info : </p> <p>* board info: nvram show | grep board | sort<br />* cpu model: cat /proc/cpuinfo | grep cpu </p> <div> <table> <tbody><tr> <td> <p><strong>Model</strong> </p></td> <td> <p><strong>boardrev</strong></p></td> <td> <p><strong>boardtype</strong></p></td> <td> <p><strong>boardflags</strong></p></td> <td> <p><strong>boardflags2</strong></p></td> <td> <p><strong>boardnum</strong></p></td> <td> <p><strong>wl0_corerev</strong></p></td> <td> <p><strong>cpu model</strong></p></td> </tr> <tr> <td> <p>WRT54G v1.1 </p></td> <td> <p> - </p></td> <td> <p> bcm94710dev </p></td> <td> <p> - </p></td> <td> <p> - </p></td> <td> <p> 42 </p></td> <td> <p> 5 </p></td> <td> <p> BCM4710 V0.0 </p></td> </tr> <tr> <td> <p>WRT54G v2.0 </p></td> <td> <p> - </p></td> <td> <p> 0x0101 </p></td> <td> <p> 0x0188 </p></td> <td> <p> - </p></td> <td> <p> - </p></td> <td> <p> - </p></td> <td> <p> BCM3302 V0.7 </p></td> </tr> <tr> <td> <p>WRT54G v2.2 </p></td> <td> <p> - </p></td> <td> <p> 0x0708 </p></td> <td> <p> 0x0118 </p></td> <td> <p> - </p></td> <td> <p> - </p></td> <td> <p> 7 </p></td> <td> <p> - </p></td> </tr> <tr> <td> <p>WRT54G v3.0 </p></td> <td> <p> 0x10 </p></td> <td> <p> 0x0708 </p></td> <td> <p> 0x0118 </p></td> <td> <p> 0 </p></td> <td> <p> 42 </p></td> <td> <p> 7 </p></td> <td> <p>BCM3302 V0.7</p></td> </tr> <tr> <td> <p>WRT54G v3.1 (AU?) </p></td> <td> <p> 0x10 </p></td> <td> <p> 0x0708 </p></td> <td> <p> 0x0118 </p></td> <td> <p> 0 </p></td> <td> <p> 42 </p></td> <td> <p> 7 </p></td> <td> <p>BCM3302 V0.7</p></td> </tr> <tr> <td> <p>WRT54G v4.0 </p></td> <td> <p> 0x10 </p></td> <td> <p> 0x0708 </p></td> <td> <p> 0x0118 </p></td> <td> <p> 0 </p></td> <td> <p> 42 </p></td> <td> <p> 7 </p></td> <td> <p>BCM3302 V0.7</p></td> </tr> <tr> <td> <p>WRT54GS v1.0 </p></td> <td> <p> 0x10 </p></td> <td> <p> 0x0101 </p></td> <td> <p> 0x0388 </p></td> <td> <p> 0 </p></td> <td> <p> 42 </p></td> <td> <p> 7 </p></td> <td> <p> BCM3302 V0.7 </p></td> </tr> <tr> <td> <p>WRT54GS v1.1 </p></td> <td> <p> 0x10 </p></td> <td> <p> 0x0708 </p></td> <td> <p> 0x0318 </p></td> <td> <p> 0 </p></td> <td> <p> 42 </p></td> <td> <p> - </p></td> <td> <p> - </p></td> </tr> <tr> <td> <p>Buffalo WBR-54G </p></td> <td> <p> 0x10 </p></td> <td> <p> bcm94710ap </p></td> <td> <p> 0x0188 </p></td> <td> <p> 2 </p></td> <td> <p> 42 </p></td> <td> <p> - </p></td> <td> <p> - </p></td> </tr> <tr> <td> <p>Toshiba WRC1000 </p></td> <td> <p> - </p></td> <td> <p> bcm94710r4 </p></td> <td> <p> - </p></td> <td> <p> - </p></td> <td> <p> 100 </p></td> <td> <p> - </p></td> <td> <p> - </p></td> </tr> <tr> <td> <p>Buffalo WBR2-G54S </p></td> <td> <p> 0x10 </p></td> <td> <p> 0x0101 </p></td> <td> <p> 0x0188 </p></td> <td> <p> 0 </p></td> <td> <p> 00 </p></td> <td> <p> - </p></td> <td> <p> - </p></td> </tr> <tr> <td> <p>Asus WL-500G Deluxe</p></td> <td> <p> 0x10 </p></td> <td> <p> bcm95365r </p></td> <td> <p> - </p></td> <td> <p> - </p></td> <td> <p> 45 </p></td> <td> <p> 5 </p></td> <td> <p>BCM3302 V0.7</p></td> </tr> </tbody></table> </div> <p>*other variables (nvram) of interest : boot_ver, pmon_ver, firmware_version, os_version </p> <p>please complete this table. Look at this thread : <a href="http://openwrt.org/forum/viewtopic.php?pid=8127#p8127"><img src="http://wiki.openwrt.org/wiki/classic/img/moin-www.png" alt="[WWW]" height="11" width="11" /> http://openwrt.org/forum/viewtopic.php?pid=8127#p8127</a> May be this table should move up to <a href="http://wiki.openwrt.org/OpenWrtDocs">OpenWrtDocs</a>/Hardware. </p> <h4 id="head-bca76ba650d7e514d474e22b0e073dc1225a83df">3. Hardware hacking</h4> <p>There are revision XH units of the WRT54G v2.0. These units have 32Mb of memory, but they are locked to 16Mb. You can unlock the remaining memory with changing some of the variables. Afterburner (aka. Speedbooster) mode can be enabled with some variables, too. </p> <p><img src="http://wiki.openwrt.org/wiki/classic/img/alert.png" alt="/!\" height="15" width="15" /> <strong>However, there are no guaranties, that these will work, and changing the memory configuration on a non-XH unit will give You a brick. Check the forums for more info.</strong> </p> If you have a look at the WRT54G v2.2 board, you can find on the left corner, near the power LED, an empty place for a 4 pins button. On the board it is printed as SW2. This is the second reset button you can find on WRT54G v3.0, except that it has not been soldered.king davidhttp://www.blogger.com/profile/17101894497352927717noreply@blogger.com0tag:blogger.com,1999:blog-7164904.post-1121335942482310342005-07-14T12:12:00.000+02:002005-07-14T12:12:22.483+02:00Running Kismet-Drone on a Linksys WRT54GInstall either the kismet or kismet_drone package. Then edit /etc/kismet_drone.conf and change the source from wrt54g,eth1,wrt45g to wrt54g,prism0,wrt54g.
<br />
<br />Then run kismet from your host, pc and off u go!Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7164904.post-1120430618592375212005-07-04T00:34:00.000+02:002005-07-04T00:43:38.596+02:00a few tips with olsr on openwrt freifunkI had this problem with the OLSR web interface on the Freifunk openwrt implementation. If entered the following for the HNA4 field<br /><br />HNA4: 10.3.13.1 255.255.255.0<br /><br />Which should advertise the whole 10.3.13.x net it would advertise the 10.0.0.0 net. I discovered that it needs the subnet mask in this format instead<br /><br />HNA4: 10.3.13.1/24<br /><br />A few other things I learnt<br /><br />1. NVRAM variable ff_hna4 stores the HNA4 setting<br />2. /etc/olsr.conf is ignored by freifunk<br />3. /rom/etc/olsrd.conf stores a permanent copy of the olsrd setup<br />4. /var/etc/olsrd.conf is a symbolic link to /tmp/etc/olsrd.conf ... this file is copied from /rom/etc/olsrd.conf into RAM (ramfs filesystem) and is the one called by olsrd.<br /><br />ps -A will reveal that olsrd is called as follows<br /><br />olsrd -f /var/etc/olsrd.conf -d 0king davidhttp://www.blogger.com/profile/17101894497352927717noreply@blogger.com0tag:blogger.com,1999:blog-7164904.post-1119990054014987902005-06-28T22:15:00.000+02:002005-06-28T22:29:15.416+02:00Linksys WRT54G hardware differencesThis has been bothering me - there are 5 different hardware versions of the WRT54G wireless router (1.0, 1.1, 2.0, 2.2, 3.0) and many of the open firmware platforms like openwrt or sveasoft (The betrayer of the word open) only run on particular hardware versions. The main changes are the processor, amount of RAM/FLASH, the wireless hardware and the ethernet hardware<br /><br />Check out all the differences here<br /><a href="http://www.linksysinfo.org/modules.php?name=Content&pa=showpage&pid=6">http://www.linksysinfo.org/modules.php?name=Content&pa=showpage&pid=6</a><br /><br />We have ordered three batches of Linksys hardware - I must check which hardware platforms we have<br /><br />My Linksys on my roof gave the following results<br /><br />Result of the command<br />$>cat /proc/cpuinfo<br /><br />system type : Broadcom BCM947XX<br />processor : 0<br />cpu model : BCM3302 V0.7<br />BogoMIPS : 199.47<br />wait instruction : no<br />microsecond timers : yes<br />tlb_entries : 32<br />extra interrupt vector : no<br />hardware watchpoint : no<br />VCED exceptions : not available<br />VCEI exceptions : not available<br />dcache hits : 3472555964<br />dcache misses : 1631950511<br />icache hits : 264142837<br />icache misses : 2075639807<br />instructions : 0<br /><br />Some of the possible clue NVRAM settings when running the command<br />$>NVRAM show<br /><br />boardrev=0x10<br />bootver-v2.3<br />boardnum=42king davidhttp://www.blogger.com/profile/17101894497352927717noreply@blogger.com0tag:blogger.com,1999:blog-7164904.post-1119512495338864842005-06-23T09:39:00.000+02:002005-06-23T09:41:35.343+02:00Setting up OLSR mesh on a LinksysSetting up OLSR mesh on a Linksys ( Assumes a stock standard Linksys out of the box)<br /><br />1. Download freifunk firmware from (http://www.freifunk.net/wiki/FreifunkFirmwareEnglish) - openwrt-g-freifunk-1.0.2-en.bin<br /><br />2. Set boot wait on linksys<br /><br />Web method:<br /><br />Navigate to web page were you can send pings and type each of these lines one line at a time<br /><br />;cp${IFS}*/*/nvram${IFS}/tmp/n<br />;*/n${IFS}set${IFS}boot_wait=on<br />;*/n${IFS}commit<br />;*/n${IFS}show>tmp/ping.log<br /><br />NVRAM method:<br /><br />telnet into box and type the following<br /><br />nvram set boot_wait=on<br />nvram commit<br />reboot<br /><br />3. Upload firmware<br /><br />Give yourself a fixed IP in the 192.168.1.x range e.g. 192.168.1.100<br /><br />Use tftp to upload firmware<br /><br />tftp 192.168.1.1<br />tftp> binary<br />tftp> rexmt 1<br />tftp> trace<br />Packet tracing on.<br />tftp> put openwrt-g-freifunk-1.0.2-en.bin<br /><br />Wait for the power light to stop flashing<br />Power cycle the box<br /><br />4. Check that the web interface is working. Visit the site http://192.168.1.1 on your web browser - you should see the main freifunk web interface appear<br /><br />5. Set up the wireless interface<br /><br />WLAN protocol: Static<br />Ip Address: 192.168.2.5<br />Netmask: 255.255.255.0<br />WLAN Mode: Ad Hoc (Peer to Peer)<br />ESSID: mesh<br />Channel: 6<br />TX Power: 100<br /><br />6. Set up the LAN interface<br /><br />LAN protocol: Static<br />LAN IP: 192.168.4.1<br />LAN Netmask: 255.255.255.0<br />Disable NAT: yes<br />Disable Firewall: yes<br /><br />7. Set up the WAN interface<br /><br />WAN Protocol: DHCP<br />Host name: Lawrence<br /><br />8. Set up OLSR<br /><br />HNA4: 192.168.4.1 255.255.255.0<br /><br />9. Restart the Linksys<br /><br />You should now be given an IP address in the 192.168.3.x range<br />You should be able to connect to another mesh access point and even get a default gateway to an internet point, if one existsking davidhttp://www.blogger.com/profile/17101894497352927717noreply@blogger.com6tag:blogger.com,1999:blog-7164904.post-1119299520135816322005-06-20T22:27:00.000+02:002005-06-20T22:32:00.140+02:00How the ETX metric in OLSR is calculatedThe ETX of a link is the predicted number of data transmissions required to send a packet over that link, including retransmissions. The ETX of a route is the sum of the ETX for each link in the route. For example, the ETX of a three-hop route with perfect links is three; the ETX of a one-hop route with a 50% delivery ratio is two.<br /><br />The ETX of a link is calculated using the forward and reverse delivery ratios of the link. The forward delivery ratio, df , is the measured probability that a data packet successfully arrives at the recipient; the reverse delivery ratio, dr , is the probability that the ACK packet is successfully received. The expected probability that a transmission is successfully received and acknowledged is df x dr .<br /><br />A sender will retransmit a packet that is not successfully acknowledged. Because each attempt to transmit a packet can be considered a Bernoulli trial, the expected number of transmissions is:<br /><br />ETX = 1/ (df x dr)<br /><br /><br />For a full description of how df and dr is actually calculated see MIT's publication <a href="pdos.csail.mit.edu/roofnet/doku.php?id=publications">site</a>king davidhttp://www.blogger.com/profile/17101894497352927717noreply@blogger.com0tag:blogger.com,1999:blog-7164904.post-1119297784516262212005-06-20T21:53:00.000+02:002005-06-20T22:03:04.520+02:00Mesh scalability by modifying the MAC layer in Altheros<a href="http://www.smallworks.com/archives/00000072.htm">This</a> is a great article that discusses the whole issue of loss of performance in a single radio mesh network with many hops. Modifying the MAC layer on our 50 Altheros cards we are getting for the massive mesh could prove a very novel way of dealing with the inherent problems in the WiFi spec when trying to build large mesh networksking davidhttp://www.blogger.com/profile/17101894497352927717noreply@blogger.com1tag:blogger.com,1999:blog-7164904.post-1119293270371667922005-06-20T20:46:00.000+02:002005-06-20T20:47:50.376+02:00Getting Kismet working with IPW2200 driverThanks to ubuntu forums for <a href="http://www.ubuntuforums.org/showthread.php?t=40875&highlight=ipw2200">this</a> link<span class="" style="display: block;" id="formatbar_CreateLink" title="Link" onmouseover="ButtonHoverOn(this);" onmouseout="ButtonHoverOff(this);" onmouseup="" onmousedown="CheckFormatting(event);FormatbarButton('richeditorframe', this, 8);ButtonMouseDown(this);"><img src="img/gl.link.gif" alt="Link" border="0" /></span>king davidhttp://www.blogger.com/profile/17101894497352927717noreply@blogger.com0tag:blogger.com,1999:blog-7164904.post-1118759282241421112005-06-14T16:28:00.000+02:002005-07-14T12:03:10.153+02:00Drawing(almost realtime) pretty network topology pictures with<DIV> <i><u><a href="http://meshcube.org/meshwiki/OlsrTopologyVisualization"><font color="#0000ff">http://meshcube.org/meshwiki/OlsrTopologyVisualization</font></a></u></i> </DIV> <DIV> </DIV> <DIV> Tried it, works well'ish. </DIV> <br>Regards,<br>Yusuf Kaka<br><br>________________________________________________________________________________<br><br>Mobile Platforms Engineer<br><br>CSIR - Meraka Institute (African Advanced Institute for ICT)<br>Web Address: www.csir.co.za or www.meraka.co.za<br>________________________________________________________________________________<br><br><br><br>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7164904.post-1116237730798381702005-05-16T12:02:00.000+02:002005-05-16T12:02:10.956+02:00Howto: Mesh Network on a WRT54G using OLSRdI followed the instructions here: <a href="http://doctormojo.com/wrt54g/">Howto: Mesh Network on a WRT54G using OLSRd</a> and now have a mesh node (AngelNET_mesh) running OLSR.
<br />I used channel SSID AngelNET_mesh, channel 11, 64bit wep, key: 1234567890Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7164904.post-1116236026033021492005-05-16T11:33:00.000+02:002005-05-16T11:33:46.573+02:00Running Kismet-Drone on a Linksys WRT54G (OpenWRT)Install either the kismet or kismet_drone package. Then edit /etc/kismet_drone.conf and change the source from wrt54g,eth1,wrt45g to wrt54g,prism0,wrt54g.
<br />Edit /etc/kismet.conf on your host pc, include the line: source=kismet_drone,10.168.1.1:3501,drone
<br />then run kismet and off u go!Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7164904.post-1112799306456473192005-04-06T16:55:00.000+02:002005-04-06T16:55:06.456+02:00Linksys Disaster Recovery Theres nothing like learning the hard way! As a result of my usual "If it ain't broke, it hasn't been fixed enough" approach to life, I fiddled with the Linksys until it innevitably went into a coma/ vegetative state. How did I manage this you ask? Simple, I started by doing a firmware upgrade using the wrong sveasoft image, which resulted in a moderately upset linksys which refused to talk to me on the web interface. With the help of our trusted Android (Andrew), I managed to do a reset-hold/ ping / tftp recovery and then flashed the poor bugger with OpenWRT, which according to OpenWRT is still not supported by them for the version 2.2 Linksys, which I subsequently found out I was using! So alas, all that remained was a perfectly dead Linksys, not responding to anything. It was time to go in, screwdrivers a blazing. I shorted out pins 15 and 16 and started up the Linksys, this created a crc error which was detected on boot, this then started up an emergency TFTP server which allowed me to ping and finally tftp the original Linksys firmware back onto it!
<br />
<br />More details on the recovery processes can be found here:
<br /><a href="http://openwrt.org/OpenWrtDocs/Troubleshooting">OpenWrtDocs/Troubleshooting - OpenWrt</a>
<br />
<br />Whew! Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-7164904.post-1112712586761243312005-04-05T16:49:00.000+02:002005-04-05T17:06:10.416+02:00War-Driving: Using Kismet and a GPSThis article "<a href="http://www.i-hacked.com/content/view/26/42/">"Configuring and Using Kismet"</a>" has a nice tutorial on how to setup Kismet and your GPS on Linux. Also look at the related links on the site for some info on hacking the Linksys!Unknownnoreply@blogger.com1