still no joy...

my netbook drops the connection with power off and takes too long on power up to make the one second window.

I think this one is a destine for the recycle bin. I appreciate all the help. The good new ... my other 7 nodes are working fine.

73 d mike

Short pins 15 and 16 on the flash chip. Please take a look at this post for more details: http://www.wi-fiplanet.com/tutorials/article.php/10724_3618616_3/Bricked-Or-How-to-Resurrect-a-Dead-Linksys-WRT54G.htm

After you do this, set your computer to a static IP and TFTP the firmware back to the router at the 192.168.1.1 address.

As for JTAG, look here:
http://www.broadband-hamnet.org/hsmm-mesh-forums/view-postlist/forum-1-general/topic-1095-can-this-be-used-for-jtag.html#ccbp4870

No joy... just spent two hours trying to catch that one second window.

i can ping 192.168.1.1

i can setup tftp as defined as a .sh and it executes, but no workie.

this is a Ver 354G

i have no jtag cable but could order one. they are on amazon, just need to know which one and then what to do with it.

I can try the pin short process.

73 de mike

JTAG is something that you do not want to necessarily mess around with unless you know what you are doing. JTAG and USB-to-TTL use completely different protocols! Don't try to go cheap. Instead, get a device that is designed to do what it is supposed to do.

Take a look hear for some ideas:
http://www.diygadget.com/tiao-usb-multi-protocol-adapter-jtag-spi-i2c-serial.html
http://www.diygadget.com/jtag-cables/universal-jtag-adapter-for-routers-modem-fta-and-more.html
http://www.tiaowiki.com/w/Debrick_Wireless_Router_Using_TUMPA_and_zJTAG

Wondering this can be used as a jtag on the wrt54g routers?

http://www.adafruit.com/products/954

I have a few laying around that I use for a gps interface and as for console access to my Raspberry Pi.

What I am worrying about is voltage levels between this and the router

James W8ISS

And I would agree. That would be the more consistent way to deal with routers in some states, but from my experience, there have only been a few routers that have the boot_wait flag enabled by default. From my understanding, when you load the mesh firmware, it enables this flag on first boot after flashing, but I have not had much luck with it.

The 1-second window starts as soon as you apply DC power.

What user action has to happen within the one second window to get "in"?
Read this: http://www.dd-wrt.com/wiki/index.php/Tftp_flash

You can TFTP whatever firmware you want. It's up to the router to read, accept and/or reject what you send.

When you short two pins on the flash chip, it erases the chip (minus the CFE) and puts the router into a TFTP recieve state until readable firmware is sent to the router. If the CFE is corrupt, your only method is to erase the flash chip and JTAG the correct CFE back to the router...at which time (after finishing the CFE write) the router goes into TFTP recieve mode.

[KF5JIM 2014-08-14- 04:24:40]:
> you can TFTP firmware to the router at this address during
> the 1 second window at boot. Make sure you set a static IP
> address on your computer too.

Seems like this could be a more consistent way to deal with routers in some arbitrary firmware state.

Questions:
When does this one second window start? Upon DC, before/after one of the LED's, or ?
What user action has to happen within the one second window to get "in"?

Can the "standard" BBHN or stock BIN file be TFTP'd over via the bootstrap or does it have to be a special one?

Guessing that if something is corrupted to the point the window does not happen, what mode does the CFE go into when you "short" something?  I didn't see initialization detection/failure defined in a cursory review of the Broadcom CFE spec.

Mark K5LXP
Albuquerque, NM

What happens when the MESH GW checkbox is enabled, saved and rebooted is that the OLSR DYN GW module is enabled in the config files

The OLSR DYN GW module controls the injecting of a 0.0.0.0/0 HNA address

http://olsr.org/git/?p=olsrd.git;a=blob;f=lib/dyn_gw/README_DYN_GW is the main readme for the DYN_GW module.

The main item is that it performs a ping to the BBHN website (single ping) every 60 seconds with a fallback to Google as a safety net (the 4exact servers are listed in the source code.)

If any of the the pings are successful for a set amount of time than a HNA of 0.0.0.0/0 is published by the module (same feature that tells nodes about your local 'direct' subnet')

Once a HNA of 0.0.0.0/0 is published other nodes will see the route and add it to the routing tables on each field node in routing table 31 so they than can then get to the internet by going to the publishing node.

If the ping fails a set number of times the route is removed from publication and the nodes remove the 0.0.0.0/0 route from the table via that node thus changing the GW routing

A route of 0.0.0.0/0 means 'SEND EVERYTHING' to me. If the node is told to send all data but does not forward it onto the internet as a whole it WILL confuse the users if they are expecting to get out to the web and can't (depending how close they are to that filtering node vs the open node)

In addition if someone else turns on mesh GW and is closer they will not be able to get to your network on your WAN port so keep that in mind with your design and be sure to set the policies for your network.

When the router firsts boots up, the CFE tells it to have a static IP of 192.168.1.1 and a netmask of 255.255.255.0 (regardless of the firmware). If the boot_wait flag is enabled (located in the CFE), you can TFTP firmware to the router at this address during the 1 second window at boot. Make sure you set a static IP address on your computer too.

If the previous method does not work, let me know your make and model of your router, I will tell you the pins we need to short and we'll have to go through it that way.

If you have a JTAG cable, let me know too.

If you have flashed the node but not set it up, then http:// 172.27.0.1:8080 should get you in to the node do the setup. 

You might want to refer to:
http://www.broadband-hamnet.org/images/stories/hsmmmesh-step-by-step.pdf

and

http://www.broadband-hamnet.org/documentation/68-firmware-installation-instructions.html

Clint, AE5CA

Bill 

Your Mars Lander Project sounds like a great use for BBHN!  Putting a camera on one node and seeing on a computer connected to a second node should be pretty straight forward.  It sounds like you can connect to your nodes and hopefully they are seeing each other on a mesh status screen.

If your nodes were flashed a long time ago, I would guess you have 0.4.3 or earlier on them.  In the 0.4.x versions the default was for NAT and you would need to set up port forwarding or else go to a DMZ mode to get to the camera.  I would suggest you update to the current version.  It uses 5-host dmz mode as its default which should work fine for what you are doing. 

On the node for the "Lander", with the camera plugged into a LAN port, go into the setup and in the Port Forwarding, DHCP and Services screen and set up the camera with a DHCP Port Reservation and then as a Service.  Once you do a save changes and reboot, you should be able to see a link for the camera on the Mesh Status Screen of the "Mission Control" node.  Click the link and you should be seeing the camera.

If you need more help just ask.

Clint, AE5CA

thanks for the help. but  (seems to always be a but)...

i don't know the IP address of the node. does it default to something at power on?

73 de mike

What exactly happens "behind the scenes" when the "Gateway" box is checked, this is to say, how does the routing change across the mesh to route other remote mesh notes to the Internet connection on the router that has "Gateway" checked? I've looked at the route tables in all of my mesh nodes and I see no changes in the routing that would tell those remote mesh nodes how to route a call to www.google.com, for instance, across the mesh to the one node that has an Internet connection on its WAN and has the Gateway checked? What exactly is the man behind the curtain doing on the Internet-connected mesh router to propagate it's Internet connection routing to the rest of the mesh? I'm trying to fully understand how the routing changes when that box is checked as I am trying to build a non-Internet Internet...I want to place a "fake" Internet on the WAN port of the one router with Gateway checked to do some testing. So far it isn't working for me so I am clearly missing something in how the routing changes across the mesh when that magic "Gateway" box is checked. Thanks. 73, Bill, N4SV

Want to learn about how mesh networks can support our emergency communications work? Need help getting started with HSMM-Mesh (http://www.broadband-hamnet.org/)?  Want to find out if that old WRT54G router can be reborn as a High Speed MultiMedia (hsmm-mesh) network #emcomm node?  Do you want to try out that Ubiquiti (http://www.ubnt.com) router? Only have one node and no one to mesh with? :(

Join a gang of "Elmers" for a mesh training event! We'll be learning about how mesh systems can support our emcomm activities, and helping people get their routers working with Broadband-Hamnet firmware!
Where: Fire Services Building, 6820 Webster Street, Landover Hills, MD 20785
When: 04 October 2014, 0900-1300L
What to bring:
-Your own laptop (Mac, Windows, or Linux) and power cord
-1 or more Linksys/Cisco WRT54G version 4 or less (please see the shopping guide on www.hsmm-mesh.org) routers with wall-wort(s), or bring a compatible Ubiquiti router.
-1 cat-5 (or cat-6) patch cable
-Optional: power-squid or power strip to make sharing power easier, Windows machines should have a ssh/sftp client like PuTTY installed, bring extra routers to share, trade.

It has been a long time since I tried to get my MESH network going. I got discouraged a while back when there was no other local stuff but me. However now I have thought of a use for it.  I am a STEM (technology) teacher and am doing a Mars lander simulation with remote control robots.  I wanted to put a remote wireless security camera on my MESH nodes so that the students can see the robot, plan their next move, execute, then see what happens.

In saying all that... I pulled my Mesh routers out and tried to hook them up.  Now it has been a while and I cannot remember much.... But I did go to the setup pages and used the addresses in the browser to connect via wireless and via LAN.  No matter the address I cannot get anything to connect.  I am thinking of reflashing a newer firmware, but cannot get anything to recognize on LAN.

Can I get some pointers?  They are 54GL routers and were flashed years ago.  I just cannot connect and I want to make sure I can before I buy a camera.

Bill R.

N5VEI

It would be best to open a new thread instead of reviving one that has been closed for a year, especially since the thread is a different topic.

It helps with avoiding sending notices to users whom do not need to see them and allows for better viewing in the forum.

I forgot the most obvious answer.  Use a second working node to connect to the first one through the mesh. The status screen should show the ip of the node or you can go into the setup screen and set the ip there.

Clint, AE5CA