This is BBHN->ticket:74, it is believed to be fixed in beta build 3.0.1b01 which you can evaluate if you wish this to work now, otherwise it should make it into the official 3.0.1 build when it is released.

Passive POE at battery voltage.   12v system. 

All's well that ends well!  I'm up and running.  Not sure what went wrong before but this install went OK.

It does come back up at the 192.168.1.1 ip address as the NOCALL node name in order for you to change the node name to contain your call and allow you to change the password.  Then when it reboots it comes back in the 10. address range.

Steve G./N4TTY

on the main status screen (localhost:8080/cgi-bin/status), do you have an IP listed under the WAN address?
also, on that same page, what does it show as your default gateway?

Another example 'hill-top' 'in-the-wild' configuration (see picture links below):

1) Bullet M2 - 15db Omni

2) Rocket M5 - 19db 120 deg sector

3) Trendnet ipCam (indoor camera has lasted 1 year under a pizza lid and still live)

4) 125aH deep cycle Walmart battery (and is 4 years old)

5) 110W solar panel with charge controller

6) UBNT aircam

This configuration went ~5 days with constant clouds in December short-sun days before dropping offline in the middle of the night in Southern California. I am considering increasing battery capacity next fall to get through the winter (and adding more equipment from my wish list of 900mhz, 3Ghz, weather station, Rasb-Pi, etc.)

https://drive.google.com/file/d/0B2bEy75HhwWhNEhuTkYyYzRwV2M/view?usp=sharing

https://drive.google.com/file/d/0B2bEy75HhwWhQ0ZvOEhRbTNVZms/view?usp=sharing

Joe AE6XE

Are we to assume installation is the "same" as the Linksys devices?  Let's improve guys!!!!

I just loaded the BBHN factory software .bin file into a brand new, out of the box NSM2.

It now seems dead!

The first part went fine (logged into the NSM2 at 192.168.1.20), but after getting the message about upload in progress, the browser screen went blank.  Thought that might be normal, but when I tried to reconnect to "http://localhost:8080" I get nothing.

The NSM2 no longer responds at 192.168.1.20, so something has changed!

Any help appreciated.

Steve G./N4TTY

Hi,

I'm trying to install NGIRCD on Linksys router.

When I refresh the pkg mgnt tool, I get the following error:

wget: no route to host (attached)

Any ideas please?

Jay, KJ6HSH

Attachments
 error.jpg [291 KB] :: wget: no route to host

Success! Thank You Conrad. You were correct in your analysis in that the camera needed to see a connection from the same IP address segment.

The fix: I changed the node to NAT, reprogrammed the camera IP to match the NAT LAN IP address range, then assigned a static IP from the DHCP range to match the IP of the camera. Then I forwarded the 554 port from WIFI to LAN.

Now, regardless of which node follows the Advertised Service link, the video streaming works to that node - with the help of my program to translate the URL for the video client.

So, now I will demo the live video link to my local mesh net group.

A big thank you to the BBHN group.

One other note: Multple nodes can watch the same live video at the same time.

My assumption and perspective is a ubiquiti mesh device:

1) The node auto-magically determine these settings and you can view/tweak in the setup.:

1a) LAN (eth0 vlan '0') -- is DHCP server and a default 5 device IP subnet

1b) DTDlink (eth0.2 vlan '2') -- no DHCP, preset IP (based on MAC), and appropriate subnet determined

1c) WAN (eth0.1 vlan '1') -- expects to obtain IP and other settings from your home network DHCP

2) It is unnecessary for 1a & 1b to consume an IP address and assign to the switch.

3) Think of the linksys as a standalone switch by itself. It already has vlan settings (just internal). I'm seeing only 2 benefits to directly connect the linksys (a switch) together with your cisco switch:

3a) DTDlink between linksys and ubnt nodes over the cisco switch. See release notes to turn linksys DTDLink on and background (working around a bug in linksys switch with no path to resolve). cisco port should be configured only to pass vlan '2'.  Should ignore all other traffic to avoid other complications.

3b) Add more LAN ports to linksys (need more than 3 or 4?)  But not efficient use of a 'smart' switch.  Only need a dumb switch to do this.

Hi folks,

I am looking at using a cisco switch to do dtdtlinking and have been looking at Clint's write up here: http://ae5ca.com/?p=49 which has been very helpful.

My cisco foo is a little rusty but I think I have come up with a config that may work.  A couple of questions for anyone who knows about this stuff:

1. If I have 2 nodes connected to the switch, how are the configured regarding DHCP, IP's and subnets?
2. If I have the nodes tagged on vlan 2, would giving that vlan on the switch an IP in the same range as the nodes help? Vlan 1 will have an IP on the switch in the same range as the internet connected subnet but not sure if I need to assign an IP to any of the others.
3. can a wrt54g be attached to the switch in this way? I have a bit of a mix of devices.

Thanks

Conrad,

Thank you for taking time to answer my dilema. As soon as I can get some free time, I will investigate further following your advise.

The passing of the logon information is very simple and can be done for any security camera model. My program takes care of re-ordering the information into a URL for use by the video client program.

I am excited about making the HD video (1280x1024) link work through the BBHN. 

Also, thank you for the new link.

I also had an unused WRT54G-L, and a ham license, so I bought one of these:

http://www.ebay.com/itm/RP-TNC-to-N-Male-WiFi-Pigtail-Cable-Biquad-USB-Linksys-WRT54G-WRT54GL-WRT54GS-US-/141123896052?pt=US_Directional_Network_Antennas&hash=item20dba3c2f4

I already had a length of LMR-400 with N connectors and some older 2.4Ghz antennas, so this was a cheap experiment.

Are you comfortable with editing files on a node using vi?