I have noticed that since the KNetwork changes, that ktorrent listens on an IPv6-style connection.

$ netstat -an | grep 6881
tcp 0 0 :::6881 :::* LISTEN

When I run an older version (pre-KNetwork) I see that it listened on an IPv4-style socket
$ netstat -an | grep 6881
tcp 0 0 0.0.0.0:6881 0.0.0.0:* LISTEN

When I look thru the ~/.kde/share/apps/ktorrent/log file, it appears that I don't have any successful authentications on this connection...
$ grep "Authentication(S)" log
Authentication(S) to [::ffff:195.135.221.130]:60510 : failure
Authentication(S) to [::ffff:130.89.163.15]:48241 : failure
Authentication(S) to [::ffff:130.89.163.15]:48611 : failure
Authentication(S) to [::ffff:195.135.221.130]:33038 : failure
Authentication(S) to [::ffff:195.135.221.130]:33714 : failure
Authentication(S) to [::ffff:130.89.163.15]:50810 : failure

Is this an issue that requires a bugzilla entry?

PS. Thanks for a great app.

Probably not, it depends why the authentication fails. It could be that you just removed a torrent and that all these connection attempts are from peers who still think you're running that torrent.

The underlying socket classes may have changed, but we still send out the same stuff during an authentication, so I don't see any reason why it would fail.

You should grep for Authentication alone, that will give you a list of all Authentication attempts.

Authentication(S) are incomming connection attempts.

Btw, are there any "Peer ip_address is blacklisted. Aborting connection." messages in the log ?

I don't think this is a problem either. I'm having lots of incoming connections that are successfull.
There could be lots of reasons why your log file shows failed authentications.

George wrote:You should grep for Authentication alone, that will give you a list of all Authentication attempts.

Authentication(S) are incomming connection attempts.

Btw, are there any "Peer ip_address is blacklisted. Aborting connection." messages in the log ?

I have two torrents that finished leeching and have been seeding for over a day. Grep'ing the log file for just Authentication I have 1906 entries. Of those, 405 are failures and 1501 are successful.
I have no Authentication(S) messages that are successful.

There are no messages in the log regarding blacklisted peers.

I just find it strange that the two IP addresses from the Authentication(S) messages that always fail, just so happen to be the two tracker hosts for the two torrents that are currently seeding:
borft.student.utwente.nl. 49044 IN A 130.89.163.15
tracker.opensuse.org. 41 IN A 195.135.221.130

Warren wrote:I just find it strange that the two IP addresses from the Authentication(S) messages that always fail, just so happen to be the two tracker hosts for the two torrents that are currently seeding:
borft.student.utwente.nl. 49044 IN A 130.89.163.15
tracker.opensuse.org. 41 IN A 195.135.221.130

It's strange indeed, and probably a bug.

EDIT: created a bug report https://bugs.kde.org/show_bug.cgi?id=115631

George, could this be the reason why uploads are not counted on some trackers? (e.g. Demonoid.com we talked about)

I don't think so, authentication and the tracker are not related.

Which reminds me, I need to get an account at demonoid.

George wrote:It's strange indeed, and probably a bug.

EDIT: created a bug report https://bugs.kde.org/show_bug.cgi?id=115631

Thanks for committing the "fix". It certainly fixes the torrents that I care about.

Warren wrote:

George wrote:It's strange indeed, and probably a bug.

EDIT: created a bug report https://bugs.kde.org/show_bug.cgi?id=115631

Thanks for committing the "fix". It certainly fixes the torrents that I care about.

Make sure you have the really latest, because I committed another improvement to it.

As it turns out, some clients only send the first 48 bytes and then wait for a reply to send the last 20 bytes.