I've updated the shopping guide. 

Sorry for the inconvenience, but we don't have a collection of these routers to test the software on, and we've received little feedback on what does or doesn't work. 

http://www.broadband-hamnet.org/images/hsmm_docs/WRT54Shop.pdf

"Please report success/failure/problems to http://broadband-hamnet.org/hsmm-mesh-forums/viewpostlist/
forum-2-hardware/topic-674-successfailure-for-different-router-models.html

There is software on the BBHN web site for the following routers.

WRT54G3G – Confirmed to work

WR850G – confirmed by one user with some problems
WA840G v1 only - unconfirmed
WE800G v1 only - unconfirmed
WRT300N_v1 (ONLY version 1. The v1.1 and higher versions don't work) -unconfirmed

WRT150N – several people have reported that they have failed to load software successfully on this model"

I need to update that list.  We've decided that the USR5461 doesn't work any more.  It doesn't have enough memory. 

I'm beginning to think the WRT150N and some of the other routers may not work, either.  I haven't been able to find anyone who had succeeded with flashing them lately.   Maybe it worked before, but doesn't work with more recent versions of the software.

Hey, that's great, Anthony. I'll be there early, probably around 6, setting up. It'll be great to hear how Mississuaga's project is coming along. Let me know if you need a map or anything.

The 172.27.0.2 address is strictly for nodes setup in AP mode. You would be interested in 172.27.0.1:8080 or localnode:808.

Just because there is software available on the website for a particular device does not mean that device is fully supported. I've modified firmware to get the .bin file to install on unsupported devices. To my surprise, I was able to configure the device and upon reboot, it failed during bootup. My only solution: To TFTP the original stock firmware to the device and use it as a normal WiFi router until I learn more information about the device and what it would take to get it supported.

From the supported hardware pdf:

Members of the Broadband Hamnet™ (BBHN) community have installed the firmware on hundreds or thousands of WRT54G series routers.

We have produced versions of the firmware for a number of other routers, but don't have much experience with using these routers. You may find some things work differently from the way WRT54G series routers work.

Please report success/failure/problems to http://broadband-hamnet.org/hsmm-mesh-forums/viewpostlist/forum-2-hardware/topic-674-successfailure-for-different-router-models.html

There is software on the BBHN web site for the following routers.

• USR5461
• WA840G
• WE800G
• WR850G
• WRT150N
• WRT300N_v1 (ONLY version 1. v1.1 and higher don't work)
• WRT54G3G

Another follow up: I must have changed a parameter somewhere. Maybe I made a boo-boo with the IP Address? Anyhow, just ordered WRT-54g from eBay. Will burn it MESH when I get it and hopefully, it can tell me if the WRT-150 is working and what IP address it is utilizing. Then I can get into it and change any errors.

Please let me know your thoughts.

bob NY2M

You might try changing the subnet masks on both to: 255.0.0.0 The first octet in each is 10, which is non-routable and correct. The other three octets are derived from the last three of the MAC address. It looks like your tighter subnet mask on the Linksys may be filtering out the Pi. Good luck, and post it this changes anything. Dave, W6DPS

I am new to MESH. I am using a Linksys WRT-150N router. I found the firmware installed it fine. I logged in to localnode:8080 and was able to set NY2M-100 as node name and added a password. The reboot was as expected, but it never recovered from the reboot.

I tried a page refresh - no luck.

I tried the cmd line entries that were the next step and got a "media disconnected" error.

I have not been able to recover from this.

I rebooted my PC under Ubuntu instead of Win 7. I am able to get a network connect (100 mbs)  as follows:

Device: 70:5A:B6:66:6D:E2

IP: 169.254.10.23

subnet: 255.255.0.0

Default Route: 0.0.0.0 (which I suspect may be the problem?)

I keep trying to connect to localnode:8080 and get "can't find server." Same for attempt to direct connect to 169.254.10.23.

I do not see any broadcasts on the wireless router side. I scanned with my tablet.

Any guesses on what I need to do?

Thanks

Bob - NY2M

Discussions have actually already surfaced a couple months back on this router.

It will require a new build.

The new Linksys (ARM based) appears to be a much closer cousin to the Ubiquiti gear (without the ruggedness) than it is to the older WRT54g's which are based on the MIPS/Broadcom architecture.