Barrie,

I actually printed the "shopping list" yesterday, (Sunday), and I didn't see it on that list either, KF5JIM's reply wasn't the best of news, but fortunately I am out less than $5.00 for the hardware, I bought it at a thrift store AND received a Veteran's discount! :) With the "shopping list" I guess to paraphrase the old song I won't get fooled again! At least I now have some spare parts for the junk box, (the two antennae and a 12V 1A "wall wart").

So on one of my rigs ( mobile ) i have a hack like the one at 

http://hsmm-mesh.org/applications-for-the-mesh/145-gps-on-a-mesh-node.html 

from looking over the olsrd there is support for "Position update plugin". the question is how would be the best way to add this to the firmware.

SIDE NOTE: I have a sd-card added to node so i have 2gb of free flash space to work with.

Even changing your workgroup to local.mesh isn't going to fix the issue. Your PC is not going to connect to the DNS of the mesh to resolve the names. I'm not even sure that fixing the DNS to resolve the 10.x.x.x IPs will work, since your windows machine is not going to route 10.x.x.x to the mesh node.

You can try entering your nodes in your 'hosts' file. Your hosts file is at 'C:\Windows\System32\drivers\etc'. Entries need to look like:

10.5.5.222                     node1name
10.23.94.191                   node2name

You will need one line for each node.

FCC ID in BBHN is performed by \wrt54g\trunk\files\usr\local\bin\fccid

...
#!/bin/sh

[ -f /etc/config/run-fccid ] || exit

# stagger the beacons between nodes
N=`ifconfig wl0 | grep "inet addr" | cut -f4 -d. | cut -c1-3`
sleep $N

netmsg 10.255.255.255 "ID: `hostname`"
...

If you add the following to your dnsmasq config, you will get proper DNS resolution of the machines, as well as browseable links from the OLSR-httpinfo plugin, port 1978 on your OpenWRT node, assuming you have httpinfo configured as well.

/etc/dnsmasq.conf
...
# include olsr nameservice
addn-hosts=/var/run/hosts_olsr
...

The services are also configured in the olsrd_nameservice plugin section of olsrd.conf. I've gotten service entries to show from my OpenWRT nodes.

/var/olsrd.conf
...
LoadPlugin "olsrd_nameservice.so.0.3"
{
    PlParam "sighup-pid-file" "/var/run/dnsmasq.pid"
    PlParam "interval" "30"
    PlParam "timeout" "300"
    PlParam "name-change-script" "touch /tmp/namechange"
    PlParam "name" "AD7PE-101"
    ## Example Service
    PlParam "service" "http://AD7PE-101:9000/|tcp|Test1"
}
...

Keep in mind that adding the service entry won't fix the firewall settings to allow access, you will need to do that manually. The node history page and service links in the HSMM UI appear to be built by perl scripts scattered around the filesystem. I've not had time to look in to them, but the SVN tree at \wrt54g\trunk\files is where you will find the answers.

I've been playing with this on a La Fonera. It works running Backfire 10.3, but the networking is a bit odd because La Fonera only has one ethernet port, so DMZ/WAN/LAN don't really exist except as vlans.

I've used dd-wrt micro with OLSR on a WAP54 to talk to V1 nodes. There isn't room on the WAP for microperl, and only one network jack, so I didn't even attempt the UI, routing, or plugins. The biggest loss will be the ease of configuring and the UI. You may also get IP address collisions if you happen on devices with the same last-3 mac address. I expect you will be manually setting IPs anyway, so that may not be as much an issue. You can look at the \wrt54g\trunk\files path in the SVN repo for the changes from stock OpenWRT. That should get you started on configuring. AD7PE

These three links will help you out:
http://hsmm-mesh.org/documentation/68-firmware-installation-instructions.html,
http://voidmain.is-a-geek.net/redhat/wrt54g_revival.html, and
http://www.dd-wrt.com/wiki/index.php/Recover_from_a_Bad_Flash#WRT54G.2FGL.2FGS
They all have good instructions for fixing your problem.

