View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001666aMuleMiscpublic2011-04-27 00:402011-04-27 00:40
Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
PlatformOSOS Version
Product Version2.2.6 
Target VersionFixed in Version 
Summary0001666: Setting bind address should also set request source address
a Debian user reported this bug [^] (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.
TagsNo tags attached.
Fixed in Revision
Operating SystemLinux Debian
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- 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

Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker