Jump to content

Suspicious Connections??

Savage.exe

I keep getting connection spam to my sisters computer, they got smart and tried changing the ports and thought I wouldn't see it, A possible DDoS attack perhaps? It lags my internet at times. I also notice they are using the same port the garrys mod server I play on is on.

Here are the logs below, and they are from multiple IPS..

[LAN access from remote] from 134.19.187.45:11241 to 192.168.1.11:27015, Friday, March 24,2017 22:55:57
[LAN access from remote] from 81.161.16.197:25377 to 192.168.1.11:27015, Friday, March 24,2017 22:55:52
[LAN access from remote] from 207.223.29.83:49313 to 192.168.1.11:27015, Friday, March 24,2017 22:55:47
[LAN access from remote] from 61.68.151.192:1105 to 192.168.1.11:27015, Friday, March 24,2017 22:55:42
[LAN access from remote] from 101.190.245.115:48718 to 192.168.1.11:27015, Friday, March 24,2017 22:55:37
[LAN access from remote] from 47.31.1.90:42682 to 192.168.1.11:27015, Friday, March 24,2017 22:55:32
[LAN access from remote] from 124.180.253.75:6881 to 192.168.1.11:27015, Friday, March 24,2017 22:55:26
[LAN access from remote] from 77.234.46.178:6881 to 192.168.1.11:27015, Friday, March 24,2017 22:55:22
[LAN access from remote] from 91.201.68.42:31632 to 192.168.1.11:27015, Friday, March 24,2017 22:55:16
[LAN access from remote] from 45.26.181.101:43481 to 192.168.1.11:27015, Friday, March 24,2017 22:55:12
[LAN access from remote] from 94.140.147.65:23035 to 192.168.1.11:27015, Friday, March 24,2017 22:55:07
[LAN access from remote] from 181.168.192.91:64449 to 192.168.1.11:27015, Friday, March 24,2017 22:55:01
[LAN access from remote] from 110.44.121.35:49111 to 192.168.1.11:27015, Friday, March 24,2017 22:54:56
[LAN access from remote] from 151.72.242.181:19715 to 192.168.1.11:27015, Friday, March 24,2017 22:54:52
[LAN access from remote] from 83.249.173.249:56218 to 192.168.1.11:27015, Friday, March 24,2017 22:54:47
[LAN access from remote] from 162.216.46.30:21294 to 192.168.1.11:27015, Friday, March 24,2017 22:54:41
[LAN access from remote] from 84.52.77.210:44961 to 192.168.1.11:27015, Friday, March 24,2017 22:54:37
[LAN access from remote] from 92.47.179.196:23617 to 192.168.1.11:27015, Friday, March 24,2017 22:54:33
[LAN access from remote] from 180.181.210.49:14125 to 192.168.1.11:27015, Friday, March 24,2017 22:54:27
[LAN access from remote] from 202.159.179.59:50592 to 192.168.1.11:27015, Friday, March 24,2017 22:54:22
[LAN access from remote] from 109.254.97.127:55848 to 192.168.1.11:27015, Friday, March 24,2017 22:54:16
[LAN access from remote] from 219.91.140.244:9220 to 192.168.1.11:27015, Friday, March 24,2017 22:54:11
[LAN access from remote] from 178.207.36.137:56011 to 192.168.1.11:27015, Friday, March 24,2017 22:54:06
[LAN access from remote] from 91.79.232.45:1375 to 192.168.1.11:27015, Friday, March 24,2017 22:54:01
[LAN access from remote] from 91.154.204.95:1352 to 192.168.1.11:27015, Friday, March 24,2017 22:53:57
[LAN access from remote] from 144.131.241.7:21969 to 192.168.1.11:27015, Friday, March 24,2017 22:53:51
[LAN access from remote] from 178.93.45.140:14532 to 192.168.1.11:27015, Friday, March 24,2017 22:53:47
[LAN access from remote] from 203.217.39.39:56998 to 192.168.1.11:27015, Friday, March 24,2017 22:53:41
[LAN access from remote] from 49.193.202.253:1236 to 192.168.1.11:27015, Friday, March 24,2017 22:53:37
[LAN access from remote] from 220.134.71.197:42791 to 192.168.1.11:27015, Friday, March 24,2017 22:53:32
[LAN access from remote] from 180.216.31.119:13797 to 192.168.1.11:27015, Friday, March 24,2017 22:53:27
[LAN access from remote] from 37.79.171.71:14811 to 192.168.1.11:27015, Friday, March 24,2017 22:53:22
[LAN access from remote] from 46.166.137.249:39749 to 192.168.1.11:27015, Friday, March 24,2017 22:53:16
[LAN access from remote] from 182.239.165.106:59380 to 192.168.1.11:27015, Friday, March 24,2017 22:53:12
[LAN access from remote] from 62.183.127.73:58528 to 192.168.1.11:27015, Friday, March 24,2017 22:53:02
[LAN access from remote] from 178.89.89.221:18146 to 192.168.1.11:27015, Friday, March 24,2017 22:52:56
[LAN access from remote] from 159.224.252.180:14966 to 192.168.1.11:27015, Friday, March 24,2017 22:52:52
[LAN access from remote] from 104.238.51.13:11841 to 192.168.1.11:27015, Friday, March 24,2017 22:52:46
[LAN access from remote] from 188.47.126.246:20090 to 192.168.1.11:27015, Friday, March 24,2017 22:52:42
[LAN access from remote] from 1.54.148.183:31106 to 192.168.1.11:27015, Friday, March 24,2017 22:52:36
[LAN access from remote] from 190.218.134.18:39729 to 192.168.1.11:27015, Friday, March 24,2017 22:52:32
[LAN access from remote] from 176.196.35.37:34197 to 192.168.1.11:27015, Friday, March 24,2017 22:52:27
[LAN access from remote] from 176.62.245.178:55409 to 192.168.1.11:27015, Friday, March 24,2017 22:52:22
[LAN access from remote] from 174.1.13.146:1024 to 192.168.1.11:27015, Friday, March 24,2017 22:52:16
[LAN access from remote] from 178.212.225.214:36312 to 192.168.1.11:27015, Friday, March 24,2017 22:52:12
[LAN access from remote] from 178.34.108.231:14873 to 192.168.1.11:27015, Friday, March 24,2017 22:52:07
[LAN access from remote] from 5.141.20.185:43135 to 192.168.1.11:27015, Friday, March 24,2017 22:52:01
[LAN access from remote] from 46.242.13.132:2737 to 192.168.1.11:27015, Friday, March 24,2017 22:51:56
[LAN access from remote] from 109.225.62.191:24856 to 192.168.1.11:27015, Friday, March 24,2017 22:51:51
[LAN access from remote] from 130.105.216.45:12128 to 192.168.1.11:27015, Friday, March 24,2017 22:51:47
[LAN access from remote] from 178.90.253.196:27248 to 192.168.1.11:27015, Friday, March 24,2017 22:51:42
[LAN access from remote] from 76.90.195.232:60485 to 192.168.1.11:27015, Friday, March 24,2017 22:51:37
[LAN access from remote] from 178.137.196.196:37148 to 192.168.1.11:27015, Friday, March 24,2017 22:51:32
[LAN access from remote] from 37.57.235.132:21363 to 192.168.1.11:27015, Friday, March 24,2017 22:51:27
[LAN access from remote] from 5.166.68.35:12063 to 192.168.1.11:27015, Friday, March 24,2017 22:51:17
[LAN access from remote] from 5.139.223.185:64659 to 192.168.1.11:27015, Friday, March 24,2017 22:51:11
[LAN access from remote] from 174.76.19.34:43903 to 192.168.1.11:27015, Friday, March 24,2017 22:51:06
[LAN access from remote] from 41.246.51.107:18035 to 192.168.1.11:27015, Friday, March 24,2017 22:51:01
[LAN access from remote] from 128.70.181.0:16910 to 192.168.1.11:27015, Friday, March 24,2017 22:50:56
[LAN access from remote] from 91.185.250.138:63792 to 192.168.1.11:27015, Friday, March 24,2017 22:50:52
[LAN access from remote] from 188.244.136.184:59146 to 192.168.1.11:27015, Friday, March 24,2017 22:50:42
[LAN access from remote] from 207.161.7.28:53804 to 192.168.1.11:27015, Friday, March 24,2017 22:50:37
[LAN access from remote] from 188.19.15.108:1024 to 192.168.1.11:27015, Friday, March 24,2017 22:50:31
[LAN access from remote] from 197.89.6.222:49155 to 192.168.1.11:27015, Friday, March 24,2017 22:50:26
[LAN access from remote] from 82.13.55.227:1062 to 192.168.1.11:27015, Friday, March 24,2017 22:50:11
[LAN access from remote] from 145.255.3.168:1056 to 192.168.1.11:27015, Friday, March 24,2017 22:50:06
[LAN access from remote] from 86.20.171.250:32878 to 192.168.1.11:27015, Friday, March 24,2017 22:50:02
[LAN access from remote] from 46.166.186.217:35024 to 192.168.1.11:27015, Friday, March 24,2017 22:49:57
[LAN access from remote] from 89.101.219.70:60515 to 192.168.1.11:27015, Friday, March 24,2017 22:49:52
[LAN access from remote] from 85.140.78.171:61828 to 192.168.1.11:27015, Friday, March 24,2017 22:49:46
[LAN access from remote] from 2.132.80.6:50962 to 192.168.1.11:27015, Friday, March 24,2017 22:49:41
[LAN access from remote] from 88.147.223.117:41241 to 192.168.1.11:27015, Friday, March 24,2017 22:49:37
[LAN access from remote] from 46.243.172.178:14667 to 192.168.1.11:27015, Friday, March 24,2017 22:49:32
[LAN access from remote] from 80.101.237.163:1171 to 192.168.1.11:27015, Friday, March 24,2017 22:49:21
[LAN access from remote] from 2.61.172.191:41514 to 192.168.1.11:27015, Friday, March 24,2017 22:49:16
[LAN access from remote] from 37.168.59.169:56768 to 192.168.1.11:27015, Friday, March 24,2017 22:49:06
[LAN access from remote] from 37.209.238.172:47478 to 192.168.1.11:27015, Friday, March 24,2017 22:49:02
[LAN access from remote] from 103.239.86.207:57306 to 192.168.1.11:27015, Friday, March 24,2017 22:48:56
[LAN access from remote] from 42.109.85.148:45245 to 192.168.1.11:27015, Friday, March 24,2017 22:48:52
[LAN access from remote] from 37.212.17.180:52791 to 192.168.1.11:27015, Friday, March 24,2017 22:48:46
[LAN access from remote] from 86.40.147.178:2331 to 192.168.1.11:27015, Friday, March 24,2017 22:48:42
[LAN access from remote] from 217.149.167.132:51156 to 192.168.1.11:27015, Friday, March 24,2017 22:48:36
[LAN access from remote] from 95.133.251.146:23943 to 192.168.1.11:27015, Friday, March 24,2017 22:48:26
[LAN access from remote] from 109.197.141.243:32515 to 192.168.1.11:27015, Friday, March 24,2017 22:48:22
[LAN access from remote] from 115.166.38.202:50584 to 192.168.1.11:27015, Friday, March 24,2017 22:48:17
[LAN access from remote] from 95.158.211.131:31381 to 192.168.1.11:27015, Friday, March 24,2017 22:48:12
[LAN access from remote] from 156.197.152.224:28309 to 192.168.1.11:27015, Friday, March 24,2017 22:48:07
[LAN access from remote] from 122.108.183.37:48698 to 192.168.1.11:27015, Friday, March 24,2017 22:48:02
[LAN access from remote] from 46.166.190.225:34964 to 192.168.1.11:27015, Friday, March 24,2017 22:47:57
[LAN access from remote] from 199.30.251.80:41715 to 192.168.1.11:27015, Friday, March 24,2017 22:47:51
[LAN access from remote] from 61.68.122.237:43145 to 192.168.1.11:27015, Friday, March 24,2017 22:47:42
[LAN access from remote] from 106.71.67.86:40209 to 192.168.1.11:27015, Friday, March 24,2017 22:47:37
[LAN access from remote] from 84.109.193.252:42955 to 192.168.1.11:27015, Friday, March 24,2017 22:47:26
[LAN access from remote] from 180.181.60.150:47664 to 192.168.1.11:27015, Friday, March 24,2017 22:47:22
[LAN access from remote] from 37.214.201.84:27817 to 192.168.1.11:27015, Friday, March 24,2017 22:47:16
[LAN access from remote] from 202.147.206.130:39966 to 192.168.1.11:27015, Friday, March 24,2017 22:47:12
[LAN access from remote] from 185.52.143.57:34028 to 192.168.1.11:27015, Friday, March 24,2017 22:47:06
[LAN access from remote] from 94.180.96.104:1032 to 192.168.1.11:27015, Friday, March 24,2017 22:47:02
[LAN access from remote] from 62.182.200.6:1308 to 192.168.1.11:27015, Friday, March 24,2017 22:46:57
[LAN access from remote] from 188.16.129.183:52257 to 192.168.1.11:27015, Friday, March 24,2017 22:46:47
[LAN access from remote] from 115.45.33.202:60334 to 192.168.1.11:27015, Friday, March 24,2017 22:46:42
[LAN access from remote] from 90.76.156.12:26819 to 192.168.1.11:27015, Friday, March 24,2017 22:46:36
[LAN access from remote] from 176.105.205.183:58191 to 192.168.1.11:27015, Friday, March 24,2017 22:46:32
[LAN access from remote] from 46.53.177.146:60210 to 192.168.1.11:27015, Friday, March 24,2017 22:46:26
[LAN access from remote] from 121.208.234.122:11058 to 192.168.1.11:27015, Friday, March 24,2017 22:46:21
[LAN access from remote] from 93.117.59.175:1081 to 192.168.1.11:27015, Friday, March 24,2017 22:46:16
[LAN access from remote] from 2.92.250.255:19299 to 192.168.1.11:27015, Friday, March 24,2017 22:46:12
[LAN access from remote] from 82.61.156.31:61656 to 192.168.1.11:27015, Friday, March 24,2017 22:46:06
[LAN access from remote] from 145.255.164.214:41494 to 192.168.1.11:27015, Friday, March 24,2017 22:46:02
[LAN access from remote] from 197.87.230.82:56352 to 192.168.1.11:27015, Friday, March 24,2017 22:45:57
[LAN access from remote] from 94.195.83.139:19429 to 192.168.1.11:27015, Friday, March 24,2017 22:45:51
[LAN access from remote] from 185.52.142.173:41540 to 192.168.1.11:27015, Friday, March 24,2017 22:45:47
[LAN access from remote] from 38.132.117.206:27182 to 192.168.1.11:27015, Friday, March 24,2017 22:45:42
[LAN access from remote] from 174.98.168.83:23116 to 192.168.1.11:27015, Friday, March 24,2017 22:45:37
[LAN access from remote] from 176.97.215.47:58494 to 192.168.1.11:27015, Friday, March 24,2017 22:45:32
[LAN access from remote] from 41.250.126.178:58749 to 192.168.1.11:27015, Friday, March 24,2017 22:45:26
[LAN access from remote] from 178.159.81.96:41022 to 192.168.1.11:27015, Friday, March 24,2017 22:45:22
[LAN access from remote] from 80.244.37.46:52323 to 192.168.1.11:27015, Friday, March 24,2017 22:45:16
[LAN access from remote] from 73.252.105.244:52639 to 192.168.1.11:27015, Friday, March 24,2017 22:45:12
[LAN access from remote] from 92.38.3.80:1037 to 192.168.1.11:27015, Friday, March 24,2017 22:45:06
[LAN access from remote] from 211.27.44.4:17021 to 192.168.1.11:27015, Friday, March 24,2017 22:45:02
[LAN access from remote] from 93.126.96.50:11530 to 192.168.1.11:27015, Friday, March 24,2017 22:44:51
[LAN access from remote] from 176.86.54.10:53649 to 192.168.1.11:27015, Friday, March 24,2017 22:44:46
[LAN access from remote] from 91.215.79.121:61893 to 192.168.1.11:27015, Friday, March 24,2017 22:44:42
[LAN access from remote] from 113.193.78.133:26996 to 192.168.1.11:27015, Friday, March 24,2017 22:44:36
[LAN access from remote] from 49.207.188.210:15018 to 192.168.1.11:27015, Friday, March 24,2017 22:44:32
[LAN access from remote] from 71.234.255.17:57173 to 192.168.1.11:27015, Friday, March 24,2017 22:44:22
[LAN access from remote] from 95.26.16.206:43606 to 192.168.1.11:27015, Friday, March 24,2017 22:44:17
[LAN access from remote] from 176.106.77.106:53324 to 192.168.1.11:27015, Friday, March 24,2017 22:44:12
[LAN access from remote] from 210.124.39.239:15974 to 192.168.1.11:27015, Friday, March 24,2017 22:44:07
[LAN access from remote] from 176.37.32.93:42167 to 192.168.1.11:27015, Friday, March 24,2017 22:44:01
[LAN access from remote] from 5.141.212.129:45758 to 192.168.1.11:27015, Friday, March 24,2017 22:43:57
[LAN access from remote] from 184.146.142.242:16762 to 192.168.1.11:27015, Friday, March 24,2017 22:43:52
[LAN access from remote] from 5.129.191.44:19012 to 192.168.1.11:27015, Friday, March 24,2017 22:43:46
[LAN access from remote] from 189.47.42.233:38414 to 192.168.1.11:27015, Friday, March 24,2017 22:43:42
[LAN access from remote] from 77.34.45.100:57098 to 192.168.1.11:27015, Friday, March 24,2017 22:43:37
[LAN access from remote] from 157.97.121.89:58524 to 192.168.1.11:27015, Friday, March 24,2017 22:43:32
[LAN access from remote] from 176.116.66.4:49355 to 192.168.1.11:27015, Friday, March 24,2017 22:43:27
[LAN access from remote] from 109.182.89.21:57481 to 192.168.1.11:27015, Friday, March 24,2017 22:43:22
[LAN access from remote] from 95.17.247.36:22114 to 192.168.1.11:27015, Friday, March 24,2017 22:43:17
[LAN access from remote] from 193.178.118.40:60442 to 192.168.1.11:27015, Friday, March 24,2017 22:43:11
[LAN access from remote] from 99.74.200.144:49663 to 192.168.1.11:27015, Friday, March 24,2017 22:43:06
[LAN access from remote] from 31.200.233.10:63699 to 192.168.1.11:27015, Friday, March 24,2017 22:43:02
[LAN access from remote] from 212.34.244.56:41812 to 192.168.1.11:27015, Friday, March 24,2017 22:42:57
[LAN access from remote] from 178.255.44.59:63795 to 192.168.1.11:27015, Friday, March 24,2017 22:42:51
[LAN access from remote] from 38.95.108.244:64947 to 192.168.1.11:27015, Friday, March 24,2017 22:42:47
[LAN access from remote] from 196.200.117.36:22970 to 192.168.1.11:27015, Friday, March 24,2017 22:42:42
[LAN access from remote] from 188.191.185.59:42513 to 192.168.1.11:27015, Friday, March 24,2017 22:42:36
[LAN access from remote] from 109.201.152.194:40447 to 192.168.1.11:27015, Friday, March 24,2017 22:42:32
[LAN access from remote] from 178.68.214.109:18656 to 192.168.1.11:27015, Friday, March 24,2017 22:42:27
[LAN access from remote] from 46.246.58.131:21765 to 192.168.1.11:27015, Friday, March 24,2017 22:42:22
[LAN access from remote] from 92.47.246.156:29134 to 192.168.1.11:27015, Friday, March 24,2017 22:42:17
[LAN access from remote] from 101.179.67.162:47875 to 192.168.1.11:27015, Friday, March 24,2017 22:42:11
[LAN access from remote] from 5.44.172.146:52881 to 192.168.1.11:27015, Friday, March 24,2017 22:42:06
[LAN access from remote] from 46.166.76.166:46215 to 192.168.1.11:27015, Friday, March 24,2017 22:42:02
[LAN access from remote] from 182.55.175.44:22899 to 192.168.1.11:27015, Friday, March 24,2017 22:41:56
[LAN access from remote] from 217.66.158.213:51522 to 192.168.1.11:27015, Friday, March 24,2017 22:41:52
[LAN access from remote] from 41.248.158.30:31639 to 192.168.1.11:27015, Friday, March 24,2017 22:41:47
[LAN access from remote] from 188.0.188.7:57177 to 192.168.1.11:27015, Friday, March 24,2017 22:41:42
[LAN access from remote] from 94.233.148.155:50438 to 192.168.1.11:27015, Friday, March 24,2017 22:41:37
[LAN access from remote] from 90.53.141.210:38866 to 192.168.1.11:27015, Friday, March 24,2017 22:41:32
[LAN access from remote] from 82.38.118.51:12624 to 192.168.1.11:27015, Friday, March 24,2017 22:41:27
[LAN access from remote] from 195.34.204.159:64410 to 192.168.1.11:27015, Friday, March 24,2017 22:41:22
[LAN access from remote] from 37.150.0.1:52998 to 192.168.1.11:27015, Friday, March 24,2017 22:41:16
[LAN access from remote] from 178.211.187.49:18628 to 192.168.1.11:27015, Friday, March 24,2017 22:41:12
[LAN access from remote] from 78.26.162.81:50589 to 192.168.1.11:27015, Friday, March 24,2017 22:41:06
[LAN access from remote] from 209.58.131.168:61059 to 192.168.1.11:27015, Friday, March 24,2017 22:41:02
[LAN access from remote] from 71.30.255.233:27879 to 192.168.1.11:27015, Friday, March 24,2017 22:40:57
[LAN access from remote] from 99.112.234.36:36449 to 192.168.1.11:27015, Friday, March 24,2017 22:40:52
[LAN access from remote] from 178.120.64.130:43122 to 192.168.1.11:27015, Friday, March 24,2017 22:40:47
[LAN access from remote] from 2.94.246.220:1144 to 192.168.1.11:27015, Friday, March 24,2017 22:40:41
[LAN access from remote] from 82.208.101.206:4096 to 192.168.1.11:27015, Friday, March 24,2017 22:40:36
[LAN access from remote] from 5.101.27.91:26334 to 192.168.1.11:27015, Friday, March 24,2017 22:40:31
[LAN access from remote] from 197.232.57.11:53450 to 192.168.1.11:27015, Friday, March 24,2017 22:40:27
[LAN access from remote] from 109.64.17.184:47307 to 192.168.1.11:27015, Friday, March 24,2017 22:40:22
[LAN access from remote] from 85.26.163.177:45051 to 192.168.1.11:27015, Friday, March 24,2017 22:40:17
[LAN access from remote] from 121.214.67.191:57916 to 192.168.1.11:27015, Friday, March 24,2017 22:40:12
[LAN access from remote] from 176.99.125.126:23044 to 192.168.1.11:27015, Friday, March 24,2017 22:40:07
[LAN access from remote] from 93.79.191.110:22286 to 192.168.1.11:27015, Friday, March 24,2017 22:40:01
[LAN access from remote] from 86.2.85.143:65206 to 192.168.1.11:27015, Friday, March 24,2017 22:39:56
[LAN access from remote] from 217.159.171.17:19793 to 192.168.1.11:27015, Friday, March 24,2017 22:39:52
[LAN access from remote] from 217.118.81.25:58332 to 192.168.1.11:27015, Friday, March 24,2017 22:39:47
[LAN access from remote] from 82.131.56.156:39044 to 192.168.1.11:27015, Friday, March 24,2017 22:39:42
[LAN access from remote] from 23.240.236.162:14889 to 192.168.1.11:27015, Friday, March 24,2017 22:39:37
[LAN access from remote] from 5.143.10.44:59616 to 192.168.1.11:27015, Friday, March 24,2017 22:39:31
[LAN access from remote] from 101.98.192.32:61347 to 192.168.1.11:27015, Friday, March 24,2017 22:39:27
[LAN access from remote] from 117.215.254.117:64143 to 192.168.1.11:27015, Friday, March 24,2017 22:39:21
[LAN access from remote] from 62.83.65.13:44914 to 192.168.1.11:27015, Friday, March 24,2017 22:39:16
[LAN access from remote] from 91.246.113.167:62347 to 192.168.1.11:27015, Friday, March 24,2017 22:39:12
[LAN access from remote] from 46.166.186.244:31337 to 192.168.1.11:27015, Friday, March 24,2017 22:39:07
[LAN access from remote] from 37.147.57.103:27684 to 192.168.1.11:27015, Friday, March 24,2017 22:39:01
[LAN access from remote] from 202.142.68.52:30830 to 192.168.1.11:27015, Friday, March 24,2017 22:38:52
[LAN access from remote] from 108.24.170.148:21812 to 192.168.1.11:27015, Friday, March 24,2017 22:38:47
[LAN access from remote] from 176.102.215.212:22751 to 192.168.1.11:27015, Friday, March 24,2017 22:38:41
[LAN access from remote] from 95.61.248.5:44353 to 192.168.1.11:27015, Friday, March 24,2017 22:38:36
[LAN access from remote] from 5.167.78.255:28799 to 192.168.1.11:27015, Friday, March 24,2017 22:38:32
[LAN access from remote] from 60.242.15.16:35620 to 192.168.1.11:27015, Friday, March 24,2017 22:38:26
[LAN access from remote] from 45.72.245.93:1063 to 192.168.1.11:27015, Friday, March 24,2017 22:38:22
[LAN access from remote] from 94.25.176.204:19511 to 192.168.1.11:27015, Friday, March 24,2017 22:38:16
[LAN access from remote] from 176.69.158.108:44244 to 192.168.1.11:27015, Friday, March 24,2017 22:38:12
[LAN access from remote] from 87.117.12.128:43719 to 192.168.1.11:27015, Friday, March 24,2017 22:38:06
[LAN access from remote] from 93.56.64.209:24534 to 192.168.1.11:27015, Friday, March 24,2017 22:38:02
[LAN access from remote] from 91.205.238.2:39747 to 192.168.1.11:27015, Friday, March 24,2017 22:37:56
[LAN access from remote] from 110.46.245.156:1389 to 192.168.1.11:27015, Friday, March 24,2017 22:37:51
[LAN access from remote] from 77.222.126.56:39496 to 192.168.1.11:27015, Friday, March 24,2017 22:37:46
[LAN access from remote] from 85.143.164.14:61541 to 192.168.1.11:27015, Friday, March 24,2017 22:37:41
[LAN access from remote] from 46.166.138.145:44852 to 192.168.1.11:27015, Friday, March 24,2017 22:37:36
[LAN access from remote] from 182.191.77.71:61878 to 192.168.1.11:27015, Friday, March 24,2017 22:37:27
[LAN access from remote] from 78.225.128.115:58763 to 192.168.1.11:27015, Friday, March 24,2017 22:37:22
[LAN access from remote] from 50.109.115.21:1046 to 192.168.1.11:27015, Friday, March 24,2017 22:37:11
[LAN access from remote] from 81.152.126.7:47009 to 192.168.1.11:27015, Friday, March 24,2017 22:37:07
[LAN access from remote] from 46.158.170.120:16211 to 192.168.1.11:27015, Friday, March 24,2017 22:37:01
[LAN access from remote] from 197.2.227.4:63371 to 192.168.1.11:27015, Friday, March 24,2017 22:36:56
[LAN access from remote] from 79.98.92.48:7009 to 192.168.1.11:27015, Friday, March 24,2017 22:36:52
[LAN access from remote] from 86.203.169.181:43383 to 192.168.1.11:27015, Friday, March 24,2017 22:36:46
[LAN access from remote] from 46.166.137.234:12976 to 192.168.1.11:27015, Friday, March 24,2017 22:36:41
[LAN access from remote] from 5.141.20.151:14741 to 192.168.1.11:27015, Friday, March 24,2017 22:36:37
[LAN access from remote] from 109.174.112.98:51087 to 192.168.1.11:27015, Friday, March 24,2017 22:36:32
[LAN access from remote] from 62.133.162.197:34325 to 192.168.1.11:27015, Friday, March 24,2017 22:36:26
[LAN access from remote] from 77.247.208.69:56124 to 192.168.1.11:27015, Friday, March 24,2017 22:36:21
[LAN access from remote] from 61.68.62.111:24665 to 192.168.1.11:27015, Friday, March 24,2017 22:36:11
[LAN access from remote] from 176.209.91.77:33450 to 192.168.1.11:27015, Friday, March 24,2017 22:36:06
[LAN access from remote] from 5.100.65.252:55711 to 192.168.1.11:27015, Friday, March 24,2017 22:36:01
[LAN access from remote] from 189.149.164.148:64102 to 192.168.1.11:27015, Friday, March 24,2017 22:35:57
[LAN access from remote] from 173.177.189.72:62016 to 192.168.1.11:27015, Friday, March 24,2017 22:35:52
[LAN access from remote] from 173.72.135.172:57291 to 192.168.1.11:27015, Friday, March 24,2017 22:35:47
[LAN access from remote] from 5.138.36.118:1024 to 192.168.1.11:27015, Friday, March 24,2017 22:35:41
[LAN access from remote] from 213.133.97.34:16884 to 192.168.1.11:27015, Friday, March 24,2017 22:35:37
[LAN access from remote] from 178.159.118.229:29147 to 192.168.1.11:27015, Friday, March 24,2017 22:35:32
[LAN access from remote] from 98.114.149.211:47144 to 192.168.1.11:27015, Friday, March 24,2017 22:35:27
[LAN access from remote] from 77.174.72.246:43861 to 192.168.1.11:27015, Friday, March 24,2017 22:35:21
[LAN access from remote] from 5.141.204.129:13546 to 192.168.1.11:27015, Friday, March 24,2017 22:35:16
[LAN access from remote] from 31.129.169.220:59565 to 192.168.1.11:27015, Friday, March 24,2017 22:35:12
[LAN access from remote] from 185.124.230.18:19806 to 192.168.1.11:27015, Friday, March 24,2017 22:35:07
[LAN access from remote] from 87.223.221.32:1659 to 192.168.1.11:27015, Friday, March 24,2017 22:35:02
[LAN access from remote] from 71.84.203.208:46092 to 192.168.1.11:27015, Friday, March 24,2017 22:34:56
[LAN access from remote] from 109.172.69.71:65429 to 192.168.1.11:27015, Friday, March 24,2017 22:34:52
[LAN access from remote] from 5.153.233.58:39029 to 192.168.1.11:27015, Friday, March 24,2017 22:34:47
[LAN access from remote] from 77.40.2.103:50811 to 192.168.1.11:27015, Friday, March 24,2017 22:34:41
[LAN access from remote] from 95.220.3.140:50009 to 192.168.1.11:27015, Friday, March 24,2017 22:34:36
[LAN access from remote] from 203.211.151.200:52038 to 192.168.1.11:27015, Friday, March 24,2017 22:34:32
[LAN access from remote] from 114.23.127.184:57370 to 192.168.1.11:27015, Friday, March 24,2017 22:34:26
[LAN access from remote] from 188.235.46.67:63599 to 192.168.1.11:27015, Friday, March 24,2017 22:34:22
[LAN access from remote] from 178.218.36.0:60255 to 192.168.1.11:27015, Friday, March 24,2017 22:34:16
[LAN access from remote] from 77.123.245.9:55317 to 192.168.1.11:27015, Friday, March 24,2017 22:34:12
[LAN access from remote] from 217.112.2.224:19364 to 192.168.1.11:27015, Friday, March 24,2017 22:34:07
[LAN access from remote] from 78.187.204.3:1057 to 192.168.1.11:27015, Friday, March 24,2017 22:34:02
[LAN access from remote] from 188.120.136.24:60527 to 192.168.1.11:27015, Friday, March 24,2017 22:33:57
[LAN access from remote] from 108.200.39.81:19115 to 192.168.1.11:27015, Friday, March 24,2017 22:33:51
[LAN access from remote] from 5.158.234.54:27330 to 192.168.1.11:27015, Friday, March 24,2017 22:33:46
[LAN access from remote] from 188.134.66.165:18639 to 192.168.1.11:27015, Friday, March 24,2017 22:33:42
[LAN access from remote] from 195.208.173.161:43690 to 192.168.1.11:27015, Friday, March 24,2017 22:33:37
[LAN access from remote] from 121.215.192.202:45001 to 192.168.1.11:27015, Friday, March 24,2017 22:33:33
[LAN access from remote] from 87.216.73.39:39757 to 192.168.1.11:27015, Friday, March 24,2017 22:33:26
[LAN access from remote] from 199.229.250.114:28142 to 192.168.1.11:27015, Friday, March 24,2017 22:33:21
[LAN access from remote] from 92.96.62.247:29445 to 192.168.1.11:27015, Friday, March 24,2017 22:33:17

 

Link to comment
Share on other sites

Link to post
Share on other sites

She's probably downloading steam games etc. Anything that is a steam download runs through 27015. It's not just source engine.

My native language is C++

Link to comment
Share on other sites

Link to post
Share on other sites

She's not downloading steam games, and I checked the IPS and some of them aren't hosting provitors. I don't even think she has steam installed atm.

 

Link to comment
Share on other sites

Link to post
Share on other sites

What is your sister doing on her computer while these connections are happening? Did some research on those IPs. def. not of valve origin.

 

EDIT: Do you have port 27015 open for 192.168.1.11? It could be just bots doing portscans.

My native language is C++

Link to comment
Share on other sites

Link to post
Share on other sites

It's been happening for a few months now, there has even been DoS attacks picked up here and there. that was back when there was spam on port 50143, it was showing up as a DoS attack in my modem/router my isp gave me, I recently switched it into bridged mode cause my other router-router keeps the logs longer.

Link to comment
Share on other sites

Link to post
Share on other sites

Some of the time she is watching shows, other times shes playing games that dont require internet.

 

Link to comment
Share on other sites

Link to post
Share on other sites

Perhaps I can run a nmap scan on that port to see what services run on it, like shoden does?

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, Savage.exe said:

Some of the time she is watching shows, other times shes playing games that dont require internet.

 

