Mesh is up in Sac.  15dBi omni in the attic.  No services.  IRC setup next.  Meshers needed!

I have not found a discussion on the topic of changing the channel on an existing MESH node. It would seem that the channel can be changed through Setup and Rebooting the node. I have also seen a requirement to turn the node OFF for a period of time and re-powering the node.

I have followed these steps to change from the Default CH-1 to CH-3 as listed in Setup. The web page updates and shows the selected value but after Reboot it appears to remain on CH-1. I have attempted this process several times.

What am I missing? Is there any special requirement to change the node channel?

I will appreciate any feedback on this question as we are looking at using a channel other than the Default for dedicated directional links.

Thanks and 73,

Dave, WA7RYV

Works Great Easy to set up very small foot print. Time stamp would be nice.

73 Bob n7wwk

Setting Capture Page to work around WEP Like WIFI Hot Spot

Nodogsplash offers a simple way to provide restricted access to an internet connection. It is intended for use on wireless access points running OpenWRT (but may also work on other Linux-based devices).

Nodogsplash offers a solution to this problem: You want to provide controlled and reasonably secure public access to an internet connection; and while you want to require users to give some acknowledgment of the service you are providing, you don't need or want the complexity of user account names and passwords and maintaining a separate database-backed authentication server.

Does the hidden node problem apply to HSMM-MESH... As with standard 802.11?  Or do the routing characteristics tend to minimize these effects?

Andre, K6AH

After following the "Learn about OLSR" link and reading how OLSR works, I now realize that since routing is solely determined by link quality, hidden nodes will be factored into the quality calculation.

Hi Dave,

I have seen this on more than one occasion, and usually to fix it, I reboot either or both ends of the connection. Simple workaround for now.

Im going to bet its a bug in the older OLSR, which is responsible for the DNS resolution. Hopefully very soon we will be releasing an firmware update which will have the latest OLSR, and hopefully a bunch of bug fixes in the OLSR.

73

Jim

K5KTF

Dave,

Thanks for your response.  I missed your Taylorsville presentation in November but have embarked on putting together a Mesh station on my own.  Everything went together just fine and you can see from the attached file what it looks like.  The cat5 cable is routed down into the hamshack in the basement.  The building the antenna is on is my workshop.  I have several channel 1 routers in the neighborhood that are around -56 so they may cause me problems.  Also I cannot go directly East as the house is in the way.  May have to put the antenna up higher.  Anyway from the conversation I had last night on 145.45 net I may improve my chances with an amplifier.  I'll get out to the Bishops storehouse to see if they have any available, however, this weekend is stake conference and I have much to set up for the meetings in the A-V arena.  Are these external amplifiers or are they a chip replacement in the router?  Also what output ratings are available?

Dick   W7SAE

Attachments
 W7SAE-8.jpg [551 KB] :: HSMM-MESH Station

At various times and on different nodes, we have seen the IP for a MESH node appear in the Neighbors but the Node Name is never displayed. In most cases, the LQ is 90-100%. The node can be pinged, telnet, and direct connection to the node which then displays all node information. Eventhough some connectivity is available to the node, since the node name is not displayed, the node does not appear as a Neighbor, as a Remote Node and is not shown in the OSLR lists.

What is the criteria for the node name being displayed? Is this an indication of a system or connection problem?

This may be one of the mysteries of life but I will appreciate a better understanding of how this connection display works.

Thanks,

73, Dave

WA7RYV, Utah

K5KTF & KF7LJH,

Thanks for your input in fixing issues and expanding the asterisk guide. When I get back to my university (where my many HSMM-MESH nodes are located), I will try these out and update the guide accordingly. Thank you both for your support!

The symbolic link won't survive a reboot though and I need to figure out a way to recreate that link at startup.

The easiest thing you can do is edit the /etc/init.d/boot file and add a new line inside the brackets that reads: ln –s /usr/lib/asterisk/sounds /var/lib/asterisk/sounds

Perhaps I missed something on the firmware download page, but I have a "GL" model and only see firmware for G or GS?

What is the recommended firmware BIN file for the GL?

Thanks!

For KF5JIM and K5KTF, I wanted to let you guys know I got voicemail working. It’s pretty simple.

I’m assuming you’ve followed FF5JIM’s instructions and have that part working ok.

I’ve attached the two required binaries, download and copy them to the mesh node the same way you copied the asterisk files to the node.

Install the packages:

ipkg install asterisk16-sounds_1.6.1-rc1-1.1_mipsel.ipk

ipkg install asterisk16-voicemail_1.6.1-rc1-1.1_mipsel.ipk

Now edit /etc/asterisk/voicemail.conf and add the following lines to the bottom:

[hsmm-mesh]

1012 => 1111,1012,test@test.com,test@test.com,attach=no

1013 => 1111,1013,test@test.com,test@test.com,attach=no

And set the user context by changing the userscontext line:

userscontext=hsmm-mesh

