I am not able to duplicate the issue in my lab.

My first thoughts would be to clear the browser cache and try again (to be sure its not a caching issue)  if the error still shows up on saving than I would suggest a different browser as a test to see if its maybe something browser related.

If that doesn't solve it than it will require more in depth searching to the cause as it seems to work fine in my lab.

Edit: See that You are already using Firefox, so my other browser choice seems less likely a cause.

Attachments
 testserviceentry.JPG [57 KB] :: Test Service Entry

Just a note, that passthrough of data on  the 2nd ethernet port on the NanoStation is not currently supported (See BBHN->ticket:56) and is currently blocked by BBHN->ticket:61 needing to be implemented first.

Also we do not out of the box support passthrough of the POE Power to the 2nd port, there are guides online on how to do it, but due to the very limited amount of official information, plus some stories in the past of ports blowing (frying the passthrough transistor) (though it may have been a bad hardware batch) the passthrough power feature is not enabled or selectable at this time from the UI.

I updated the node to v3 BBHN firmware and re-entered the IP camera. No difference. I captured some screen shots and attached them. The MAC and IP addresses were blurred out as they should not be relevant to the discussion - and I did not use the broadcast IP address for this node.

Any ideas?

Attachments
 Screenshot-N4FWD-2 mesh status - Mozilla Firefox.png [61 KB] :: No link in spite of correct set up
 Screenshot-N4FWD-2 setup - Mozilla Firefox.png [90 KB] :: Camera set up for Advertised Services

Glad to hear that I was not crazy. What you say is certainly good news. But, the down side is that active POE devices cannot be powered by Ubiquiti passive devices - example: an IP camera (active POE) coupled with a NanoStation M2 (not Nano Loco M2). In this given example, one would have to hunt up a passive POE camera to use with the NanoStation.

Thank you Sir

Here is a link to a minimalistic GUI for asterisk on the node as well: http://www.broadband-hamnet.org/hsmm-mesh-forums/view-postlist/forum-9-voip/topic-354-asterisk-gui-management.html

I would place it as an install-and-configure type solution. Maybe I am a fast learner, but I learned/figured out how to do all of this in one month where I started from not knowing anything about Linux other than "cd" and "ls."

1. No question is a stupid question. :) Asterisk can be installed directly onto a router (I've personally tested 3 con-current calls 6 phones channels and left them open for two+ hours spread out all over a building without any jitter or choppy sound). Let me dig up my documentation from two years ago and I will point you to the correct link.

I have been trying to find a good answer for you but I keep finding that a server seems to be involved. 

In windows xp there was a program called netsh.  I believe it would work like you want.Win 7 and 8 replaced it with a program called msg. It does not seem to work quite the same. 

If you were running Linux on your computers than a command called talk would be an excellent choice. 

There is an article on installing an irc server directly on your node on the website. I am not sure if it still fits on a wrt54g or not. 

II would recommend putting a server on one of your pc's. Do a google search on windows chat server freeware. You will find instructions and videos on how to set one up 

1. Navigate to HSMM-MESH Info --> Videos --> and click on "Install Asterisk on a Raspberry Pi." Alternatively, you can use AsteriskNOW (or any other PBX) in it's place.

2. Please note that the firmware will still be readily available, but no longer updated.

3. BBHN/HSMM-MESH uses OpenWRT. So, you can install whatever packages you would like.

Hello  everyone,

I am somewhat new to this but let me give you all an intro about me, what I am looking to do, and a few questions.

I am an IT guy who recently (3/2014) was appointed ARES Emergency Coordinator for my county. Being the IT nerd I am and my new interest in ARES, I have started the beginning of a mesh network project. I have a few Linksys WRT54G's I am playing with, one of which has the Hamnet firmware installed. I did notice that this is a very basic/simple to use firmware but it left me with a few questions.

1. I would like to implement a VOIP/SIP solution to have another form of communication when the mesh is deployed. Is there an easy to implement solution that will use the mesh to to make phone calls to other phones on the mesh? Maybe its just better/easier to use Mesh Potatoes. They are being used by other ARES groups too. :)

