Version: 0.19 (using KDE KDE 3.5.4) Installed from: SuSE RPMs OS: Linux When I connect to IRC, the first connect has no issue when I want to initiate a DCC file transfer. However, my ISP renews IP addresses every 24 hours via DHCP once konversation reconnects after an IP refresh or change, DCC transfers fail. The receiver can see the transfer initiated, but when they accept it times out. Find me in #scribus on freenode.net for more info if needed.
I've fixed a bug that prevented Konvi from getting the correct IP from the server during reconnects on the Freenode IRC network a couple of month back in the SVN version. Sounds like you're hitting the same problem here. I'll keep this open for now; if you can get a SVN checkout to test (see http://konversation.kde.org/wiki/SVN) or eventually upgrade to 0.20 and the problem disappears, please inform us.
OK, I have current SVN installed and will test today and report.
Any update?
Does not seem any better, in fact worse. DCC does not work at all outgoing - even after a fresh reboot. If you want I can give you an NX account to test. I would just need a gpg key to send you an encrypted password.
We've done a massive amount of DCC testing over the last two weeks as we rewrote nearly all of the info messages, so I'm a bit suspicious of DCC supposedly being broken. Are you sure that your DCC port range is accessible by recipients, and that you are identified on Freenode? DCC works by sending CTCP messages to recipients, and Freenode does not allow unidentified chatters to send messages.
Closing WORKSFORME since repeated tests do not reveal a problem, and I'm reasonably confident that we fixed the originally reported bug which is known to have been present in 0.19.