Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › Kimsufi IP banned from public torrent trackers?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Kimsufi IP banned from public torrent trackers?

iceTwyiceTwy Member
edited May 2014 in Help

I got a Kimsufi KS-1 server a couple of weeks ago. Ever since, I've had issues with public torrent trackers - I haven't tested private ones -. Out of the four major public trackers (OpenBitTorrent, PublicBT, iStoleIt, Demonii), I can only connect to Demonii. Transmission comes up with the following error: "Announce error: Connection failed" for the three others.

I've triple-checked my network settings, and I've used three different clients (Deluge 1.3.4 & 1.3.6, rTorrent 0.9.4/libtorrent 0.13.4, Transmission 2.8.2) on two different distros (Debian 7 & Arch) to track the cause of my issue. I use an iptables config that I use across different VPS and I haven't had any problem with it.

The only logical explanation I can come up with is that my server IP may have been banned from those public torrent trackers. Could that be possible?

«1

Comments

  • wychwych Member

    @joodle - how are your trackers?

  • HC_RoHC_Ro Member

    Use Magnet links.

  • iceTwyiceTwy Member

    @HC_Ro said:
    Use Magnet links.

    I do.

  • harisharis Member

    ovh could also make it impossible for your server to connect to the trackers, I find it more logical instead of trackers doing it.

  • iceTwyiceTwy Member
    edited May 2014

    @haris said:
    ovh could also make it impossible for your server to connect to the trackers, I find it more logical instead of trackers doing it.

    I've talked to a few people on IRC, and it seems that public trackers work wonders on their Kimsufi boxes. There isn't any reason OVH would have blocked my server from accessing those trackers since I haven't been abusing torrents in any way since I've had the server. Which makes the whole situation even stranger.

  • linuxthefishlinuxthefish Member
    edited May 2014

    Was working before...

    Still can't reach full 100mbit though :(

  • BlazeMuisBlazeMuis Member

    @wych said:
    joodle - how are your trackers?

    They all work fine for me

  • zhuanyizhuanyi Member

    How did u guys set up Transmission? I kept getting Permission Denied after my torrents start to download for a while. Tried both Debian and Ubuntu and got the same error. Tried to change the download folder to 755 and have chown to have it run under transmission-daemon and that didn't help.

  • linuxthefishlinuxthefish Member

    @zhuanyi said:
    How did u guys set up Transmission? I kept getting Permission Denied after my torrents start to download for a while. Tried both Debian and Ubuntu and got the same error. Tried to change the download folder to 755 and have chown to have it run under transmission-daemon and that didn't help.

    I use the ubuntu desktop with x2go installation template.

  • zhuanyizhuanyi Member

    @linuxthefish said:
    I use the ubuntu desktop with x2go installation template.

    x2go has pre-compiled Transmission?

    I still prefer to use the apt-get install rather than reinstalling my entire server since I have already got a few things running on it.

  • hostnoobhostnoob Member

    Maybe the trackers are down? If it's an old torrent maybe they changed the tracker URL since then?

  • linuxthefishlinuxthefish Member
    edited May 2014

    @zhuanyi said:
    I still prefer to use the apt-get install rather than reinstalling my entire server since I have already got a few things running on it.

    If it's a server with cli only then install transmission-daemon and configure the webgui. If you have a desktop installed on your server, install transmission package from apt-get.

    They should both work, but be aware torrenting will rape your disk and bandwidth, making server kinda useless for anything else.

  • NeoonNeoon Community Contributor, Veteran

    Maybe OVH is pissed and blocking torrents now?

    Thanked by 1linuxthefish
  • zhuanyizhuanyi Member

    @linuxthefish said:
    If it's a server with cli only then install transmission-daemon and configure the webgui. If you have a desktop installed on your server, install transmission package from apt-get.

    By default I think the download folder for Transmission is in /root/downloads, I am wondering if Debian/Ubuntu locks down any folder in /root/ to only permit access by root account even if you change the ownership of the folder.

    Do you have the download folder outside of /root? Or if it is in /root/, what is the permission for it?

    linuxthefish said: They should both work, but be aware torrenting will rape your disk and bandwidth, making server kinda useless for anything else.

    The only other thing it does it to backup my PC using CrashPlan, and my pathetic bandwidth at home is the primary reason why I don't want to do this again....

  • linuxthefishlinuxthefish Member

    @zhuanyi

    Running a torrent client as root is a bad idea, i run mine as the user "desktop", and use the download folder /home/desktop/Downloads.

    If you want to use /root/downloads as a download folder when running transmission as a non root user then you will need to set the permissions on that folder accordingly.

  • tridinebandimtridinebandim Member

    opening dht in torrent program helps to gain more peers (dont know if it causes any issue)

  • J1021J1021 Member

    I've no problems pushing 100Mb/s up for hours a day on torrents.

  • iceTwyiceTwy Member
    edited May 2014

    @Infinity580 said:
    Maybe OVH is pissed and blocking torrents now?

    OpenBT, PublicBT and iStoleIt are all used to share both legal and illegal torrents, which means that if OVH were to block those trackers, they'd also block a good part of legit torrents. Plus, some people don't seem to be running into any issues.

    @linuxthefish said:
    Was working before...

    Yep... exactly that. Only Demonii is working - how odd.

  • ATHKATHK Member

    Can you ping them from the box?

  • AlexanderMAlexanderM Member, Top Host, Host Rep

    Is it possible because the trackers have hundreds of peers in the DC they are rate limiting IP's etc?

  • texteditortexteditor Member

    It's because of UDP

  • NyrNyr Community Contributor, Veteran

    Public trackers banned multiple datacenters yesterday in the (European) morning. This is the case with LeaseWeb too for example, not a problem with OVH.

    I suspect this has to do with DoS prevention more than anything else. If you want to use the trackers, you are going to need a proxy.

    Thanked by 1Mark_R
  • zhuanyizhuanyi Member
    edited May 2014

    @linuxthefish said:
    zhuanyi

    Running a torrent client as root is a bad idea, i run mine as the user "desktop", and use the download folder /home/desktop/Downloads.

    If you want to use /root/downloads as a download folder when running transmission as a non root user then you will need to set the permissions on that folder accordingly.

    I tried to run it under debian-transmission account but that is where I got the permission denied error.

    The only way I managed to get it to work now is to start a screen (like the program) and run transmission-daemon -f as root and that seems to resolve all the issue. However this is far from a neat solution.

  • nunimnunim Member

    @Nyr said:
    Public trackers banned multiple datacenters yesterday in the (European) morning. This is the case with LeaseWeb too for example, not a problem with OVH.

    I suspect this has to do with DoS prevention more than anything else. If you want to use the trackers, you are going to need a proxy.

    This seems quite silly as many people run Seedboxes out of OVH, do you have any news articles or related information to this "ban" ?

  • NyrNyr Community Contributor, Veteran
    edited May 2014

    nunim said: This seems quite silly as many people run Seedboxes out of OVH, do you have any news articles or related information to this "ban" ?

    Many people do, but it is a very little percentage compared to people torrenting from their houses. Additionally boxes on datacenters can always use DHT, in comparison to restrictive or crappy networks where a tracker does really help.

    Sorry, I don't have any further public info at this time nor I do know if this is temporary or not.

  • iceTwyiceTwy Member
    edited May 2014

    Right, I've found the issue after digging on Kimsufi's forums and other sources. A whole block (/24 or more?) of IPs from OVH is being blocked by AMS-IX, and unfortunately the connection from Kimsufi servers to many trackers (OpenBT, PublicBT and iStoleIt included) goes through AMS-IX.

    Apparently, some Kimsufi customers who asked OVH's support about the situation were told that OVH is not willing to fix the issue with AMS-IX.

    My IP is in the 5.39.89.0/24 block and my box is at the RBX5 DC, fyi. Does OVH usually accept requests to change IPv4 addresses? If not, the only solution would be to cancel my Kimsufi server subscription and reorder another one.

  • VladorzVladorz Member
    edited May 2014

    @nunim
    http://torrentfreak.com/public-bittorrent-trackers-ban-piracy-monitoring-outfits-140523/

  • iceTwyiceTwy Member

    Here are traceroutes to OpenBT, PublicBT and iStoleIt:

    $ traceroute tracker.openbittorrent.com
traceroute to tracker.openbittorrent.com (31.172.63.252), 30 hops max, 60 byte packets
 1  vss-9a-6k.fr.eu (5.39.89.253)  1.221 ms * *
 2  rbx-g1-a9.fr.eu (91.121.131.155)  2.245 ms  2.636 ms  2.612 ms
 3  ams-1-6k.nl.eu (94.23.122.186)  5.682 ms ams-1-6k.nl.eu (94.23.122.114)  5.677 ms ams-1-6k.nl.eu (178.33.100.239)  5.632 ms
 4  ams-ix.as39138.net (195.69.147.245)  10.433 ms  11.092 ms  11.075 ms
 5  te-2-1-800.bbr-dtm-01.de.infra.rrbone.net (31.172.1.10)  11.709 ms  11.687 ms  11.865 ms
 6  * * *
 7  * * *
 8  * * *
 9  * * *
[...]
30  * * *
    $ traceroute tracker.publicbt.com      
traceroute to tracker.publicbt.com (31.172.63.226), 30 hops max, 60 byte packets
 1  vss-9a-6k.fr.eu (5.39.89.253)  232.780 ms * *
 2  rbx-g2-a9.fr.eu (91.121.131.157)  0.795 ms  1.094 ms  1.064 ms
 3  ams-5-6k.nl.eu (91.121.131.174)  5.548 ms * ams-5-6k.nl.eu (178.33.100.231)  5.453 ms
 4  ams-ix.as39138.net (195.69.147.245)  11.971 ms  11.944 ms  11.900 ms
 5  te-2-1-800.bbr-dtm-01.de.infra.rrbone.net (31.172.1.10)  11.444 ms  11.689 ms  11.575 ms
 6  * * *
 7  * * *
 8  * * *
 9  * * *
[...]
30  * * *
    $ traceroute tracker.istole.it   
traceroute to tracker.istole.it (192.121.121.30), 30 hops max, 60 byte packets
 1  vss-9a-6k.fr.eu (5.39.89.253)  1.075 ms * *
 2  rbx-g2-a9.fr.eu (91.121.131.157)  1.114 ms  1.387 ms  1.355 ms
 3  ams-5-6k.nl.eu (178.33.100.231)  47.394 ms * ams-5-6k.nl.eu (91.121.131.174)  47.309 ms
 4  20ge-amsix.ams1.nl.portlane.net (195.69.145.25)  6.269 ms  6.135 ms  6.139 ms
 5  te-2-2.sto5.se.portlane.net (80.67.4.178)  27.831 ms  27.809 ms  27.760 ms
 6  xe-0-0-8-dcp-demarc.pe1.sto5.se.portlane.net (80.67.0.162)  27.969 ms  28.159 ms  27.968 ms
 7  te3-1.v1650.cr1.sth1.as13214.net (192.121.86.239)  28.416 ms  28.301 ms  28.003 ms
 8  * * *
 9  * * *
[...]
30  * * *
  • J1021J1021 Member

    I'm blocked from accessing open.demonii.com from my IPv4 address but not my IPv6 address.

    root@ns3282823:~# ping6 open.demonii.com PING open.demonii.com(2001:bc8:3400:102::1) 56 data bytes 64 bytes from 2001:bc8:3400:102::1: icmp_seq=1 ttl=56 time=13.8 ms 64 bytes from 2001:bc8:3400:102::1: icmp_seq=2 ttl=56 time=42.8 ms 64 bytes from 2001:bc8:3400:102::1: icmp_seq=3 ttl=56 time=8.77 ms 64 bytes from 2001:bc8:3400:102::1: icmp_seq=4 ttl=56 time=29.8 ms 64 bytes from 2001:bc8:3400:102::1: icmp_seq=5 ttl=56 time=10.7 ms 64 bytes from 2001:bc8:3400:102::1: icmp_seq=6 ttl=56 time=46.3 ms ^C --- open.demonii.com ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5006ms rtt min/avg/max/mdev = 8.774/25.401/46.307/15.192 ms root@ns3282823:~#

    Anyway to configure my transmission-daemon setup to connect using IPv6 when available?

  • hostnoobhostnoob Member

    @iceTwy said:
    Here are traceroutes to OpenBT, PublicBT and iStoleIt:

    $ traceroute tracker.openbittorrent.com
> traceroute to tracker.openbittorrent.com (31.172.63.252), 30 hops max, 60 byte packets
>  1  vss-9a-6k.fr.eu (5.39.89.253)  1.221 ms * *
>  2  rbx-g1-a9.fr.eu (91.121.131.155)  2.245 ms  2.636 ms  2.612 ms
>  3  ams-1-6k.nl.eu (94.23.122.186)  5.682 ms ams-1-6k.nl.eu (94.23.122.114)  5.677 ms ams-1-6k.nl.eu (178.33.100.239)  5.632 ms
>  4  ams-ix.as39138.net (195.69.147.245)  10.433 ms  11.092 ms  11.075 ms
>  5  te-2-1-800.bbr-dtm-01.de.infra.rrbone.net (31.172.1.10)  11.709 ms  11.687 ms  11.865 ms
>  6  * * *
>  7  * * *
>  8  * * *
>  9  * * *
> [...]
> 30  * * *
    $ traceroute tracker.publicbt.com      
> traceroute to tracker.publicbt.com (31.172.63.226), 30 hops max, 60 byte packets
>  1  vss-9a-6k.fr.eu (5.39.89.253)  232.780 ms * *
>  2  rbx-g2-a9.fr.eu (91.121.131.157)  0.795 ms  1.094 ms  1.064 ms
>  3  ams-5-6k.nl.eu (91.121.131.174)  5.548 ms * ams-5-6k.nl.eu (178.33.100.231)  5.453 ms
>  4  ams-ix.as39138.net (195.69.147.245)  11.971 ms  11.944 ms  11.900 ms
>  5  te-2-1-800.bbr-dtm-01.de.infra.rrbone.net (31.172.1.10)  11.444 ms  11.689 ms  11.575 ms
>  6  * * *
>  7  * * *
>  8  * * *
>  9  * * *
> [...]
> 30  * * *
    $ traceroute tracker.istole.it   
> traceroute to tracker.istole.it (192.121.121.30), 30 hops max, 60 byte packets
>  1  vss-9a-6k.fr.eu (5.39.89.253)  1.075 ms * *
>  2  rbx-g2-a9.fr.eu (91.121.131.157)  1.114 ms  1.387 ms  1.355 ms
>  3  ams-5-6k.nl.eu (178.33.100.231)  47.394 ms * ams-5-6k.nl.eu (91.121.131.174)  47.309 ms
>  4  20ge-amsix.ams1.nl.portlane.net (195.69.145.25)  6.269 ms  6.135 ms  6.139 ms
>  5  te-2-2.sto5.se.portlane.net (80.67.4.178)  27.831 ms  27.809 ms  27.760 ms
>  6  xe-0-0-8-dcp-demarc.pe1.sto5.se.portlane.net (80.67.0.162)  27.969 ms  28.159 ms  27.968 ms
>  7  te3-1.v1650.cr1.sth1.as13214.net (192.121.86.239)  28.416 ms  28.301 ms  28.003 ms
>  8  * * *
>  9  * * *
> [...]
> 30  * * *

    It's not being blocked by AMS-IX in those traceroutes though

Sign In or Register to comment.