View Issue Details Jump to Notes ] Issue History ] Print ]
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 
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.
Additional Informationhttp://forum.amule.org/thread.php?threadid=12025&sid= [^]
TagsNo tags attached.
Fixed in Revision
Operating SystemAny
Attached Files

- Relationships

-  Notes
(0002583)
Xaignar (manager)
2008-02-17 02:56

Do you still experience this problem using current SVN?
(0002727)
vir (reporter)
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 (manager)
2008-07-10 10:53

Does this still happen?

- Issue History
Date Modified Username Field Change
2007-01-10 22:38 snp New Issue
2007-01-10 22:38 snp Operating System => Any
2008-02-17 02:56 Xaignar Note Added: 0002583
2008-03-19 10:48 vir Note Added: 0002727
2008-03-19 10:55 vir Note Edited: 0002727
2008-07-10 10:53 Wuischke Note Added: 0002863
2008-07-10 10:53 Wuischke Status new => feedback


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker