Seamlessly Extending IRC to Mobile Devices

Internet Relay Chat (IRC) is one of the older real-time communications methods still in active use on the Internet. Due to its popularity, flexibility and cross-platform nature, it still has a very vibrant user base today. Personally, I've been on IRC since the late 1990s, and it's been very useful and lots of fun—particularly the #linuxjournal room on Freenode—stop in sometime!

Drawbacks to IRC

As great as IRC can be, there's one thing about it that's always bothered me, and it's something that Jabber got right—the concept of a resource and priority. In IRC, when you log in as whatever user you are, you can't log in as that user again from another machine. Jabber allows multiple user logins, so long as the "resource" is different, and it'll route your messages to the client with the lowest priority. IRC doesn't even have that concept, so once you log in on your desktop, you have to log in as another user if you want to log in on your laptop, which results in lots of logins like "WildBill|Laptop" and such. This causes a problem if people want to private-message (PM) you, as they never know what login you're on.

For years, I've used a fairly common workaround to bypass this problem to a certain degree. If you use a text-based client like Irssi, and run that client on a machine that's on all the time, you can run the client within a terminal multiplexer, such as GNU Screen. That gives you the ability to run the client, detach from the terminal session, then log in via SSH on another machine and reattach to your session, where you can catch up on what you may have missed. By and large, this is an acceptable workaround...except when I forget to log in to that Screen session. I've been known to have a few days' worth of PMs piled up before I remember to log in and check. By that time, people who PM'd me probably forgot what they pinged me about.

The other major flaw with this scheme is that it doesn't work well with mobile devices like tablets and mobile phones. Yes, I could SSH from my iPhone to my Linux server and attach to that Screen session with Irssi running in it, but a terminal emulator on a 3.5" screen, where a good portion of the screen is taken up with an on-screen keyboard, is a recipe for a headache. There are excellent IRC clients for mobile phones, like Colloquy on the iPhone, Yaaic for Android and wIRC for WebOS, but if you run them while you have a Screen session going, you're back to the same problem mentioned above where you wind up with a "WildBill|Phone" login. There simply had to be a better way.

Is There a Better Way?

It turns out, after noodling around for a while one day, I did find a way. Irssi, the text-mode client I usually use via Screen and SSH, has a "proxy" (or "bouncer") mode where you can have it listen on a couple additional ports and then attach another IRC client to it. Enabling the proxy is relatively easy, and it can be done from within Irssi with only a few commands (assuming your Irssi is packaged and includes the proxy module). This also assumes you have Irssi already configured to work properly with whichever IRC networks you wish. Of course, substitute your own password for "mypassword", define whatever IRC networks you want to proxy with Irssi, and pick an arbitrary open port on which to have the proxy listen:

/LOAD proxy
/SET irssiproxy_password mypassword
/SET irssiproxy_ports linuxjournal=9000

Once you get the proxy module running successfully, connecting to it is as easy as pointing another IRC client at it. Just specify the fully qualified domain name of the host running your Irssi client in your second IRC client's configuration, and give it the password and ports you called out in the Irssi commands above. This client can be a "regular" desktop or laptop, or it can be a mobile device, such as an Android phone or an iPad running an IRC client.

Although this works just fine, it bothers me a little bit, as the password that's sent between the mobile device and your Irssi session that's running in Screen is sent in the clear. I'd much prefer that to be SSL-encrypted, so no one can intercept that password. Unfortunately, the Irssi proxy module doesn't support SSL, but there's a way around that through the use of the stunnel utility.

Stunnel is a generic encryption wrapper that's designed to add SSL encryption to any non-encrypted service. It's not hard to wrap the Irssi proxy service with stunnel. First, to prevent anyone on the outside from accessing the proxy without SSL, I bound the ports on the Irssi proxy to the loopback interface using the following Irssi command:

/SET irssiproxy_bind

Next, use your distribution's method for installing stunnel. On Ubuntu 10.04, a simple sudo apt-get install stunnel4 took care of that. I had to create a self-signed SSL certificate (see Resources for a how-to on this), and I put that cert in /etc/stunnel. Next, I had to create an /etc/stunnel/stunnel.conf that referred to the certificate I created and specified the Irssi proxy in the stunnel.conf file. An example follows below (adjust the file paths, "accept" IP address and port as necessary):

; stunnel.conf code snippet
; Certificate/key is needed in server mode and optional in client mode
cert = /etc/stunnel/cert.pem
key = /etc/stunnel/key.pem

