Greetings all!

I saw the article on QRZ.com and registered.  This was very informative and shows that the developers have all done a great deal of work to make this so much more than I've seen in the past.

I hope to have at least 3 WRTs up and going soon. 1 at a high repeater site and 1 each in mobile and portable service.  If I understood the rules correctly there was to be no foriegn traffic on these.  Would that include any DX stations over Echolink?  I want to be able to use this to route Echolink to a high repeater site from a site we use now about 6 miles away that has good line of site.  We are now doing this on 440 but we want to put the 440 repeater on the tower as well and move data this way.  Is this within the rules?

BTW to the person that asked for the GPS logging there is a way to do it now.  Fire up Netstumbler and sort what you find by SSID.  It works great with most GPS RX.  I do look forward to seeing it in the firmware though. 

Ronny Julian

K4RJJ

Dallas GA

I agree.  While I was watching the webinar I ordered a WRT54G v2 on EBay for $25 including shipping.  It arrived Tuesday and installing he new firmware was a snap.

I want to set this up with my AMPR.ORG IP address.  Has anyone else done this?  How to route the traffic to and from this IP to my normal Internet?

Also, is there a place to watch the video from the webinar again?  I think it's a must-see for folks getting into this and you really make it easy.  The PDF slides are great too!

73!

Jack, K6JEB

(HEY DAVE... Here I go down that rabbit hole :-) )

I have my 1 node normally on my LAN (its offline at this very moment), behind my regular D-Link router. The trick is, you have to change the LAN on the node FROM the 172.27.0.1 to a static IP of your LAN (mine being in the 192.168.0.X subnet).

Then, DISABLE the WAN on the node, and then a GATEWAY box will appear under the LAN settings. If your LAN uses 10.0.0.X, you are in for some hurt and headaches. I actually changed my entire LAN over to 192.168.0.X to make this work.

THEN, for machines on your LAN that you want to talk to the node, you have to add it to the routing tables (be it *nix or Windoze).

Against Dave AD5OO's better judgement (he prefers I dont confuse anyone with this stuff) , I am working on a thorough document how to set this up to work.

There will be some things that still wont happen (like having that node be a gateway for the rest of the mesh, as ONLY that 1st node will be able to talk out through the other router to get to the internet, like to get firmware updates, etc).

Unless you have a major Cisco router and can program it better than the home type routers (which I dont).

As for the Webinar video, we are currently working on getting it edited and posted to the site here. Check back in a while. Ill make sure to update the NEWS banner on the main page when its up and running.

73

Jim K5KTF

Thanks for the explanation for bridging the two routers!

I've been hoping to create some buzz around this here at UC Berkeley's W6BB.  We've got some hams that are some real networking wizards so I think we'll get this figured-out.

Looking forward to showing some others what all the excitement is about.  :)

73!

Jack, K6JEB