The one pictured is a 15. I believe we upgraded to 60 watts and added a larger battery. It stayed on all night last night and went out this morning for an hour before the sun came up.

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)

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

I will continue to hammer at it...

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

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.

I am not familiar with convers, so I can't comment on that. However, comparing hatchet to irc is like comparing a little red wagon to a Mack truck. Hatchet is a single channel ("room") and uses a standard browser window for the interface. Irc is, well, infinite and requites a special client (GUI or text). 

If all you want is an open comm channel between a small number of meshnet users, hamchat will probably work just fine. If you need the granularity of multiple chat rooms, file transfer, extensibility, etc. etc. then use irc.  

Or, just install both.

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 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 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

I also have a mix of hardware (LS and UBNT). I think the LS devices have their place as do the UBNT devices. The 600mw output of the NSM2 is great (vs. the LS 100mw at it's cleanest/strongest power).  The MIMO technology in the NSM2 and RocketM2's are really good performance enhancers as well.

In my opinion, the LS devices are good for "light" RF work and tunnel connections (If you can find the rare  WRT54GS models).

The "aimer" script on UBNT is nice for easily aiming antennas. 
The ability to patch firmware in UBNT instead of a full reload is also a big time saver.
I'm currently trying to find a workaround for a nasty bug in the Kamikaze build on Linksys around the package management stuff.  (to support tunnels).   Working with the Attitude Adjustment (UBNT) build is much more elegant/stable.

The lack of multiple ports on UBNT is a bit of a pain, but, not every node needs extra ports.

I think there can be some trade off here and cost factors can be rather different than what you have projected. For instance: I currently have 3 WRT54G v2 nodes that only cost me $5 each on craigslist and work perfectly. I can also get a 12db outdoor omnidirectional antenna for under $40 and an outdoor enclosure for as little as $13. So that brings me to a total cost of $58/node using WRT54G. Im not sure I see any real need for POE with nodes but there could be a purpose that I might not be thinking of. If you wanted the nodes to have their own power, as you should, then that is a cost that would still apply to any configuration.

With all of that said, I definitely feel that Ubiquiti has some great hardware over the WRT54G's. In the ideal situation, I would go with Ubiquiti but since I am just starting my ARES team (2 of us right now) all of the money is coming out of my own pocket. But it is clear to see that on a cost perspective there is still a lot of money to be saved using the WRT54G's if you know where to look. If the ability and funds were there I would even go as far as trying to do an 802.11ac mesh. Of course, that being a new technology, we will have to wait for that to get better over the years. I would also have to use a newer version of OpenWRT unless BBHN came up with a supporting firmware. ;)

There is some very good info in your write-up though. Very well done and thought out.

I couldn't think of a better subject for this.

I finally finished my efforts on the use of RMS Express and Telnet WL2K tonight.  I had help from Mikes Burton XE2/N6KZB who's retired and lives in Baja, MX.  He's done a lot of work with the folks in the aja and San Diego environs in Mesh development.  Using Teamviewer, he put some effort in fine tuning my RMS Trimode Gateway as a prelude to putting RMS Express/Telnet into use on my Mesh project.

As of tonight, Thursday 1/2, I now have a working message system with RMS Express on my Mesh.  I was able to successfully transfer messages back and forth between two nodes.  My Gateway RMS Relay is sitting on my desktop Acer Aspire and the nodes connected with the RMS Relay IP just fine.

I then threw caution to the wind <GRIN> and sent Mike a message from my W6IDS-002 node and it looks like it was sent just fine.  The connection and transfer on MY end went as usual.  It was sent via Telnet WL2K.  Hopefully, Mike will reply back as requested to confirm success.

RMS Relay will pass the traffic from my mesh to Telnet directly through a selected CMS.  That is, as long as there is a working internet.  Should the Internet crash somewhere that affects MY operation, RMS Relay will handle the message traffic as Radio Only traffic and move it to another RMS Station like mine for entry into the internet and ultimate delivery.  

So far as local users are concerned, using RMS Express allows them to have 24/7 local messaging on the Mesh.  RMS Express can automagically poll Telnet periodically and retrieve any messages that are pending for the user.  That allows the user to be away from his/her station - they don't have to plant themselves at their station to get traffic.  That gives me the local Mesh messaging capability I wanted. PLUS, it gives me the ability to provide a secure message path to Winlink outside of my local area. 

Now, how this all fits into the REAL Wayne County, IN BBHN Mesh - I don't know.  The Mesh doesn't exist yet.  The only Mesh in town is in my home <GRIN>.  Things are a bit vague on the subject. However, I'm plugging along creating these utilities that I like.  They may not be implemented generally, but they're available for use.

Next, I think I need to look into putting up an outside antenna in some fashion so that I can be ready to hit the local hospital where a node may be installed.

BBHN - the "Never Ending Story" and I'm having a ball!

Howard W6IDS

Richmond, IN 

I have just installed hamchat on bbhn 3.0.0. I needed to make a few minor tweaks, but it works just fine. The changes are in the sections where html is sent back to the browser.  It appears the v3 html server behaves somewhat differently so made the following change in 3 places.

From:

print "HTTP/1.0 200 OK\r\nContent-type: text/html\r\n";

To:

print "Content-type: text/html\r\n";

I also updated the timestamp suggestion to use the system date function:

$now_string = `date +"%m/%d %H:%M"`;

printf FILE '<p><span class="date">' . $now_string . '</span><span class="callsign">' . $name . ':</span><span class="message">' . special_chars($msg) . '</span></p>' . "\r\n";

 Which prints a timestamp of the form 01/01 19:59

I've attached a photo. Don't have any of the inside but it consists of a WRT54G, charge controller, and AGM battery.

Attachments
 node.jpeg [221 KB] ::

Sometime it is just evil

the comcast modem model is Model: TG862G

System software is eMTA & DOCSIS Software Version: 7.6.86L

I left the IP six security set high, so the change only was for IP4

Hope this will help in the future.

now I have bricked another node... I will post it in another topic... how could you have more fun that this?????

73 de Mike/K3MMB