So, what the previous code snippet does is specify the cert/key file for the self-signed SSL cert, then binds the SSL side of stunnel to the external IP address on port 9000, and it'll hand off packets to my Irssi proxy running in the clear on (localhost) on port 9000. The last adjustment to this setup would be to go to the mobile device and specify that the IRC connection should be SSL, and now I have a secure proxy I can attach to with any client of my choice. Now I can log in to IRC from my regular Irssi client, but then when I'm on my phone, I can use the friendlier interface that Colloquy provides, all without having different nicknames on IRC.

Being "Pinged" and Getting Alerted

I still have a problem though. I still forget to log in to IRC and check my private messages—and some friends stack up many "pings" before they finally give up in frustration. I got to thinking and realized that since I'm on a mobile phone, it might be possible to send an e-mail to the SMS gateway my mobile provider runs when I get a PM. That'd give me a reminder to log in to IRC in the event that I forget. After searching the Internet for a bit, I discovered some other fellow had much the same idea. Michael Lustfield explains it on his blog in far more detail than I can put in this article (there's a link in the Resources section), but I'll summarize his technique here. He's got two Irssi scripts he uses: monitors if there's an active connection to the Irssi proxy, and sends any highlights off to a designated e-mail address if there isn't an active client connected to the Irssi proxy.

Figure 1. Getting an SMS on WebOS

"But Bill...e-mail isn't an SMS!" You may think that, but just about every mobile carrier can accept SMS messages for delivery to a mobile phone via e-mail. In my case, I use AT&T, so any e-mail sent to <myphonenumber> will arrive as a text message on my phone. So, all I have to do is drop Michael's scripts in my Irssi scripts folder, adjust so that the $config{emailto} variable is, and then activate both scripts from within Irssi by doing a /script load and /script load Now, any mention of my name in any of the channels I sit in will cause an SMS to be fired off to my phone, and I can log in from my phone or tablet and jump into the conversation.

Figure 2. Jumping into the Conversation—Using wIRC on WebOS


Bill Childers is the Virtual Editor for Linux Journal. No one really knows what that means.


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Without this, perhaps, the

garnier's picture

Without this, perhaps, the life of mobile technology will not be as great as we currently have.

Garnier, an ipad 2 keyboard designer

IRC on an Android device

Vidofnir's picture

I use ConnectBot on my Android device. I have a shortcut to my server where irssi is running and ssh keys set up, it also executes 'screen -UD -RR -s irssi'. So I can reach IRC with just one click.
I'm actually very happy with the setup, it is usable and the character size can be adjusted, and it is the exactly same environment as if I'm doing the exactly same way of connecting from my desktop computer :-)


Blade's picture

XMPP is not really a good solution -- it's terrible for mobile devices.

More dropped in to post a pic of something I've been working on for webOS and IRC :)

IRC from Messaging :) will probably only work on 3.0+ though :(

RE: forgetting to re-attach

taborj's picture

RE: forgetting to re-attach your Screen session

I use tmux (very similar), and have this in my .profile:

if [[ -z "$TMUX" ]]; then
tmux att

Basically, when I log in, if a tmux session exists, it will automatically attach to it. Bingo! I never forget to reattach my session.

I think I found this on, and I'm pretty sure there are some for Screen up there as well.

XMPP conferences

Paul Johnson's picture

Seems like the ultimate fix would be to start transitioning to XMPP conferences. Would help if Google Talk more readily supported this natively in their official clients.

One Click, Universal Protection: Implementing Centralized Security Policies on Linux Systems

As Linux continues to play an ever increasing role in corporate data centers and institutions, ensuring the integrity and protection of these systems must be a priority. With 60% of the world's websites and an increasing share of organization's mission-critical workloads running on Linux, failing to stop malware and other advanced threats on Linux can increasingly impact an organization's reputation and bottom line.

Learn More

Sponsored by Bit9

Linux Backup and Recovery Webinar

Most companies incorporate backup procedures for critical data, which can be restored quickly if a loss occurs. However, fewer companies are prepared for catastrophic system failures, in which they lose all data, the entire operating system, applications, settings, patches and more, reducing their system(s) to “bare metal.” After all, before data can be restored to a system, there must be a system to restore it to.

In this one hour webinar, learn how to enhance your existing backup strategies for better disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible bare-metal recovery solution for UNIX and Linux systems.

Learn More

Sponsored by Storix