![]() Just before coming back to this ticket and reading your post, then I also just finished testing another VPN I have from older times, tigervpn, where I got both as life-time accounts previously, and same happens there(qbittorrent on win10 VM, so libtorrent 1.2.6). I checked another site ipleak, which listed the communication transcript, or some of it, and there lists both announces and stopped even etc, and afterwards same with started event etc. If getting an announce with additional &IP, &IPv4 or &IPv6 field, then I believe it lists only one line for each announce, with the extra included IP listed after the main one(SRC address of announce packet), so on same line, and when seperate lines, then it's seperate announces, unless i'm wrong. I just checked this time in my win10 VM on linux(virtualbox with bridged networking), and not the other win10 physical machine of family memember, but always where the same before, and/so shouldn't make a difference.ītw, I check on the ipmagnet website directly, as when just checking the tracker status in qbittorrent for the ipmagnet torrent, then it states 'IP: VPN-IP', but it presumably only lists last announce gotten(as shows latest status report from tracker there), as on website then lists two entries as seperate lines on each new announce, one with own public IPv4 address and one with VPN public IPv4 address. ![]() Then as per your question, it states succesfully listening on: It lists that it detects external IP of VPN and next line same with my real IP. ![]() Yes, TAP adapter installed through 's community client installer. Windscribe, through 's community client, with windscribe's ovpn configs added. I tested this in a windows 10 VM(deluge-lt1.2.7/qbt-lt1.2.6), and stationary win10 machine(deluge-lt1.2.7), and linux stationary machine(deluge-lt1.2.7 - arch linux - not affected here). Btw, I hope i'm not misunderstanding something fundamentally here, in which case, I apologize in advance. As you state, would be nice working out-of-the-box. They limits/binds connectivity to specific interface's name/IP. I don't experience this during a binding to network interface of TAP device in qbt. ![]() Firstly, I much apologize, as somehow got in my head that the latest qbittorrent installer for windows was using libtorrent 1.2.7, but remembered wrong, and was 1.2.6. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |