aMule Bug Tracker - aMule
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001037aMuleExternal Connpublic2007-01-10 22:382008-07-10 10:53
Reportersnp 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusfeedbackResolutionopen 
PlatformOSOS Version
Product Version2.1.3 
Target VersionFixed in Version 
Fixed in Revision
Operating SystemAny
Summary0001037: 20070109 "bind address" doesn't work correctly
DescriptionIf computer has 2 addresses (e.g. main 172.22.1.2 and alias 172.22.1.4) and I filled "bind address" field with address 172.22.1.4, aMule still uses main address 172.22.1.2 to make outgoing connections instead of using given address.
Steps To Reproduce
Additional Informationhttp://forum.amule.org/thread.php?threadid=12025&sid= [^]
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2007-01-10 22:38snpNew Issue
2007-01-10 22:38snpOperating System => Any
2008-02-17 02:56XaignarNote Added: 0002583
2008-03-19 10:48virNote Added: 0002727
2008-03-19 10:55virNote Edited: 0002727
2008-07-10 10:53WuischkeNote Added: 0002863
2008-07-10 10:53WuischkeStatusnew => feedback

Notes
(0002583)
Xaignar   
2008-02-17 02:56   
Do you still experience this problem using current SVN?
(0002727)
vir   
2008-03-19 10:48   
(edited on: 2008-03-19 10:55)
This is due to the limitation of wxwidgets 2.6 (outgoing tcp connection source address can not be specified).
I use this patch to fix that issue:
http://vir.otvt.ru/amule/amule-bind-fix.diff [^]
This is rather dirty hack, but it works for me. Tested on debian (sarge and etch).
Also, building with wxwidgets >= 2.7 may help.

edited on: 03-19-08 10:55
(0002863)
Wuischke   
2008-07-10 10:53   
Does this still happen?