Hey all, just discovered this recently, thanks Dallas (HNX) for addicting me to more in the hobby. My node is up no working on building a biquad to re-purpose my "old" dish ! Cant wait to get my 1st link ! Who will it be ?

If you can do this somewhat manually, in the chat client, try to connect to KN5G-002.austin.tx.us.mesh , the fully qualified domain name.

If that fixes it, then you will need to add the FQDN to your DNS so as to NOT have to always add the rest of the URL.

If its Windows, see http://hsmm-mesh.org/documentation/96-using-the-mesh.html and at the bottom where it says "For DNS to work properly.....", specifically the "Append these DNS suffixes" instructions.

Let me know if that works!

K5KTF

No, it does not matter which node I try to access the IRC Server from.  I get the same error that server KN5G-002 is unknown.

I don't know if all clients use the same form to name or point to the desired server but it seems like I am not telling the client the right server name, or I may have not configured something just right in the Server when I was setting it up.

I would be curious to know what others have set in their irc client apps to point to the IRC Server on their nodes.

Thanks,

I was going to say try using the ip address 172.27.0.1, but I see you are on a remote node. We're you able to connect to the server while connected via cat5 to the node with the irc server?

73s

w5cwt

Here is what I am getting :

Asterisk will attempt to rout the call, but I will get a message stating "Everyone is busy"

But nothing comes up on the second node even showing an attempt.

when I do a 'dundi show keys' it shows no keys loaded

Every time I reboot the routers /var/lib/asterisk/keys and the keys within them are gone again.

sorry... It seems that DUNDi is just not finding the Keys.. in /var/lib/asterisk/keys

I might have forgotten to mention that you need to uncomment the res_crypto.so module in the /etc/asterisk/modules.conf file and change it to read "load=res_crypto.so" in order for the module to get loaded. Don't forget to restart Asterisk and/or issue a module reload command from Asterisk's CLI afterwords.

Thanks.  I can't take credit for any of the documentation.  That's from the developers, although I do want to write some "Broadband-Hamnet for newbies" guides once the new software is finalized.   The guys who know what they're doing are so far up the experience curve from me that a bit of a description from a relative dummy might help a lot of the folks without that kind of experience. 

Also, don't forget the Wireless Networking book that has a lot of info on wireless networking in general.

Well, I have gotten to the point where I'm am forced to ask for a little help.  I have the IRC Server set up on one of my nodes, KN5G-002 and have double checked the configuration according to the article found here in the forum.  The server is showing up as a service on the node and I can click on the link and the ChatZilla client opens on the computer connected to the remote or second node, KN5G-001 but that is as far as I can get.

The ChatZilla client complains about "The network "kn5g-002" is not known to ChatZilla.

When I manually tell ChatZilla to join I get the "Unknown host" error shown here, using the string irc://kn5g-002.mesh:6667 in the manual connect to server window.

Obviously I am missing something, (probably something really simple) but I have run out of ideas where to look for the problem at.

What I have done.

I went into the firewall on the computer on the client's kn5g-001 node and opened the 6667 port.

I have the 6667 port open in both mesh nodes for both the LAN and the WiFi.

I have a laptop connected to the LAN port on each node so my setup represents two full nodes with attached computers.

I have called the computers and nodes dirty names, (made me feel better, what can I say).

So, can anyone suggest where else I might check to find and correct my problem?

Are there any issues with using ChatZilla?  I picked it as a client just because I thought it would handy to have a plug-in for the browser rather than a separate client application to keep up with.

Would there be an issue with the "dash" I used in the node's name: kn5g-002 ? (I've seen crazier things blow up a whole system, ha...)

Anyway, rather than continue to pull my hair out I thought I would see if anyone could offer some suggestions as to what to try or what to look at next to get the client talking to the server.  Any help and or suggestions would be greatly appreciated.

Keith - kn5g - Henderson, TX.

You can set up your own Ubiquiti mesh system right now and the systems will work right now.  They just won't talk to HSMM-MESH systems until the new BH is released and loaded on the WRT54G routers. 

You'll have to figure out how to load OpenWRT, OLSR, and configure it to be compatible. 

For that matter, you can probably make a BH compatible system on anything that will run OpenWrt, like Raspberry Pi, laptops, regular PCs, smartphones, etc.

You'll still have to do all this configuration work yourself once BH is released if you're loading anything other than WRT-54G.  HSMM-MESH is mostly a preconfigured load of the software needed to do an OpenWrt/OLSR setup on WRT-54G along with some nice "wrappers," configuration tools, etc.

Presumably some people will figure out the Ubiquity configuration for BH, and publish it, but you'll still have to do a lot of the work yourself to load and configure it.  We may have a "pretty, easy, bundle" for Ubiquiti later, but for now, it's going to be much more complicated than loading HSMM-MESH on a WRT-54G. 

Depending on your hardware choice, and how many others have worked on it and documented it, there will be a LARGE variation in the amount of work and skills needed to make a particular device BH compatible.

By the way, why do you want Ubiquiti?  Yes, the package is pretty, but other than the packaging, it doesn't really have that much advantage over a WRT-54G.  

Just found the following opinion on the web, would you think it is correct?

watch : http://www.tmcnet.com/tmc/videos/default.aspx?vid=7526

You cannot install DUNDi for Asterisk 1.6 with the packages found on OpenWRT. So to fix this problem, I had to downgrade Asterisk by a version. I haven't lost any functionality at all. In fact...I gained a functionality!