There are (were?) two problems holding back the Bullet devices from working on the mesh.

The first rumor was there was an indian-ness problem in the radio and the code that made the secure module in the mesh fail.   As I remember, technically, the Bullet was correct, and the WRT54G's, X86 and ARM are all doing it "wrong".  I've personally built and run olsrd on x86, Pandaboards, and Gumstix w/o any problems and connected into the hsmm-mesh with security enabled, so I find it hard to believe that three platforms are wrong, but anyway.   It should be reasonable to make our own 'hacked' module that does whatever translation and basically uses a 'backwards' security module to work with the existing hsmm-mesh.    Anyway, I never got to see becuase you run into the bigger problem first.  

The 2nd issue was there was no ad-hoc support in the wifi stack used in revisions of software in the bullet and that kept you from getting a 'layer 2' connection to even start playing.    It's easy enough to build the latest openWRT which should have updated wifi stack to support adhoc, but mangling that to run on the bullet had it's own annoying buglist.  It builds, but doesn't have any of the goodies to setup root correctly and be workable.

On a whim, I looked at the latest 5.5 firmware release notes and it looks like they have fixed the ad-hoc problem.  Basically, it looks like they just picked up the latest linux projects and merged that into the ubnt firmware.  

If all that's broken is the security part, assuming that's even a real problem I might have enough free time to fix the other things that need attention.

 Has anybody looked into this in the last month or so?  I don't want to duplicate work that's being done.

Thanks,

KE5TNO

I've run WRT54G and GS directly from the 13.8v supply in my motor home (which often is about 14.5v), and I've run them on 9v wall-warts.  Except for WRT54Gv1, they have internal 5v regulators.  The regulator runs a little hotter on higher voltages because it's dropping the input a little more, but I've never had one fail.  Anyway, I wouldn't worry about the losses from a 12v supply working over a couple hundred feet of CAT5e.

The power LED never lights at all.  The Easy Setup LED lights up after a while and glows steady white.  The other three LEDs (wireless, internet, and ethernet) appear to operate normally, each in accord with what's happening on those three interfaces.  There is no DMZ LED.

The ethernet port and the internet port (RJ-45s) apparently are swapped in function with HSMM-MESH running.

Except for those cosmetic items, HSMM-MESH appears to run just fine on the WTR54GS -- which is what I originally expected, since the circuitry is basically the same as a WRT54GS.  Note that only Version 1 of the WTR54GS (serial number starting SJH0) has enough EPROM and RAM to run HSMM-MESH:  4M and 16M respectively.  Later versions (SJH1 and later) have only half as much.

Perhaps these things could be corrected in a version special-made for the WTR54GS, or perhaps a future common release could detect what it's running on and behave accordingly.

If any developer would like to work on such a version, I would happily supply a WTR54GS to experiment with.  Just tell me where to send it.

 -- Carl

That's Awesome!!  Glad you dug it out and tried again!  We would have never known otherwise!

How about the lights?  still not working?

I spoke too soon. It works. A couple hours after I threw it away, it was time to carry out the trash. I decided to play a little more and dug it out. The WTR54GS has only two CAT5 ports. One is labeled "internet" and is normally the WAN port. The other is labeled "ethernet" and is normally the LAN port. I had tried to get DHCP services etc. from the "ethernet" port. I decided to try the other port, and Lo! -- I got DHCP. Then I went after the Web interface -- and got it! So I was able to configure the node. Except that on the WTR54GS the WAN and LAN ports apppear to be reversed, HSMM-MESH works just fine. The binary that I loaded, by the way, is the one listed for the WRT54GS. It works. It all seems perfectly normal and is just like being on a WRT54G, except for having only one local port instead of four. My two mesh nodes (one running on a WRT54G and one running on this WTR54GS Travel Router) see each other and seem to talk to each other. So my original conjecture, that it would work on a WTR54GS, seems correct. And I almost threw it away because it didn't occur to me to try sticking the cable in the other hole. It's a drag being old and pigheaded. -- Carl

I see comments that suggest a robust mesh network reaches critical mass somewhere around 40 or so nodes.  In those areas where that density has been achieved, I'd love to know what got you there?

My reading and shopping around indicates that a good mesh node installation is going to run between $200 and $300... not much more than a good HT.  However most of my ham buddies are serious skinflints as far as investing in new equipment, unless they get jazzed about a project.  Then things happen quickly.

So in those regions where you have been successful, What sells the MESH?  How have you gone about recruiting new node operator/owners?

What bombed; what worked?

Planning a campaign and looking for ideas.

Thanks!

