#356 new defect

bitlbee does not detect connection loss

Reported by: duncan@… Owned by:
Priority: normal Milestone:
Component: BitlBee Version: 1.0.3
Keywords: Cc:
IRC client+version: Client-independent Operating System: Linux
OS version/distro:


It would appear that if the network connection is lost bitlbee does not notice.

Today I was sending messages every 3 minutes to an MSN contact as a test. I pulled the network connection for a few minutes, during that time 2 messages were sent. Bitlbee did not complain and appeared to send the messages however they were (obviously) never received by the msn contact.

On reconnecting the cable, bitlbee reconnected automatically and the next messages were sent and received as expected.

I also noticed that it took MSN quite a number of minutes to detect the bitlbee msn user had gone away.

Doesn't appear to make any difference whether auto reconnect is on or off.

Is there some timeout after which bitlbee will notice it has lost the connection? Is there anyway to adjust the timeouts?

Thanks Duncan

Attachments (0)

Change History (8)

comment:1 Changed at 2008-02-04T23:29:09Z by wilmer

BitlBee sends keepalives every minute but usually doesn't really care about a response. So yeah, until something decides to kill the TCP connection, BitlBee won't really be aware of any problems.

That's indeed room for improvement, so maybe I should do that. :-)

Not sure if it will work out with all protocols. Right now the keepalive in Jabber is just some whitespace, the server doesn't have to respond to that. There's also a ping facility, but I don't think all servers support it.

comment:2 Changed at 2008-02-05T08:48:59Z by duncan@…

Perhaps an option whether to send pings or test for keepalive responses would be good.

comment:3 Changed at 2008-02-05T08:49:56Z by anonymous

By which I mean a parameter you can set to turn it off and on

comment:4 Changed at 2008-05-21T14:46:56Z by tim

anonymous, that's a good idea. Then we could simply change the value if the server doesn't pinging.

comment:5 Changed at 2010-06-27T13:58:22Z by wilmer

Milestone: 1.2.x

marchino in #bitlbee brought this up again, it's pretty bad in the Jabber module (at least when talking to GTalk). This should probably get some more priority.

comment:6 Changed at 2010-11-21T15:26:46Z by wilmer

Partially solved, if a login isn't completed within two minutes it'll be timed out (and retried after the usual interval).

Keepalives are otherwise still one-way. :-/

comment:7 Changed at 2012-01-18T17:19:35Z by anonymous

This is still a major issue - I pretty much have to just close and reopen bitlbee when I switch network connections.

comment:8 Changed at 2016-07-07T20:51:01Z by dx

Milestone: 1.2.x

Modify Ticket

as new The ticket will remain with no owner.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.