Hi Sil,

it sounds like you got a good orientation to the organization. I wish we could have our PSO at the lake.

Sounds like you have a lot on your hands and that is always the time for a hardware failure. I hope you've backed up that sole hard drive :-)

I've used WDS at my house and it works pretty well. It does though halve your throughput (since half the bandwidth is reserved for inter-router communication). You probably won't notice this though. I've never used OpenWRT, but I'm a big fan of DD-WRT. Those linksys routers are pretty easy to come by---though watch out since the later hardware revisions won't run the custom linux firmware.

Thanks for the update!

Hey Sil,

Great post! I almost feel like I'm sitting there at work with you.

I went through quite a bit of work evaluating custom vs. open-source CMS options earlier this year with the StoriesForChange.net project, so let me know if you need any help in that area. We put out an RFP so I got a good range of proposals from folks doing everything from custom CMS to Plone to Drupal. [We went with somebody doing Drupal, btw, because they included a really great technology planning component to the project planning.]

-Danielle

Well, technically I've installed X-WRT, which is OpenWRT plus the webif^2 configuration interface. DD-WRT is similar, running an OpenWRT kernel with a few added packages and a user-friendly web config. (Using OpenWRT naked is NOT for the faint of heart!)

hey sile u can try to go into the router's config. & set one up as the gateway & one as a router that should fix the problem

I've never had much opportunity to fiddle with it, but besides WDS you can also install OLSR through OpenWRT's package manager. It's an open-source mesh routing protocol, and while I'm not sure how much set up it requires, it can scale up to clouds of 5-10 nodes pretty easily (don't have exact specs for running it on WRT's, which are a little less than ideal for mesh node hardware). But it might be overkill for just two or three nodes. Of course the easiest way, unless you really need a reason for roaming through the building is just to partition the network. That's what we do here in our building, where we have "OpenUCIMC0-3" in different parts of the building, and they all route to the same physical subnet. If you can't run ethernet lines then you could also run two routers back to back, with one in wireless client mode and the other in AP mode. Finally, you could just get a big antenna. Super Cantennas (http://www.cantenna.com) have pretty great signal penetration, we use two to provide coverage in a pretty huge old stone building. You could hook one up to your first WRT and just blast it through the whole building (depending on layout and the kind of materials your building is made of). Or just use WDS, which would probably work fine too. Just wanted to suggest some other options.

re: partitioning... are all your "OpenUCIMC0-3"'s on separate channels? or are they all sufficiently far away that they can all coexist on the same channel... we're in a building too big for the Linksys by itself, but too small to put to AP's on the same channel. hmmm. the antenna option might actually be the right one; i'll have to dig farther into that.

I believe they are all on separate channels, though I'd have to go check to be sure. The thing to remember is that channels 1,6,and 11 are the only 802.11b/g channels which are fully orthogonal (if that's the right word). So if you have multiple routers, try and put them on those channels to minimize interference.