Opened 18 years ago

Closed 18 years ago

#11098 closed defect (wontfix)

BUG: xchat2 2.6.8_0 - NAT DCC error from perl scripts (resubmit)

Reported by: dir123@… Owned by: mij@…
Priority: Normal Milestone:
Component: ports Version: 1.3.2
Keywords: Cc: mij@…
Port:

Description

NOTE: This was previously submitted as Ticket #11070, but with the wrong properties. After 5 days of no one fixing the properties, I'm resubmitted correctly. Please cancel the other one (since I can't do it myself)

Using Xchat 2.6.6 and Obsidian2 2.0.0-rc2, I think I've uncovered what appears to be a problem with the interaction between the perl module and the "Get my address from the IRC server" preference.

Obsidian sends the following command: Xchat::command("dcc chat $nick", undef, $server);

If the "Get my address" box is unchecked, and there is no DCC IP address specified, $nick receives a dcc chat with an IP and port ("DCC CHAT chat 3232238182 55532", for instance). If either one of those is filled in, then all that comes across is the string "DCC CHAT chat". This doesn't appear to be a problem with Obsidian, as it appears to rely on Xchat to provide the IP and port.

I'm pretty sure this is not a problem with xchat itself, as I've failed to reproduce it on a Gentoo install, and an xchat dev couldn't reproduce it either.

Attachments (1)

testcase.pl (418 bytes) - added by dir123@… 18 years ago.
Script to demo the problem

Download all attachments as: .zip

Change History (5)

Changed 18 years ago by dir123@…

Attachment: testcase.pl added

Script to demo the problem

comment:1 Changed 18 years ago by dir123@…

I should tell you how to use the script too, since I didn't comment it. Simply connect two connections to the same server (or get someone else to help). One runs the script, the other uses /ctcp to send a message (any message) to the script-runner. You should get a DCC chat message back. Depending on the "Get my address" setting, it'll either be valid or malformed.

comment:2 Changed 18 years ago by dir123@…

Actually, upon further testing, this seems to have nothing to do with perl at all. Simply type "/dcc chat <other user>" while using the "get my address" setting, and watch the Raw log. You'll see the malformed DCC message (no IP or port).

comment:3 Changed 18 years ago by markd@…

Cc: mij@… added

2.8.0 is out and has a DCC related fix. Perhaps the newer version fixes this. Asign to maintainer.

comment:4 Changed 18 years ago by mij@…

Resolution: wontfix
Status: newclosed

xchat2 has been updated to version 2.8.0. Please update and file a new bug if the problem still exists (be sure to assign it to me if you can so I see it).

Note: See TracTickets for help on using tickets.