Looking at code: "iw dev wlan0 station dump"  the signal strength is in the brackets is each chain, otherwise it's a single chain connection.

I believe multiple chains will only apply if you get into the MCS Data rate for the connection, otherwise its a diversity receive and the strong of the two signals is reported regardless of which chain it came in on.

Majority of packets will be 1mbps single chain (required as you have to broadcast to support the slowest device, aka Linksys)  as they are intended for all devices to receive.

As for the mesh gateway inetd takes it from 2004 to 2003.  I will have to double check if the firewall rules permit it on WAN or not and if that was a design decision or bug if it doesn't (off hand I don't see a firewall rule in /etc/config/firewall to allow access on wan side) 

Your node should have the exact same data however.

Darryl:

I'd be interested in trying your mesh crawler if you are willing to share your code.

Thanks

Richard

Q1) How can I allow access to port 2004 (olrsd_dot_draw) from the Wi-Fi (mesh) port? Presently, I can access the service from the LAN port, but not from "the mesh."  Curiously, in /etc/configure/olsrd I found

config LoadPlugin
  option library 'olsrd_dot_draw.so.0.3'
  option accept '127.0.0.1'
  option port '2003'

I tried changing "option accept" to 0.0.0.0, but no change. And then there is the port setting of 2003???

Q2) On the Rocket and NanoStation/NS Loco (I.e. MIMO radios), is there a way to see the receive information for the two chains separately?  I tried iwinfo, but it only shows the overall received Signal and Noise.  iw didn't do much better.

Greetings,

We are a group of Ham operators in Malta who have been experimenting with HAM BROADBAND for a few months now and found it to be absolutely amazing. There is a learning curve, as with everything, but so far so good.

We have set up network tests using FTP, Web Services, Streaming Services (HD cams) and in the future plan to implement VOIP for emergency amateur use. All worked fine for us so far, but did find an issue with speed.

Prior to continue building the MESH, we are testing SPEED limitations and we have found out that we we cannot transfer anything (in controlled ideal conditions) faster than 15Mbt/s (that is: at a 1.5MB/s approx). We have tried the FTP transfer experiment between two nodes and yet, this is the maximum speed we're achieving.

We are using LINKYS WRT54GS as well as UBIQUITI M2 (also 2.4GHz). The Ubiquiti's performed at the same rate of 15Mbt/s, just like the Linksys, when we know that the Ubiquiti devices can perform at a MUCH faster rate (on their commercial original firmware). The Uniquiti devices have a directional 'dish type' antenna and they are POE's with 24V, whist the Linksys were tested using their original rubber ducky and voltage supply.

Hence our queery ... what is throttling us? Is it the Ham Broadband firmware? Is the implementation of 802.11 used in Ham Broadband? Can't we go faster than 15Mbt/s (1.5MB/s FTP transfer rate) on 2.4 GHz? Do we necessarily need 5GHz equipment to achieve faster and better bandwidth than this?

We appreciate any help and/or opinions on the matter. All our nodes are set up in the mode: MESH NODE.

If anybody would like test firmware for UBNT M2 with open 2 Ghz bandplan the firmware is available :

http://hamnet.ugu.pl/download/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin

MD5: 77a39c6c9feb6427b8f6fb8cbc80b682

When you put the  firmware via TFTP you can obtain IP address via DHCP from range:

172.16.1.x

Connect to UBNT M2:

telnet to 172.16.1.1

set password use command:

passwd

next set current date and time UTC:

date -s '2015-02-01 15:00'

setup hamnet network use script

hamnet NODE-Name IP-address Net-Mask

for example:

hamnet KA2ABC-2 44.128.1.1 255.255.255.0

After reboot system  you can go to simple status page:

http://172.16.1.1:8080

and on this page click on penguin icon  to see OLSR status

default setup channel 247 2.362 Ghz and bandwidth 5 Mhz with olsr SSID "HamNET"

but you can change via uci or editor in /etc/config/wireless

This test version of FW don't have any WebGUI to setup.

73 Waldek SP2ONG

