Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[dingelen]

When I'm not downloading/uploading anything, I have over 2000 connections registered in my router going to port 6881 (torrent port) which register as unreplied. This seems to clog up my network connection by times.

If I turn the P2P service off, this number falls to a few dozen.

The modem is up-to-date with DD-WRT firmware and the NAS also has the latest 2.03 firmware.

Does anyone else have this problem? Is there a solution for it?

Thanks!



Nee.   Protocol   Tijdsoverschrijding (s)   Bron Adres   Remote Adres   Servicenaam   Status
1   UDP   53   219.245.67.170   192.168.2.163   6881   UNREPLIED
2   UDP   50   194.42.150.239   192.168.2.163   6881   UNREPLIED
3   UDP   50   125.27.234.1   192.168.2.163   6881   UNREPLIED
4   UDP   42   59.146.0.45   192.168.2.163   6881   UNREPLIED
5   UDP   4   86.19.104.12   192.168.2.163   6881   UNREPLIED
6   UDP   1   192.168.0.2   88.244.158.35   29620   ASSURED
7   UDP   56   192.168.0.2   184.144.210.193   51413   UNREPLIED
8   UDP   30   192.168.0.2   78.244.203.182   51413   UNREPLIED
9   UDP   54   213.87.101.131   192.168.2.163   6881   ASSURED
10   UDP   40   182.19.186.13   192.168.2.163   6881   UNREPLIED
11   UDP   52   80.39.238.3   192.168.2.163   6881   UNREPLIED
12   UDP   8   197.1.237.196   192.168.2.163   6881   UNREPLIED
...
...
...
2120   UDP   7   186.247.6.39   192.168.2.163   6881   UNREPLIED
2121   UDP   55   192.168.0.2   78.159.136.43   10293   UNREPLIED
2122   UDP   34   46.232.228.176   192.168.2.163   6881   UNREPLIED
2123   UDP   1   46.27.0.216   192.168.2.163   6881   UNREPLIED
2124   UDP   47   114.25.150.218   192.168.2.163   6881   UNREPLIED
2125   UDP   22   192.168.0.2   94.23.28.50   51413   UNREPLIED
2126   UDP   89   220.136.8.127   192.168.2.163   6881   ASSURED
2127   UDP   18   189.48.248.54   192.168.2.163   6881   UNREPLIED
2128   UDP   11   113.151.149.114   192.168.2.163   6881   UNREPLIED
2129   UDP   56   208.114.155.157   192.168.2.163   6881   UNREPLIED
2130   UDP   44   186.225.150.186   192.168.2.163   6881   UNREPLIED
2131   UDP   35   192.168.0.2   60.44.150.174   26387   UNREPLIED
2132   UDP   95   142.176.56.225   192.168.2.163   6881   ASSURED
2133   UDP   58   175.139.66.28   192.168.2.163   6881   ASSURED
2134   UDP   47   211.246.237.32   192.168.2.163   6881   UNREPLIED
2135   UDP   46   192.168.0.2   114.40.220.172   15726   UNREPLIED
2136   UDP   40   126.57.181.198   192.168.2.163   6881   UNREPLIED
2137   UDP   57   60.52.125.30   192.168.2.163   6881   UNREPLIED
2138   UDP   31   213.113.213.74   192.168.2.163   6881   UNREPLIED
2139   UDP   60   183.62.37.109   192.168.2.163   6881   UNREPLIED
2140   UDP   47   1.22.217.57   192.168.2.163   6881   UNREPLIED
2141   UDP   36   101.51.189.85   192.168.2.163   6881   UNREPLIED
2142   UDP   45   192.168.0.2   5.139.197.25   6881   ASSURED

[ivan]

I would assume this is normal for any device that has been used as a p2p server - your IP is listed and the p2p clients check if it is up and running.

We have a similar problem at times only with us it is FTP - we don't use p2p.  20 thousand attempts at ports 20 and 21 in a couple of hours does tend to slow things down a bit but so far the firewall has kept them out.

[albert]

Turning on P2P service itself (without active torrent) should not result in unwanted network connections. The rule of thumb is to use non-standard P2P port (> 1024) and disable ICMP reply on the router. Use IP filtering if your P2P client support, unfortunately the NAS built-in one doesn't!!

In short, time to change the P2P client.