When using both ipv4 and ipv6, tixati is not announcing ipv6 address to the tracker, can you fix that?

It will announce the IPv6 address if it's set to IPv6 prefered or IPv6 only.

See this http://forum.tixati.com/support/1503/

sure about that? because in ipv6 prefered it will not send ip (2.16), did not tried ipv6 only because i would need tracker with ipv6 address to test it :)

Is the tracker in question on IPv6?

I use Tix on a tracker that is accessible via v4 and v6, v4 prefered connects to the tracker via v4 and tracker gets the v4 address, v6 prefered connects to the tracker via v6 and tracker gets the v6 address.

my tracker has only ipv4 address, so if yours has ipv6, client probably connects with both, but is not sending either, tracker is using connection ips

just sniff packets, you will see that tixati is not sending ip parameter, not matter settings

if i use utorrent2, deluge, transmission it will announce ipv6 to the same tracker

what Iam talking about is this
https://wiki.theory.org/BitTorrentSpecification#Tracker_Request_Parameters  + this http://www.bittorrent.org/beps/bep_0007.html

ofc tracker gets your ip from connection, but thats entirely something else

here is the example what i would like to see

GET /announce?peer_id=aaaaaaaaaaaaaaaaaaaa&info_hash=aaaaaaaaaaaaaaaaaaaa
&port=6881&left=0&downloaded=100&uploaded=0&compact=1
&ipv6=2001%3A%3A53Aa%3A64c%3A0%3A7f83%3Abc43%3Adec9&ipv4=261.52.89.12

both ips announced, if using both networks

this is a really flawed "feature" in the tracker protocol, I am not surprised it is not supported by Tixati, and I know it is not used by any of the major trackers

it would allow anyone to stuff a tracker full of bogus IPs... there is no verification mechanism for the extra IP parameter

the source address of the request is the only address a tracker should pay attention to.  Anything else is asking for DDoS fun.

If you need IPv6 tracking, set up a tracker with an IPv6 address.  It's simple and it works perfectly.  This IPv4/6 crossover nonsense was ill-conceived to begin with (like many many other parts of the BitTorrent protocol and ecosystem in general).

On public trackers, sure.

But on private trackers it has a use. People behind proxies needing to announce the correct IP, or again announcing IPv4 or v6 address when connection from the other.

there are risk to everything, that why it should be optional, but for example transmission, bitorrent, deluge, vuze etc all announce ipv6, if you have one, sending custom ips is different matter

and as mentioned before, private trackers mostly benefit from this

any progress on this? maybe we could get param (ipv6) in individual tracker options so we can use it in alias and manually send ipv6 to the tracker

any hope with this?

still think if you are using ipv4/ipv6 prefered connection mode, it should announce both ips, as it does to pex