Attachments
 mesh-owrt-ns2.jpg [87 KB] :: Nanostation2 with AA v12.07
 mesh-owrt-m2-ms.jpg [42 KB] ::
 mesh-owrt-m2-stat.jpg [84 KB] ::
 mesh-owrt-m2-mn.jpg [84 KB] ::

Yeah...  But I have a hard time convincing old fart ham operators with tight wallets to spend that kind of money on a beginners node when Linksys routers can be had for 15-25 bucks...

But we are running Ubiquiti bullets for the actual link transmitters - the combo of the two seems to work well so far...  So far...

Bill - N5MBM

My Node - http://n5mbm.endoftheinternet.org:8080/cgi-bin/mesh

Just a reminder, Linksys devices are going End of Support April 30th. 

While the firmware and devices will continue to work after this date I strongly recommend for anyone looking at buying new hardware to support this feature I would recommend looking at the Ubiquiti gear.

I would like to create a relay point half way between the two endpoints in order to go around a mountain.  If I have two Nanostation M2s mounted in the RF Armor shields, can I mount them on the same mast facing in different directions?  Does it help to mount them a certain vertical distance apart?  What else should I be considering?

Attachments
 NanostationRelay.png [146 KB] ::

Hello again Shawn - please give me some GPS co-ordinates, or an address where your location is at Dixie and Burnhamthorpe. I would like to do a mobile test for you to see if we can make a link to the mesh from your location there. Bob, ve3cwu at rac.ca

And that's pretty much all the "secret" files.  And for fun, here is a list of files located in the cgi-bin folder:

[paul@CentOS www]$ ls -lh cgi-bin/
total 160K
-rwxrwxr-x 1 paul paul 17K Jan 27 22:42 admin
-rw-rw-r-- 1 paul paul 5.3K Jan 29 12:05 channelmaps.pm
-rwxrwxr-x 1 paul paul 338 Jan 27 22:42 fwinfo
-rwxrwxr-x 1 paul paul 12K Jan 27 22:42 mesh
-rw-rw-r-- 1 paul paul 35K Jan 28 21:45 perlfunc.pm
-rwxrwxr-x 1 paul paul 26K Jan 27 22:42 ports
-rwxrwxr-x 1 paul paul 1.5K Jan 27 22:42 scan
-rwxrwxr-x 1 paul paul 24K Jan 27 22:42 setup
-rwxrwxr-x 1 paul paul 4.9K Jan 27 22:42 signal
-rwxrwxr-x 1 paul paul 9.3K Jan 27 22:42 status
-rwxrwxr-x 1 paul paul 962 Jan 27 22:42 sysinfo
[paul@CentOS www]$ 

one other page shows firewall rule config... /cgi-bin/fwinfo

I have build a sysinfo.json page that returns this type of data as a json doc, which can be integrated into scripts/applications/other pages easily.

I have a script that will crawl the mesh nodes I am connected to and return info about them (HWtype, FWversion, etc)

d

73, K5DLQ

Interesting "secret" page link. Does have the information I was referring to, but would like to see the info displayed "easier" on one of the node web pages, either the front page, an OLSR page, or a Setup page.

Are there any other neat-o "secret" pages?  hi,hi

thanks, 73, bob

Good plan, Vance.  Yep, I use my Linksys the same way.   Andre 

Hi,

Having just bricked my WRT54G by trying to solder an SD card onto it and not being able to currently justify the expense of any ubiquiti kit, I was looking at my spares box and wondering if I could make use of the 2x tp-link TL-WR841ND's I have sat here doing nothing.

They both currently have Openwrt running on them and I did manage to get OSLR running on a x86 openwrt install in a VM and have it join a mesh so not completely new to openwrt hacking.

Is it a big job to adapt the current firmware for a different hardware platform?

Cheers

Jon

Hello All,

I am very new to this,

I wanted to know if it was possible to link 2 HAM repeaters on 2 different mountian tops together using MESH ?

any help would be apperchaited, and where is the spell check icon above ?

Thanks