View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001417aMuleTransferpublic2008-09-21 12:382008-09-21 12:38
Reporterpedromc 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusnewResolutionopen 
PlatformOSOS Version
Product Version2.2.2 
Target VersionFixed in Version 
Summary0001417: "Bind Address" and UPnP not working together
DescriptionMy system has several IPs for several devices and a few alias.

I have set amule to "Bind Address" to 192.168.1.200, an IP alias (eth0:0) for the main IP (192.168.1.2/eth0). When I enable UPnP I get the ports open in the router but the ports are forwarded to the IP 192.168.1.2 and not 192.168.1.200, as it should. The result is that no traffic gets back to amule.

When I set the router to forward the ports to the 192.168.1.200 it works great.
Additional InformationI want the amule traffic to have a different IP so I can traffic shape it for low priority.

If amule had an option to set the DSCP to a given value (like ktorrent), it would be a better solution to help traffic shaping (I will open a feature request for this). Even so, UPnP and "Bind Address" not working together is a bug anyway.
TagsNo tags attached.
Fixed in Revision
Operating SystemLinux
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2008-09-21 12:38 pedromc New Issue
2008-09-21 12:38 pedromc Operating System => Linux


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker