[Mldonkey-bugs] [bugs #2682] force_client_ip don't work

[spiralvoice]

This mail is an automated notification from the bugs tracker
 of the project: mldonkey, a free e-Donkey client.

/**************************************************************************/
[bugs #2682] Latest Modifications:

Changes by: 
                spiralvoice <address@hidden>
'Date: 
                Tue 12/02/2003 at 19:40 (Europe/Berlin)

            What     | Removed                   | Added
---------------------------------------------------------------------------
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
This patch report is very old. If the bug still exists in current

versions please post a new bug report - spiralvoice






/**************************************************************************/
[bugs #2682] Full Item Snapshot:

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=2682>
Project: mldonkey, a free e-Donkey client
Submitted by: 0
On: Fri 02/28/2003 at 20:35

Category:  Core
Severity:  5 - Average
Item Group:  None
Resolution:  None
Assigned to:  None
Status:  Closed
Release:  None
Release:  2.02-19
Platform Version:  FreeBSD i386-i686
Binaries Origin:  Compiled From CVS


Summary:  force_client_ip don't work

Original Submission:  i run mldonkey cvs 2.02-19 on freebsdd 4.7 

i will to run mldonkey in another ip, so i have to set 2 ip in my system, both 
is public ip. 

then i set "force_client_ip = true" and client_ip with second ip in mldonkey's 
download.ini. but it don't work. 

i use id to see what ip used, unfortunately mldonkey still use first ip to 
comment with server. So i guest force_client_ip can't work with Firewall/NAT, 
too. 



vo 

client_ip = xxx.xxx.209.90 

force_client_ip = true 



id 

For 212.83.54.136:4661  --->   xxx.xxx.209.88 

For 140.115.10.30:4661  --->   xxx.xxx.209.88 

For 207.44.206.27:4242  --->   xxx.xxx.209.88 



Follow-up Comments
------------------


-------------------------------------------------------
Date: Tue 12/02/2003 at 19:40       By: spiralvoice
This patch report is very old. If the bug still exists in current

versions please post a new bug report - spiralvoice

-------------------------------------------------------
Date: Tue 03/18/2003 at 17:53       By: None
client_ip is the IP reported to servers and clients in the protocol stream, not 
the IP used to open sockets.

See bind_addr instead.














For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=2682>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/