Wireless router forums

Toggle sidebar Toggle sidebar
Status
Not open for further replies.
F

fachhoch

Honorable
Nov 29, 2012
1
0
10,510
my router security logs
Code: 
11/29/2012  22:48:24 192.168.2.4 login success 
11/29/2012  22:48:07 **TCP FIN Scan** 173.194.77.113, 80->> 68.100.62.118, 50184 (from WAN Inbound)
11/29/2012  22:47:16 sending ACK to 192.168.2.6
11/29/2012  22:47:03 sending ACK to 192.168.2.3
11/29/2012  22:44:51 sending ACK to 192.168.2.6
11/29/2012  22:44:38 sending ACK to 192.168.2.3
11/29/2012  22:42:26 sending ACK to 192.168.2.6
11/29/2012  22:42:10 sending ACK to 192.168.2.3
11/29/2012  22:40:02 sending ACK to 192.168.2.6
11/29/2012  22:39:45 sending ACK to 192.168.2.3
11/29/2012  22:37:37 sending ACK to 192.168.2.6
11/29/2012  22:37:20 sending ACK to 192.168.2.3
11/29/2012  22:35:13 sending ACK to 192.168.2.6
11/29/2012  22:34:55 sending ACK to 192.168.2.3
11/29/2012  22:32:48 sending ACK to 192.168.2.6
11/29/2012  22:32:31 sending ACK to 192.168.2.3
11/29/2012  22:30:22 sending ACK to 192.168.2.6
11/29/2012  22:30:06 sending ACK to 192.168.2.3
11/29/2012  22:27:57 sending ACK to 192.168.2.6
11/29/2012  22:27:40 sending ACK to 192.168.2.3
11/29/2012  22:25:32 sending ACK to 192.168.2.6
11/29/2012  22:25:15 sending ACK to 192.168.2.3
11/29/2012  22:23:08 sending ACK to 192.168.2.6
11/29/2012  22:22:50 sending ACK to 192.168.2.3
11/29/2012  22:20:43 sending ACK to 192.168.2.6
11/29/2012  22:20:25 sending ACK to 192.168.2.3
11/29/2012  22:18:19 sending ACK to 192.168.2.6
11/29/2012  22:18:00 sending ACK to 192.168.2.3
11/29/2012  22:15:54 sending ACK to 192.168.2.6
11/29/2012  22:15:35 sending ACK to 192.168.2.3
11/29/2012  22:13:30 sending ACK to 192.168.2.6
11/29/2012  22:13:10 sending ACK to 192.168.2.3
11/29/2012  22:11:05 sending ACK to 192.168.2.6
11/29/2012  22:10:45 sending ACK to 192.168.2.3
11/29/2012  22:08:41 sending ACK to 192.168.2.6
11/29/2012  22:08:20 sending ACK to 192.168.2.3
11/29/2012  22:06:16 sending ACK to 192.168.2.6
11/29/2012  22:05:55 sending ACK to 192.168.2.3
11/29/2012  22:03:51 sending ACK to 192.168.2.6
11/29/2012  22:03:31 sending ACK to 192.168.2.3
11/29/2012  22:01:27 sending ACK to 192.168.2.6
11/29/2012  22:01:06 sending ACK to 192.168.2.3
11/29/2012  21:59:02 sending ACK to 192.168.2.6
11/29/2012  21:58:40 sending ACK to 192.168.2.3
11/29/2012  21:58:26 sending ACK to 192.168.2.5
11/29/2012  21:56:38 sending ACK to 192.168.2.6
11/29/2012  21:56:15 sending ACK to 192.168.2.3
11/29/2012  21:54:13 sending ACK to 192.168.2.6
11/29/2012  21:53:50 sending ACK to 192.168.2.3
11/29/2012  21:51:48 sending ACK to 192.168.2.6
11/29/2012  21:51:25 sending ACK to 192.168.2.3
11/29/2012  21:49:24 sending ACK to 192.168.2.6
11/29/2012  21:49:00 sending ACK to 192.168.2.3
11/29/2012  21:47:00 sending ACK to 192.168.2.6
11/29/2012  21:46:35 sending ACK to 192.168.2.3
11/29/2012  21:44:35 sending ACK to 192.168.2.6
11/29/2012  21:44:10 sending ACK to 192.168.2.3
11/29/2012  21:42:11 sending ACK to 192.168.2.6
11/29/2012  21:41:45 sending ACK to 192.168.2.3
11/29/2012  21:39:46 sending ACK to 192.168.2.6
11/29/2012  21:39:24 **TCP FIN Scan** 173.194.77.101, 80->> 68.100.62.118, 56557 (from WAN Inbound)
11/29/2012  21:39:20 sending ACK to 192.168.2.3
11/29/2012  21:37:22 sending ACK to 192.168.2.6
11/29/2012  21:36:55 sending ACK to 192.168.2.3
11/29/2012  21:34:57 sending ACK to 192.168.2.6
11/29/2012  21:34:30 sending ACK to 192.168.2.3
11/29/2012  21:32:32 sending ACK to 192.168.2.6
11/29/2012  21:32:05 sending ACK to 192.168.2.3
11/29/2012  21:30:08 sending ACK to 192.168.2.6
11/29/2012  21:29:40 sending ACK to 192.168.2.3
11/29/2012  21:27:43 sending ACK to 192.168.2.6
11/29/2012  21:27:15 sending ACK to 192.168.2.3
11/29/2012  21:25:19 sending ACK to 192.168.2.6
11/29/2012  21:24:50 sending ACK to 192.168.2.3
11/29/2012  21:22:54 sending ACK to 192.168.2.6
11/29/2012  21:22:25 sending ACK to 192.168.2.3
11/29/2012  21:20:30 sending ACK to 192.168.2.6
11/29/2012  21:20:00 sending ACK to 192.168.2.3
11/29/2012  21:19:05 **TCP FIN Scan** 173.194.64.113, 80->> 68.100.62.118, 35384 (from WAN Inbound)
11/29/2012  21:18:05 sending ACK to 192.168.2.6
11/29/2012  21:17:35 sending ACK to 192.168.2.3
11/29/2012  21:15:41 sending ACK to 192.168.2.6
11/29/2012  21:15:10 sending ACK to 192.168.2.3
11/29/2012  21:13:16 sending ACK to 192.168.2.6
11/29/2012  21:12:45 sending ACK to 192.168.2.3
11/29/2012  21:10:51 sending ACK to 192.168.2.6
11/29/2012  21:10:21 sending ACK to 192.168.2.3
11/29/2012  21:08:27 sending ACK to 192.168.2.6
11/29/2012  21:07:56 sending ACK to 192.168.2.3
11/29/2012  21:06:44 sending ACK to 192.168.2.4
11/29/2012  21:06:02 sending ACK to 192.168.2.6
11/29/2012  21:05:30 sending ACK to 192.168.2.3
11/29/2012  21:03:38 sending ACK to 192.168.2.6
11/29/2012  21:03:05 sending ACK to 192.168.2.3
11/29/2012  21:01:13 sending ACK to 192.168.2.6
11/29/2012  21:00:41 sending ACK to 192.168.2.3
11/29/2012  20:58:16 sending ACK to 192.168.2.3
11/29/2012  20:55:51 sending ACK to 192.168.2.3
11/29/2012  20:53:26 sending ACK to 192.168.2.3
11/29/2012  20:51:01 sending ACK to 192.168.2.3
11/29/2012  20:48:36 sending ACK to 192.168.2.3
11/29/2012  20:47:38 sending ACK to 192.168.2.6
11/29/2012  20:47:34 sending ACK to 192.168.2.6
11/29/2012  20:46:11 sending ACK to 192.168.2.3
11/29/2012  20:45:10 sending ACK to 192.168.2.6
11/29/2012  20:43:46 sending ACK to 192.168.2.3
11/29/2012  20:42:45 sending ACK to 192.168.2.6
11/29/2012  20:42:40 sending ACK to 192.168.2.6
11/29/2012  20:41:21 sending ACK to 192.168.2.3
11/29/2012  20:40:16 sending ACK to 192.168.2.6
11/29/2012  20:40:12 sending ACK to 192.168.2.6
11/29/2012  20:38:56 sending ACK to 192.168.2.3
11/29/2012  20:37:47 sending ACK to 192.168.2.6
11/29/2012  20:37:43 sending ACK to 192.168.2.6
11/29/2012  20:36:31 sending ACK to 192.168.2.3
11/29/2012  20:35:18 sending ACK to 192.168.2.6
11/29/2012  20:35:14 sending ACK to 192.168.2.6
11/29/2012  20:34:06 sending ACK to 192.168.2.3
11/29/2012  20:32:50 sending ACK to 192.168.2.6
11/29/2012  20:32:46 sending ACK to 192.168.2.6
11/29/2012  20:31:41 sending ACK to 192.168.2.3
11/29/2012  20:30:22 sending ACK to 192.168.2.6
11/29/2012  20:29:16 sending ACK to 192.168.2.3
11/29/2012  20:27:57 sending ACK to 192.168.2.6
11/29/2012  20:26:51 sending ACK to 192.168.2.3
11/29/2012  20:25:33 sending ACK to 192.168.2.6
11/29/2012  20:24:26 sending ACK to 192.168.2.3
11/29/2012  20:23:08 sending ACK to 192.168.2.6
11/29/2012  20:22:01 sending ACK to 192.168.2.3
11/29/2012  20:21:23 **TCP-SYN with data** 192.168.2.2, 50038->> 216.115.20.136, 80 (from LAN Inbound)
11/29/2012  20:21:21 **TCP-SYN with data** 192.168.2.2, 50036->> 216.115.20.135, 80 (from LAN Inbound)
11/29/2012  20:21:19 **TCP-SYN with data** 192.168.2.2, 50034->> 216.115.20.136, 80 (from LAN Inbound)
11/29/2012  20:21:17 **TCP-SYN with data** 192.168.2.2, 50032->> 216.115.20.135, 80 (from LAN Inbound)
11/29/2012  20:21:15 **TCP-SYN with data** 192.168.2.2, 50030->> 216.115.20.136, 80 (from LAN Inbound)
11/29/2012  20:21:13 **TCP-SYN with data** 192.168.2.2, 50028->> 216.115.20.135, 80 (from LAN Inbound)
11/29/2012  20:21:11 **TCP-SYN with data** 192.168.2.2, 50026->> 216.115.20.136, 80 (from LAN Inbound)
11/29/2012  20:21:09 **TCP-SYN with data** 192.168.2.2, 50024->> 216.115.20.135, 80 (from LAN Inbound)
11/29/2012  20:21:07 **TCP-SYN with data** 192.168.2.2, 50022->> 216.115.20.136, 80 (from LAN Inbound)
11/29/2012  20:21:05 **TCP-SYN with data** 192.168.2.2, 50020->> 216.115.20.135, 80 (from LAN Inbound)
11/29/2012  20:21:03 **TCP-SYN with data** 192.168.2.2, 50018->> 216.115.20.136, 80 (from LAN Inbound)
11/29/2012  20:21:01 **TCP-SYN with data** 192.168.2.2, 50016->> 216.115.20.135, 80 (from LAN Inbound)
11/29/2012  20:20:59 **TCP-SYN with data** 192.168.2.2, 50014->> 216.115.20.136, 80 (from LAN Inbound)
11/29/2012  20:20:57 **TCP-SYN with data** 192.168.2.2, 50012->> 216.115.20.135, 80 (from LAN Inbound)
11/29/2012  20:20:55 **TCP-SYN with data** 192.168.2.2, 50010->> 216.115.20.136, 80 (from LAN Inbound)
11/29/2012  20:20:53 **TCP-SYN with data** 192.168.2.2, 50008->> 216.115.20.135, 80 (from LAN Inbound)
11/29/2012  20:20:51 **TCP-SYN with data** 192.168.2.2, 50006->> 216.115.20.136, 80 (from LAN Inbound)
11/29/2012  20:20:49 **TCP-SYN with data** 192.168.2.2, 50004->> 216.115.20.135, 80 (from LAN Inbound)
11/29/2012  20:20:47 **TCP-SYN with data** 192.168.2.2, 50002->> 216.115.20.136, 80 (from LAN Inbound)
11/29/2012  20:20:45 **TCP-SYN with data** 192.168.2.2, 50000->> 216.115.20.135, 80 (from LAN Inbound)
11/29/2012  20:20:43 sending ACK to 192.168.2.6
11/29/2012  20:19:36 sending ACK to 192.168.2.3
11/29/2012  20:19:24 DHCP Client: Receive Ack from 172.19.105.13, 'Lease time'=86400
11/29/2012  20:19:24 DHCP Client: Domain name = dc.dc.cox.net
11/29/2012  20:19:24 DHCP Client: Send Request, Request IP=68.100.62.118
11/29/2012  20:19:24 DHCP Client: Receive Offer from 172.19.105.13
11/29/2012  20:19:24 DHCP Client: Domain name = dc.dc.cox.net
11/29/2012  20:19:24 DHCP Client: Send Discover
11/29/2012  20:19:06 DHCP Client: Receive Ack from 192.168.100.1, 'Lease time'=20
11/29/2012  20:19:05 DHCP Client: Send Request, Request IP=192.168.100.11
11/29/2012  20:19:05 DHCP Client: Receive Offer from 192.168.100.1
what does **TCP-SYN with data** mean? sometimes I see inbound and sometimes outboud ?
Please advice do I have some virus or spyware in any of my devices, I have lot of devices, my android cell,phone xoom tablet, computer, router , modem, google tv .
 
Sort by date Sort by votes
Saga Lout

Saga Lout

Retired Mod
Mar 31, 2010
24,042
310
69,740

Hello and welcome to Tom's Hardware Forums.

This could be serious if your system has been compromised and is being used for flooding attacks - so-call DDOS denial of service attacks on large servers. It's the sort of attack hackers band together to use against, the FBI or a corporate giant which has upset the hacktivists.

That said it could be something of nothing - I wouldn't put it past Google as you have an Android and Google TV.

Don't lose sleep but make sure your defences are up to date and have scanned recently. Any doubts, go to http://www.grc.com/intro.htm and click on Services then Shields Up. Gibson research is safe and trusted and you can get a report on the security of your system, to put your mind at rest.


 
Upvote 0 Downvote
Status
Not open for further replies.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom