Recently got a new belkin n300 router modem. At first it worked fine, if a bit slower than my previous G router. But recently it's been getting massive lag spikes. If I'm watching a youtube video it will randomly completely stop buffering for upwards of a minute. If I'm playing anything online eg. WoW, LoL, tf2, I get massive ping spikes every other minute (jumping from ~50 to anywhere between 1,000-15,000 ms). I've tried it on other computers on the network, same thing. I've run a full virus scan using both McAfee and Avast, nothing. Is there anything I can try to figure out whether it really is the belkin or somewhere further down the line?
Edit: Checked router's security log, it's throwing out tonnes of **TCP FIN Scan** (from ATM1 Inbound) alerts, but the times logged don't seem to relate to the spikes. posting a log anyway:
It was also throwing out a bunch of **SYN FLOOD** (from ATM1 Inbound) earlier , to a different computer on the network (192.168.2.4), but they've both been scanned and shown nothing.
Edit 2: Did a netalyzr test: http://n3.netalyzr.icsi.berkeley.edu...5665-4de4-ad74
Edit: Checked router's security log, it's throwing out tonnes of **TCP FIN Scan** (from ATM1 Inbound) alerts, but the times logged don't seem to relate to the spikes. posting a log anyway:
Quote:
|
07/13/2013 23:07:59 sending ACK to 192.168.2.9 07/13/2013 23:07:58 sending OFFER to 192.168.2.9 07/13/2013 23:05:59 IP:192.168.2.13 ARP failed, IP recycled to free pool 07/13/2013 23:05:45 sending ACK to 192.168.2.5 07/13/2013 23:05:45 IP:192.168.2.2 ARP failed, IP recycled to free pool 07/13/2013 23:05:23 192.168.2.4 login success 07/13/2013 22:51:31 sending ACK to 192.168.2.5 07/13/2013 22:47:04 sending ACK to 192.168.2.2 07/13/2013 22:47:03 sending OFFER to 192.168.2.2 07/13/2013 22:27:50 sending ACK to 192.168.2.2 07/13/2013 22:27:49 sending OFFER to 192.168.2.2 07/13/2013 22:19:04 sending ACK to 192.168.2.2 07/13/2013 22:19:03 sending OFFER to 192.168.2.2 07/13/2013 21:43:22 sending ACK to 192.168.2.7 07/13/2013 21:43:19 sending ACK to 192.168.2.7 07/13/2013 21:06:25 sending ACK to 192.168.2.8 07/13/2013 20:54:18 sending ACK to 192.168.2.2 07/13/2013 20:54:16 sending OFFER to 192.168.2.2 07/13/2013 20:45:20 192.168.2.4 login success 07/13/2013 20:34:43 User from 192.168.2.4 timed out 07/13/2013 20:29:30 Can't find NTP time. 07/13/2013 20:29:00 Can't find NTP time. 07/13/2013 20:28:30 Can't find NTP time. 07/13/2013 20:28:00 Can't find NTP time. 07/13/2013 20:27:30 Can't find NTP time. 07/13/2013 20:27:00 Can't find NTP time. 07/13/2013 20:26:30 Can't find NTP time. 07/13/2013 20:26:00 Can't find NTP time. 07/13/2013 20:25:30 Can't find NTP time. 07/13/2013 20:25:00 Can't find NTP time. 07/13/2013 20:21:07 sending ACK to 192.168.2.3 07/13/2013 20:21:03 sending ACK to 192.168.2.3 07/13/2013 20:04:26 192.168.2.4 login success _______________________________________________ 07/13/2013 22:28:29 **TCP FIN Scan** 74.125.237.69, 443->> 192.168.2.3, 51251 (from ATM1 Inbound) 07/13/2013 22:28:29 **TCP FIN Scan** 74.125.237.92, 80->> 192.168.2.3, 51384 (from ATM1 Inbound) 07/13/2013 22:28:29 **TCP FIN Scan** 66.59.45.132, 80->> 192.168.2.3, 51375 (from ATM1 Inbound) 07/13/2013 22:28:29 **TCP FIN Scan** 50.16.244.245, 80->> 192.168.2.3, 51382 (from ATM1 Inbound) 07/13/2013 22:28:29 **TCP FIN Scan** 74.125.237.89, 80->> 192.168.2.3, 51422 (from ATM1 Inbound) 07/13/2013 22:28:29 **TCP FIN Scan** 8.27.255.254, 80->> 192.168.2.3, 51368 (from ATM1 Inbound) 07/13/2013 22:28:29 **TCP FIN Scan** 31.13.70.1, 80->> 192.168.2.3, 51407 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 67.225.183.157, 80->> 192.168.2.3, 51301 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 50.112.243.14, 80->> 192.168.2.3, 51399 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 184.87.34.127, 80->> 192.168.2.3, 51515 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 68.67.151.32, 80->> 192.168.2.3, 51420 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 173.203.40.173, 80->> 192.168.2.3, 51372 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 184.29.111.215, 80->> 192.168.2.3, 51371 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 66.150.149.24, 80->> 192.168.2.3, 51416 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 74.121.141.100, 80->> 192.168.2.3, 51418 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 184.87.33.224, 80->> 192.168.2.3, 51421 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 202.56.9.146, 80->> 192.168.2.3, 51485 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 208.49.63.35, 80->> 192.168.2.3, 51299 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 98.136.10.33, 80->> 192.168.2.3, 51423 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 184.87.36.211, 80->> 192.168.2.3, 51383 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 74.125.237.91, 80->> 192.168.2.3, 51393 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 54.230.134.121, 80->> 192.168.2.3, 51309 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 68.232.44.139, 443->> 192.168.2.3, 51405 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 54.230.134.90, 80->> 192.168.2.3, 51317 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 54.230.133.210, 80->> 192.168.2.3, 51322 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 54.230.133.185, 443->> 192.168.2.3, 51525 (from ATM1 Inbound) 07/13/2013 22:28:28 **TCP FIN Scan** 54.230.132.166, 80->> 192.168.2.3, 51327 (from ATM1 Inbound) |
Edit 2: Did a netalyzr test: http://n3.netalyzr.icsi.berkeley.edu...5665-4de4-ad74