I've confirmed it with Amule, Shereaza and Neoloader. I thought this was a new interaction but I've found reports of the behaviour dating back to 2011 and was originally reported when sending to shereaza clients. * (old - and relatively major): sending to some clients (particularly amule) stalls out and fails before uploading a single chunk. * (new): 'enable import parts' only activates on a per-session basis (it's not saved)

* (quite old it's in 0.5* too): When importing downloads, the location of the last import isn't remembered, so one must navigate to the directory containing the partfiles each time This post has been edited by stoatwblr: 22 June 2021 - 01:39 PM (*) The test host has one main address using nm-team and a bunch of macvlan attachments behind it with real world IPv4 addresses (doing this gives each interface its own mac address which simple IP aliasing doesn't do - that makes firewalling much easier) So it looks like this is a wine/windows issueĪdditionally, TCPdump shows no UDP traffic on the 'unwanted' IP addresses(*), so it looks to be a false alarm I'll check with some older binaries and get back to you

It's no longer built for windows (*nix/macos only). If the bindaddr directive is being used then the TCP/UDP and Kad UDP ports should _all_ use them.ĭoes it look different if Windows build of amule was run under Wine?

Amule 2.3.2 mac