It is really not nice to be doing this when the user has not requested to do this, especially when ip filter is even set to inactive. Happens with both ipv4 and ipv6 connections.
Many people run torrents on privileged ports to escape ISP traffic throttling, or vanity, or whatever reason - nevertheless i don't think anyone wants a single seed or peer to be dropped off because of their port number. Never encountered this kind of port [wording edited Eoin] before, it's an interesting thing to implement on a protocol which tries to maximize connectivity.
This is a brand new install (never tried Halite before) on Win7-64, running on a privileged port itself (making it sure not a single Halite client is going to connect to it...).
Another issue, on this magnet uri
magnet:?xt=urn:btih:546cf15f724d19c4319cc17b179d7e035f89c1f4&dn=Ubuntu+Desktop+GNU%2FLinux+14.04.2+Trusty+Tahr+LTS+x64+64bit+amd64&tr=udp%3A%2F%2Fopen.demonii.com%3A1337&tr=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969&tr=udp%3A%2F%2Fexodus.desync.com%3A6969
leechers-paradise.org:6969 gets truncated into leechers-paradise.or, log entry:
None, Alert Ubuntu Desktop GNU/Linux 14.04.2 Trusty Tahr LTS x64 64bit amd64 (udp://tracker.leechers-paradise.or) (-1) No such host is known (1), Status code: -1, Times 1. ()
Another issue, UI has phantom message "Port nnnnn open" in lower left corner which is not seemingly related to anything, since Halite has been bound to a single port in options (not this one). Checking with netstat, this port is not listening or in use either.
Also wondering how many issues did go unreported because seemingly the only way to do it is to register an account with Github, i'd say 99,99% of people will just quietly drop it instead (i just happened to have way too much time atm). An email account like [email protected] could be rather welcome.