BBHN does not put the node in the DMZ. It only puts those devices plugged into the LAN into the DMZ. So you will need to switch the node back to NAT and follow the directions. The guide was created before the switch to the new default mode in the v1.0.0 release.

If you want to keep 5 Host Direct and also host a service on a node, you could also go into the node and modify /etc/config/firewall and /etc/config.mesh/firewall, add an entry for port 6667, and reboot the node.

No luck with changing to NAT and forwarding the port. I also added the port in the firewall config files. The ngircd.conf file checks fine.

Well the nodes talk to each other as designed and the remote node can even see the internet on the node hooked to my local network. I just can't get any irc client to connet to the ngirc server. Other than seeing the ngirc service running on the node I can't even say that it is running. I have attached some screen shots of the configuration. Thanks for any help.

Jay - KE6GLA

Attachments
 node-setup1.jpg [112 KB] :: Node-setup
 node-forward.jpg [106 KB] :: Node-Forward
 node-ngirc.jpg [106 KB] :: Node-ngric

True, I wrote those instructions prior to my knowledge of DMZ/Direct mode being the default for the v1.0.0 firmware so they need some adjustment.

In the DMZ/Direct node, no holes need to be explicitly punched in the firewall (via web interface or editting the /etc/config files) after installing 'ngircd v20.2' EXCEPT if you desire access to the IRC server via the WAN port.

Two things to try:

1. Change the protocol from IRC to irc.  The Opera browser doesn't have a problem with the uppercase protocol in the link but the chatzilla plugin may...
2. Use the 'ps' command on the node to verify ONLY ONE copy of 'ngircd' is running on the node. Not sure how more than one could have gotten started but there might be two or more running depending on what you've done with the node.
3. Verify that /usr/local/bin/ngircd is running, not /usr/bin/local/ngircd as you stated earlier (yes, I'm slightly slysdexic too).
4. Run 'netstat -tl' on the node running the ngircd program.  The output from 'netstat' should contain one line that looks like this:

tcp        0      0 *:6667                  *:*                     LISTEN 

5. You can always 'telnet' or 'nc' into TCP port 6667 of your node from your PC (after installing such program).  After connecting, type 'user' followed by a carriage return  and the node should return a syntax error.
6. Worst case, remove and reinstall the 'ngircd' software with a reboot before the package install.

I removed and reinstalled the ngirc server on the node hoked up to my local network. I can connect to the IRC server using the home lan IP address and the node name of AG6AU-10. I can't connect to the IRC server using the WIFI address nor can I connect to it from another node. Do I need to forward the IRC port 6667 on the other nodes? I wouldn't think that is nessary. When I try to connect to the IRC server from another node is IRC client says it can't find AG6AU-10 and I also tried the IP address of AGUAU-10. I'm a litter closer but still don't have the IRC server working through additional nodes.

Thanks again,

Jay - KE6GLA

Jay

Is your mesh node that's running 'ngircd' in Direct or NAT mode?   Verify this by going to the initial Setup page and look in the LAN section.   If you're using NAT then you'll need to follow my instructions document to open holes in the WiFi firewall.  Be sure to save your config!

Holes in the firewall (at least on our mesh nodes) are for inbound packets so you only need to poke holes in the firewall for the node running the 'ngircd' server program and no other nodes.

If you're using Direct mode on the IRC node then the firewall doesn't need to be messed with ('cause there ain't none!) unless you want to open a port on the WAN interface.

If your IRC client program can't find the node name then you are having DNS problems on your PC.  If your PC is using two network interfaces then turn off the one NOT connected to your mesh node.  This should fix your DNS issues.

    -Rusty-

Rusty,

I was in NAT mode. The only way I could connect was to use the IP assigned to my mesh node from my home router. I can't connect using the wireless IP assigned by the node or the node name of ag6au-10. I think I will reload the firmware and start with only the nodes and I will see if I can get the IRC working. Then I will try to incorporate one of the nodes back into my home network..

Jay - KE6GLA

After all the tinkering with the mesh-server found the problem was with the client. An anti-virus program also block IRC ports. I disabled that feature and it works good.

Jay