Jump to content
Not connected, Your IP: 54.144.55.253

Search the Community

Showing results for tags 'torrent'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • AirVPN
    • News and Announcement
    • How-To
    • Databases
  • Community
    • General & Suggestions
    • Troubleshooting and Problems
    • Blocked websites warning
    • Eddie - AirVPN Client
    • DNS Lists
    • Reviews
    • Other VPN competitors or features
    • Nonprofit
    • Off-Topic
  • Other Projects
    • IP Leak
    • XMPP
    • Mirrors

Product Groups

  • AirVPN Access
  • Coupons
  • Misc

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Twitter


Mastodon


AIM


MSN


ICQ


Yahoo


XMPP / Jabber


Skype


Location


Interests

Found 74 results

  1. This guide will explain how to setup OpenVPN in a way such that only select programs will be able to use the VPN connection while all other life continues as usual. Please read this notice before applying the guide Advantages: fail-free "kill switch" functionality (actually better than 98% of VPNs out there) continue using another VPN as primary or don't reroute any other traffic at all nobody, not even peers on LAN, will be able to connect to your torrent client (the only way: through the VPN connection) - eliminating unintended leaks Disadvantage: the apps will still use your default DNS for hostname lookups (secure your DNS separately!) See two more drawings at the end. The guide is applicable to all VPN providers who don't restrict their users to use the OpenVPN client. The method however is universally applicable. It was made with examples from Windows, but with Linux/BSD you will only need little tweaking to do. Specifically, net_gateway placeholder may not available and that's all there is to it. Android clients are probably too limited for this task and lack options we need. - Since there'll be a lot of text, sections titled in (parantheses) are entirely optional to read. The other guide by NaDre is old (2013), hard to read and pursues a slightly different approach. A Staff member actually posted a good first comment there, that's what we're gonna do. (Preface) The BitTorrent as a network is entirely public. Through the decentralized technology called DHT, everyone in the world can find out what torrents you are presumably participating in (this does not apply to private trackers who disable DHT). Clearly this creates an unhealthy atmosphere for privacy of users, e.g. one could find out the OS distribution one is using for a more targetted attack etc. Sometimes the ISPs are outright hostile to peer-to-peer technologies due to the traffic and bandwidth these are consuming. Instead of upgrading dated infrastructure, they cripple their users instead. There are many reasons to use a VPN, that was but a limited selection. ("Split-tunneling") This has become somewhat a marketing term nowadays, but actually explains the nature of the traffic flow well. In this guide only the programs set to use the VPN connection will use it, nothing else. All your traffic goes past the VPN while torrent client traffic (or any other selected program) uses only the VPN connection. ("Kill switch") We'll literally nail it using software settings of your program (the torrent client). This is a marketing-loaded name. In short: if the VPN connection is not available, no traffic ought to be sent bypassing it. In most cases where you have a VPN redirect all your system traffic - you should not rely on it as a feature. The OpenVPN software on Windows is not 100% proof, based on empirical evidence (reconnects and startup/shutdown phases) and some other VPN providers do no better (based on comments and stories). The only bulletproof solution: the VPN tunnel is set up on an intermediary device your PC is connected to - your end device (the PC) has no chance whatsoever to bypass the tunnel in that case. If the VPN provider uses a firewall under the hood, that's good too but with this guide you will not need a firewall nor rely on the VPN software. ("Dual-hop") With the knowledge and methods from this guide you will be able to daisy-chain multiple VPN servers. In essence, your traffic passes PC->VPN1->VPN2->Destination. This was not intended for this guide nor with AirVPN, it's finicky and I wouldn't recommend it myself without a real need and skills to automate the setup and configuration. How it will work Many users (aka mostly idiots on Reddit) are running in circles like qBittorrent is the only client (or probably the only application in the universe, unconfirmed) that can be set to use a certain VPN. Here's the technicality: this is called 'binding' - you can 'bind to IP' which will force the app to use a specific IP address and nothing else. If it cannot use the IP (when VPN is disconnected) then it will not be able to do any networking at all. The OS will deny any communication with the internet: boom! Here's your praised 'kill switch' and 'split-tunneling', 2-in-1. This is the next best bulletproof solution (the only better alternative is to use an intermediary VPN device, as any software could choose a different interface now to communicate with the internet). In a broader sense, you want to 'bind to a network interface' - your client will use any available IPs from the VPN interface - making it ready for IPv4 and IPv6. Oh and you don't need to change the IP once the VPN connection changes to another server. The OS handles the rest. Examples of programs that can bind to user-defined addresses include: (Windows) ping, tracert (IPv6-only, WTF?), curl and wget, and many others, including your favorite torrent client You will find guides online how to do that in your client or just look in settings. (Linux-specific differences of the guide) If you are a Linux/*nix user, there're some minor changes to the quick guide below: * Create custom VPN interface: Create with ip tuntap command. The below line will create 5 interfaces "tun-air1" etc. for YOUR user. Specifying your user allows OpenVPN to drop root rights after connection and run under your user (security). AirVPN allows up to 5 connections. If you have no use for this, create only one. user="$(whoami)"; for i in {1..5}; do sudo ip tuntap add dev "tun-airvpn$i" mode tun user "$user" group "$user"; done Check their existance with ip -d a -- the interfaces will not be shown under /dev/tun* ALTERNATIVE: openvpn --mktap/--mktun. See manual with man openvpn * Select custom VPN interface: This config part differs from Windows, very confusing. Steps: 1. Replace "dev-node" in config with "dev" 2. Add "dev-type tun" or "tap". Example of config: # if you have these defined multiple times, last entries override previous entries dev tun-airvpn1 # previously dev-node dev-type tun # previously "dev tun" on Windows There're no more differences. In-depth explanation: If you try to use dev-node like for Windows, you will see: OpenVPN log: ERROR: Cannot open TUN/TAP dev /dev/tun-airvpn1: No such file or directory (errno=2) Example strace of error: openat(AT_FDCWD, "/dev/tun-airvpn1", O_RDWR) = -1 ENOENT (No such file or directory) OpenVPN cannot find the TUN/TAP with the name? No, on Linux/*nix/*BSD dev-node has a totally different meaning. Dev-node specifies where the control interface with the kernel is located. On Linux it's usually /dev/node/tun, for the "mknode" command. If OpenVPN can't detect it for some reason, then you'd need to use dev-node. Finally you can start OpenVPN from terminal: sudo openvpn --config 'path/to/config.ovpn' --user mysystemusername --group mysystemusergroup Windows Quick Guide Go to the folder where you installed OpenVPN and its exe files: 'C:\Program Files\OpenVPN\' Open CMD inside the 'bin' folder: Hold Shift + Right Click the 'bin' folder -> 'Open Command Window here' We will use tapctl.exe to create a new VPN network interface solely for use with AirVPN (to look around: run "tapctl.exe" or "tapctl.exe help") C:\Program Files\OpenVPN\bin>tapctl create --name AirVPN-TAP {FDA13378-69B9-9000-8FFE-C52DEADBEEF0} C:\Program Files\OpenVPN\bin> A TAP interface is created by default. I have not played enough with Wireguard's TUN to recommend it. You can check it out, it will be under adapters in your Windows network settings Important: Configure your app/torrent client to use this 'AirVPN-TAP' interface. This is what ensures your traffic never leaks. It may appear under a different name, in such case find out which one it is in the output of 'ipconfig /all' (enter this into CMD) If your client does not allow to bind to a general interface but a specific IP (poor decision) then connect to the VPN first to find out the local IP within the VPN network. In this case with AirVPN you may only use one single server or you'll have to constantly change the IP in settings. Generate AirVPN configs where you connect to the server via IPv4! This is important Add these to the .ovpn config files (either under 'Advanced' on the config generator page or manually to each config file) # NOPULL START route-nopull # IF YOU DO NOT USE ANOTHER VPN THAT TAKES OVER ALL YOUR TRAFFIC, USE "net_gateway" (just copy-paste all of this) # net_gateway WILL BE AUTOMATICALLY DETERMINED AND WILL WORK IF YOU CONNECT THROUGH OTHER NETWORKS LIKE A PUBLIC WIFI # personally, due to a second VPN, I had to specify my router IP explicitly instead of net_gateway: 192.168.69.1 # "default"/"vpn_gateway"/"remote_host"/"net_gateway" are allowed placeholders for IPv4 route remote_host 255.255.255.255 net_gateway route 10.0.0.0 255.0.0.0 vpn_gateway route 0.0.0.0 0.0.0.0 default 666 route-ipv6 ::/0 default 666 dev-node AirVPN-TAP # END OF NOPULL Test if the configuration works. Full tests, don't leave it up to chance. In-depth explanation of the OpenVPN config route-nopull rejects any networking routes pushed to you by the server, we will write our own route remote_host 255.255.255.255 <router IP> we tell our system that, to reach remote_host (the AirVPN server IP), it must send traffic to <router IP>. The subnet mask 255.255.255.255 says that this only applies to this single IP set <router IP> to be net_gateway (only for Windows users, check availability on other platforms) <router IP> may be any of the OpenVPN placeholders too, for example "net_gateway" should work universally (you avoid hard-coding the router IP and if it ever changes: wondering years later why the config no longer works) <router IP> is "192.168.1.1" in my case, for my home router that connects me to the internet. route 10.0.0.0 255.0.0.0 vpn_gateway we tell our system that all 10.x.x.x traffic will be sent to the AirVPN server the internal VPN network with AirVPN is always on the 10.0.0.0 - 10.255.255.255 network range. The subnet mask reflects that. However this may interfere with other VPNs if you ever need to be connected to both at once. I will not go into detail on this. What you need to do is to be more specific with 10.x.x.x routes in this config, i.e. instead of /8 subnet, only route the specific /24 subnet of the current VPN server (AirVPN uses a /24 subnet for your connections on each VPN server -> 10.a.b.0 255.255.255.0) vpn_gateway is one of OpenVPN placeholders route 0.0.0.0 0.0.0.0 default 666 allow routing of ANY traffic via the VPN we set the metric to 666, metric defined as path cost (historically) so setting it to a high value will make sure no normal connection runs through it, unless specifically bound to the VPN IP. route-ipv6 ::/0 default 666 same for IPv6. How many can claim they have working VPN IPv6 setup? Welcome in the future. IPv6 is over 20 years old at this point anyhow. dev-node AirVPN-TAP (Windows-only) tell OpenVPN to ONLY use this network interface to create the VPN tunnel on. Nothing should interfere with our setup now That's all, folks! Note: Somehow on Windows my AirVPN connection receives a wrong internal IP that doesn't enable networking at first. In my case I need to wait 1-3 minutes until OpenVPN reconnects itself based on ping timeout: after the reconnect I receive another IP and everything starts to work. I do not know whether it's an OpenVPN or a Windows bug. One last note: using multiple VPNs Actually this will work, that's how I roll. As long as both VPNs don't clash by using the same 10.0.0.0/8 subnet. If this happens, you will need to change Line 5 to point to a more specific (aka smaller) subnet tailored to your AirVPN server. Specifying a 10.x.x.0/24 subnet for routing will surely do (subnet mask: 255.255.255.0). Just be aware that you cannot practically use the same IP range in both networks at the same time (well, you'd need to bind the application you are using to either interface, which you cannot do with a browser or the printing service in case of internal resources). (The story of broken net_gateway) For this placeholder, OpenVPN attempts to determine your 'default gateway', i.e. the router all your internet traffic passes through. It normally works, but may not be supported on other platforms (Linux, sigh). However it has one unintended side-effect: if you already have a VPN that reroutes all your traffic, net_gateway will make all AirVPN traffic go through the first VPN: Your traffic -> VPN1 -> Internet Torrent traffic -> VPN1 -> AirVPN -> Internet That's the unintended dual-hop. Surely you can extend that scheme to 3,4,n-hops if you fiddle enough with routing, subnet masks and correct order. I'm not responsible for headaches We avoid that behavior with Line 4 from our config - the remote_host line forces the AirVPN traffic to go straight to the internet (through your LAN router). One more thing: net_gateway is not available for IPv6 routes in OpenVPN. That's why it currently only works with a IPv4 connection to the VPN server. (Crash course: Subnet masks) You've seen the weird number 255.0.0.0 above. You should refer to other pages for a proper explanation, but basically this is a very simple way for computers to determine the range of IP addresses that are part of a network (a subnet). What's simple for computers is very hard to grasp for us humans. 255 means there are NO changes allowed to the first set of IP numbers. I.e. the 10 in 10.0.0.0 always stays a 10. 0 means all numbers can be used. I.e. the zeroes in 10.0.0.0 can be (0-255), lowest address is 10.0.0.1 and the last address is 10.255.255.254 (technically, 10.0.0.0 is the first and the last 10.255.255.255 is reserved for 'broadcast') Any number in between denotes ... a range in between. 2^(32-prefix)=number. Number is the amount of available addresses and prefix is called the subnet prefix. Both are meant to describe the same thing. For 10.0.0.0/26 or 10.0.0.0 with subnet mask of 255.255.255.192 you get addresses in range 10.0.0.0-10.0.0.64 -- 2^(32-26) = 64. Similarly you can convert the subnet mask into the prefix number and work from there; or eyeball it: 256-192 = 64. (Two ways to accomplish routing) If you have two equal routes, e.g. 0.0.0.0 goes through VPN with metric 666 0.0.0.0 goes through LAN router with metric 10 then obviously the default route for a packet will travel through (2) - because it's a cheaper path. Unless an application specifies to talk only on the VPN interface. However a different rule applies whenever a more specific route exists 0.0.0.0/0 goes through VPN2 with metric 666 0.0.0.0/0 goes through LAN router with metric 10 0.0.0.0/1 goes through VPN1 with metric 30 128.0.0.0/1 goes through VPN1 with metric 30 Here the routes (3) and (4) cover the entire addressing space, just like 0.0.0.0/0. However because they are more specific, they'll be preferred for all traffic because these routes are more selective. This is how OpenVPN does override system routing with VPN routing by default. This is also what the other guide attempted as well, by pushing four {0,64,128,192}.0.0.0/2 routes. Since that was more specific, it would in return override the 0,128 routes and so on. We can calculate how many multi-hops we would be able to do with this method: IPv4 has 32 bits, we will not touch the last 8 bits of the subnets. That leaves us then with 24 bits or 24 maximum amount of hops. Theoretically. The routing table would be outright f---- to look at. This method is a bit more 'secure' in a way because you don't need to rely on overriding a certain metric value, you just slap a more specific route on top and it's automatically made default. Also you don't need to override the default gateway (router) and all that junk. However with my preferred method (first) you can quite easily do DIY dual-hop routing: 0.0.0.0/0 goes through VPN2 with metric 666 0.0.0.0/0 goes through LAN router with metric 10 0.0.0.0/1 goes through VPN1 with metric 30 128.0.0.0/1 goes through VPN1 with metric 30 <VPN2-IP>/32 goes through VPN1 with metric (any) Such a setup will make sure that all traffic destined for the internet (hits 3 and 4) will go through VPN1. If a program specifies the VPN2 network interface, then VPN2 will be reached via VPN1 first (you->VPN1->VPN2). This is quite 'quizzacious' to set up/control. Not part of this guide. As a part of this guide we told the system to route VPN2 via router on LAN. Yet you could indeed chain multiple VPNs this way and force the VPN1 to not only catch all traffic but also be chained via multiple VPNs itself so you would not need to manually set programs. I've seen scripts online for that purpose. Although be aware of MTU issues due to encapsulation. Troubleshooting tips TEST. SERIOUSLY, TEST YOUR SETUP BEFORE ENGAGING YOUR DATA CANNONS! A couple hours now are infinitely many times more worth than a 'leaked' mistake and headaches later on. https://ipleak.net/ - tests your client's default connection route. It would not tell you if your client is alternatively available on LAN for example. If you followed this guide and set up your client correctly, it will not be available on LAN etc. See the images below: 'without interface binding' (most newbie users) and 'with interface binding' (this guide) Wireshark to inspect how the traffic is actually flowing. Follow online tutorials, you only need to select the right network interfaces and filter traffic by port/IP (tcp/udp and your local or VPN IP) curl to send network requests. Like ifconfig.co / ifconfig.io will respond with the IP address it sees you as: curl --interface <your computer IP> http://ifconfig.co curl --interface 192.168.1.42 http://ifconfig.co # for IPv4 or IPv6, default route curl -4 http://ifconfig.co curl -6 http://ifconfig.co > route -4 print and > route -6 print on Windows. To compare the outputs, you can use Notepad++ with the compare plugin (you need two documents open, one in left and another in right pane before comparing). PS: AirVPN configuration generator does not support #comment lines. Please fix. Sorry Linux users, maybe another time I will write something tailored to you. But I believe you are smart cookies and will adapt the OS-specific steps to fulfill this guide's goal.
  2. for the past 2 days IPLeak is resolving DNS verrryyy slowly and getting 0 results with 100 errors, while there are 2 DNS IP one each IPv4 and IPv6. active torrent is not working as the link does not download anything.
  3. Am trying to setup up qBittorrent with my AirVPN app to prevent the bittorent app from working when AirVPN isn't active. I read from this post here that it's possible to set qBittorrent to use the tun0 interface or activate the network lock using Eddie. In the settings of my Eddie app, I see my VPN interface is called utun1 and see this same option under the advanced settings of the qBittorrent app -- as well as options for utun0, utun2, and utun3. Lastly, is it better to just use Network Lock instead?
  4. I use airVpn only for torrenting. And now everytime I connect to your service, through the eddieUI I will connect to no seeders, nor peers. Not using the vpn is no problem on the other hand. If I start downloading a torrent file nothing happens, unless I restart the utorrent client. Sometimes needs a couple of restarts. This is very annoying and should not be happening and has not been happening before. I have a forwarded port and I tried another.
  5. Since the beginning of using your service I have been using it for torrenting without any problems. But after a period of no use I have come back to your service(my subscription and settings were still active though) and most torrents show the trackers disabled. This is happening when I try to download from public trackers and a few private ones aswell. Other private ones do work though. So my question is, why suddenly am I having this problem, is it my setup/settings or do simply some trackers blacklist vpn servers? Although on every tracker you see ads that provoke using vpn´s... Note, I have tried 3 different server from 3 different countries, tried multiple ports and checked every port. Thanks in advance.
  6. The main TPB URL appears to be inaccessible on many servers. I am not sure whether this is due to TPB being blocked by the VPN server provider's ISPs or whether TPB is blocking IPs (never heard of this before). This can be checked by entering https://thepiratebay.org/ into https://airvpn.org/routes/ I can also see that UK servers are being routed through NL, presumably to bypass ISP blocks, though I am unable to access the site via UK servers. For anybody else experiencing this problem, it is still accessible via the Tor network @ http://uj3wazyk5u4hnvtk.onion/
  7. Someone I might know has found recently while torrenting the download speed suddenly drops dramatically to almost zero and on many occasions the modem router suddenly loses line sync. Prior to disconnection openvpn (running in a terminal window) reports numerous possible replay attacks. Setup is Ubuntu 16.06 LTS running openvpn with ovpn files from config generator (keys separate, hosts resolved). Numerous different servers and ports have been tried. ovpn files modified to run update-resolv-conf on up / down. ipv6 disabled in grub.cfg. ufw used to deny all incoming ports except 67,68/udp 80,443/tcp and the airvpn mapped port over tcp (further restricted to tun0 interface). Are they just being paranoid or is their ISP or some other actor able to detect torrent activity and cause the router to disconnect?
  8. So, here we go again. The Persei server located in California refuses to magnet link ANYTHING or download torrents from rarbg.to at decent speeds. But a few days ago it was just fine and fast as usual. I had this problem a few months ago, and once last year as well, and now it is back. Again. I have to switch servers, any server (Heze or Aquila in California or Pisces in Canada), then do the magnet link, THEN it downloads. If I then switch back to Persei it downloads, eventually. Also, the Status of most every URL in the Trackers is "Not Working" when I am on Persei server. But, right now I am on Pisces in Canada and most all are Working. Once I got back to Persei, Not Working again. There is something with RARBG and Persei server that they just don't like each other all the time. It goes away in a few weeks and everything works fine, then it comes back again. Does anyone have any idea what this is?
  9. I have been going through a headache since installing a new hard drive and fresh OS install. Eddie works fine, but once I start to torrent the speeds go down very fast. I never had this issue on my previous OS install. I could torrent many files and still surf with relative ease. This is not happening now and I do not know what the issue it. I have two previous posts asking for help. Here: https://airvpn.org/topic/29841-copy-old-settings-file-of-eddie-to-new-os/?view=findpost&p=78316 (It seemed resolved after trying the suggested fix there, for one day, but then went back to being slow again today) and my first post here: https://airvpn.org/topic/29761-connection-issues-after-fresh-os-install/ Attached is a copy of my log. All the "AEAD Decrypt error: bad packet ID" start when I turn qBittorrent on and start downloading. Please help. This is perplexing me as to why this is happening. I always had fast torrenting and able to still surf the net before. It's as if once I start torrenting my connection get's capped or tunneled. ALL torrents lose speed WAY down and I can hardly load a web page. The second I turn torrent off, back to be normal. Eddie_20181008_023110.txt
  10. I have AirVPN all set up and running great on a pf Sense router that my home network sits behind. I am trying to get port forwarding set up for torrenting on a server running Windows Server 2016. As far as I can tell everything is set up exactly as it should be but I just can't get it to work. I am connected to Metallah. I have created the forwarded port on the AirVPN site. I have the port open in my Windows firewall. I have the port forwarded in pfSense. I have my torrent client configured to listen on the port I've set up in AirVPN and pfSense and I have my torrent client running with an active torrent trying to download. I have verified that the port is open and can be connected to on my LAN. I have tried 2 different torrent clients (qBittorrent and Deluge) as well as a port listener tool that simply opens any port you specify on TCP or UDP and just listens for connections. When I check the port on the AirVPN site I get error 110 timeout. I've also tried other sites and tools for performing external tests on that port and they all indicate that the port is not open. I have tried creating several new ports on AirVPN (at least 4) and tested on multiple computers on my network all with new corresponding NAT rules in pfSense. No matter what I do I can't get port forwarding to work and I'm at my wits end. I hope someone can help me figure this out. Here is a screenshot of my NAT rule in pfSense.
  11. Hi I've recently upgraded my service with my ISP to a faster speed. Haven't changed any setting in Eddie but now have noticeable decline in speed and stability. Especially noticeable with torrents. I've usually gotten up to speeds of 3mb and steady transfer but now have sudden drops to 0 and not reaching higher than 1mb before doing so. The service upgrade from cox was supposed to double my internet speeds which has been working when not using eddie. Using latest utorrent and haven't changed any of the preferences than before. Have gone through most of settings recommended on the forums which all seemed to work previously. Attaching log, are there any new changes I should be making? Protocols for eddie are set to automatic, and the only ovpn directives added were mssfix to 1430 which after re-checking didn't seem to change and I left it the same.
  12. Hay! So I recently bought myself a subscription of 3 days just to test things out, and so far I am completely and utterly lost. My initial reasons for buying the vpn services was to torrent, however are there things I NEED to know first? Do I need to connect anything to something? I use deluge if that helps. I tried looking into the FAQ and sadly everything on it is just a bit too TECHNICAL for me to fully understand Sadly I'm an idiot when it comes to understanding things and very nervous about all of this, since this is again new to me I'm sorry for bothering anyone (and hopefully I didnt post in the wrong forum O_O)
  13. I have set up AirVPn on Pfsense according to the guide here in the forums and running well for many years. Also port forwarding worked flawless in the past. Some days ago I started Vuze to do some torrenting and and wondering about the slow speeds. The NAT/Firewall test revealed that only the port forwarding for UDP packets seem to work. The test for incoming TCP connection always times out. Please see attached NAT-rule from my pfsense box. Worked flawless in the past and I have not changed any configuration. Whats wrong ?
  14. Hello everybody, it's my first time using torrent, that's why I am a little bit paranoid. I configured everything, port-forwarding, network-lock, checked via IPleak and so on. And everything seems to be fine. But it's odd, that during AirVPN connection the speed of qTorrent is much higher (shouldn't there be no connection at all during that phase?) and afterwards it drops a little. I am not concerned about the speed, just about any IP leaks. I attached screenshots of all my configurations. Can you please check. Maybe i am too paranoid, but better safe than sorry!
  15. Hi, After I've forwarded the right port in AirVPN client area and put the right settings in qBittorrent, I finally get great speeds while connected to the VPN service. However, the speeds (for torrents), seem to fluctuate heavily between 0 and 200Mbit (my max speed). I have the feeling it is because of some setting or limit somewhere that high speeds cannot be sustained. Here is a screenshot of the Eddie speed: More info: - Using network lock - Using OS X 10.12.6 - Using an SSD - Using Asus AC-3200 router - Only using the utun3 network interface in qBittorrent - Used settings described here for qBittorrent - Disabled firewall on router - Looked for any settings in my router that might impede sustained speed like ICMP flood detection but cannot find those - Using port forwarding in client area Is this normal behaviour? I don't really mind it for the time being, as speed is much faster than before, however maybe I'm missing a setting that could prevent this?
  16. My torrent speeds are much slower when connected to AirVPN. I'm just getting frustrated now because I usually look around forums for solutions, but I've tried about everything and its no use x - port forwarding x - protocols x - utorrent preferences x - different torrent programs x - different servers And I know its not a torrent problem because when I use my connection without vpn I get 7-12 mbps but with I get 300 - 600 kbps. I'm out of ideas and was hoping someone could help me.
  17. I've searched on this forum for multiple suggestions and nothing is working....... I Created a new port, Put said port in ubittorrent port listening box... made sure UPnP is off/random port is off. Pressed okay. tested port thru airvpn port client area.... message i got back is connection timeout.. checked on canyouseeme.org, got a connection timeout. YET im downloading the torrent however at VERY slow speeds. (200mb/s) I did the process again, but this time i left the box open when i created a port so it can create a random one, and i entered it in bittorrent client, and same as above happened... connection refused. What am i doing wrong???? im selecting UDP+TCP for port. is that right?
  18. Hi There! Recently I'm having issues with my connection speed. I used to be able to hit about 1.25 MBs on torrents, but about 2 weeks ago I noticed a massive slowdown in speed, now I'm lucky if I can hit 100 KBs. I've tried switching around servers with lower latency, changing the protocol connection settings without any meaningful change in speed. I have a port forwarding enabled, so I tried changing the enabled forwarded port with no change in speed. When disconnected from the VPN, speed on the torrent is about 3 MBs. I ran a speedtest on the website Down: 32.699 Mbit/s Out, 12.695 Mbit/s In (38%), 20MB - Up: 10.437 Mbit/s Out, 8.565 Mbit/s In (82%), 20MB - Date: Tue, 25 Jul 2017 23:27:29 GMT - Buffers: 20MB/20MB - Laps: 3, Time: 86.50 secs I'm on a windows machine using the AirVPN client and Vuze 5.7.5.0 for torrents, Speed should be well above what I'm getting while torrenting, and I can't figure out where the throttle is. Any thoughts?
  19. Hi all, The screenshot below shows the struggles I've been having with AirVPN, since I bought a subscription yesterday My internet connection is 30 mbit, but I already know from experience without vpn that the provider delivers a consistent 10 mbit connection (something they won't fix), However, since I joined AirVPN the p2p capacity has grinded to a halt! Using a private torrent subscription, I normally download 1mb/s, and I still seem to be able to reach those speeds for a few minutes per hour, but the rest of the time the speeds are reduced to 50kb/s max. I've set up Deluge to only listen on a specific port, which I received through this website, but it seems to no avail. Looking at the eddie log, it appears that the slowdown either started or ended around the 9:50 mark (I wasn't tracking when I took the screenshots), and would really like to consistently receive quicker speeds. Is there anything I can try? I've already tried a few different servers and did the general reading-up on the forum.
  20. Hi, AirVPN Community I just join the AirVPN community. I choose AirVPN becomes its open privacy policies and some advance features like SSL over VPN. However, the Torrent download speed got me disappointed a little. I did some speed test before I used Torrent client. My Wifi Download speed was around 50 mbps and it dropped to 38~ mbps after I connected to AirVPN. This is understandable since I know using VPN is bound to have some performance hit. At the end of the day, I was still able to stream 4k. So, it was all good. Yet, when I tried BitTorrent to download something. The difference was too drastic. I could go from a download speed of 3~4 Mbyte/s when I NOT connected to AirVPN to somewhere around 300~1000 Kbyte/s when I connected. The maximum torrent download speed with AirVPN connection I have seems was only around 1.2 Mbyte/s. That was about 80% drop in performance. I have set up remote port forwarding, disable UPnP port mapping and NAT-PMP. It didn't help. I think since I could reach to 38~ mbps on Youtube with AirVPN, the only two explanations will be either AirVPN is not friendly to p2p, or my Torrent client and setting is not friendly to AirVPN. I have tried pBittorrent but It was the same story. Could you please share your thoughts on why would this happen? Thank you very much! ======================================================================================================================================================================= Update#1 I followed this post:https://airvpn.org/topic/23389-p2p-connection-slow-no-matter-what-i-do/ I changed the protocols to SSL:443, and used Ubuntu torrent to test the speed. It's working perfectly and I can see my speed went up to 8 Mbyte/s. I don't know why it needs to be obfuscated with SSL. If anyone knows the reason, please let me know. Thank you! ======================================================================================================================================================================= Update#2 The bottleneck seems came from UDP Protocols. TCP Protocols is working fine as well. My guess is UDP Protocol drops too many packets between me and vpn server. I cannot get those losing packets from vpn server due to its UDP. So I had to keep requesting for losing packets from peers which makes other peers less likely to passing me more packets, or some of them simply just got timeout.
  21. hi i note that it is impossible to download torrent on the french torrent website http://www.cpasbien.cm and torrent 411 help me, which server can allow any download ? thanks a lot
  22. I'm not sure if it is a problem or just a harmless bug or something, but my upload speed goes well into the mb's when I use a torrent client, even though the client (Tixati) informs me that my upload is below the 1 mb. Without using a torrent client my upload speed is as expected, mostly at zero and then sometimes shooting towards 440 kbit/s or less but just for a second. I tried finding answers but only found one thread about this on this forum and it didn't contain a solution or even an explanation. So if someone can shed some light on this, that would be most welcome.
  23. Hi, When I'm torrenting, I notice that I'm getting sometimes (random) disconnected. I see some post about that but without any "good" response. I'm using eddie 2.12.4 on linux and qbittorrent I notice that when using the simple OpenVPN client I get no problem at all...May be it's just a coincidence...Or the problem is with some servers and the way they are chosen is different. Any ideas are welcome ;-)
  24. Hello, I'm having an issue where I cannot download torrents since I did port forwarding. I forwarded my port through the website because qBittorrent had a yellow "connection status." I set the port in qBittorrent, and now the "connection status" is green, but torrents are not downloading. I did this yesterday, and when I initially forwarded my port, it was working just fine, and today it's not. Also, I was able to run the "TCP Test" and got a green light yesterday. I ran it today, and it stays gray. Not sure what that means, but figured I should include that info. Any suggestions? Thank you, all
×
×
  • Create New...