Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - FliessendWasser

Pages: [1]
1
Windows / [v3.4.0beta] Average time in queue number high
« on: August 12, 2017, 02:07:48 am »
Hi there.
I'm happy to test out the freshest build of qBittorrent, currently v3.4.0beta (the one that has been released a few days ago).
Besides the huge changes in the code and on the appearance, I noticed that the number mentioned in the statistics under "Average time in queue" appears to be waaaaay higher than in v3.3.15

See:



While in v3.3.15 the number was at 28ms or some number around that, it keeps rising and rising in v3.4.0beta.
I tried limiting the OS cache to 15MiB, with the same effect. Other than that, everything seems to work fine enough. Disabling OS cache did not solve the problem either.

OS: Win10 Home 64-Bit v1703
qBittorrent: v3.4.0beta x64
Qt: 5.9.1
libtorrent: 1.1.4.0
Boost: 1.64.0

2
Windows / NAT-PMP frequently mapping port
« on: July 27, 2017, 11:27:53 pm »
Hello there.

I am used to the comfort of UPnP and qBittorrents functionality to support it. Usually qBittorrent would map the port via UPnP right at the start, once for all.
Lately I noticed that qBittorrent is mapping the port every 42 minutes, but via NAT-PMP, which never worked before on my router (Compal CH7466CE), or at least returned with a failure in the log for not mapping the port.

Now, we had a power outage for one hour due to bad weather conditions here, which obviously forced the router to restart.

This, lets describe it as 'thing', happens via LAN and via WiFi as well. Both PCs run Windows 10 Home 64-Bit with qBittorrent 3.3.14 64-bit (the official version).

Now, I am curious if this is just a normal behaviour or if I need to be somewhat concerned... I did not want to open an issue on GitHub, as it seems not that serious to me. Couldn't find anything relatable on GitHub either.


Excerp of my log:
Code: [Select]
27.07.2017 23:04 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: 64307
27.07.2017 23:04 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: 64307
27.07.2017 22:22 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: 64307
27.07.2017 22:22 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: 64307
27.07.2017 21:40 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: 64307
27.07.2017 21:40 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: 64307
27.07.2017 20:58 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: 64307
27.07.2017 20:58 - UPnP/NAT-PMP: Port mapping successful, message: successfully mapped port using NAT-PMP. external port: 64307

3
Windows / UPnP not working over LAN?
« on: April 13, 2017, 03:01:04 pm »
Hi there.
I am kinda lost now, I'm hoping for your help.

Recently I switched ISPs, implying that I have a new router now (Fritz!Box 6490 Cable). I both have my laptop and my desktop connected to it, both have qBittorrent v3.3.12 x64 installed.
Now, the difference between these two PCs is, that my laptop is connected via WiFi and my desktop via LAN cable - and this seems to make a difference too with UPnP. While my laptops qBittorrent easily maps the needed ports via UPnP, my desktops qBittorrent returns an error "router not found".

Now, restarting both my computer and the router (took it off the power line) did not bring success, neither did disabling and enabling UPnP on the routers interface, or fiddling around in qBittorrents settings. Removing the LAN cable from my desktop and connecting it to the WiFi did bring success, as my desktops qBittorrent now mapped the port.  :-\

Re-installing qBittorrent wasn't successful either.

EDIT: I checked the router's log, just to find that it permitted my desktop to open ports UPnP.
EDIT 2: Deluge successfully opened its used port via UPnP, Tixati reports: "UPNP mapping TCP port 26771 on gateway 192.168.178.1 > error searching: Timed out searching for commands (50178)"
EDIT 3: The firewall is configured correctly for qBittorrent.

OS of desktop: Win10 Home 1703 Build 15063.10
OS of laptop: Win10 Home 1604 Build 14393.1066
(I think the OS could be the problem here, but seeing that it worked on WiFi makes me re-think that part.)

Here an excerp of my log:
Code: [Select]
13.04.2017 14:51 - UPnP/NAT-PMP: Port mapping failure, message: could not map port using UPnP: no router found
13.04.2017 14:51 - UPnP/NAT-PMP: Port mapping failure, message: could not map port using UPnP: no router found
13.04.2017 14:49 - External IP: x.x.x.x
13.04.2017 14:49 - [several fast resumes for torrents]
13.04.2017 14:49 - Options were saved successfully.
13.04.2017 14:49 - GeoIP database loaded. Type: GeoLite2-Country. Build time: Di Apr 4 21:37:44 2017.
13.04.2017 14:49 - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/54864
13.04.2017 14:49 - qBittorrent is successfully listening on interface :: port: TCP/54864
13.04.2017 14:49 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/54864
13.04.2017 14:49 - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/54864
13.04.2017 14:49 - qBittorrent is successfully listening on interface :: port: TCP_SSL/4433
13.04.2017 14:49 - qBittorrent is successfully listening on interface :: port: TCP/54864
13.04.2017 14:49 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP_SSL/4433
13.04.2017 14:49 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/54864
13.04.2017 14:49 - UPnP / NAT-PMP support [ON]
13.04.2017 14:49 - Embedded Tracker [OFF]
13.04.2017 14:49 - Encryption support [ON]
13.04.2017 14:49 - Anonymous mode [OFF]
13.04.2017 14:49 - PeX support [ON]
13.04.2017 14:49 - Local Peer Discovery support [ON]
13.04.2017 14:49 - DHT support [ON]
13.04.2017 14:49 - HTTP User-Agent is 'qBittorrent/3.3.12'
13.04.2017 14:49 - Peer ID: -qB33C0-
13.04.2017 14:49 - qBittorrent is trying to listen on any interface port: 54864
13.04.2017 14:49 - qBittorrent v3.3.12 started

