Process of elimination:

1) Move the MAP node to another channel (while staying in band for our licensing).  To have clear freq separation move up to ch 11 under part 15 normal wifi licensing and revert back to factory linksys image.   (Shouldn't have any effect in your test given there's no mesh RF traffic in your setup to compete, but for expanded use...)

2) The linksys are flaky with combined usage of ports for both DtD and devices that can be plugged into any given LAN port.  Since Linksys factory images don't combine vlan tags on the same external port, we can't be assured this will ever work robustly.  To eliminate this as a problem, you can edit a couple of files (you or friend know ssh and vi?):

Find these configuration files and edit the sections to look like (or similiar to this).  Different versions of linksys have different port mappings (and becareful as some have internal port 1 labeled as port 4 external).  Openwrt website gives the details.  This example turns port '1' internal to be the DtD only port.   vlan2 (or tag 2) is for DtD.  The "option auto no" line is commented out and is only a change to do in the recently uploaded 3.0.0 image to turn DtD on.

/etc/vlan

----------------------------------

config switch eth0

option vlan0 "2 3 4 5*"

      option vlan1 "0 5"

      option vlan2  "1t 5t"

---------------------------------------

/etc/config.mesh/network

---------------------------------------

config interaface dtdlink

      option ifname "eth0.2"

      option proto static

      option ipaddr <ditdlink_ip>

      option netmask 255.0.0.0

#    option auto no

---------------------------------------------

************ in setup, save settings and reboot ****************

3) install 'wireshark' on the laptop and capture the packets to get an idea of the traffic.  Everything is going from correct source to destination IP addresses between all the nodes?  Nothing looks unusual?

HI everybody,

I have 3 Linksys WRT54GLs (all version 1.1).  Two are configured as mesh nodes (A and B), and the third is configured as a mesh access point (MAP).  The MAP has an ethernet cable connecting one of its LAN ports to a LAN port on mesh node A.  Mesh node B has an ethernet cable connecting one of its LAN ports to laptop B's ethernet port.  Finally, Laptop A makes a wireless connection to the MAP.  All 3 WRT54GLs are running on channel 1 with the same SSID.

I checked the mesh status on mesh nodes A and B and they see each other.  I saved the DHCP registration so that DNS will work for laptop A and B.  I can ping from laptop A to laptop B and back with no problems.  So, now I am trying to copy a small 3MB file from laptop A to laptop B via sftp.  Both laptops are running Andy's Ham Radio Linux (an Ubuntu 14.04 remix).

From laptop A: sftp user@laptopB
successfully makes the connection
put <some file>

The file transfer begins, but it takes 5-7 minutes for the file transfer to complete.  I expected it to complete in a few seconds.

Note that all 3 WRT54GLs and the two laptops are sitting in very close proximity on my kitchen table.  AFAIK, there is nothing else on wifi channel 1 in the area.  All antennas are pointing straight up.  I'm using this firmware:  bbhn-1.1.2-wrt54g-2.4-squashfs.bin

Do I perhaps have faulty hardware?  I tried moving the WRT54GLs further apart, to no avail.  I'm not sure what else to try.  Does anybody have any suggestions?

Thanks, and 73,

Andy
KB1OIQ

My Linksys router should arrive any time now, and I already downloaded the mesh firmware.

Should I connect one of its LAN ports to my existing router, or do I connect to another NIC on the PC so that the mesh is on its own IP network? If the mesh should have its own network, should I enable IP forwarding between the NICs or connect the Linksys's WAN port to my existing network (or neither)?

No worries,

We are very much attempting to embrace a more open development environment than had been seen with the group in the past so feedback, comments, suggestions, etc are welcomed.

i think you are reffering to this commit

http://olsr.org/git/?p=olsrd.git;a=commit;h=2beaac8b9b1b9eef09e312b165fe61e3fef99eda

Which is actually in the Quagga module only. Quagga is another routing daemon and we don't utilize it and we don't load the quagga module so if this is the one you mean it should not be related.  If it's a different unrelated commit than honestly I haven't seen it and would love the pointer as i would certainly consider it relevant.

Hi-

Trying to get IRC working.  Any help would be much appreciated.  We believe that the node has successfully installed the server software.

 We are using Pidgin client software.   This client software is asking for basic setup.  First box is a Protocol box which we selected IRC.    

Second Box is "User Name"   What goes here?  My call sign I would presume.

Third Box is "password"    What goes here?   I would presume the node password.?? 

another way is an advanced tab  option while selecting IRC. 

Port 6667 is entered

Encoding  UTF-8

Ident name is empty

Real name is empty

the three remaining boxes having to do with encription are unchecked.

"just 2 olsr restarts reported"

thats excessive on it's own, so maybe more useable but goes to show something much more than OLSR secure was at work, just enough of a solution to let things run but FAR from a fix...

Correct,

Due to the issues with the onboard switch on Linksys devices DTDLink ships in a disabled state in the 3.0.0 beta build.

Please see http://ubnt.hsmm-mesh.org/products/BBHN/wiki/HowTo/Enable%20DTDLINK%20on%20Linksys for the current procedure to enable DTDLINK on Linksys

What is the node count on your mesh? Ideally send the olsr-topology-view image.

http://www.broadband-hamnet.org/download/firmware/olsr-topology-view

ae6xe@cox.net

How did you tell the other nodes to query you for the time?

I have a linux box on the air, people can ssh/http to the box ok. I know how to setup ntpd (have done it many times before) but how do you advertise the service for other nodes to discover it?

Are you stating it is a: Mesh Gateway [x]

but it really isn't hanging off the internet??

I am ready to announce today that I have had success creating a stratum-1 server supplying time to a none internet connected mesh. In a nut shell,

A GPS unit was installed on a Raspberry Pi taking a time signal from the stratum-0 satalites' signals.

Then the computer was set up to become an NTP server.

Then a DHCP server was install on the same computer to provide an address to the WAN port of the node.

Finally, a DNS server was also install on the same computer to create an address reference from the US pool servers to the Raspberry Pi.

Plugging the computer into the WAN port and being patient while each node makes a query to the gateway, they will set their clocks to the GPS time. This also works on the Ubiqitie's through a Linksys node.

It works and has been tested in the field.