Firmware problem,

[RNetSwe]

Hello!

I have heard so much good things about the Nanostation, so I decided to give it a try.
But this isn't a nice first view of the product.

One of my Mikrotik customers are using many NS2 and NS5 and he is very satisfied, when I told him that I was going to test the NS2, he recommended me to upgrade the firmware to the latest version, so I took his advices and installed the latest firmware from the GUI.
After the upgrading process started, I went for a coffee and when I got back after a hour, the device didn't respond....
I looked for a recovery process and went trough it, not just one time but with all available binaries in the NS2 firmware section.
But still the unit didn't respond.
I've tried with direct connection to my Linux box and trough a switch, but I get the same result, no ping respond.
Have something been changed from the documented default values IP, etc in the firmware?
It's a bit strange because the unit seems to respond (it blinks) when I try to ping the unit.
As you can see in the log, the unit responds fine in the recovery process so I don't think it's a hardware problem

This is my log when I'm doing the recovery:

# ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=0.000 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.000 ms

--- 192.168.1.20 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1009ms
rtt min/avg/max/mdev = 0.000/0.000/0.000/0.000 ms
# arp -na
? (192.168.1.20) at 00:15:6D:E0:94:B7 [ether] on br0
# ls -la
totalt 13520
drwxr-xr-x 2 someone someone 4096 2008-09-13 01:23 .
drwx------ 4 someone someone 4096 2008-09-13 00:07 ..
-rw-r--r-- 1 someone someone 2462653 2008-09-13 00:06 flash_update
-rw-r--r-- 1 someone someone 2843774 2008-09-13 01:24 NS2.ar2316.v3.1.1.3498.080725.1324.bin
-rw-r--r-- 1 someone someone 2921403 2008-09-13 01:23 NS2.ar2316.v3.2.3734.080909.1631.bin
-rw-r--r-- 1 someone someone 2462653 2008-09-13 01:23 NS2.v2.2.1.bin
-rw-r--r-- 1 someone someone 3112604 2008-09-13 01:24 NS2.v3.0.bin
# tftp 192.168.1.20
tftp> bin
tftp> put flash_update
Sent 2462653 bytes in 11.8 seconds
tftp> quit
# ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
From 192.168.1.5 icmp_seq=1 Destination Host Unreachable
From 192.168.1.5 icmp_seq=2 Destination Host Unreachable

I have tried the recovery process on my windows laptop with direct crossover cable with the same result.

Today, I'm not happy with the NS2 product... It have cost me 4 hours of work (thats 5 times more than the NS2 costs) and the result is a bricked device.
Can anyone make me happier?

Regards,
Paul Eriksson

[RNetSwe]

Hello!

I have heard so much good things about the Nanostation, so I decided to give it a try.
But this isn't a nice first view of the product.

One of my Mikrotik customers are using many NS2 and NS5 and he is very satisfied, when I told him that I was going to test the NS2, he recommended me to upgrade the firmware to the latest version, so I took his advices and installed the latest firmware from the GUI.
After the upgrading process started, I went for a coffee and when I got back after a hour, the device didn't respond....
I looked for a recovery process and went trough it, not just one time but with all available binaries in the NS2 firmware section.
But still the unit didn't respond.
I've tried with direct connection to my Linux box and trough a switch, but I get the same result, no ping respond.
Have something been changed from the documented default values IP, etc in the firmware?
It's a bit strange because the unit seems to respond (it blinks) when I try to ping the unit.
As you can see in the log, the unit responds fine in the recovery process so I don't think it's a hardware problem

This is my log when I'm doing the recovery:

Did anyone else seen this problem?
If so, please back me up with this.
Thanks
/Paul

[RNetSwe]

Update:

I have donwloaded and install the SDK and toolchain, compiled my own binary.
I installed it with the same result.

Then I tried to recreate the cfg partition in the flash as described in this thread: http://ubnt.com/forum/viewtopic.php?t=2184 in my own compiled binary. I discovered that the RedBoot binary wasn't in there so I recreated the official v2.2.1 with the cfg partition.
Again the same result, no respond after flashing.
I tried the same with the v3.2 and again..... same result

Anyone, please!!!!
Paul

[UBNT-keba]

