so I got my rocket M900 all hosed up,

I need to flash stock ubiquiditi firmware into it

does anyone know how, I have the orignal firmware

Thanks

http://www.extremetech.com/computing/213351-new-fcc-rules-could-ban-dd-wrt-and-router-modification

What are the ramifications for Broadband-Hamnet??

http://www.extremetech.com/computing/213351-new-fcc-rules-could-ban-dd-wrt-and-router-modification

Any ramifications for Broadband-Hamnet??

http://www.extremetech.com/computing/213351-new-fcc-rules-could-ban-dd-wrt-and-router-modification

Any ramifications for Broadband-Hamnet??

Hello fellow meshers,

I have 2 rocket M900's I have sucessfully flashed the mesh firmware to them ( I think ) I have released and renewed my IP address, I have re started my machine and rocket, when I try to log in with my browser I can not get in, I have tried loging in with

http://localnode:8080/

localnode:8080

anyone know what I'm possibly doing wrong ?

thanks

Rick.

I went through the same thing with my WRT-54GL's a few days ago. I wound up having to use the procedure at:

http://www.broadband-hamnet.org/documentation/71-using-safe-mode-to-reset-a-forgotten-password.html

to recover.

I strongly recommend using the specified password in the above document. Once you can reliably reboot then you can change to something you like. I found that if I used 12 character length passwords upon reboot I could not get back in. However using the 3 character password specified in the doc I could get back in after reboot. I have not experimented beyond using 4 characters at this point.

Chuck

Thanks for the lead on the connector. It more closely matches than anything I found. My guess is the Ubiquiti device is a custom connector. I may give them a call. I tried to buy a couple of used devices off of e-Bay but even the ones looking like they were dragged to the jungles of Viet Nam in the late 60's went over the top of my price point.

The idea about using a pigtail is likely as close as I will be able to come at this point. I am thinking of using an SMA on one end and an adaptor at the antenna SMA to Type N. The unit still works but the pad for the connector was ripped right off the board. There is just a spec of very narrow track emerging from the interior shield. <sigh> That will teach me to lash things up.  :-)

Again thanks es 73.

Chuck

I've never seen a bullet in person but based on some photos it looks like you need to find an "edge-mount N connector".  In a quick search the only thing that looks close is at the bottom of this page:

http://www.cosmtec.com/products.asp?Page=3&pname=N+RF+Connector&pfid=4&flev=2&puid=14&N+RF+Connector.html

Unfortunately I don't see detailed drawing or an obvious way to buy one of these online. 

If all else fails, you could solder a short coax pigtail to the board. 

I finally got my WRT54G V1.1 setup and running. Since I am new at this when I went to see what the new IP address was I noticed that it was not 172.x.x.x it was 10.x.x.x. Is this correct?

Next I wanted to go back into the SETUP and change my password and I can't log in with any password. It's like it reset to something new.

How do I open to reset the password???

First let me say thanks to the Mods for adding CT to the forum, KB1UUX for introducing me to this technology and to W9NIZ & KB1MZL for reaching out to me via email after I was heard conversing about MESH on our local 441.700 repeater.  Hopefully, by moving our conversation to the forum, it will help others in CT beside myself.

At this point I have ordered a NanoStation M2 to play with.  When all goes well with that, I would like to try a Bullet M2 at a good site in Bridgeport.

Sunday afternoon I was merrily checking the long list of SSID's on a Ubiquiti device I had attached to a TP-Link antnenna. It was attached to a fiberglass pole on my back deck. As it was a temporary lashup I mounted the fiberglass pole to the deck with bungee cords. Long story short the bungees failed and the result was an antenna with attached Titanium splatting the ground. The splat ripped out the threaded section of the Ubiquiti Type N connector from the printed circuit board.

Does anyone have an old defective device that could be cannibalized for the connector? If so contact me at wcmoore@verizon.net with price info and acceptable forms of payment.

Thanks

Chuck

I have spent a bit of time over the last month working with the current release of BBHN Firmware 3.1.0. Along the way I stumbled into a few non-BBHN gremlins. Hopefully my notes below will help.

• localnode:8080 does not work - following a failed attempt to use localnode:8080 to enter the status screen of the device it was noticed if the browser cache was cleared this would change the result. It appears the browser keeps a copy of the prior page results and if you try to go the the page the browser can and frequently does pull the last cached page from memory rather than pull a fresh copy from the server. To clear your cache press the "Shift and F5" keys at the same time.
  
  
  
• If  localnode:8080 still is intransigent try this. Open a command prompt window. (In later editions of Windows (7, 8.1, 10) you can open a Command Prompt Window by pressing the Windows Key - the key with the Windows logo on it - and the X key at the same time. Select "Command Prompt" from the popup menu. DO NOT SELECT THE "COMMAND PROMPT (ADMIN)" unless you know specifically you need admin access.)
  
  In the Command Prompt (DOS) window type "ipconfig". A listing of network adaptors and their connections will appear. Note the IP Address associated with "Default Gateway". It will look similar to 172.25.0.243 but what is important is to pull the numbers that appear in your window and write them down. Again WRITE THEM DOWN! Then change focus to the browser window again.  Type the IP address you wrote down in the URL Field (where you type the web address) and then :8080. Using the above noted sample ip address you would type 172.25.0.243:8080      Then press enter. Be sure to use the IP Address you wrote down. In all the procedural processes it is easy to mix things up.

This has worked on both Linksys boxes and Ubiquiti devices I have uploaded the firmware.

If the above fail then make sure other network adaptors such as the wireless are "disabled". Windows prioritizes the network adaptor. If the Wireless or other adaptor has higher priority the browser traffic will be directed to it first and the browser times out.

Hello Darryl

Thanks for the info on the Elmers. Mark and Thor are the two closest.

Question 1 - Is there a limit on the Password Length? I usually use 10 to 12 character passwords. When resetting to recover from a password not working I noticed one attempt were I use a sequence of four numbers only and the password worked afterwards. I have not attempted to close the gap between the 12 character and 4 character password at this point. 

Question 2 - Are there characters which are excluded from use in passwords?

Both units (Ubiquiti and Linksys WRT54GL ver 1.1) exhibit this phenomena thus I think whatever I am doing is not allowed by the firmware rather than the devices.  If I use the longer password I cannot get back in after the password change. Using 3 or 4 characters for the password works. For the time being I will use short passwords but would prefer to use those from my select list which are longer. Call me paranoid.

Thanks

Chuck

Hi Chuck, It definitely sounds environmental with your setup.

Are you giving it enough time to boot-up and sync names? (try and give it 2 mins after power on) before using the name.)

Are you removing the CAT5 between initial config and trying to access with your node name? (this renews the IP address)

Beyond that, you may want to consider contacting one of your regional mesh elmers to sit with you and work thru it.

Here's the list from the Elmer page on the site:

Virginia

Central VA (Albemarle County area) Mike KQ9P mike@kq9p.us

General Central VA Mike AE4ML AE4ML@arrl.net

Fairfax County Mark W4MRW webberm@gmail.com

Fairfax/Vienna Thor KK4UYT thor.berglie@gmail.com

Evening Darryl

I have tried two different laptops and
one desk with integral ethernet card
- no wireless. Same symptoms occur with
all three boxes plus the Ubiquiti and
Linksys are exhibiting the same behavior
relative to the password.

I have just finished recovering the
Linksys WRT54GL v1.1. The Ubiquiti did
the same thing relative to setting the
password. I had to take it back to
default. Very strange as a couple of
years back I set up 11 Linksys boxes
with no issues. They worked well and
allowed me to set up remote sensors.

I am obviously doing something not
required or not doing something that
is required but thus far it has eluded
my search efforts.

I upgraded the Linksys box to version
3.1.0 using the TRX file. It came up
as expected, allowed me to log in with
User ID [root] and Password [hsmm].
I changed the Node Name to WD4HXG-27530-01
and set the password. Then clicked on
"Saved Changes".  

The box rebooted. I attempted to use
the http://WD4HXG-27530-01.local.mesh:8080
string in the browser URL field. The
retort was "Timeout"

I then used IPCONFIG to check the status
of the ethernet connection and it had
pulled an IP Address. The gateway value
in the network connection had automagically
been set to 10.10.88.177. I pinged that IP
Address and received a response. I went back
to the browser, entered 10.10.77.177:8080
and Voila. I was taken to the initial screen.

Then clicking on the "Setup" button I was
challenged for the User ID and Password.
For the User ID I entered "root", and then
the password I assigned earlier. The login
screen refreshed but did not allow me to
enter setup. I tried a couple of more times
but was not allowed to enter.  I also tried
the original default of "root" and "hsmm" a
few times.

I finally used the reset routine to induce
the DMZ to a blinking state and ran the steps
in Telnet to reset the password.

I had the same issue with the Ubiquiti. Had
to go back, reset the password on it. I plan
to continue to see if I can identify the
error of my ways but at this time I am at a
loss. :-)

Chuck