qBittorrent 4.2.5

[anon]

As of version 4.0.4, this client uses an individual peer_id, so it's okay to run both mRatio and qBittorrent at the same time. Also, this emulation has support for the "IP/hostname to report to tracker" feature.

This client emulates the following settings, so make sure your real qBittorrent 4.2.5 also uses them:

Encryption mode: Allow encryption
Optional IP address to bind to: All addresses

[sigduwksnsksis9283]

sorry to ask here anon but since you said qbit uses individual peer_id so it has static key right or no?
cause im seeing different key's on torrents https://i.imgur.com/RMGC1tJ.png & https://i.imgur.com/ZY9ogjg.png (which should be normal for mr tho) so my last bit of paranoia hits me and makes me ask this question... is it still okay if i use qbit(on mr) and seed big files through this on higher level trackers like ggn,ab,ahd,etc and use it to download files normally too since you said it won't cause any trouble...

sorry for these noob questions im just paranoid before i fuckup on upper tier trackers.

[anon]

sorry to ask here anon but since you said qbit uses individual peer_id so it has static key right or no?
cause im seeing different key's on torrents https://i.imgur.com/RMGC1tJ.png & https://i.imgur.com/ZY9ogjg.png (which should be normal for mr tho)

Static and global are two different terms... which I used interchangeably in my previous explanation, sorry :frusty: I've just corrected my posts in the "RatioMaster Plus 2.1" thread.

Here's the summary. In qBittorrent's case, the peer_id and key are static, but not global. So it uses a different pair of values for each torrent (which is the behavior you're seeing in those screenshots) and remembers them when a torrent is stopped and started. The port is global, but can be configured manually to match the real client, so no worries there. In any case, the main idea was correct: in mRatio, it doesn't matter that you can't use the memory reader for qBittorrent, you're okay as long as the port number is the same.

[sigduwksnsksis9283]

Here's the summary. In qBittorrent's case, the peer_id and key are static, but not global. So it uses a different pair of values for each torrent (which is the behavior you're seeing in those screenshots) and remembers them when a torrent is stopped and started.
but when a torrent is stopped and restarted i see both of those being changed so i assume its a common behavior?


The port is global, but can be configured manually to match the real client, so no worries there. In any case, the main idea was correct: in mRatio, it doesn't matter that you can't use the memory reader for qBittorrent, you're okay as long as the port number is the same.
Nice, thanks for the explanation

[anon]

but when a torrent is stopped and restarted i see both of those being changed

I'll look into this...

[sigduwksnsksis9283]

i'll post a detailed report on the mratio thread... this maybe either due to me seeding loads of torrent like 2k-3k right now. so torrents get deleted after each start and ask for confirmation and stuff...

[anon]

I'll look into this...

I was not able to reproduce this problem. The client emulation is configured to use a static, non-global peer_id and key, and mRatio obeyed said behavior during testing.

[silencer1980]

4.3.0 version is out yesterday :))

[anon]

Two requests in one hour, this update must be pretty important... client files for RM+ and mR coming soon.

[silencer1980]

Two requests in one hour, this update must be pretty important... client files for RM+ and mR coming soon.

best regards.

[anon]

I uploaded both yesterday :gwink: And cloud99 did the ones for Extreme Mod, also.