FYI... a "wierd" workaround for the vtun_up command not executing on Linksys...

in /etc/hotplug.d/net/13-vtun

change this:

....

# Handles setting up rules for tunnel interfaces               
#echo "Interface is $INTERFACE $ACTION" >> /tmp/vtundscript.log
ISVPN=false

...

TO THIS

...

# Handles setting up rules for tunnel interfaces               
#echo "Interface is $INTERFACE $ACTION" >> /tmp/vtundscript.log
echo "BUG WORKAROUND IN HOTPLUG.  DO NOT REMOVE THIS LINE" >> /dev/null
ISVPN=false

...

Sure:

I have placed a copy of the archive on Dropbox.

The archive includes the original perl script and css stylesheet as well as my modified versions.  The original README is also included.  I was going to add notification for when someone leaves the chat. But, in the end I decided the code was really only good for very light usage, or demonstrations. The basic problem is with the refresh mechanism. In HamChat this is accomplished by continuously reloading the web page. This is not too bad if you are in a chat, but when the chat window is in the background, I found it distracting.

In any case, UYMMV, so good luck. I will be glad to try and answer any questions.

Richard -- wb6tae

Richard (Richard WB6TAE), since you asked if there was any interest, I'd really like a copy of your modified HamChat script if you could either post a link or email to me at nhbfc(at)metrocast.net

Thanks,

Allan KB1TKM

I have the connection working...

I changed to client setup to point to the lan ip addrees of the server. the connection was made.

I changed the  srtup back to the dyndns setup and things still seem to be working... go figure

OK,

just for the fun of it, here goes....

NS5 connected to Comcast router as tunnel server loaded and enabled

node sees internet and has a lan address xx.xx.xx.20. port forwarded 5525 on Comcast router to this address.

attached laptops can access both the node and the internet.

Linksys GS V2 loaded with 3.01 connected to the Comcast router and tunnel client enabled

node sees internet and has a lan address of xx.xx.xx.40.

attached laptop can access both node and internet

both nodes list default gateway as xx.xx.xx.1

I can ping the dyndns address used to connect the two nodes. have checked rererecheck ip address and password for tunnel setup.

issued vtun_up tun0 up on the Linksys gsv2 got the expected response.

there are 5 other local 2.4 GHz nodes seen by the Linksys node.

the ns5 see the other 5GHz node in the mix

not sure how to test further, any suggestions are appreciated.

73 de mike

This may be the lack of FQDN that affects chatzilla or may be the link just doesn't match what the application wants .

you may just want to configure  the app manually most have fields for server name  port number etc, links are but I can see how you would want the link to work, in that case contact the program support and ask them how irc:// links need to look for their application.

I have tried about six of them from app store and download from web and they all seem to say the same thing.

syntax error, wrong link, ect

Looks like they may add the :6667   to the end of the add line.

I did remove the port # from the set up and it will not let me, said it has to be in the set up.

Daryll kg9nd

Bill, you may try reading this thread as it covers several methods...

http://www.broadband-hamnet.org/hsmm-mesh-forums/view-postlist/forum-3-

firmware/topic-1088-112-load-filed-how-to-recover-bricked-router.html

Haven't had the misfortune to try any of them yet despite several screwups that scared me into thinking I was going to have to!

Allan KB1TKM

I got same thing,  i flashed firmware with hardware setup:   laptop-24vpoe-m2hp.  no router.

Firmware updated with tftp, worked good. 1982.168.1.1:8080 took me straight into status page and setup.

I tried to save the new node name and password, got the "restart in 60 seconds" page,  then nothing.

Nothing works, hostmode, localhost  192.168.1.1:8080 or 192.168.1.20:8080   ---all inop.  ping wont work to the router either. the lights are on, but no connections.

i pushed button and held for 20 sec while turning on power, lights in disco mode, re-flashed firmware, all went well again, unill I save the node name/password, then again, no connections can be made to the M2.

Do i need a router or switch between the laptop and m2?

What 10.x.x.x address should i be looking for?

IRC is a standard protocol (read as: everyone who wants to can and does support it)

Check the App Store for "IRC Client".   AndroidIRC is pretty popular on a lot of the non mesh servers I am on but there are likely hundreds of other apps.

Howdy

I have the irc installed in node. Chatzilla working. I have a d-link set up as a wireless access point.

Has anyone found a chat app that will work with android phone and the irc node server?

Firefox on phone, yes   chatzilla add on said not compatible.

Daryll kg9nd

The main issue standing in the way of tunneling out of my bridge router - the WAN port cannot be disabled...  Food for thought!  :)  The tunnel router needs to talk to the internet through the WAN port, not a LAN port!

Bill - N5MBM

Hi AE6XE,

Sure, no problem. We´re open to all kinds of cooperation over the borders.

Just drop me a mail: sm7i.ham(at)gmail.com and we´ll look into this.

It works!  It works!!  It works!!!

With the help of K5DLQ I got the tunneling to work!

But in order to do it, I had to add another router onto the stack in the shack.  We set it up as JUST the tunneling node with no other duties.  And N5MBM-3-TUNSERVER was born. see for yourself at http://www.n5mbm.net:8085

The node is setup as a 5 node host with DHCP enabled and a static address on the 192. home network on the WAN interface with that interface plugged into the main home internet router.  In this config, tunneling works.

We originally tried it on my N5MBM-3-Bridge node but since it was setup as NAT to allow all my 192. network devices the chance at being advertised services.  It didn't want to tunnel anywhere.  And it is evident that being setup as NAT the tunneling just didn't want to work.

Now I am going to add ANOTHER router onto the heap (N5MBM-3-TUNCLIENT) so I can run the client software to enable me to be more flexible about people connecting to me and vice-versa.  One for Tunnel Client.  One for Tunnel server.  One as a NAT bridge to advertise my local network services and one as my internet gateway.

So that makes 4 linksys routers, stacked on top of each other, just to interface with the internet, my home servers, my local network and the mesh.  Kind of clumsy, perhaps a little "kludgey" but it works!

Many thanks for all the help getting it up and running.  The first time I saw my status page proliferated with Waco nodes, I became ecstatic!

Bill - n5mbm

www.n5mbm.net

I get the following message after executing that command

      Firewall rules for tun0 up
      iptables: No chain/target/match by that name
      Adding vtun firewall rules...

I am now able to connect from the client node to the server node but I cannot connect to the other nodes at the servers location.

I cannot physically get to the server location until tomorrow--do I need to issue a similar command on the server node?

It appears the command needs to be reissued after a node reboot.

KE6TIM, It appears that there is an issue on Linksys tunnel nodes.  (Possibly a OpenWRT Kamikaze issue, still researching)

Try this as a temporary fix:

ssh into the the tunnel client node (ssh -P2222 root@nodename)

type the following cmd:

vtun_up tun0 up

Then, try and access the remote nodes.

I just got it setup and am trying to do some testing with K5DLQ and can't get a connection either...

We can't get them connected...  Your setup looks right...  My setup looks right...  There's something simple we are both missing...

I am wondering if it is because I left the DTDlinking OFF after the last upgrade - I can't find the file that describes how to turn DTDlinking back on because it sort of mysteriously disappeared from the net, I keep getting "File not found" when I try to click on any link referencing it.  It makes me wonder if I NEED to turn it back on for it to work.

I am a little unclear as to why it was turned off - probably router looping problems?

I will be watching this thread!

Bill - N5MBM