Thanks KF5JIM, the problem is that the Win 10 unit is on the 10.0.0.1 network and the router is on the 192.168.1.1 network. I'm going to leave it be for now. I'm building a Linux machine and I will be able to get it set up then. 73, Jim

If you are working in x-host DMZ, then you need not forward ports on the BBHN nodes. However, if your node is set to NAT mode, then you must forward the needed ports on the BBHN node the Raspberry Pi is plugged into. You do not need to enable mesh services unless you want the service advertised (clickable) to allow users to access it via a web browser.

The main problem I see is that you have another Echolink node on your home LAN is that you are forwarding ports to that particular Echolink node too. If a packet were to arrive at your home's IP Address, your router will not be able to know which of the two internal IP addresses it should be forward the information to.

Because of that, try disconnecting the Echolink node on your home network. Plug the one sitting on your mesh network in to the same BBHN node as the one advertizing internet onto the mesh. Forward UDP/5198-5199 and TCP/5200 to that particular node from your home network. And try again. If that works, then try moving the Mesh Eholink node out to another node.

Hope this helps!

Hi All,

I have a 70cm repeater at a remote site running OpenRepeater on a raspberry Pi. The Pi has Echolink enabled and the network back to the internet gateway is via HamNet nodes on WRT54's.

The topology is made up of 3 nodes as follows:

1 node at the repeater site, 1 node at my QTH (link) and finally a node connected to my PC.

Internet services are connected to the QTH link node and is available across the mesh. Another Echolink node sits on my home LAN and works, so I know port forwarding is ok through my home network router.

I have added port forwarding for TCP/UDP 5198-5200 on all of the nodes but to date I have had no success in getting it working.

Has anyone in Hamnet land got Echolink running on the mesh and if so what are your settings?

Do I need to enable mesh services at the repeater end and or can the localnode setting be used on one or more of the nodes?

Kind regards

Maarten

VK6MP

What you'll have to do is put the router in fail-safe mode which allows you to telnet into the router. You can find those instructions here: http://www.broadband-hamnet.org/documentation/71-using-safe-mode-to-reset-a-forgotten-password.html. Instead of typing setpasswd abc, type cat /etc/httpd.conf to see your old password. You can then exit, reboot the node and type in the password you just recovered.

As to manually setting your own IP Address and Netmask, you'll need to right click on the start menu, go to Control Panel, click on Network and Internet, click on View Network Status and Tasks, Edit Adapter Settings (on the left), right click your network adapter and go to properties, highlight Internet Protocol Version 4 (TCP/IPv4) and click on properties. Fill in the information you need and "Ok" your way back out of everything.

I hope this helps you out!

I'm trying to get on the same network as my router (WRT54GL V1.1 modified)so I can telnet to it. Thanks, & 73, Jim

Edit: Maybe it would be better to put the router on the same network as my PC, so how do I do that?

The main problem is that I need to give it a new password so I can logon and modify.

Ladies and Gents

Following a presentation on BBHN hosted by Crawley Amateur Radio Club on the south coast of the UK this weekend past, I am keen to try and expand the UK interest in MESH networking.

As part of this I am attempting to establish a link to our club house which is within a historic Victorian hillfort upon the coastline of Portsmouth UK, Fort Purbrook.

One of the key "selling" points to other amateurs would be to show the services which can be provided on a MESH including the tunnel feature to MESH's in other countries and continents.

As such I am keen to identify anyone who would grant a tunnel client hosted by myself connectivity to their tunnel server.

Could anyone who is able to assist me with this request or able direct me to someone who can contact me via the forum or directly?

Many thanks in advance

John / M0XXF 

You don't even need to run the program previously mentioned. Just downgrade the firmware to any AirOS v5.5.x version first.

I figured it out. I had to put in 3 localnet commands into the Asterisk file I previously mentioned. I entered the LAN address of each of the 3 nodes and now it is working perfectly from all 3 nodes.

I have 3 Linksys nodes setup in my house. I can connect my laptop to node 1 OR node 2 and everything works fine. I can place calls using the softphone software on the laptop. If I connect the laptop to node 3, the call lasts about 5 seconds and then it hangs up. During the 5 seconds you can talk to the other extension just fine. I'm calling an HT701 ATA.

What could be going on with node 3? It's a WRT54G V 3.1.

Mike N9MS

The Miami Valley Mesh Alliance will host a Mesh Networks booth located in the north-east corner of East Hall, behind the Luso Tower display (booth EH659).  Our booth area will include a large table and chairs that can be used for meetings, informal discussions, etc.  The booth area can also serve as a "home base" for meshers, to include a (real paper) bulletin board for messaging.  All mesh people are welcome to use these facilities.  Likewise, all meshers are invited to take a shift staffing the Mesh Networks booth if they desire.

Hamvention mesh access on Channel +1 at 20 MHz bandwidth will be available in the East Hall.  No 5.8 GHz coverage is planned.

All other nodes will be operating on Channel -2 at 10 MHz bandwidth.  Outside omni-directional nodes will be located on the tower on the south side of East Hall, on a tower close to the Arena (west end of the complex), and on the DARA Van mast.  We expect these nodes to cover the Flea Market and adjacent parking areas well.  Inside coverage will include the East Hall, Food Court, and the BallArena (including the ARRL area). Directional client nodes (NanoStations) with telephones will be located at the Flea Market office, the on-grounds trailer park at the east end of the complex, the DARA Booth, Inside Exhibits office, and a few other locations.  High resolution PTZ cameras will be mounted on the East Hall and Arena towers, providing a view of the Flea Market and adjacent parking areas.  If all comes together well, the mesh will also host a WinLink post office, and a HackRF receiver controlled by SDR-Radio/SDR Console software.

The mesh will host a Tunnel Server with limited access; please contact the undersigned if you wish to arrange a tunnel connection.

Hamvention Mesh Services will be advertised at the "Hamvention Mesh Info" ftp link on the mesh.  Additional information will be available at the Mesh Networks booth.

We welcome all to join us, on the mesh, or at the booth!

Bill Curtice WA8APB

Miami Valley Mesh Alliance

mvma@roadrunner.com

I figured it out -- actually I found a similar problem on Stack Exchange and there was an answer to a similar problem and  that fixed my problem.

The answer was to check the file /etc/asterisk/sip_nat.conf and be sure it was set like:
localnet=192.168.1.0/255.255.255.0

Well that is wrong for the Mesh but my file contained absolutely nothing -- it was blank.

I opened up the file and put in:
localnet=10.64.68.2/255.255.255.248

I then rebooted the system and now it WORKS!! I'm getting voice over my Raspberry PI/FreePBX system!!

I don't understand how Asterisk could ring the phones but not complete the call but this seems to be an important file that in my case needed to be updated.'

Mike N9MS

I forgot to mention that FreePBX was working great on my home network. The phones stopped talking to each other when I connected to the Mesh network. 

I followed the instructions on the video by KF5JIM. The phones can call each other and the phones ring BUT you can't talk. I get a hangup. 

Here is a portion of the Asterisk log with the error. Any idea how I can correct this? I read the wiki page but I'm not sure what I should do next.

I was interested in trying to make a IRC server for my node, but it looked like too much work. I started to consider a TinyMUX game server instead. I might still end up doing that too. But since then I found a good walkthrough for setting up a IRC server. It is at https://www.howtoforge.com/tutorial/how-to-build-your-own-irc-server-with-inspircd-and-anope/

You will need to be familiar with Linux or another Unix-like operating system to follow it.

If you prefer Debian, there is a package for the server in stable and for anope in backports. Both packages are available for armhf, so, if you prefer, it should be possible to run the server on a Raspberry Pi instead of a PC or Mac.

The server supports encryption. Be careful that you keep encryption disabled.

Read through these posts:

http://www.broadband-hamnet.org/hsmm-mesh-forums/view-postlist/forum-3-firmware/topic-1670-i-forgot-the-setup-password-how-to.html  (Note: video link doesn't work anymore)

http://www.broadband-hamnet.org/hsmm-mesh-forums/view-postlist/forum-5-problems-a-answers/topic-1683-hsmm-linksys-unknown-password.html

Basically, both these links (and the removed video) followed the instructions found under User Documentation -> Page 2 -> 23. Using Failsafe Mode to reset a forgotten password:  http://www.broadband-hamnet.org/documentation/71-using-safe-mode-to-reset-a-forgotten-password.html

Follow these instructions (23. Using...).  Diverge where it states to type "setpasswd abc" and instead type "cat /etc/httpd.conf"  This will allow you to see your old password.  Finish the instructions and login with the password you just rediscovered.