Package: bip
Version: 0.8.2-1
I have bip running on a stable server, connected to some irc servers
(including freenode).
My irc client at home is xchat.
My xchat and bip are connected through an ssh tunnel (as i don't want to
open another port for bip ssl). So xchat connects itself on localhost:x
and bip sees it as localhost:y (ssh doing the mapping between home:x and
server:y).
It looks like this:
xchat <-------(ssh tunnel)--------> bip <-------> ircd (freenode, ...)
^ ^
| |
localhost:x localhost:y
For the last few weeks, my (ADSL) connection has been unstable, hence, i
depend on bip to keep me in sync with the channels on which i'm active,
especially when the disconnection happens in the middle of a discussion.
My disconnections last from a few seconds to 5min. When I come back, i
have a new IP address (from my ISP), hence a new tunnel, and a new
connection to bip.
But the remote users are not aware that i was offline and expect me to
answer.
With "backlog_always = false", i never see what happened while i was
offline.
If i properly quit xchat, and restart it after the same kind of delays,
i get the expected backlogs from bip.
It seems bip is not able to detect fast enough that the client is gone.
I went through the doc and the code and i was unable to find anything
that would allow me to shorten the timeout (between bip and the client)
or to trigger a faster "irc ping".
I'm not sure if my tunnel really matters here, it seems the key
difference is the *unexpected* disconnection. Even if i lower the ssh
keepalive to the lowest-but-still-sane value, it won't allow bip to
replay what happened when the disconnection happened.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