Be careful on eBay.  Of three "WRT54GL" routers I recently picked up, for an average price of $25, ONE was the real deal.  One was a WRT54G version 3.0, compatible so I kept it.  The third was a WRT54G version 6.0, unusable for this application (not enough RAM) Fortunately that seller is accepting a return, so it's on its way back.

Since then I've begun asking for and getting serial numbers on the listings I am interested in.  Most sellers are glad to oblige.

Well, now I know.  What I found out is that it bricks it so thoroughly that the power light doesn't come on at all and it won't ping at any address, so TFTP recovery is not possible.  Probably a JTAG recovery would work, but it's too much work.  Ah, well, I took that risk with eyes open.  I still have three of these, and they've been on a shelf for a long time because I don't need them; and several WRT54G and GS routers (not to mention some Netgear N routers), all running DD-WRT and mostly on a shelf too.  So I threw it away.

This would make me feel dumb, except that nothing makes me feel dumb.

Edited my original post.

Saw one go on ebay for $35 bucks.  So that's not so bad.  

Interested to hear what you find out.

TeamSpeak 3 - VoIP Conferencing

Team Speak 3 (TS3) is a powerful Server and Client software package for voice conferencing. Once set up any user on the MESH can access the TS3 Server using the client software. Within the server you can set up various channels, and permissions for users. TS3 also allows the use of a Shared File Storage Folder for every channel.

Our group is going to deploy TS3 over the MESH to accomplish several tasks. First is the obvious use of Voice and Text chat over the network. Second is a file server. By adding a couple of other plugins we also will have a live whiteboard for drawing out various information.We also could connect a scanner or radio and stream audio to the server. 

Team Speak

Anyways.... Now onto the good stuff: How to get it set up!

Team Speak 3 Server Set Up for MESH:

First you will need to download the server software from Team Speak. The server can run under Windows, Linux, and Mac. There are many tutorials for getting the server set up depending on what type of O/S you are using.

After getting the initial setup you will want to get a Non-Profit License from Team Speak this allows you to run the sever over a LAN network, and also increases the allowed virtual servers, channels, and users. TeamSpeak will email you a .dat file that needs to be placed into the server folder. 

Now to set up the MESH Ports:

• Both, UDP, 9987, 172.27.0.5, 9987
• Both, TCP, 30033, 172.27.0.5, 30033
• Both, TCP, 10011, 172.27.0.5, 10011

And now advertise the TS3 Server:

• link= ts3server 9987

At this point you should be ready to start up the server. The Server itself has no interface, it will just run in the background, or in the taskbar. you will admin the server via the client (other options for more advanced users)

The first time youstart the server is going to open a window with a Token in it. COPY THIS TOKEN AND SAVE IT. This Token will be in the logs but it is much easier to save it somewhere else where you can locate it easily.

Team Speak Client Software:

Each user will need to install client software. The software is available for most all major operating services, and also iPhone, iPad, and Android giving you WiFi access if you have a AP!

On the server pc once you have the client installed and running you will connect to your server. You should be able to do this from the MESH status page with the ts3 advertised link. If not you can connect manually by entering the NODE name that is connected to the server computer.

The first time you connect to the server a window will open and guess what goes into it? That's right the TOKEN that the server gave us before. You now are the Server Owner and can make any changes to the server.

When other users connect they will not have to use a token at all. You can give permissions to users though and they will need a token to verify those. Once up and running you the system is ready to go. There are THOUSANDS of different ways to set up your system. I will not even begin to get into the details here. You can find a bunch of information on the Team Speak Forums about permissions, server settings, addons, and more.

Feel free to ask questions, give thoughts, or share you groups TS3 set up. 

Yep that is how it works.  BTW the adaptors I use are about $2 each for a set shipped.  Check eBay.  Not a waste of money at all.  They work great!

Has anyone tried HSMM-MESH on one of these?  Note that the WTR54GS is not the same as a WRT54GS despite its confusing name.

Anyway, I own several 4Meg versions of these, most running DD-WRT but one NIB with Linksys firmware.  As soon as I find one of them -- I think they're in a box in a friend's garage -- unless someone warns me I'm going to try flashing one of them from DD-WRT to HSMM-MESH.  Getting DD-WRT flashed on one of these initially is a little bit intricate, but once DD-WRT is on it you can flash anything that'll run.  But I wouldn't try flashing a WTR54GS directly to HSMM-MESH from factory firmware.

I'll let y'all know in a couple days whether I brick it or not.  If so, what the heck, I have several -- and can likely unbrick with TFTP anyway.

Wish me luck.

According to this document http://hsmm-mesh.org/images/stories/hsmmmesh-step-by-step.pdf the default userid/password is root and hsmm.  I found that this was correct.  Try root and hsmm.