Ticket 48 was written to address this issue.  It looks like it is still present in 1.1.2. 

I can confirm that I have been able to forward port 80 to the wan using a Rocket M2 and a Netgear GS105E or GS108E Ethernet switch with the switch programmed to tag the WAN Connection as VLAN 1 before continuing on to the Rocket. 

My friend that had the original problem has since switched to a NanoStation M2 and he is also able to port forward to Port 80.

I believe this is just a matter of adding the right line in iptables but I am not 100% sure of the command. 

Clint, AE5CA

After reading through the information, it states that the whole section is for amateur satellite use, and if there are no satellite operators in the area to interfere with, then the bands can be used for amateur TV. It doesn't state that data equipment can be used.

I know that the 2.4GHz spectrum is licence free and channel 1 is within that allocation, but is it still legal if the system is used as the mesh instead of a home wireless point?

Jack.

Greetings All,

My name is Chris (K2CTC) and I just purchased a WRT54GL to configure as a HSMM-MESH node.  The device has not arrived yet, but I am excited to play with the technology.  I would appear that this forum is the place to be if you are in Utah and interested in mesh.  I will post an update once I get things up and running.

I am curious,

Why are you rebooting the node if internet is lost ?

Nodes can still be very useful even if they don't have internet, putting it in a reboot loop every 5 minutes would degrade the network, and if you have an entire area internet outage and this is on lots of nodes you could take your entire mesh network down at once as all the nodes going into constant reboot cycles (a cascade failure)

Nevermind, found a persistent storage in /jffs/usr/bin/ and storred the script there. if anyone is interested, the i used this script to get the job done:

#/bin/sh

count=$((`ping -c 3 8.8.8.8 | grep -c '64 bytes'`))

if [ $count -le 1 ]

then

  `echo "timeout" >> /tmp/network_watchdog` # add timeout to watchdog

else

  `> /tmp/network_watchdog` # reset timeouts

fi

count=$((`cat /tmp/network_watchdog | grep -c "timeout"`)) # count occurred timeouts

if [ $count -ge 5 ]

then '/sbin/reboot` #reboot if more than 5 concurrent timeouts

fi

That's a high noise level.  I would definitely try horizontal polarization.  On the multipath question, you need to be sure the Freznel Zone is clear (see http://en.wikipedia.org/wiki/Fresnel_zone).  You can estimate the required clearance using the formula: 36*sqrt(miles/GHz)=clearance in feet.  Using 15 miles and 2.4GHz, that results in a clearance requirement of about 90' above and below the beam at the midpoint between the two nodes:

36*sqrt(15/2.4)=

36*sqrt(6.25)=

36*2.5=90’

So check to be sure that area isn't obstructed in any way.  However, again I'll suggest Ubiquiti gear in a scenario such as this.  You will gain nearly 10dB in receiver sensitivity (which will help when you get the noise issue resolved) and nearly 10dB in higher power output.  I don't have any experience in circular polarization.

Andre, K6AH

Hi All,

I have tried to install a script to check internet connectivity, and reboot a remote node if the connectivity has been gone for more than five minutes, this script was supposed to be executed by cron every minute. Where do I store the script on the hsmm firmware image to persist between reboots?

73 and Best Regards

LA3QSA

Per Øyvind

Thank you both for your replies!

our remote site node is co-located with a 2 meter and 70 cm repeater.  but,  there are lots of commercial transmitters close by.  the router shows a noise floor of ~-70 dBm.

the antenna used on the remote site is a commercially built sector array (HBW=90 degrees, VBW=7.5 degrees, gain ~16 dBi)

we are wondering also if multi-path is a factor. on the node opposite the remote site (located in a park), when lots of people show up, the signal levels really start to vary.

i have read several articles where circular polarization was used to mitigate multi-path. has anyone experimented with circular polarization?

thanks for your help!

N7RTA

I was able to recover back to the Ubiquiti OEM firmware using TFTP. I just tried attempted another upload of the BBHN firmware (1.0.1) and I am back to the same problem.  I uploaded the 1.0.1 version a few more times and could never get to the config screen.

I uploaded the 1.1.2 firmware, I can configure just fine.  I was able to upload the 1.1.2 firmware, then downgrade back to the 1.0.1 firmware, and everything is working fine now.

I just flashed a Ubiquiti Bullet with bbhn-1.01-ar71xx-ubnt-bullet-m-squashfs-factory.bin

After the firmware upload was complete, the DHCP in the bullet is assigning my computer an IP: 192.168.1.23, instead of one of the Class A addresses the rest of the mesh nodes assign.  DHCP also assigns a gateway of 192.168.1.1.  I try to ping that IP, and there is nothing there.  A broadcast ping did not reveal any other IP's on the LAN.

Did I brick my bullet?  How can I recover?

Edit: I should have mentioned that localnode:8080 does not get to the config screen either.