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!

Hi there all,

I have a newly installed (this day in fact) HSMM node on a Linksys WRT54GL. Installation and first time configuration was a breeze. Probably the first node i southern Sweden....

Router rebooted and I logged on again from LAN side and checked that everything was OK and it was. I can even see other normal SSID´s in the neighborhood.

BUT, neither of my computers or other wireless devices, such as iphone or ipad, sees the SSID of the MESH. Tried to manually configure my Windows 7 to connect to HSMM-MESH, but nada....the SSID is not there....

Very strange problem. The radio in the Linksys is apparantly working or else I wouldn´t see other SSID´s...

Anyone else had this problem ? I´d be happy to hear from you :)

The Linksys WRT54GL is HW rev.1.1

73sss SM7I

AJ4TW -> I'm also not a huge fan of ActiveX, so it will be interesting to see how you are doing that, might have to get a few more details on that from you.

When you log in to the camera it gives you the option of using either IE, Firefox/Chrome or Mobile.  Here's some screenshots that might make it clearer.

AJ4TW -> I guess since they saw that we were racing at the race track near their house they assumed we were pro racing?

There's always someone wanting to be an "Amateur Observer" in every mode. 

OT - I run a high-level APRS Digi/IGate 250' on the University's tower and I've had ops running 4 hops and such I try to be nice and educate to the suggested paths, but if you were running the minimum path to get to an IGate (assuming you were wanting to be seen on the APRS-IS) at a standard smart beacon rate (no more than every 3 minutes when over 60mph) I'd consider you in line.  If you were beaconing more often than every 3 miles to get your tracking more granular on the maps, yeah, you could be considered a lid, but it would be for excessive beaconing and clogging the network, not because it was assumed you were using the Amateur bands for commercial use.  The safe bet in that situation is to not use the WIDEn-N path at all, that way the local infrastructure wouldn't react to you.  You could still monitor direct locally, and you could set up your own IGate to get your info to aprs.fi.   We used a path of CAVEn-N with WB4APR and his Mammouth Cave tests earlier this year.  You could use a path of RACE1-1 just as easily.