Why some bittorrent clients can connect to mine even if I have blocked their port?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












0














I am using transmission as my bittorrent client. I tried to block most Thunder(Xunlei) clients with



-A INPUT -p tcp -m tcp --sport 15000 -j REJECT --reject-with icmp-port-unreachable
-A INPUT -p udp -m udp --sport 15000 -j REJECT --reject-with icmp-port-unreachable
-A OUTPUT -p tcp -m tcp --dport 15000 -j REJECT --reject-with icmp-port-unreachable
-A OUTPUT -p udp -m udp --dport 15000 -j REJECT --reject-with icmp-port-unreachable


in iptables filter table, as 15000 is default port of Thunder. However, there is also some Thunder clients with port 15000 connected to me and downloading from me. Why do these iptables rules not work?










share|improve this question





















  • try turning transmission off and on again after you have applied your rules
    – Arthur2e5
    Dec 16 at 18:51











  • @Arthur2e5 These are not transmission settings. They are iptables rules.
    – Steven Yang
    Dec 17 at 4:01










  • That is for making sure the new connections don't do certain things. As for the other connections, uTP and its hole punching might end up moving the ports up a few numbers.
    – Arthur2e5
    Dec 17 at 16:43










  • I started a new transmission-daemon on another machine with the same iptables rules applied. There are also some Thunder clients with port 15000 connect to and download from me when I start a new torrent. In fact, if I block their IP instead of port, they will disappear suddenly in my peer list.
    – Steven Yang
    Dec 17 at 17:25
















0














I am using transmission as my bittorrent client. I tried to block most Thunder(Xunlei) clients with



-A INPUT -p tcp -m tcp --sport 15000 -j REJECT --reject-with icmp-port-unreachable
-A INPUT -p udp -m udp --sport 15000 -j REJECT --reject-with icmp-port-unreachable
-A OUTPUT -p tcp -m tcp --dport 15000 -j REJECT --reject-with icmp-port-unreachable
-A OUTPUT -p udp -m udp --dport 15000 -j REJECT --reject-with icmp-port-unreachable


in iptables filter table, as 15000 is default port of Thunder. However, there is also some Thunder clients with port 15000 connected to me and downloading from me. Why do these iptables rules not work?










share|improve this question





















  • try turning transmission off and on again after you have applied your rules
    – Arthur2e5
    Dec 16 at 18:51











  • @Arthur2e5 These are not transmission settings. They are iptables rules.
    – Steven Yang
    Dec 17 at 4:01










  • That is for making sure the new connections don't do certain things. As for the other connections, uTP and its hole punching might end up moving the ports up a few numbers.
    – Arthur2e5
    Dec 17 at 16:43










  • I started a new transmission-daemon on another machine with the same iptables rules applied. There are also some Thunder clients with port 15000 connect to and download from me when I start a new torrent. In fact, if I block their IP instead of port, they will disappear suddenly in my peer list.
    – Steven Yang
    Dec 17 at 17:25














0












0








0


1





I am using transmission as my bittorrent client. I tried to block most Thunder(Xunlei) clients with



-A INPUT -p tcp -m tcp --sport 15000 -j REJECT --reject-with icmp-port-unreachable
-A INPUT -p udp -m udp --sport 15000 -j REJECT --reject-with icmp-port-unreachable
-A OUTPUT -p tcp -m tcp --dport 15000 -j REJECT --reject-with icmp-port-unreachable
-A OUTPUT -p udp -m udp --dport 15000 -j REJECT --reject-with icmp-port-unreachable


in iptables filter table, as 15000 is default port of Thunder. However, there is also some Thunder clients with port 15000 connected to me and downloading from me. Why do these iptables rules not work?










share|improve this question













I am using transmission as my bittorrent client. I tried to block most Thunder(Xunlei) clients with



-A INPUT -p tcp -m tcp --sport 15000 -j REJECT --reject-with icmp-port-unreachable
-A INPUT -p udp -m udp --sport 15000 -j REJECT --reject-with icmp-port-unreachable
-A OUTPUT -p tcp -m tcp --dport 15000 -j REJECT --reject-with icmp-port-unreachable
-A OUTPUT -p udp -m udp --dport 15000 -j REJECT --reject-with icmp-port-unreachable


in iptables filter table, as 15000 is default port of Thunder. However, there is also some Thunder clients with port 15000 connected to me and downloading from me. Why do these iptables rules not work?







iptables bittorrent transmission






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 16 at 17:22









Steven Yang

292




292











  • try turning transmission off and on again after you have applied your rules
    – Arthur2e5
    Dec 16 at 18:51











  • @Arthur2e5 These are not transmission settings. They are iptables rules.
    – Steven Yang
    Dec 17 at 4:01










  • That is for making sure the new connections don't do certain things. As for the other connections, uTP and its hole punching might end up moving the ports up a few numbers.
    – Arthur2e5
    Dec 17 at 16:43










  • I started a new transmission-daemon on another machine with the same iptables rules applied. There are also some Thunder clients with port 15000 connect to and download from me when I start a new torrent. In fact, if I block their IP instead of port, they will disappear suddenly in my peer list.
    – Steven Yang
    Dec 17 at 17:25

















  • try turning transmission off and on again after you have applied your rules
    – Arthur2e5
    Dec 16 at 18:51











  • @Arthur2e5 These are not transmission settings. They are iptables rules.
    – Steven Yang
    Dec 17 at 4:01










  • That is for making sure the new connections don't do certain things. As for the other connections, uTP and its hole punching might end up moving the ports up a few numbers.
    – Arthur2e5
    Dec 17 at 16:43










  • I started a new transmission-daemon on another machine with the same iptables rules applied. There are also some Thunder clients with port 15000 connect to and download from me when I start a new torrent. In fact, if I block their IP instead of port, they will disappear suddenly in my peer list.
    – Steven Yang
    Dec 17 at 17:25
















try turning transmission off and on again after you have applied your rules
– Arthur2e5
Dec 16 at 18:51





try turning transmission off and on again after you have applied your rules
– Arthur2e5
Dec 16 at 18:51













@Arthur2e5 These are not transmission settings. They are iptables rules.
– Steven Yang
Dec 17 at 4:01




@Arthur2e5 These are not transmission settings. They are iptables rules.
– Steven Yang
Dec 17 at 4:01












That is for making sure the new connections don't do certain things. As for the other connections, uTP and its hole punching might end up moving the ports up a few numbers.
– Arthur2e5
Dec 17 at 16:43




That is for making sure the new connections don't do certain things. As for the other connections, uTP and its hole punching might end up moving the ports up a few numbers.
– Arthur2e5
Dec 17 at 16:43












I started a new transmission-daemon on another machine with the same iptables rules applied. There are also some Thunder clients with port 15000 connect to and download from me when I start a new torrent. In fact, if I block their IP instead of port, they will disappear suddenly in my peer list.
– Steven Yang
Dec 17 at 17:25





I started a new transmission-daemon on another machine with the same iptables rules applied. There are also some Thunder clients with port 15000 connect to and download from me when I start a new torrent. In fact, if I block their IP instead of port, they will disappear suddenly in my peer list.
– Steven Yang
Dec 17 at 17:25
















active

oldest

votes











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489348%2fwhy-some-bittorrent-clients-can-connect-to-mine-even-if-i-have-blocked-their-por%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489348%2fwhy-some-bittorrent-clients-can-connect-to-mine-even-if-i-have-blocked-their-por%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown






Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay