It amazes me that I can break almost anything... here we go

Processing Bullet M2 to flash from V3Beta to V3 Production. Something failed.

Current situation: during power up the unit flashes:

Power LED   <-> LED1 Led2 Led3 Led4

        solid                                      F

next  solid                                      solid

a connected windows laptop will not obtain a DHCP assignment. A connected Linux laptop says the cable is disconnected. I tried the TFTP script trying a connect to 192.168.1.1, it failed.

Tried the reset button, if made no difference.

Is there another magic button to try?

73 de mike/k3mmb

It's really hard to 100% brick a bullet. Have you tried a Google search for "UBNT Firmware Recovery?" It works for me every time...even when I "brick" them on purpose.

The issue holding me up, finding the IP address of the bullet. I have tried fixed IP on the laptop (all the normal addresses used by airmax, BBHN, and 192....).  DHCP does not work and fixed IP efforts have failed.

I will repeat the list connected to a switch.

73 de mike

response from ping is host not reachable.....

I will continue to hammer at it...

It doesn't sound bricked to me, this is the normal light pattern for a bootup.

What I find interesting is you don't mention the LED next to the power LED. That one should flash as packets are sent and received, if it isn't lit  your network cable isn't plugged in, has gone bad, or the port some how took an ESD shock (not likely on a work bench this is usually only seen on towers)   Might of come loose while moving cables around from the POE injector or computer.

Also the default IP address on "just flashed" is 192.168.1.1 (the 1.20 is when you are in firmware recovery mode only)

the led in question does not blink during boot.

none of the attempts worked

in recovery mode

network Ip set manually...

root@K3MMB-Gateway:/home/k3mmb/Downloads# ifconfig
eth0      Link encap:Ethernet  HWaddr 04:7d:7b:7e:55:2d  
inet addr:192.168.1.254  Bcast:192.168.1.255  Mask:255.255.255.0
inet6 addr: fe80::67d:7bff:fe7e:552d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:918 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B)  TX bytes:157406 (153.7 KiB)
Interrupt:43 Base address:0x6000

lo        Link encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:337 errors:0 dropped:0 overruns:0 frame:0
TX packets:337 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:33650 (32.8 KiB)  TX bytes:33650 (32.8 KiB)

wlan1     Link encap:Ethernet  HWaddr 08:ed:b9:05:56:0f  
inet6 addr: fe80::aed:b9ff:fe05:560f/64 Scope:Link
UP BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:11143 errors:0 dropped:0 overruns:0 frame:6020
TX packets:6869 errors:56 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14382247 (13.7 MiB)  TX bytes:814272 (795.1 KiB)
Interrupt:17

root@K3MMB-Gateway:/home/k3mmb/Downloads# ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
From 192.168.1.254 icmp_seq=1 Destination Host Unreachable
From 192.168.1.254 icmp_seq=2 Destination Host Unreachable
From 192.168.1.254 icmp_seq=3 Destination Host Unreachable
^C
--- 192.168.1.20 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3014ms
pipe 3
root@K3MMB-Gateway:/home/k3mmb/Downloads#

If that network led doesn't light up you have no chance at speaking to the node until it does.

That LED is controlled by hardware so even a crashed bricked node would still light it up (assuming the LED doesn't go bad obviously).  It is lit when a cable is plugged in and flashes off when packets are sent. It is the same as the LED on a switch that light up when you plug in a cable and turns off when you unplug a cable.

I recommend swapping out the cable between the injector and node, and the cable between the injector and the computer (make sure you plug the POE side to the node and not the computer)

If that doesn't light up with new/different cables you may want to try instead of plugging into your computer plug the cable from the LAN side of the injector into a switch and see if that works any better to rule out PC problems.

I figured it out..

The problem was a bad LAN port on the power supply. I connected the bullet to a trended s44 poe switch and it booted. The IP address was 192.168.1.1. Since I had just flashed it, and never completed a reboot and setup, I guess it was correct.

Thanks for all the help

73 de mike

A bad port on the injector, now that is the first time I have heard that one.

Glad you have it working and sorted out, and funny it happens right after the update as well.

Remi Thanks,

I do have the ubitiquiti adaptors to handle the situation. I have both the indoor and outdoor units. It makes things a bit easier when working in the field.

Happy MESHING in 2015

mike