| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001417 | aMule | Transfer | public | 2008-09-21 12:38 | 2008-09-21 12:38 |
|
| Reporter | pedromc | |
| Assigned To | | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | |
| Platform | | OS | | OS Version | |
| Product Version | 2.2.2 | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0001417: "Bind Address" and UPnP not working together |
| Description | My 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 Information | I 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. |
| Tags | No tags attached. |
|
| Fixed in Revision | |
| Operating System | Linux |
|
| Attached Files | |
|
Relationships 
Relationships 