Difference between revisions of "Bitlbee"

From ArchWiki
Jump to: navigation, search
m (cleanup)
m (Setup)
Line 17: Line 17:
 
Bitlbee currently does not run on a daemon of its own; rather, it uses xinetd. The installation created a file: <code>/etc/xinetd.d/bitlbee</code>
 
Bitlbee currently does not run on a daemon of its own; rather, it uses xinetd. The installation created a file: <code>/etc/xinetd.d/bitlbee</code>
  
We need to edit this because at the moment xinetd doesn't know you want to use bitlbee. Open <code>/etc/xinetd.d/bitlbee</code> in your preferred text editor and tell it not disable bitlbee:
+
We need to edit this because at the moment xinetd doesn't know you want to use bitlbee. Open <code>/etc/xinetd.d/bitlbee</code> in your preferred text editor and tell it not to disable bitlbee by changing the line:
 +
 
 +
disable = yes
 +
 
 +
to:
  
 
  disable = no
 
  disable = no

Revision as of 20:21, 3 September 2007

About

Bitlbee is a "console-based IRC to IM chatting gateway, including ICQ/MSN/Jabber". Basically, it allows the user to interact with popular chat networks (ICQ, MSN, Jabber, AIM, YIM) within their IRC client.

The users' buddies appear as normal IRC users in a channel and conversations use the private message facility of IRC.


Setup

First, download and install the package using pacman:

# pacman -S bitlbee


Bitlbee currently does not run on a daemon of its own; rather, it uses xinetd. The installation created a file: /etc/xinetd.d/bitlbee

We need to edit this because at the moment xinetd doesn't know you want to use bitlbee. Open /etc/xinetd.d/bitlbee in your preferred text editor and tell it not to disable bitlbee by changing the line:

disable = yes

to:

disable = no


Finally, you need to allow the loopback interface in /etc/hosts.allow, add this line:

bitlbee: 127.0.0.1

Start Up

To get things up and running we must start xinetd. As root, run:

# /etc/rc.d/xinetd start

(replacing 'start' with 'restart' if xinetd was already running, you'd know if it was)

This will need to be started every time you boot your machine. You can either do this manually (by running the above command after each boot) or have it started automatically by adding 'xinetd' to the DAEMONS array in /etc/rc.conf:

DAEMONS=(syslog-ng network alsa esd xinetd)


Configuration

Now that xinetd is running your computer is acting as a bitlbee server. You are now able to connect to this in an IRC client. To connect, just connect to your machine in an IRC client:

/connect 127.0.0.1

Hopefully this will connect and you should immediately join a channel called '&bitlbee'. When you join this channel it will tell to type 'Help' if you're new... type 'Help' ;)

I won't bother repeating what the help section of bitlbee says. There are some great guides online too:

http://quark.humbug.org.au/publications/internet/bitlbee.pdf

http://princessleia.com/bitlbee.php


How to connect to Jabber using your Gmail account

In your control channel do the following:

account add jabber username@gmail.com mypasswd talk.google.com:5223:ssl

After root responds with "Account successfully added" you can check your accounts with "account list".

<@user> account list 
<@root> 0. JABBER, username@gmail.com (connected) 
<@root> End of account list

After you have added the account, type "account on 0" and it should log in:

<@user> account on 0 
<@root> JABBER(username@gmail.com) - Logging in: Connecting 
<@root> JABBER(username@gmail.com) - Logging in: Connected 
<@root> JABBER(username@gmail.com) - Logging in: Requesting Authentication Method
<@root> JABBER(username@gmail.com) - Logging in: Authenticating 
<@root> JABBER(username@gmail.com) - Logged in

If you get errors like the following:

<@user> account on 0 
<@root> JABBER(username@gmail.com) - Logging in: Connecting
<@root> JABBER(username@gmail.com) - Logging in: Connected
<@root> JABBER(username@gmail.com) - Logging in: Requesting Authentication Method
<@root> JABBER(username@gmail.com) - Logging in: Authenticating
<@root> JABBER(username@gmail.com) - Login error: Error 403: Unknown error
<@root> JABBER(username@gmail.com) - Signing off...

Switching the domain from "gmail.com" to "googlemail.com" may help. This seems to be the case for some European countries, especially Germany where Google doesn't own the trademark for the name Gmail [1].

The easiest way to change your account settings is to simply delete the account you created and add it again.

account del 0
account add jabber username@googlemail.com mypasswd talk.google.com:5223:ssl

If you are still unable to connect, try switching the port to 5222. For some reason some people must connect on 5223 while others have to connect on 5222. There appears to be no way to know which one to use other than trial and error.