# |
Time
|
Message
|
Source
|
Destination
|
Note
|
1
|
2006-09-20 03:14:58 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
2
|
2006-09-20 03:14:57 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
3
|
2006-09-20 03:14:56 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
4
|
2006-09-20 03:14:16 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
5
|
2006-09-20 03:14:15 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
6
|
2006-09-20 03:14:14 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
7
|
2006-09-20 03:14:01 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
8
|
2006-09-20 03:11:56 |
Successful HTTP login |
192.168.1.33:2284 |
192.168.1.1:80 |
User:admin |
9
|
2006-09-20 03:09:47 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
10
|
2006-09-20 03:01:12 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
11
|
2006-09-20 02:59:13 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
12
|
2006-09-20 02:59:13 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
13
|
2006-09-20 02:59:12 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
14
|
2006-09-20 02:58:58 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
15
|
2006-09-20 02:58:46 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
16
|
2006-09-20 02:58:46 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
17
|
2006-09-20 02:58:45 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
18
|
2006-09-20 02:49:28 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
19
|
2006-09-20 02:49:23 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
20
|
2006-09-20 02:49:23 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
21
|
2006-09-20 02:49:22 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
22
|
2006-09-20 02:49:08 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
23
|
2006-09-20 02:44:15 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
24
|
2006-09-20 02:44:02 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
25
|
2006-09-20 02:44:01 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
26
|
2006-09-20 02:44:00 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
27
|
2006-09-20 02:43:38 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
28
|
2006-09-20 02:43:37 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
29
|
2006-09-20 02:43:37 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
30
|
2006-09-20 02:39:19 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
31
|
2006-09-20 02:38:50 |
SMTP fail (Cannot connect to SMTP server 192.168.1.163) |
|
|
|
32
|
2006-09-20 02:38:19 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
33
|
2006-09-20 02:37:47 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
34
|
2006-09-20 02:37:27 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
35
|
2006-09-20 02:37:26 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
36
|
2006-09-20 02:37:25 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
37
|
2006-09-20 02:37:25 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
38
|
2006-09-20 02:37:25 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
39
|
2006-09-20 02:37:25 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
40
|
2006-09-20 02:37:25 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
41
|
2006-09-20 02:37:24 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
42
|
2006-09-20 02:37:23 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
43
|
2006-09-20 02:37:22 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
44
|
2006-09-20 02:37:22 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
45
|
2006-09-20 02:37:21 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
46
|
2006-09-20 02:37:20 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
47
|
2006-09-20 02:37:19 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
48
|
2006-09-20 02:37:18 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
49
|
2006-09-20 02:37:18 |
Successful HTTP login |
192.168.1.33:2167 |
192.168.1.1:80 |
User:admin |
50
|
2006-09-20 02:37:17 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
51
|
2006-09-20 02:37:16 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
52
|
2006-09-20 02:37:15 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
53
|
2006-09-20 02:37:14 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
54
|
2006-09-20 02:37:12 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
55
|
2006-09-20 02:37:11 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
56
|
2006-09-20 02:37:09 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
57
|
2006-09-20 02:37:09 |
ip spoofing - WAN UDP |
192.168.1.3:138 |
192.168.1.255:138 |
ATTACK |
58
|
2006-09-20 02:37:09 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
59
|
2006-09-20 02:37:09 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
60
|
2006-09-20 02:37:08 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
61
|
2006-09-20 02:37:08 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
62
|
2006-09-20 02:37:07 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
63
|
2006-09-20 02:37:07 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
64
|
2006-09-20 02:37:06 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
65
|
2006-09-20 02:37:06 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
66
|
2006-09-20 02:37:06 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
67
|
2006-09-20 02:37:05 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
68
|
2006-09-20 02:37:04 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
69
|
2006-09-20 02:37:03 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
70
|
2006-09-20 02:37:03 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
71
|
2006-09-20 02:37:02 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
72
|
2006-09-20 02:37:01 |
ip spoofing - WAN IGMP |
192.168.1.3 |
224.0.0.22 |
ATTACK |
73
|
2006-09-20 02:37:01 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
74
|
2006-09-20 02:37:00 |
ip spoofing - WAN UDP |
192.168.1.3:137 |
192.168.1.255:137 |
ATTACK |
75
|
2006-09-20 02:37:00 |
ip spoofing - WAN IGMP |
192.168.1.3 |
224.0.0.22 |
ATTACK |
76
|
2006-09-20 02:37:00 |
ip spoofing - WAN IGMP |
192.168.1.3 |
224.0.0.22 |
ATTACK |
77
|
2006-09-20 02:36:59 |
ip spoofing - WAN IGMP |
192.168.1.3 |
224.0.0.22 |
ATTACK |
78
|
2006-09-20 02:36:58 |
ip spoofing - WAN IGMP |
192.168.1.3 |
224.0.0.22 |
ATTACK |
79
|
2006-09-20 02:35:58 |
WAN connection is up. |
|
|
WAN1 |
80
|
2006-09-20 02:35:57 |
WAN interface gets IP:172.25.21.126 |
|
|
WAN1 |
81
|
2006-09-20 02:35:51 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
82
|
2006-09-20 02:35:46 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
83
|
2006-09-20 02:35:45 |
IP collision, peer's MAC 00:00:AA:80:80:89 (WAN1). |
199.227.88.162 |
199.227.88.162 |
ARP REQUEST |
84
|
2006-09-20 02:35:43 |
Successful SMT login |
|
|
User:admin |
85
|
2006-09-20 02:35:40 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
86
|
2006-09-20 02:35:35 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
87
|
2006-09-20 02:35:30 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
88
|
2006-09-20 02:35:29 |
IP collision, peer's MAC 00:00:AA:80:80:89 (WAN1). |
199.227.88.162 |
199.227.88.162 |
ARP REQUEST |
89
|
2006-09-20 02:35:25 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
90
|
2006-09-20 02:35:20 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
91
|
2006-09-20 02:35:19 |
IP collision, peer's MAC 00:00:AA:80:80:89 (WAN1). |
199.227.88.162 |
199.227.88.162 |
ARP REQUEST |
92
|
2006-09-20 02:35:15 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
93
|
2006-09-20 02:35:10 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
94
|
2006-09-20 02:35:09 |
IP collision, peer's MAC 00:00:AA:80:80:89 (WAN1). |
199.227.88.162 |
199.227.88.162 |
ARP REQUEST |
95
|
2006-09-20 02:35:05 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
96
|
2006-09-20 02:35:00 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
97
|
2006-09-20 02:34:59 |
IP collision, peer's MAC 00:00:AA:80:80:89 (WAN1). |
199.227.88.162 |
199.227.88.162 |
ARP REQUEST |
98
|
2006-09-20 02:34:55 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
99
|
2006-09-20 02:34:50 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
100
|
2006-09-20 02:34:49 |
IP collision, peer's MAC 00:00:AA:80:80:89 (WAN1). |
199.227.88.162 |
199.227.88.162 |
ARP REQUEST |
101
|
2006-09-20 02:34:45 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
102
|
2006-09-20 02:34:40 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
103
|
2006-09-20 02:34:39 |
IP collision, peer's MAC 00:00:AA:80:80:89 (WAN1). |
199.227.88.162 |
199.227.88.162 |
ARP REQUEST |
104
|
2006-09-20 02:34:35 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
105
|
2006-09-20 02:34:30 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
106
|
2006-09-20 02:34:28 |
IP collision, peer's MAC 00:00:AA:80:80:89 (WAN1). |
199.227.88.162 |
199.227.88.162 |
ARP REQUEST |
107
|
2006-09-20 02:34:25 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
108
|
2006-09-20 02:34:20 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
109
|
2006-09-20 02:34:18 |
IP collision, peer's MAC 00:00:AA:80:80:89 (WAN1). |
199.227.88.162 |
199.227.88.162 |
ARP REQUEST |
110
|
2006-09-20 02:34:15 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
111
|
2006-09-20 02:34:10 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
112
|
2006-09-20 02:34:08 |
IP collision, peer's MAC 00:00:AA:80:80:89 (WAN1). |
199.227.88.162 |
199.227.88.162 |
ARP REQUEST |
113
|
2006-09-20 02:34:05 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
114
|
2006-09-20 02:34:00 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
115
|
2006-09-20 02:33:58 |
IP collision, peer's MAC 00:00:AA:80:80:89 (WAN1). |
199.227.88.162 |
199.227.88.162 |
ARP REQUEST |
116
|
2006-09-20 02:33:55 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
117
|
2006-09-20 02:33:50 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
118
|
2006-09-20 02:33:48 |
IP collision, peer's MAC 00:00:AA:80:80:89 (WAN1). |
199.227.88.162 |
199.227.88.162 |
ARP REQUEST |
119
|
2006-09-20 02:33:45 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
120
|
2006-09-20 02:33:40 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
121
|
2006-09-20 02:33:38 |
IP collision, peer's MAC 00:00:AA:80:80:89 (WAN1). |
199.227.88.162 |
199.227.88.162 |
ARP REQUEST |
122
|
2006-09-20 02:33:35 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
123
|
2006-09-20 02:33:30 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
124
|
2006-09-20 02:33:27 |
IP collision, peer's MAC 00:00:AA:80:80:89 (WAN1). |
199.227.88.162 |
199.227.88.162 |
ARP REQUEST |
125
|
2006-09-20 02:33:25 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
126
|
2006-09-20 02:33:20 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |
127
|
2006-09-20 02:33:17 |
IP collision, peer's MAC 00:00:AA:80:80:89 (WAN1). |
199.227.88.162 |
199.227.88.162 |
ARP REQUEST |
128
|
2006-09-20 02:33:15 |
Connectivity ping check fails. |
199.227.88.162 |
199.227.88.161 |
WAN1 |