Summary: | DCC fails when IP changes | ||
---|---|---|---|
Product: | [Applications] konversation | Reporter: | mrdocs <mrdocs> |
Component: | general | Assignee: | Konversation Developers <konversation-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 0.19 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
mrdocs
2006-08-18 00:18:19 UTC
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. |