cancel
Showing results for 
Search instead for 
Did you mean: 

out of nowhere, new IN and OUT connections

Newbie
Posts: 3
Registered: 4 weeks ago

out of nowhere, new IN and OUT connections

could someone explain me what`s that

 

21:26:26, 08 Jan. (104664.030000) Admin login successful by 172.16.0.66 on HTTP
21:26:23, 08 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [81.110.91.185]:57352 ppp3 NAPT)
21:26:19, 08 Jan. (104657.020000) New GUI session from IP 172.16.0.66
21:25:45, 08 Jan. IN: BLOCK [7] ICMP replay (ICMP type 3 code 1 2.96.88.134-​>51.6.13.90 on ppp3)
21:25:34, 08 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [90.240.120.27]:53438 ppp3 NAPT)
21:23:24, 08 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [92.6.80.234]:52158 ppp3 NAPT)
21:23:18, 08 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [90.240.120.27]:53438 ppp3 NAPT)
21:21:03, 08 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [92.6.80.234]:52158 ppp3 NAPT)
21:20:57, 08 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [95.150.9.213]:56597 ppp3 NAPT)
21:18:41, 08 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [95.150.9.213]:56597 ppp3 NAPT)
21:18:37, 08 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [82.19.24.21]:50503 ppp3 NAPT)
21:17:07, 08 Jan. IN: BLOCK [7] ICMP replay (ICMP type 3 code 1 90.240.71.187-​>51.6.13.90 on ppp3)
21:17:04, 08 Jan. BLOCKED 1 more packets (because of ICMP replay)
21:16:55, 08 Jan. IN: BLOCK [7] ICMP replay (ICMP type 3 code 1 90.240.71.187-​>51.6.13.90 on ppp3)
21:16:52, 08 Jan. BLOCKED 1 more packets (because of ICMP replay)
21:16:51, 08 Jan. IN: BLOCK [7] ICMP replay (ICMP type 3 code 1 90.240.71.187-​>51.6.13.90 on ppp3)
21:16:21, 08 Jan. IN: BLOCK [7] ICMP replay (ICMP type 3 code 1 2.101.2.94-​>51.6.13.90 on ppp3)
21:16:21, 08 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [82.19.24.21]:50503 ppp3 NAPT)
21:16:07, 08 Jan. IN: BLOCK [7] ICMP replay (ICMP type 3 code 1 2.101.2.94-​>51.6.13.90 on ppp3)
21:15:35, 08 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [87.242.135.66]:56193 ppp3 NAPT)
21:15:20, 08 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [137.221.148.203]:64310 ppp3 NAPT)
21:15:17, 08 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [82.28.194.230]:61005 ppp3 NAPT)
21:14:08, 08 Jan. IN: BLOCK [7] ICMP replay (ICMP type 3 code 1 2.26.213.249-​>51.6.13.90 on ppp3)
21:13:19, 08 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [87.242.135.66]:56193 ppp3 NAPT)
21:13:00, 08 Jan. IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [137.221.148.203]:64310 ppp3 NAPT)
21:11:32, 08 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [62.232.12.204]:60417 ppp3 NAPT)
21:11:27, 08 Jan. IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [172.16.0.66]:63283 <-​-​> [51.6.13.90]:63283 -​ -​ -​ [92.236.92.11]:59774 ppp3 NAPT)
21:11:05, 08 Jan. IN: BLOCK [7] ICMP replay (ICMP type 3 code 1 90.216.162.169-​>51.6.13.90 on ppp3)
21:11:02, 08 Jan. BLOCKED 1 more packets (because of ICMP replay)
1 REPLY 1
Newbie
Posts: 3
Registered: 4 weeks ago

Re: out of nowhere, new IN and OUT connections

ok i got it.

Battle.net and diablo 3 using that port.

and now have another problem with previous ( packet lost in client because blocking )

requesting lease while i was in game .

00:37:50, 09 Jan. ( 4355.970000) Wire Lan Port 3 up
00:37:49, 09 Jan. ( 4354.540000) Lease for IP 172.16.0.66 renewed by host weew (MAC 74:d4:35:ea:5f:ac). Lease duration: 30240 min
00:37:49, 09 Jan. ( 4354.540000) Device connected: Hostname: weew IP: 172.16.0.66 MAC: 74:d4:35:ea:5f:ac Lease time: 30240 min. Link rate: 1000.0 Mbps
00:37:49, 09 Jan. ( 4354.470000) Lease requested
00:37:49, 09 Jan. ( 4354.160000) Lease for IP 172.16.0.66 renewed by host weew (MAC 74:d4:35:ea:5f:ac). Lease duration: 30240 min
00:37:49, 09 Jan. ( 4354.160000) Device connected: Hostname: weew IP: 172.16.0.66 MAC: 74:d4:35:ea:5f:ac Lease time: 30240 min. Link rate: 1000.0 Mbps
00:37:49, 09 Jan. ( 4354.090000) Lease requested
00:37:47, 09 Jan. ( 4352.970000) Wire Lan Port 3 down
00:37:45, 09 Jan. ( 4350.330000) Lease for IP 172.16.0.66 renewed by host weew (MAC 74:d4:35:ea:5f:ac). Lease duration: 30240 min
00:37:45, 09 Jan. ( 4350.330000) Device connected: Hostname: weew IP: 172.16.0.66 MAC: 74:d4:35:ea:5f:ac Lease time: 30240 min. Link rate: 1000.0 Mbps
00:37:45, 09 Jan. ( 4350.250000) Lease requested
00:37:44, 09 Jan. ( 4349.970000) Wire Lan Port 3 up
00:37:42, 09 Jan. ( 4347.880000) Device disconnected: Hostname: weew IP: 172.16.0.66 MAC: 74:d4:35:ea:5f:ac
00:37:41, 09 Jan. ( 4346.970000) Wire Lan Port 3 down