Bug 213752

Summary:	Switching the method to get the IP to use for DCC file transfers doesn't work at runtime
Product:	[Applications] konversation	Reporter:	Eike Hein <hein>
Component:	dcc	Assignee:	Bernd Buschinski <b.buschinski>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	konversation-devel
Priority:	NOR
Version:	Git
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:

Description Eike Hein 2009-11-08 20:45:25 UTC

Starting with "Reply From IRC Server", switching to "Network Interface" or "Specify Manually" at runtime didn't make newly-started transfers use either setting. This used to work, i.e. it's a regression.

Comment 1 Bernd Buschinski 2010-01-09 16:57:01 UTC

Just for the record, I am still not sure howto handle the bug, but I guess it is not our bug.

What I do to reproduce this is:
Starting konv with Specify Manually 127.0.0.1 Active
-> sending works correct
Changing to Network Interace Passive
-> sending works
Changing back to Specify Manually 127.0.0.1 Active
-> sending fails

On the first and last Specify Manually+Active send I send the same
IP(numerical 2130706433) and port, on the first send the receiver gets the correct IP(numerical 2130706433), everything fine.
On the third send I still send correct Ip and port but now the receiver gets
my external IP and a different port, I have no clue who changes it, it could be my router or the irc server, but I send the correct IP so... no clue

Comment 2 Eike Hein 2010-01-09 17:05:43 UTC

I'm not convinced this is the bug I was experiencing, however. In the case that led me to file the report, the way that I determined the IP to be wrong was to see it being wrong in the transfer panel's listview. How could the router or server influence that?