2. Not to take away from BBHN which I feel is a great resource and mesh network firmware solution, and taking into consideration of the Linksys end of life, are there other widely used, supported, mesh focused firmwares out there?

3. Am I able to install "packages" with this firmware like what can be done in DD-WRT and OpenWRT, or is this a "it is what it is" type firmware? Im just curious about this in regards to being able to add extra functionality (if needed) to the Hamnet firmware.

Thank you all for the help.

Thanks for the report, probably better if we move it to a new thread for any further on it.

BBHN->ticket:74 created for this issue.

Overview: It looks like the Linksys devices (but not Ubiquiti) are trying to download via a newly published IPv6 Record for the BBHN domain.  Problem with this is most houses don't have IPv6 yet.

I suspect this is due to the age of the backend that some of these IPv6 situations hadn't been fully worked out yet when it was first released in 2007 so I will do some digging and see what our solution path is to resolve this.

Further updates can be found by watching the ticket.

Correct,  Ubiquitit does not use Active PoE (802.3at/802.3af) it uses Passive PoE (a common industry practice) as noted in the datasheet which is simply sending voltage up the spare pairs that are not used for data and essentially turns the cable into a long extension cord + data pair

This mostly has advantages on manufacturing side where it would cost a couple bucks for the PoE chip on the receive side and again on the power sending side.  This also has the benefit for ham operations in that we can run it straight off a power source without the need for additional integrated circuits in the path.

The voltage range has been discussed in the past  so i wont go into to much depth other than to say its around 10.5-24v AT THE DEVICE this means it can be run from 12v battery (short cable run), 18v battery (longer runs) directly.  Can run from a car source, etc.

I just wanted to share this nugget of information with my fellow Meshers.

Ubiquiti Network POE adapters are not compliant with the IEEE 802.3af standard.  I'm not sure if their equipment is compliant either.

The difference? IEEE 802.3af is a 48 VDC POE standard whereas Ubiquiti Network products use a 24 VDC POE.

When you purchase equipment which is IEEE 802.3af compliant, that equipment will not work using a Ubiquiti manufactured POE adapter. You will need to purchase an IEEE 802.3af POE adapter to power the equipment.

73 and keep meshing

With Regard to KF4WEO's question and AE5AE's answer, I get the following Error:

Package Management

Downloading http://broadband-hamnet.org/download/kamikaze/7.09/brcm-2.4/packages/Packages wget: cannot connect to remote host: No route to host Downloading http://broadband-hamnet.org/download/kamikaze/7.09/packages/mipsel/Packages wget: cannot connect to remote host: No route to host An error ocurred, return value: 2. Collected errors: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-OqsAlH http://broadband-hamnet.org/download/kamikaze/7.09/brcm-2.4/packages/Packages' ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-OqsAlH http://broadband-hamnet.org/download/kamikaze/7.09/packages/mipsel/Packages'

I have 12 of the WRT Routers and have used the NGIRCD 20.2 download several times through package Management with no problems until now.

Regards

Rick AJ4FW

Awesome, thanks!  I was worried there for a minute. I guess I put mine up on the roof before ever connecting to another node.  I had to walk outside and look at the lights. Sure enough my other node has a red light too.  Thanks for explaining that to me!

Matt

W6MCP

One of our poorly documented features.

The solid red led (Known as LINK1)  is illuminated when your node sees another node.  It is a quick indicator to see if you see another node.

Being lit doesn't always mean you have a good bi directional connection, it just means your node sees another node and you may have a chance at a connection.

it was added back in 1.0.1, and has turned out to be a great diagnostic tool (I've used it a lot more than I thought I would) as you can quickly see just by looking at the node lights if contact has been made.

Thank you. I was not sure about the situation. I'll update the nodes with v3 and let you how it goes with the camera.