0001666: Setting bind address should also set request source address

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0001666

aMule

Misc

public

2011-04-27 00:40

Reporter

morph

Assigned To

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

new

Resolution

open

Platform

OS Version

Product Version

2.2.6

Target Version

Fixed in Version

Summary

0001666: Setting bind address should also set request source address

Description

Hello,
a Debian user reported this bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609181 [^] (he confirms it's replicable on both 2.2.6 and 2.3.1rc1):

>>>
On machines with more than one address, it is sometimes necessary to
set the bind address for the local service ports. This feature
appears to work correctly. However, this should also change the
source address for requests to the servers such that the address used
by the servers to connect back to the amule session is the address
where the ports are bound.

Consider the case where a host has a local and unroutable primary
address on eth0. By default, TCP requests from this host will be
forwarded through a firewall and give NAT. A second address which is
routable is added to the host. The amule bind address is set to the
second routable address. Yet when the application makes requests to
the servers it will have the NAT address of the firewall instead of
the routable address.

Changing the source address for TCP connections as the bind address
will correct this problem.
<<<

Issue History
Date Modified	Username	Field	Change
2011-04-27 00:40	morph	New Issue
2011-04-27 00:40	morph	Operating System	=> Linux Debian

Relationships

Notes
There are no notes attached to this issue.