So then is port 27015 ip 192.168.1.11 open from some previous forgotten gmod server?

My native language is C++

Link to comment
Share on other sites

Link to post
Share on other sites

Also, that port is closed, and I also attempted to block it

Link to comment
Share on other sites

Link to post
Share on other sites

2 minutes ago, rrubberr said:

It's just the NSA. No worries.

shhhhhhhhhhhh... they are now monitoring this chat..... "tip-toes out of thread"

| Ryzen 9 3950X | EVGA 1200P2 | AMD 5700XT | ASUS Crosshair VIII Hero WiFi | G. Skill 4x16GB 3600Mhz CL16 F4-3600C16D-32GTZN | 2x1TB Samsung 980 Pro | Lian Li O11 Dynamic |

 

Link to comment
Share on other sites

Link to post
Share on other sites

1 minute ago, Savage.exe said:

Also, that port is closed, and I also attempted to block it

Ok, so somehow they seem to be establishing connections TO that IP address. This makes no sense if the port is blocked. Are these attempted connections? Or established connections? Also, is UPnP enabled?

My native language is C++

Link to comment
Share on other sites

Link to post
Share on other sites

UPnP is enabled, And I don't know, the logs don't tell me that much. I guess I could break out Wireshark and watch on that port.

Link to comment
Share on other sites

