Hi all,

In hope that anyone can shine a light on my problem, I post my findings here.

I´ve set up 4 (four) WRT54GL routers with HSMM-MESH firmware. All routers are v.1.1 and has been serving as regular routers before so I know they are OK from a HW and radio perspective.

THe issue I have is that the mesh seems unconditionally unstable. Some router cannot see the mesh at all, others can hook up with another mesh for a short while and then loose the connection resulting in that the neighboring node just sits in the list of previous neighbors forever.

I´ve tried to manually synchronize the time and date of the units, but with no success so apparantly the time and date is not cruicial for the function.

One of the routers is a gateway node and connected to internet using WAN port, the others are just loose nodes without any wired connections.

Has anyone else experienced this and have a solution to the problem ?

I also should mention that the nodes are spread out in my house so the range is absolutely no issue here.

I just wanted to say thanks for the awesome chat room! (and to others who donated additional info for this app.) I am trying encourage others to make a mesh in my area and this provides a quick high value addition to spur interest.

Jim

Hi all, Just want to tell you that I successfully installed IP-GRE for IPtunnel on my WRT54GL 1.1 which makes it possible to establish a more versatile VPN between two devices.


I did modify the /etc/ipkg.conf with the following (commenting out the hsmm-mesh packages temporarily)


src release http://hsmm-mesh.org/download/kamikaze/7.09/brcm-2.4/packages
#src packages http://hsmm-mesh.org/download/kamikaze/7.09/packages/mipsel
src packages http://downloads.openwrt.org/whiterussian/packages
dest root /
dest ram /tmp

Issued: ipkg update


Then I simply installed the kmod-gre by issuing: ipkg install kmod-gre


After that I issued: insmod ip_gre


To be sure it all holds up I rebooted at this point


Then I issued (for test purposes): iptunnel add gre1 mode gre local 10.42.43.224 remote 192.168.10.1 ttl 225


Please note that the IP adresses seen above should be the ones on the WAN sides....


After this we can verify that the new interface exists by issuing just: iptunnel


Now we need to assign IP addresses to our new GRE interface like so:

ifconfig gre1 10.10.10.2/24
ifconfig gre1 up
ifconfig gre1 multicast
ifconfig gre1 pointopoint 10.10.10.1
 

Now we just have to issue some route statements that specify what network we want to connect to and that the new GRE interface should be used.


route add -net 172.27.1.0/24 gw 10.10.10.1 dev gre1


Ofcourse, don´t forget to configure both ends :)

I'm not sure you really want to do a 30/30/30 reset. 

However, there is a description of how to do it here: http://www.dd-wrt.com/wiki/index.php/Hard_reset_or_30/30/30

BTW, there's a LOT of info on WRT-54G on the DD-WRT and Open WRT project web pages.  Also the Wikipedia WRT-54 page is pretty good, too.

What do you mean by "vx55?" 

The WRT-54GL routers have the same 16/4 MB memory as all the other mesh compatible WRT-54 routers.  The current tunnel code doesn't fit in 16/4 MB.  Only the WRT-54GS versions 1 through 3 have the higher 32/8 MB memory and can hold the tunnel code.

It might be possible to optimize and recompile the software to get the tunnel code to run on a standard 16/4 MB WRT-54GL router.  As always, we suffer from too many projects, not enough manpower.

It occurs to me that the tunneling node doesn't need to be a router or even have a wireless interface.   Something like a Raspberry Pi could easily run tunneling software if someone ported it to the Pi.

For those who don't already know, the current tunneling software won't run on the standard WRT-54G because it needs more memory.  You have to have a router such as one of the WRT-54GS versions 1-3 with more memory.

I had a feeling that would probably be the case because of the fact that you have to specify where DUNDi is supposed to look for the other Asterisk server. If you could make Asterisk announce to the mesh that it has Asterisk+DUNDi installed (maybe by scanning the Mesh Status page for "Asterisk+DUNDi" as a service), you could write a script that looks for that announcement, gets the needed information (MAC and IP Address) from that HSMM-MESH node and adds it to and reloads the Asterisk+DUNDi configuration and extension files.

That sounds like a solution that could work!