I am really grateful for any help!

4
Windows / "Slow" speeds in LAN
« on: April 14, 2016, 08:40:34 pm »
Recently, I transferred some files to my laptop from my desktop over the Local Area Network. My desktop has a LAN-line (100mbit/s) directly to the router, my laptop has the best connectivity to the WiFi (72mbit/s - 802.11n)

To get to the point, I tried different BitTorrent-clients (µTorrent, Deluge and qBittorrent) to test the speeds for transferring the same file over and over again, and qB was the slowest by far.

µTorrent to µTorrent = about 4MiB/s
µTorrent to Deluge = about 4MiB/s (and the other way around too)
qBittorrent to µTorrent/Deluge/qBittorrent* = Peaks to 1.6MiB/s, usually about 600KiB/s (same the other way around) -> 3.4.0alpha gave me peaks to 1.8MiB/s

*qBittorrent to qBittorrent resulted in frequent disconnects.

All tests were done with the best circumstances (laptop and PC were the only devices in the network, no inbound/outbound traffic).

Laptop OS: Win7 SP1 Home Premium 64bit
Desktop OS: Win10 Home 64bit

Code: [Select]
qBittorrent: 3.3.4 / 3.4.0alpha
libtorrent: 1.0.8
Qt: 5.6.0
Boost: 1.60.0

Code: [Select]
µTorrent versions: 2.2.1; 3.4.6
Code: [Select]
Deluge: 1.3.12
Python: 2.7
libtorrent: 1.0.9


I'd be glad to be enlightened why this is occuring, and why qBittorrent behaves like this. Thank you in advance :)

If you need aadditional information, I will provide them asap.

// EDIT: I could have put this elsewhere... Mods, do not hesitate to move this thread if it is in the wrong sub-forum.

5
Cafe lounge / IPv6 peer flood
« on: June 20, 2015, 12:24:13 pm »
https://torrentfreak.com/popular-torrents-being-sabotaged-by-ipv6-peer-flood-150619/

This, and a lot of other things concerning µTorrent/BitTorrent just prove that changing to qBittorrent was the best thing I did so far.

- But -
The article states, that it only affects µTorrent (thus BitTorrent too, as they are built from the same scratch).
What about libtorrent, and all other clients out there, like Tixati?


Nevertheless, it shows a perfect example for not downloading copyrighted stuff illegally. If this "peer-attack" comes from anti-piracy groups, their mission probably was successful.

6
Introductions / Beh.
« on: March 07, 2015, 05:31:40 pm »
Hello.

I actually have no idea why I should introduce myself, as I probably won't be a daily user on this forum.

However. I am brot0, a daily qBittorrent user since some months.

My little BitTorrent history begins back when µTorrent 2.2 (or BitTorrent 7.2) got released. Unexperienced and unaware of the power of P2P I randomly downloaded files, without knowing how the system works. After reading some articles (Wikipedia and many other more or less reliable sources), I somewhat got into BitTorrent now.
I've been a user of µTorrent until version 3.3, back then I changed to BitTorrent (not a big difference though), then to Deluge and various other clients.
Right now, I am somewhat stuck with qBittorrent, as µTorrent/BitTorrent has gone adware and other clients can't beat qBittorrent at all. Since version 3.1.12 got released, I am more than satisfied with qBittorrent, as it is stable, fast, reliable with seeding/leeching and... free :)

As a daily user of this program, I'd like to dearly thank the developers at this point for creating the program. When the time has come, I'm going to donate some money, as this software is definitely worth it!

What I nearly forgot to mention is, that I have my little own-coded website. It's not the best-looking one on the internet, but it definitely fulfills its purpose.
Link: http://sumtingwentrong.bplaced.net/
Also, I mirrored both the Mac OS X-version and the Windows-version of qBittorrent on it, in the hope that this is okay with you (which I believe).

Otherwise, if any help is needed with things in translation, I'd be ready to work with you guys. My current vocabulary contains fluent German (as it is my mother tounge), pretty much fluent English, some (bad) French, and a little piece of Swedish (learning it on my own).

~brot0

7
Generic / Implement random port rather than 6881 by default
« on: March 07, 2015, 05:18:45 pm »
Hello there.

I'm a fresh user, as you can see, and during the years I have been trying out various BitTorrent-clients until now. Currently I'm pretty much stuck with qBittorrent, and I'm happy with it.

To come to my point:
As I have seen it many many times, the default port that qBittorrent uses is 6881.
Seen from one side, this has no real matter. From the other side, it is more of a obstacle for some users, as their ISPs throttle a special range of ports (AFAIK 6881-6889).
Advanced users can change this, as I did. But the normal-day user, who more or less accidentially came to qBittorrent might have some problems and would switch to the better known BT-clients, as they probably don't have such problems, just because they set a random port by default.
Now, my question is: Is there the possibility to set a random port by default excluding the port ranges 6881-6889?
My thoughts would go the way, that directly after starting qBittorrent the very first time the default port is anything but the previously mentioned port range.

Pages: [1]