Link to post
Share on other sites

Remember that unless you are using wireshark on the destination pc, you will not be able to see that computer's packets. I think you should disable UPnP. UPnP is in layman's terms automatic port forwarding. It allows devices like tvs and smart devices to open the ports necessary to send all your personal data to the home company for "safe" keeping

My native language is C++

Link to comment
Share on other sites

Link to post
Share on other sites

After looking around on my sisters computer, when I did the command in cmd prmt I ran across that port, it ended up being Vuze, I discovered in the network usage in the task manager it's using anywhere from 0.1mbps, and 1mbps. 

Edit:

On my computer there's random intervals of 0.1mbps, on my sisters computer its constant 0.1mbps, Seeding is also off.

Link to comment
Share on other sites

Link to post
Share on other sites

2 minutes ago, Savage.exe said:

After looking around on my sisters computer, when I did the command in cmd prmt I ran across that port, it ended up being Vuze, I discovered in the network usage in the task manager it's using anywhere from 0.1mbps, and 1mbps. 

Sounds right. Didn't know vuze used 27015 though. Interesting.

My native language is C++

Link to comment
Share on other sites

Link to post
Share on other sites

6 hours ago, tt2468 said:

Sounds right. Didn't know vuze used 27015 though. Interesting.

Vuze - in case people aren't aware, is a Bit Torrent client.

 

