Comedic title aside, I had three well functioning nodes running as a small tribe and was cleaning up some options one node at a time remotely. I had tested services, hamchat, remote cameras, wan access, meshing and unmeshing and everything worked just fine. I thought I had turned off the DHCP switch on two of the nodes, leaving the third one on but in my zeal I turned all three off and rebooted them all. Now I have three nodes that seem quite content to talk to each other but not me.

I can turn them on and off via power and from past behavior of the led's the nodes seem to find each other and chat away happily ( probably laughing at me I suspect ) but I can no longer connect to any of them. Only one had WAN enabled and it was static... though I can't get it to respond any more. I can even connect two wifi computers to each other via the Mesh wifi network itself but that's it but I can't access the mesh itself via a non-mesh computer. I'm assuming that's a good thing and if so it works well here.

All three nodes ignore my pleas via an IP spider that runs for hours scanning the LAN and WAN ports but so far has not found the current address of these three runaways. And since the addresses span multiple subnets and are derived from the Mac addresses, which I also cannot see, the time it takes to scan possibilities across multiple subnets is like watching paint dry. And as productive.

So, while I wait for yet another node to arrive from eBay to use to get back into the Mesh network... does anyone have any other ideas?  They are all WRT54G V2 models, running 3.1.0 and Hamchat 0.1 in 5 host mode.

Thanks in advance and I don't mind if anyone sniggers.

It seem's IPlvl4 pings are blocked on Comcast, but IPlvl6 pings go through no problem. 

Is there a way to use IPlvl6 with BBHN??

Thanks for the report.  No problem, just something I noticed. 

73, Bob

Here is a picture of my vtun client/server hardware using Linksys routers:

http://s1238.photobucket.com/user/ve3rrd/media/Broadband-Hamnet/VTUN%20at%20VE3RRD.jpg.html?sort=3&o=0

Both routers are Rogers WRT54G-RG Linksys (same as WRT54GS). The bottom unit is the vtun client currently only connected to K5DLQ's server, the other is the vtun server which connects to several local client nodes. The two switches are cheap Dynex units, the lower one feeds internet to both nodes from one port of my ISP modem/router. The upper switch enables DTDLink communications between the vtun nodes rather than have all the data on the RF link.

I have DHCP disabled on the vtun client node, DHCP is handled by the vtun server node.

I notice that the links have gone AWOL on the google map mesh nodes ?

Is this correct?

thanks, Bob VE3CWU

Well it all works great, except every time I reboot any of the routers, I have to Manually put the routing rules back in. 

WHERE in NVRAM or JFFS2 can I put the router rules so that they apply automatically at boot time???

Thanks!

Darryl K5DLQ pointed me in the right direction, this is from one of his previous posts about this problem:

Cannot reach remote nodes across the tunnel

 A defect in the hotplug subsystem on Linksys hardware will cause errors when trying to connect to nodes across the tunnel.

The workaround is to insert the line below IN BOLD into the following file:   /etc/hotplug.d/net/13-vtun

====================== TOP OF THE FILE ==============

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

Echo “BUG WORKAROUND IN HOTPLUG ON LINKSYS” >> /dev/null
ISVPN=false
case "$INTERFACE" in
tunl0)
ISVPN=false;

......

===== REMAINDER OF THE FILE =========

Without this line, the firewall rules are not executing properly.

After adding this line to both my tunnel nodes (using WinSCP) and rebooting, I am now able to connect to the far end node from my vtun server and even log into it to make changes.

Not at all as other people have had success. Furthermore, if you compare the configs that claim that they are for the 7960, they are infact the same ones as the 7940 configs. If you want, try adding the remaining four lines (ie. line3_name and et. al., line4_name and et. al., etc.).

Here are some other ideas for you to try out:

• What program are you using to change edit the configs? (could be a different character encoding scheme)
• Go here, and let me know if you are on SCCP, SIP, or MGCP.
• Verify that the TFTP settings on the phone are correct.
• Verify that the phone is indeed connecting to the TFTP server. Login to the TFTP device and check the log files. Also, change the value for line1_shortname to something else and see if changes the display name accordingly.
• Try not using a TFTP server and manually change the settings on the phone. (the Asterisk-on-a-Pi video shows a 7940 at the end. Behind the scenes: That was done manually through the phone and not via TFTP. Somehow I got the settings right for it to work.
• Here is a gold mine of Cisco SIP information: http://www.jtech.net/ip_phone_pages.aspx. Hopefully this can provide some pointers help you out.

Let me know how it goes.

Has anyone come up with a solution to the following limitation: I have a VTUN server which is connected to two other ham's VTUN clients (all nodes are WRT54GS with bbhn-3.1.0 and the latest vtun software install).  

If I am plugged directly into a LAN port of my tunnel server and I try to connect to one of the tunnel clients, the message on the screen says "Redirecting to Status Page" and the browser says it is connecting which looks normal, but after a while it times out with "This webpage is not available".

But if I plug my laptop into another bbhn node that I have (another WRT54GS with bbhn-3.1.0) and try the same thing (clicking on one of the tunnel nodes that appears under Remote Nodes), the connection is successful and I can even log into the remote node and make changes.

So the question is, why does it only work if I am using another node which is connected via RF to the vtun server node; and not when I am directly plugged into the vtun server node?

I have a tunnel working using a Verizon jetpack as the WAN.

My configuration:

(1) Verizon Jetpack (IP default 192.168.1.x

(2) Cradlepoint 1200B router setup to use WIFI as WAN, with LAN IP set to 192.268.0.x

(3) Netgear GS105EV2 switch configure as VLAN:

(4) NS2 LOCO v3 node with client configured per documentation (IP direct 5 10.x.x.x)

Server

(1) Comcast router (10.x.x.x)

(2) NS5 v3 with server configured per documentation (IP direct 5 10.0.0.0)

(3) Netgear GS108T configured as VLAN

This is working for me, I hve not tried using a Linksys with it yet.

hope this helps.

73 de mike

I see exactly what the problem is.  You did nothing wrong.  I made typographic errors in the first zip file.  Use this link instead (http://www.broadband-hamnet.org/download/7940/NG5V-Cisco-11-12-2014.zip). I'll see about getting the link below the video updated.

I am finally getting around to configuring the phones, after everything loads line 1 shows up as a00a instead of what I called it in the config.

Line 1 Registration Information
line1_name: “3000”                        ; Extension number
line1_authname: “3000”                    ; Extension number
line1_shortname: “3000”                    ; Name that appears on the screen
line1_password: “Password”       

I left the line 2 entries blank.

Any ideas where I might be going wrong?

Thanks