Broadband-Hamnet™ Forum :: Applications
Welcome Guest   [Register]  [Login]
 Subject :IRC Client Configuration.. 2013-05-17- 14:59:10 
KN5G
Member
Joined: 2013-04-25- 15:30:05
Posts: 5
Location: Henderson, Texas

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.

Screen Shot of KN5G-001 node


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


ChatZilla Client Window

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.

Error Message in ChatZilla Client 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.




IP Logged
Keith - KN5G - Henderson, TX.
 Subject :Re:IRC Client Configuration.. 2013-05-19- 08:03:54 
NR1X
Member
Joined: 2013-04-29- 14:46:03
Posts: 6
Location
Not too sure as i have never used Chat-zilla, but it seems you need to add KN5G-002 to the server list... Google can help you find out how to do this. NR1X Al, CT
IP Logged
 Subject :Re:IRC Client Configuration.. 2013-05-19- 14:47:03 
w5cwt
Member
Joined: 2013-04-12- 14:16:38
Posts: 7
Location: Henderson, Texas

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

IP Logged
Last Edited On: 2013-05-19- 14:51:56 By w5cwt for the Reason
 Subject :Re:IRC Client Configuration.. 2013-05-19- 16:07:44 
KN5G
Member
Joined: 2013-04-25- 15:30:05
Posts: 5
Location: Henderson, Texas

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,


IP Logged
Keith - KN5G - Henderson, TX.
 Subject :Re:IRC Client Configuration.. 2013-05-19- 16:16:41 
K5KTF
Admin
Joined: 2010-01-18- 23:04:04
Posts: 266
Location: 5' from this webserver
  

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

IP Logged
B-) Jim K5KTF EM10bm Cedar Park, TX :star:
 Subject :Re:IRC Client Configuration.. 2013-05-20- 15:08:14 
KN5G
Member
Joined: 2013-04-25- 15:30:05
Posts: 5
Location: Henderson, Texas
Thanks Jim, I'll give that a try in a few minutes. Will let you know if that scratches my itch. Keith
IP Logged
Keith - KN5G - Henderson, TX.
 Subject :Re:IRC Client Configuration.. 2013-05-20- 16:14:17 
KN5G
Member
Joined: 2013-04-25- 15:30:05
Posts: 5
Location: Henderson, Texas

Success ! Sealed

Chalk it up to operator error and 55 plus year old eyes. Yes, it was my typo.  No space between the equal sign and the node name in the server config file.  Been a lot of years since I dabbled around with Linux and the vi editor.  Had forgotten how unforgiving they can be. Typo? No problem, we'll just sit here and do nothing till you figure out your mistake... ha...

Anyway, thanks to those who took the time to offer suggestions while I was pulling out what hair I have left.  At least now the IRC Server is up and working across the MESH Network and both clients can connect and exchange information in the chat.

The "Take-away" from this; always double check your edits for typos ! They will drive you nuts !

David, guess we have a club meeting this Thursday.  You going to be able to make it?


Thanks again,


IP Logged
Keith - KN5G - Henderson, TX.
 Subject :Re:IRC Client Configuration.. 2013-05-21- 18:58:20 
ae5ae
Member
Joined: 2010-10-27- 00:47:17
Posts: 144
Location: Van Alstyne, TX
Keep in mind, too, the you can run 'ngircd -t' to have ngircd test your config file. Spaces around an equal sign are not needed in the config file. You'd be surprised what you can learn by running a command with either the -h or --help options. :) Glad you got it running! -Rusty-
IP Logged
Page # 


Powered by ccBoard


SPONSORED AD: