I have send the tracker a custom ip or hostname enabled, custom ip/hostname is set to a hostname.

In the tracker log file I get this:
/announce?peer_id=-KT21DV-742640061477&port=11801&uploaded=0&downloaded=0&left=0&compact=1&numwant=100&key=114555907&info_hash=%c5%1c%400e%c2%f3~%b0%c88%df%06%c3%95%90*b.T

is this option ignored?

neuron wrote:I have send the tracker a custom ip or hostname enabled, custom ip/hostname is set to a hostname.

In the tracker log file I get this:
/announce?peer_id=-KT21DV-742640061477&port=11801&uploaded=0&downloaded=0&left=0&compact=1&numwant=100&key=114555907&info_hash=%c5%1c%400e%c2%f3~%b0%c88%df%06%c3%95%90*b.T

is this option ignored?

If the hostname cannot be resolved, the ip value in the tracker request will not be used.

the hostname can defenatly be resolved though.

I set it to a mine.nu domain subdomain.

Setup:
my server, updating my mine.nu domain subdomain, and keeping the ip.
my desktop, has only ip's 192.168.0.2, 10.0.0.2, 127.0.0.1.

If I write in the ip my subdomain resolves to it works, and that's the ip I get from pining my subdomain from the desktop computer.

this is defenatly a bug, now I've left the client running for ages, with custom ip set (and I mean ip now, not hostname).

And it worked when I turned it on, but now it's no longer sending the ip.


//some testing:

I restarted application, still didn't work.

Went to settings, removed the ip and turned "send the tracker a custom ip" off, clicked ok, then went into the settings again and set everything back, now it works again.

I will check it out when I find some time.

I have fixed it, it now will be applied properly at startup.

very nice, thank you