In looking over what is happening and what is wanted, Im thinking if you crank down the subnet on the mesh node WAN/route to only allow ONE IP might give what you want easily.

Try changing 255.255.255.0 to 255.255.255.254 on the node's WAN subnet mask and/or in the static route .

KTF

Owncloud is decent, but, haven't played with the sync capabilities.

Also, this looks promising:   http://sourceforge.net/projects/freefilesync/

My setup is a Cisco router with sub interfaces to use my set of VLANs on a Cisco switch.  In this case VLAN 1 is the mesh WAN VLAN and my local LAN is a totally different VLAN and network. That way I can setup INBOUND and OUTBOUND Access control list on the  MESH VLAN and Network  to block access to and from the mesh, Internet and local lan.  The mesh has its own wan network on the router and certain access to the internet and not local LAN.  I have run into the same issues going from the LAN to the mesh. I never got into the firewall on the node yet. I can see having it there as not everyone is savvy enough to setup firewalls outside of the nodes. But there should be instructions as to how to remove, disable or bypass them as needed. Mike AE4ML

I'm sorry, but let us be respectful of people who still use Linksys devices. Linksys routers still have their place and their hardware is no "real-er" than Ubiquiti hardware. Sure Linksys hardware has some limitations over Ubiquiti's, but Linksys nodes are still a great tool for those to use who are interested in learning about mesh networking.

KK4DUW, whatever supported platform you use, we are always happy to help you out!

BTW, glad to see you move to *real* hardware and away from the dark side (LS).  ;-)

I think you will be pleasantly surprised with the Ubiquiti gear.

I've setup 2 of the Linksys routers, so I figured I'd try my hand on a Ubiquiti Bullet M2.  I'm following the instructions on https://www.youtube.com/watch?v=Dz3VOvhforg

I successfully flashed the new firmware (bbhn-3.1.0-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin) into the unit and change my network setting back to automatically obtain an IP.  But I get a timeout when trying to go to localnode:8080.

Any ideas where I'm going wrong with this one?

Hi All,

There's a small group of hams near me that are interested in mesh networking. I'm trying to do what I can to make things happen.

One application we are looking for is the ability to sync a folder over the mesh network. I know there's rsync, but since I've never used it, I wanted to ask some questions. To start off with, let me try to explain the setup we're aiming for. Several of us would like to setup Raspberry Pi file servers and have the contents of (/share) folder synced between nodes. Unfortunately, there is no RF links, nor tunnel links between these nodes while we are all at our QTH's. We do meet up once-in-a-while for breakfast, tech discussions & such and would like it if the nodes in our vehicles, once they see each other, would automatically start to sync the data.

We each add files to the folder under our own subfolder (eg, /share/george, /share/matt etc) and will likely have another RPi file server at our QTH. We just need to figure out the best way to sync the data when links are available.

Questions: Is there a way to setup rSync so that it will sync once a rf link is present? How would that be done? The only way I know of (again, with little to no knowledge of rSync) is to setup a cronjob to sync the files every 5 minutes or so. The task will simply fail if no link is present (I think). Furthermore, if we do setup a tunnel between nodes, or if an RF link is present for several hours/days, we'd only need to sync these files (likely) no more than once a day.

Any suggestions are greatly appreciated.

73

Matt KD2HKB