The article describing the install process for the IRC on the Linksys router says the software can be found in the repository. Where is a this exactly (URL?). 

Thanks, Ron, N1AHH

Finally home from travels. I did as you specified and it loaded and runs as advertised. Thank you very much. It will be a very useful addition to our mesh.

Ron, N1AHH.

http://broadband-hamnet.org/download/backfire/10.03.1/ar71xx/packages/

It is probably newer because ya much newer operating system.

Doesn't likely have any custom mods that may have been done in the OLD version.

Hey Gene,

I will circle around the side with you so you have my details. Great news on that progress.

it sounds like the package has installed.

You should see a lin "installing"  and than the last line "configuring"  at this point the package should be installed and should also than show up in the "remove package" list on the Admin page.

After that you can install the next package.

Scratch that previous version.

I can't say that I've run into that before.  When you get a connection refused, have you gone back to the node that's running the IRC server and verified that 'ngircd' is still running?   I can't vouch for that 15.2 version working correctly. even on the Rocket, as I have ZERO experience with it.

The firewall on the PC shouldn't be of any concern unless it is blocking outgoing traffic to port 6667 on the remote host.

Elmer, your mesh node that you are trying to download a package into needs to have some connectivity to the Internet, either directly through its WAN port or over the mesh to another node that does.  This is why I wrote this:

"...press the [DOWNLOAD] button and given connectivity to the Internet and the BBHN servers you should have..."

Also, the .ipk files are NOT intended to be opened on your PC.  If you were able to somehow download the file to your PC from our WRT54G repository then, go back to the mesh node's webpage, click on the [Choose File] button to the right of "Upload Package", point the file selector to where the ngircd_20.2_mipsel.ipk file is located on your PC, and then click the [UPLOAD] button and the package will be sent to your mesh node and automagically installed.

-Rusty-

After the download to the mesh-node, you also have to have a chat program on the local computer & the computer you will chat with. I use Chatzilla and Firefox browser. The issue with ngircd is that while the chat server is located on the mesh-node, it will not recall the chatroom link. You have to manually enter it in Chatzilla in its setup from find chatroom (localnode:6667/#mesh) in Chatzilla on computer connected to mesh-node with ngircd. On the second mesh-node you will have to find the proper link to the first mesh-node by adding irc://specific-node-name:6667/#mesh into the Chatzilla set up, instead of localnode:6667/#mesh used on the ngircd loaded mesh.

With Regard to KF4WEO's question and AE5AE's answer, I get the following Error:

Package Management

Downloading http://broadband-hamnet.org/download/kamikaze/7.09/brcm-2.4/packages/Packages wget: cannot connect to remote host: No route to host Downloading http://broadband-hamnet.org/download/kamikaze/7.09/packages/mipsel/Packages wget: cannot connect to remote host: No route to host An error ocurred, return value: 2. Collected errors: ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-OqsAlH http://broadband-hamnet.org/download/kamikaze/7.09/brcm-2.4/packages/Packages' ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-OqsAlH http://broadband-hamnet.org/download/kamikaze/7.09/packages/mipsel/Packages'

I have 12 of the WRT Routers and have used the NGIRCD 20.2 download several times through package Management with no problems until now.

Regards

Rick AJ4FW

Thanks for the report, probably better if we move it to a new thread for any further on it.

BBHN->ticket:74 created for this issue.

Overview: It looks like the Linksys devices (but not Ubiquiti) are trying to download via a newly published IPv6 Record for the BBHN domain.  Problem with this is most houses don't have IPv6 yet.

I suspect this is due to the age of the backend that some of these IPv6 situations hadn't been fully worked out yet when it was first released in 2007 so I will do some digging and see what our solution path is to resolve this.

Further updates can be found by watching the ticket.

I'm a recent newcomer to IRC but not networking software, so I was able to set up several test chat servers on 54G and 54GS routers using ngircd 20.2 and testing port action using a sniffer. I had problems getting access to the servers though. I found that the clients I was using in Opera and Thunderbird were partly to blame for a lack of an easy setup.

On the setups here at first there was no way I could get a client to connect other than punching in the IP address. Also, as long as "0.0.0.0" is the default for the dns search the wifi address of the router will always be seen first, since the lan address is not available to the server. I found I had to enable the DNS search switch in the ngircd.conf file also.

Then, it wasn't really clear from the docs that you should only put in the node name when setting up the client account (ie ab9u-gr4) and nothing else after it such as "ab9u-g4.mesh". So once that was all working I tried external (wan) access and ran into a wall.

OK, here's my problem, I can not connect to the server using any irc client external to the mesh network via the WAN port.

Everything works within the mesh network address space via wifi or lan ports but nothing comes through the wan port firewall. I can open up ports all day, even enable gateway mode, but in setting up an "outside" client account I can't name the account the same name as what's in the mesh and that seems to be the only way to access the server by the client.

I can connect over the mesh and via tunnels without effort either by lan port or by wifi but not via the wan port at a different IP address range. I've tried adding the router external wan 192.168.3.6 ip to the server listening port list in ngircd.conf but nothing appears using netstat -tl. The other ports show up and are being listened to such as 6667, 6697 but those do not appear on 192.168.3.6. Using a sniffer port 6667 does not respond at the wan port.

What am I missing in the setup? It would be nice to access the IRC via the wan port.