Broadband-Hamnet™ Forum :: Hardware
Board Index Latest Posts Welcome Guest   [Register]  [Login]
 Subject :TFTP HELP.. 2015-01-08- 02:54:32 
kc8rgo
Member
Joined: 2014-01-27- 20:44:36
Posts: 33
Location: 

I have a NSM2 that I successfully reflashed and was using.

For whatever reason (probably me) SETUP would not take my LOGIN.

I downloaded the instructions from this site's downloads, and put the NSM2 into recovery mode (proper lights flashing.   I believe I set my computer to use the IP address of 192.168.1.22 with the submask.

I have WIN 7 and turned on the TFTP client. 

I copied my Ubiquiti factory software to my D drive.  i.e. D:UBNT.BIN 

I brought up the command line and typed:

TFTP -i 192.168.1.22 PUT D:UBNT.BIN 192.168.1.20

It just comes back "connect request failed".

Any help appreciated - thanks in advance


Vance, KC8RGO
IP Logged
Last Edited On: 2015-01-08- 04:05:41 By kc8rgo for the Reason
 Subject :Re:TFTP HELP.. 2015-01-08- 04:21:18 
KG6JEI
Member
Joined: 2013-12-02- 19:52:05
Posts: 516
Location: 

if you flashed version 3.0.0  you could just use the password reset function (after node boots press and hold reset button for 5 seconds and the password resets to our default password)

The connection refused error is because your telling it to upload to host 192.168.1.22  while the node is at 192.168.1.20

>tftp

Transfers files to and from a remote computer running the TFTP service.

TFTP [-i] host [GET | PUT] source [destination]

-i              Specifies binary image transfer mode (also called
octet). In binary image mode the file is moved
literally, byte by byte. Use this mode when
transferring binary files.
host            Specifies the local or remote host.
GET             Transfers the file destination on the remote host to
the file source on the local host.
PUT             Transfers the file source on the local host to
the file destination on the remote host.
source          Specifies the file to transfer.
destination     Specifies where to transfer the file.


Note that you have 192.168.1.22 in the host field,   the 'destination' paramater where you put 192.168.1.20 is a filename not an IP address field.


http://bloodhound.bbhndev.org/products/BBHN/wiki/HowTo/FlashUbiquiti may also be useful to you.
IP Logged
Note: Most posts submitted from iPhone
 Subject :Re:TFTP HELP.. 2015-01-08- 05:21:20 
kc8rgo
Member
Joined: 2014-01-27- 20:44:36
Posts: 33
Location: 
I have tried the reboot and 5 seconds press on the POE reset - no success probably because I am far enough downstream that . . . . I would like to get back to a NSM2 fresh out of the box config. (Just to know I can do it.) I can follow the instructions to get to "RECOVERY MODE". My RJ45 is 192.168.1.22 with submask. I have no idea what the NSM2 has for an address at this point, but since I did the RESET to get to RECOVERY MODE, the NSM2 should be at 192.168.1.20. My copy of the original Ubiquiti software is at D:UBNT.BIN Can you give me the TFTP line that would move the binary to the NSM2? I have read and re-read and am "pushing a rope" at this point. Thanks - Vance, KC8RGO
IP Logged
 Subject :Re:TFTP HELP.. 2015-01-08- 06:45:50 
kc8rgo
Member
Joined: 2014-01-27- 20:44:36
Posts: 33
Location: 
I used: tftp -i 192.168.1.20 PUT d:ubnt.bin which transferred the Ubiquiti file, so starting to have success. Then transferred the MESH software. Do not have it running again, but some forward progress. localnode:8080 redirects, but Webpage not available.
IP Logged
 Subject :Re:TFTP HELP.. 2015-01-08- 16:32:43 
KG6JEI
Member
Joined: 2013-12-02- 19:52:05
Posts: 516
Location: 

Try clearing your browser cache (or at least closing your browser)  might clear up.

As Andre just pointed out in another post (and reminded me of how often the basics need to be done) you can be surprised what browser can do to muck things up, especially when you been flashing/reflashing/reflashing software.
IP Logged
Note: Most posts submitted from iPhone
 Subject :Re:Re:TFTP HELP.. 2015-01-11- 05:08:50 
kc8rgo
Member
Joined: 2014-01-27- 20:44:36
Posts: 33
Location: 
Last night was an "ah ha" moment and I got my node to recognize the user id and password under "SETUP" after being re-flashed 3.0.0. My problem was another error between the chair and the keyboard. :) For some reason I thought that when the node was re-flashed and I went into "setup" that the user-id was the new node name. When I finally tried the uid of root and my new password everything worked. I used to ask candidates at job interviews if they had 25 years experience or 1 years experience 25 times. (I now have the re-flash experience 25 times - another education.) Thanks for all the advice and counsel - now to get Linksys SPA 941 phones on the MESH.
IP Logged
Page # 


Powered by ccBoard


SPONSORED AD: