I have an isolated RF node and have not been had any luck getting the system to either retrieve DHCP information or get an ARP answer from my TWC cable modem.  I have successfully set the static IP and gateway addresses but the system will not talk to the router because it doesn't know its MAC address.

As far as I can tell the ARP command will not take arguments so I am at a loss what to try next.

73,

Alan - W5ARH

Tony, I assume that your node is running and only the DHCP service was turned off. Set up your PC with a manual IP address. I suggest you use 192.168.1.100 with a net mask of 255.255.255.0. Then open your web browser and enter the URL: http://localnode:8080

Russ

KI6MLU

I have a wrt54G router which I think I accidentally turned off DHCP and no I can't get into it.

Is there a way to get back into them via lan port without dhcp please.

Thanks & 73's Tony N2SIQ

The way I setup my PBX was give the phone/ATA a static IP on the mesh node they are attached to.  Then the pbx a static IP on the node its attached to.   The phones are programed with extensions of birthdays right now so the user who has the phone birthday is there ext number.   You can setup a dial by name directory also or call sign if you so desire. By no means am I an expert but that is the way I handled it.

My PBX is running on a BeagleBone Black and the phone/ATA boxes are

http://www.ebay.com/itm/Sale-SIP-FXS-VOIP-Analog-Phone-Adapter-UNLOCKED-/271771876790?pt=LH_DefaultDomain_0&hash=item3f46ddbdb6

these off ebay
then utilize regular of the shelf phones and dect wireless ones

I had an old Dell, slapped a fresh HD into it and installed the FreePBX Linux kit onto it...

The install went well.  I can get into the web gui, even over the mesh!

I just can't figure out how or where you attach phones to users and IDs to mac addresses...

I don't have much of a clue as to what I am doing and I am looking for some help getting my Cisco 7960 and some polycom phones up and running.

Any AsteriskNOW guru's out there?!?

Bill - N5MBM

I have confirmed with Conrad that there is a bug in OLSR and a report has been filed. 

Conrad notes that until the issue has been addressed the best way to force an update to go out would be to turn off the node advertising the details for around 5-10 minutes (gives the rest of the network time to purge the details) and then power it back up.

Hello  -

I see from the instructions that Ubiquiti has made a modification that prevents some newer models from being used -  the "XW" issue. There was another statement that the issue was being worked  - but no status was given. Has this issue been resolved yet? 

Thanks

John, N9CNM

I just replaced an older R-Pi with a new R-Pi-v2. In the process I assigned (reserved) a new IP Address (so I could have both systems running for a while) and then moved all my apps to the new hardware and updated my services links.  After testing I removed the old hardware completely, but for consistency I kept the old name for the new system.

I.e. wb6tae-svcs.local.mesh was 10.0.0.1 and is now 10.0.0.2

After rebooting my node, all works well locally. But, none of the other nodes in our mesh see the new address. They still resolve wb6tae-svcs.local.mesh to 10.0.0.1.

So, my question: Is there a way too force a network wide update of the DNS data or do we have to resort to rebooting every nice on the mesh?

After looking around a bit (well, quite a bit) I have settled on using Redmine. At least as a prototype system. This is offered as a bug tracker, but with a little customization (and imagination) it can actually serve as a decent community incident reporting system.

NOTE WELL: I was not looking to create a dispatch or resource tracking system.  My implementation was designed solely to allow neighborhood groups to input specific types of serious incidents to be logged. It was also a firm requirement that this system be able to run solely on the mesh and run on a low-power Single Board Computer (R-Pi).

Getting this to run on the Pi was NOT EASY. But, after a but of fooling around, I got it installed and was able to start with the customizations I needed.

I have attached a screenshot of the input screen. It should give a rough idea of what we trying to accomplish.

Next steps: Since the principal type of disaster we expect to experience here is an earthquake, we must assume that parts of the mesh will fail (for various reasons). So, we need to find a way to get this to run in a distributed (Cloud?) mode so individual groups can still input data locally, even if the data cannot propagate to the responders immediately.  

And, here is a key point: the nature of a significant earthquake is that it will strike a large area at once. Thus, it is very likely that emergency response agencies will be completely overloaded for the first 2 to 4 hours immediately post-quake. They will be neither soliciting, nor accepting neighborhood reports during this period. Local neighborhood CERT groups will be the sole responders.  However, as things settle down, the official agencies will, if only for statistical purposes, want to see the extent of damage in the neighborhoods. and this is the need we are trying to address.

Attachments
 redmine.png [158 KB] ::

Just out of curiosity, I went to look for example WebEOC pricing.

Not surprisingly, they list NOTHING on their website.

BUT.....

If you Google "WebEOC pricing", (be sitting down first!) you can find PDF files of quotes for counties/organizations around the nation. Good thing I wasnt taking a drink at the moment I scrolled down to the itemized quotes (one I saw was >$127K!), else I would now cleaning sprayed Mountain Dew off my monitors/keyboard. :-)

So to actually have WebEOC running over BBHN, it would have to be a taxpayer-funded version, unless the ARRL can make some agreement with them... (not holding breath)

73

Jim

Are you using the TRX file or BIN files? (the files' name extension ex: FILE.TRX FILE.BIN)

Anytime you are upgrading an existing node, you only use the TRX file.

73 & Happy Meshing!

Jim

I am trying to flash a Bullet M2-HP from bbhn 1.0.1 to 3.0.0. The firmware will upload to the Bullet from my laptop but will not flash. I get a message saying "Firmware CANNOT be updated the uploaded file is not recognized". Any suggestions are greatly appreciated.

Thanks

Dave KM2O

I have 3 WRT54Gs and one Ubiquity Bullet M2.  All were connected fine via RF on CH 1.  In an effort to minimize interference over a 20 mile path to another station, we decided on CH 3.  The bullet connected fine to the remote station on CH 3 (across the Las Vegas valley, I might add :) - still fine tuning though).

I changed the 3 WRT54Gs to CH 3; their physical locations remained unchanged.  Applied the change, used the "Save Changes" button and rebooted each of them.  They see each other, but not the bullet.  Oddly, I know I noticed that when I changed the first one to CH 3, it still saw the other two that I hadn't changed yet from CH 1.  At that point, I chalked it up to being tired / a fluke.

A WiFi scan from the bullet, and from at least one of the WRT54Gs, shows BroadbandHamnet-20-v3 on CH 1 (not CH 3!) (the bullet also shows a second entry - the remote station's -71 signal on CH 3).

I'm coming to the conclusion that for whatever reason, changing the channel on the WRT54Gs had no effect - is this a known issue?  

I know I can work around the 3 nodes being on RF only paths with the bullet; it was just my inability to replicate my original setup that was frustrating since everything worked fine on CH 1.