Before you try anything, try the failsafe method first and make sure the boot_wait flag is turned on (http://www.macfreek.nl/memory/OpenWRT_on_WRT54GL#Install_from_LinkSys_to_Kamikaze_with_Linux_2.4_kernel)

You will need to download the stock Linksys firmware before going back to BBHN. I've bricked my routers many times, and sometimes the fastest way for me to recover was by jtag or TFTPing after shorting pins 15 & 16 on my WRT54G v2.

You will want to try TFTPing first (you might have to be very patient and try multiple times).  If you don't have a jtag device, but you do have good eyes and a steady hand, short pins 15 & 16 (WRT54G only, WRT54GL is 16 & 17) and then TFTP the firmware.  Only do the last one after doing a lot of reading so you know what you are doing.

Well I have 2 routers I managed to crash and I cant get back in to reload them! Any ideas on how to reload the firmware I had them working at one point then I hit the firmware upgrade button in the administration area and that was that!

It looks like it will be more work than what it's worth. However, it does look like a pretty nice piece of hardware!

https://forum.openwrt.org/viewtopic.php?id=4378

I think it would still be worth trying.  You'd have to use a hex editor to change the first 4 bytes of one of the *.bin firmware files to be what the WCG200 looks for, but since linksys' website doesn't have any firmware posted, I can't even tell you unless I hooked up a jtag cable to the device to download the firmware from the WCG200.

Is the Linksys WCG200 router, (wireless-G "cable gateway), compatible with HSMM-MESH, can it be modified to be compatible, or did I just "blow" about $5.00 buying it?

I have been debating connecting the mesh to the internet full time with some of the people in my area. I've found 3 major schools of though.

1: it should never ever be connected to the internet (I completely disagree with this)

2: it can be connected but only temporarily in an emergency or for testing purposes (not quite what I'm looking for as an answer)

3: it should be connected at all times

I'm leaning toward the third option there but to get others to change their mind I've had to prove that we can maintain part 97 compliance. To that end I started recreating a simple web content filter (I use large, expensive filter appliances like M86, Bluecoat, and Lightspeed all the time in schools because it's required by CIPA, state and federal aid, and E-rate) on a ubuntu box using iptables, squid, and dansguardian. I have not built the captive portal yet but I plan to using something like nocatauth and some sort of LDAP service. 

I believe this can all be built in to the firmware of the mesh gateway (this is done on DD-WRT regularly) so we don't need a computer between the mesh gateway and the ISP. It would be cool if filter configs and the LDAP DB could replicate automatically between multiple mesh gateways. It would also be good to have the filter's category files update regularly.

So I'm thinking if you enable the gateway mode it configures the use of the content filter and captive portal, and maybe new tabs on the management interface so you can add users by callsign to LDAP, maybe manually link other gateways for synchronization... or find a way to identify other gateways on the mesh and auto sync. 

There should be some basic services that do not require a login so served agencies may use it directly. for instance aprs.fi should be totally open, and perhaps things like skype, facetime, etc. but if you want to do much more on the web you need to login and then certain categories of sites are blocked such as shopping and porn.

I've attached a screenshot of a test of the filter which allows me to google but not playboy.

I (and others I've discussed this with) would very much like to see this built into the next update of the firmware if possible... and I'd love any feedback on the idea.

Attachments
 Filter test.jpg [148 KB] :: Filter test screenshot

Is there anyone in the SE Michigan, NW Ohio, or Windsor region that would like to do some testing across Lake Erie this winter?

What I would like to do is see if we could make connections from as far East as Cleveland and back into the Detroit area across Lake Erie.

Looking to see if this would be a viable means as an alternative for arranging contacts during the 10GHz contest each August and September. Currently during the 10GHz contest, we are allowed to use 2m and cellphones to help in arranging contacts as long as the full exchange of info is via 10GHz and above. I would prefer to use this means as a liaison compared to using the cellphone.

This is just an idea that I would like to give a shot at to see if its viable or not. If I can make a contact from Monroe, MI (EN81hv) to Conneuat ,OH (EN91rx) on 10GHz using 250mw on a bad day, what could be done on 2.4GHz?

James W8ISS