The port, just like pretty much any Bit Torrent client, is configurable. You can literally set any port you want - it also has a built-in randomizer option to select a port at random.

 

@Savage.exe does your sister use Vuze? Is it running while these connections are being made? If so, you're probably just picking up seeds and peers connecting to her computer.

 

If Vuze is not running, then likely someone is just piggybacking on the port that Vuze uses. I too would suggest disabling UPnP, since that's likely what's opened the port, on Vuze's behalf.

For Sale: Meraki Bundle

 

iPhone Xr 128 GB Product Red - HP Spectre x360 13" (i5 - 8 GB RAM - 256 GB SSD) - HP ZBook 15v G5 15" (i7-8850H - 16 GB RAM - 512 GB SSD - NVIDIA Quadro P600)

 

Link to comment
Share on other sites

Link to post
Share on other sites

4 hours ago, dalekphalm said:

Vuze - in case people aren't aware, is a Bit Torrent client.

 

The port, just like pretty much any Bit Torrent client, is configurable. You can literally set any port you want - it also has a built-in randomizer option to select a port at random.

 

@Savage.exe does your sister use Vuze? Is it running while these connections are being made? If so, you're probably just picking up seeds and peers connecting to her computer.

 

If Vuze is not running, then likely someone is just piggybacking on the port that Vuze uses. I too would suggest disabling UPnP, since that's likely what's opened the port, on Vuze's behalf.

We are aware that Vuze is a bit torrent client. He also found that Vuze was the cause of all the connections.

My native language is C++

Link to comment
Share on other sites

Link to post
Share on other sites

12 minutes ago, tt2468 said:

We are aware that Vuze is a bit torrent client. He also found that Vuze was the cause of all the connections.

Well, unless you've had communication with the OP outside of this thread, I'd say that what he said is not explicitly clear in saying "Vuze was the cause of all the connections". Perhaps it was - it would certainly make sense, and it would certainly cause the Internet Lag he's seeing. But he didn't go into very many details, and his answer can be interpreted in multiple ways.

 

I do hope you are correct though, and that's all it was.

For Sale: Meraki Bundle

 

iPhone Xr 128 GB Product Red - HP Spectre x360 13" (i5 - 8 GB RAM - 256 GB SSD) - HP ZBook 15v G5 15" (i7-8850H - 16 GB RAM - 512 GB SSD - NVIDIA Quadro P600)

 

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×