Hi, first of all Redboot v2.2.1 does not support cfg recovery. It should be from v3.0 at least.

How long did you wait after
# tftp 192.168.1.20
tftp> bin
tftp> put flash_update
Sent 2462653 bytes in 11.8 seconds
tftp> quit
?

It could take about 5minutes to complete recovery.

[RNetSwe]

Hi, first of all Redboot v2.2.1 does not support cfg recovery. It should be from v3.0 at least.

How long did you wait after
# tftp 192.168.1.20
tftp> bin
tftp> put flash_update
Sent 2462653 bytes in 11.8 seconds
tftp> quit
?

It could take about 5minutes to complete recovery.

As I wrote in the beginning I went for a coffee, so about a hour.
I've read it might take up to 7 minutes, so I've been waiting....
Is there any "special" image that I can use to get back on track or do I need a serial or JTAG to connect up?
/Paul
/Paul

[UBNT-keba]

If you can do recovery procedure it means that device is still alive. Can you do recovery procedure by using original v2.2.1?

[RNetSwe]

If you can do recovery procedure it means that device is still alive. Can you do recovery procedure by using original v2.2.1?
Yes I can recover all the firmware that's in the download page, but they all give me the same result, I cannot access nor ping it after reflashing.
The first upgrade I did was from the Web GUI and I upgraded to 3.2, after that I couldn't ping the device. I left the unit running at least an hour after reflashing.
If anything went wrong with this, but the unit still can get into recover mode, should the recover into 2.2.1 work?
If I cannot connect after 2.2.1 is installed, what can I do to reset the configuration?
What about the bootloader could it be something wrong with it?
The behavior is likely the same as someone who flashed with dd-wrt, but the difference is that I have only used the StarOS files.
/Paul

[RNetSwe]

Update:
This is my trial with v2.2.1 firmware:
A ping from the Linux host when I powering on the unit holding the reset button.
From 192.168.1.5 icmp_seq=24 Destination Host Unreachable
From 192.168.1.5 icmp_seq=25 Destination Host Unreachable
From 192.168.1.5 icmp_seq=26 Destination Host Unreachable
From 192.168.1.5 icmp_seq=27 Destination Host Unreachable
From 192.168.1.5 icmp_seq=28 Destination Host Unreachable
64 bytes from 192.168.1.20: icmp_seq=29 ttl=64 time=169 ms
64 bytes from 192.168.1.20: icmp_seq=30 ttl=64 time=0.000 ms
64 bytes from 192.168.1.20: icmp_seq=31 ttl=64 time=0.000 ms
64 bytes from 192.168.1.20: icmp_seq=32 ttl=64 time=0.000 ms
64 bytes from 192.168.1.20: icmp_seq=33 ttl=64 time=0.000 ms

--- 192.168.1.20 ping statistics ---
33 packets transmitted, 5 received, +27 errors, 84% packet loss, time 32229ms
rtt min/avg/max/mdev = 0.000/33.999/169.997/67.999 ms, pipe 4
# tftp 192.168.1.20
tftp> bin
tftp> put flash_update (v2.2.1)
Sent 2462653 bytes in 13.4 seconds
tftp> quit
# date
Mon Sep 15 22:30:43 CEST 2008
During this time the unit "SIGNAL STRENGTH" leds were walking up and down. And in the end the LAN led dropped and came on again.
# date
Mon Sep 15 22:38:16 CEST 2008
# ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
From 192.168.1.5 icmp_seq=1 Destination Host Unreachable
From 192.168.1.5 icmp_seq=2 Destination Host Unreachable

I made a power recycle with the same result.
Do I need try try an older version?
I'm not sure of the original one, but I think it was v2.2.1.
The test date was 03/27/08, if this gives a clue of the original.

Regards,
Paul

[UBNT-keba]

What was last IP you used? Was it 192.168.1.20? Use discovery utility http://ubnt.com/downloads/discovery/ubnt-discovery_v2.2.1.zip to find the device after boot.

[RNetSwe]

What was last IP you used? Was it 192.168.1.20? Use discovery utility http://ubnt.com/downloads/discovery/ubnt-discovery_v2.2.1.zip to find the device after boot.

Sorry to say this, but the configuration was the default configuration.
And yes I've tried the discovery and sniffed the network at the same time, nothing comes from the NS2. :-(
Is there a way to save this?

Regards,
Paul

[RNetSwe]

I read this in an other tread:

[quote=Actually the problem may be a switch. I have nanos running cable lengths of 100' or more with no problem. However, I have seen problems with switches that auto negotiate. I would try a different switch. We use Linksys sd205, sd208's on our outdoor installations due to their temperature ranges and have had no problems.[/quote]

I'm using a HP ProCurve 1800-8G, is the NS2 sensible to auto negotiation?
When in the recovery mode, it works fine. So then it must be something with the ether chip drivers.

[UBNT-keba]

Is it work if connected directly to PC?

[RNetSwe]

It didn't answer before the last recovery.
So, I doubt that it's working now neither
I'm on travel now, so I cannot test.
I'll be back on friday.

Keba- Do you have any ideas of what have happened, I talk to my Mikrotik customer today, he has a lot of NS2 and 5 as CPE in his network, And he has never failed with the upgrades, the difference is that he did the upgrades to 3.1.1.
So again, why me :cry:
I really want this to work, since I love the concept.
Can I reset the configuration when I'm on 2.2.1, how?

/Paul

[ahooper]

I seem to be having a similar problem.
I upgraded the FW to 3.0 then to a custom version based on the 3.0 SDK, then back to the 3.0 but now the unit looks dead.

I tried doing a recovery by holding the reset pin in while the power was applied for 10 seconds but can nto ping the default IP.

If I try using the discover software from a PC connected directly via a crossover cable i still dont get anyting.

Unless i am missign something in the recovery proceedure

[UBNT-keba]

RNetSwe, yes you can reset to defaults in any version. All versions uses +- the same saint defaults.

[RNetSwe]

Good News!!!
I've managed to get the unit running, but is cost me lots of pain.
After trying the recovery procedure lots of times with different versions and split images without any luck, I decided to give the screwdriver a try.
I have asked how to get into a console, but..... :evil:
I cut my old Nokia DUA-9p cable in pieces and analyzed the pinout on the board. After wiring the ends to the pins on the board (thanks to my old tool box and a nice little wire wrap tool). I managed to see what was wrong with my unit. It stopped on the RedBoot prompt, aha!!! it had dropped the fconfig script configuration.

What went wrong in the beginning?
I upgraded the unit from 2.2.1 to 3.2 and the fconfig script went away, hmmm....
My RedBoot loader was 0.8.2395, was this the problem?
Why isn't the fconfig script rewritten when upgrading or recovering?
I have now enabled the RedBoot BOOTP network configuration, so now I can telnet into RedBoot before the script timout (5s), why isn't this configured by default?
/Paul

[UBNT-keba]

There are a loot of info about Serial Console on the forum. Some of that are on:
http://www.ubnt.com/forum/viewtopic.php?t=4094
http://www.ubnt.com/forum/viewtopic.php?p=13041

The script timout increase will increase boot time of device it is not a solution for normally functional devices.

We will check what can cause fconfig script corruption. Thanks for co-operation.

[cerebro2005]

[QUOTE = UBNT-Keba; 12364] Hay un botín de información acerca de la consola de serie en el foro. Algunos de los que se encuentran en:
[url] http://www.ubnt.com/forum/viewtopic.php?t=4094 [/ url]
[url] http://www.ubnt.com/forum/viewtopic.php?p=13041 [/ url]

El aumento de timout script aumentar el tiempo de arranque del dispositivo no es una solución para dispositivos que normalmente funcional.

Vamos a comprobar lo que puede causar la corrupción fconfig guión. Gracias por la cooperación. [/ QUOTE]

Intento entrar en esos link y me dice que ya fueron borrados, les comento que soy novato y al actualizar a la vercion 3.4 me ha pasado lo mismo, no tengo acceso a la NS2 x ningun lado .... alguien puede ayudarme a recuperarla, les cuento que la luz de power enciende y tambien la de LAN pero no puedo acceder a ella x ninguna lado ya scanee mis puertos IP para ver donde estaba pero no tuve suerte tambie e provado el ubnt-discovery_v2.2.1 y tampoco lo ve .... HELP