I also changed a few of the defaults in that file to shorten the length of messages, the number of messages, etc. The config file is well documented.

Now edit /etc/asterisk/extentions.conf and add the lines to what you’ve already entered so it looks like this:

[hsmm-mesh]

exten => 1012,1,Dial(SIP/1012)

exten => 1012,n,VoiceMail(1012@hsmm-mesh,u)

exten => 1013,1,Dial(SIP/1013)

exten => 1013,n,Voicemail(1013@hsmm-mesh,u)

exten => 2000,1,Answer(500)

exten => 2000,n,VoiceMailMain(@hsmm-mesh)

So you are adding one new voicemail line for each extension, and one new extension (2000) you use to get into voicemail.

Now one last piece. The asterisk voicemail sounds package loads the sounds into /usr/lib/asterisk/sounds. But the voicemail package wants them in /var/lib/asterisk/sounds. If you move the base directory to /usr/ though the spool directory will move with it, and that’s no good from a space point of view. So I made a symbolic link –

ln –s /usr/lib/asterisk/sounds /var/lib/asterisk/sounds

You may need to recreate the /var/lib/asterisk directory first.

Now restart asterisk, get back into the console, and type “voicemail show” and you should see the new voicemail boxes defined.

If you dial the extension “2000” the lady says “mailbox” – she’s asking for the mailbox number you want to get VM for. Type in 1012. Then the password, in this case it’s 1111 (from the line in voicemail.conf). from there you can get messages, set up your custom greeting, etc.

This configuration keeps VM on the volatile filesystem, so VM will non survive a reboot. I think that's fine. The symbolic link won't survive a reboot though and I need to figure out a way to recreate that link at startup. I found this link helpful for figuring out the setup

Thanks again KF5JIM for you work on this – and thank you K5KTF for your work on HSMM-MESH!

KF7LJH

Attachments
 asterisk16-voicemail_1.6.1-rc1-1.1_mipsel.ipk.zip [562 KB] ::
 asterisk16-sounds_1.6.1-rc1-1.1_mipsel.ipk.zip [1014 KB] ::

Just got an HSSM-Mesh station up and running.  Location:  4930 South Woodhaven Dr. (1365 West) in Taylorsville.    Have TP-Link grid parabolic antenna (24 dBi) up about 15 feet.  It is vertically polarized.  Find plenty of routers around the neighborhood but no MESH activity.  Directions aimed:  West, SW, South, NW, North, NE.  Nothing yet.

Dick W7SAE

I just wanted to say thanks for the awesome writeup! You made the setup simple, took me about 15 min. 

While I don't have any other mesh-nodes connected, I figured I'd try to establish a connection with a ham friend who has a hardware voip phone, but we'd do it over the internet. With some natting on our home firewalls it worked - I called his ext from a sip client on my smartphone and we had great voice quality. All from the mesh router. Very cool.

I was going to put Asterisk on my HSMM-MESH RaspberryPi file/web/aprs server, but why bother, this works great. 

Thanks for taking the time to do the write up and provide the packages.

73 KF7LJH

I just wanted to say thanks for the awesome writeup! You made the setup simple, took me about 15 min. 

While I don't have any other mesh-nodes connected, I figured I'd try to establish a connection with a ham friend who has a hardware voip phone, but we'd do it over the internet. With some natting on our home firewalls it worked - I called his ext from a sip client on my smartphone and we had great voice quality. All from the mesh router. Very cool.

I was going to put Asterisk on my HSMM-MESH RaspberryPi file/web/aprs server, but why bother, this works great. 

Thanks for taking the time to do the write up and provide the packages.

73 KF7LJH

Jerry  W0HU......would you please contact me.   I'm looking for a person that could come and give a demo of HSMM-MESH at one of our next live net meetings.   The City of Cottonwood Heights has an emergency system in place that will aid the city in the time of an emergency.   We are now in the process of getting D-Star set up to report our CERT conditions in the neighborhoods.   Several of us are also interested in the MESH possibilities.  Let me know if that is possible or if you would rather just suggest someone else to us to contact.

If anyone else on the board can help let me know.

Ron

KC7WVS

I've been (slowly) working on a temperature/voltage sensor based on the Dallas DS2438 IC.  The DS2438 is a battery management IC that can read voltage as well as temperature; that way you could also monitor the voltage present at the router.

Using the digitemp software package, which is compiled for the WRT routers already, it should be fairly easy to put the voltage and temperature readings on one of the status webpages, even keep a log of the internal temperature of the case at a regular interval.

Eventually the plan is to have a PCB spun that plugs directly into the TTL-RS232 header of the WRT54 routers and incorporates the one-wire interface and DS2438 IC all on one daughtercard.

http://datasheets.maximintegrated.com/en/ds/DS2438.pdf

http://www.digitemp.com/

http://www.lecad.fs.uni-lj.si/~leon/other/wlan/wrt54ow/