No, never did get a reply for my question so I have not done anything else with that 300N.

I did however find 6 brand new wrt54g-rg but am a bit worried that they might not work. They

have 8mb and 4mb of flash so they should work but not sure as they have special software in them

right now from Rogers. It is just slightly modified linksys but is optimized for voice.

I wonder if it is wise to flash it to ddwrt first and then go to the hsmm-mesh as the router is supported

by ddwrt.

Let the router decide. 

Separate transmit and receive is needed if you have a one way amplifier and/or preamp.  Other than that, you have to make a two way link to any other node you're talking to, so there's no real reason to separate transmit and receive.

Amplifiers aren't a good idea anyway in most cases with HSMM.

It's fairly common to put a beam on one port and the stock antenna omni on the other port.  That way, you can beam to another node, and then mesh with other local nodes wirelessly. 

If you want to put two beams at one location, it may very well be easiest to use two routers and let them mesh wirelessly.  The fact that coax has such a high loss rate per foot at 2.4 GHz has a big effect on what's practical in terms of situating antennas vs. the routers.

Internet (WAN) link light is are on, connected to a router with a DHCP server enabled. Status page does not show IP address for WAN.

I have verified that the cable is good and that the DHCP server is working.

The upstream router is not showing an connection on the related port nor an IP address assigned.

If I set up a static IP, the upstream router can see the IP address and MAC address, but I can't ping the router from the MESH router.

Check the link lights. If those are lit;

   Check the main status page -- Does it show an IP for the WAN?

     If not;

        Do you have a DHCP server of sorts on the network the node WAN is attached to?

        (I personally have static public IP's so I would have to set mine manually)

     If IP showing, then follow upstream to see if the next device in line has connectivity.

Jim

Did you ever get a response on this? I have a WRT300N v1.1 that I would like to use as a mesh node, but I'm leery of trying it without knowing if the firmware will work.

I have spent some time looking around and found that you can purchase a 24dbi 2.4Ghz grid antenna from Walmart online of all places (there's a first) They will deliver to the nearest store for free and the total cost here in AZ with our tax is $50.81. Not bad for new equipment with a warranty. I have since ordered the antenna and should be here in a few days. I thought letting everyone else know about this source may be helpful. The price is $46.57 before tax.

N7SKV Brent

 TP-Link TL-ANT2424B 2.4GHz 24DBi Grid Parabolic Antenna 

I have just loaded my first HSMM-MESH node firmware v 0.43 into a WRT54GS v.2 router. Everything appears to be fine except even though I have the WAN port connected to my home network, it doesn't show that it has obtained an IP address nor has an internet connection.

All three, WiFi address, LAN address, and WAN address, show Link.

I have the WAN set up for DHCP, and I have Mesh Gateway checked.

Any help on where to start troubleshooting will be greatly appreciated.

Richard, nz7k

You're probably not going to find anyone willing and able to port the software to WNR2000v3 and make it compatible with the existing HSMM-MESH software just for you.  It certainly won't be me.  I'm not on the development team, and my brain turns to mush when I try to do a software build that complicated.

There are some other mesh firmware projects out there.  You might find one of them that uses OLSR and will work on your router.  Or get the OLSR code and roll your own.  It's probably not going to be able to talk to the existing HSMM-MESH software, and it probably won't be as pretty or self configuring. 

For now, the real thing WRT54GL routers are readily available new at Amazon for $50 or refurbed for $40 on ebay.

You should only download HSMM-MESH to the specific router model and version  the particular binary file is intended for.  For instance, WRT54Gv2 is good, but WRT54Gv7 will not run HSMM.  Loading the wrong file will probably brick your router.

There are some significant roadblocks to moving to other routers without breaking things in the current setup.  There are plans to get to a wider range of routers sometime in the future, but it will probably be a major software change that won't work with routers on the current version of the software. 

For now, brand new WRT54GL's are readily available and work well. 

The WRN200v3 doesn't seem to have an external antenna connector, which limits it's usefulness for  many potential HSMM-MESH uses.  It could still be useful to some degree if there were a HSMM version of software for it.

I have been playing with a NetGear WNR2000v3 the past couple days, finally had to build a serial cable so I could regain control of it.

I tried a flash to dd-wrt, and it took.  Then I got greedy and decided to throw the 'hsmm-mesh' build at it.  brick

Looking at the hyperterminal information after getting control of it again, the original software was from OpenWRT.

With my limited and rusty knowledge of Linux, would it be possible that this particular router can use our HSMM-MESH software?  It seems to have more memory than the WRT54GL unit.

... and would open up the possibility to more hardware being able to be used!

Thanks!