Ticket #498 (closed defect: fixed)
IRC client fails to reconnect after IP change.
|Reported by:||ipv6guru||Owned by:|
When buildbot is running on a machine with dynamic IP the IRC client won't rejoin after an IP change.
It will never get a clientConnectionLost because no data is send over the TcpConnection?.
Christoph von Wittich Christoph@…
Submitted: Nobody/Anonymous? ( nobody ) - 2006-08-25 07:19
Extra Comments :-
Date: 2007-01-31 09:43 Sender: r33d
While most IRCds actually send you a PING with a random token that you need to send back in order to remain connected, it seems that other IRCds do not. One way of fixing this is by pinging yourself through the server. Just send a CTCP PING to yourself and calculate how long it takes to get back to you. If it never comes back within a certain time period, you probably have been disconnected and should reconnect. I'll ponder some more on this.
Date: 2007-01-31 09:34 Sender: warner
yeah, we need to have something in the IRC bot that pings or otherwise generates some traffic every once in a while. I think that would be enough to trigger a connectionLost, after which the usual ReconnectingClientFactory? behavior ought to be enough to make it reconnect (with the new IP address).
Does anyone know which IRC command we should use? I know that PING is usually directed at someone else.. what can we do to just make sure we can still talk to the ircd?
- Summary changed from IRC bot problem to IRC client fails to reconnect after IP change.