f/w 1.12 on 2330l
192.168.0.129 is my DNR-202L.
41. 2016-08-23 16:51:51 User from 192.168.0.129 login failed & lock web service
42. 2016-08-23 16:05:57 User from 192.168.0.129 login failed & lock web service
43. 2016-08-23 15:39:13 User from 192.168.0.129 login failed & lock web service
44. 2016-08-23 15:16:37 User from 192.168.0.129 login failed & lock web service
45. 2016-08-23 14:28:57 User from 192.168.0.129 login failed & lock web service
46. 2016-08-23 13:28:53 User from 192.168.0.129 login failed & lock web service
47. 2016-08-23 12:57:01 User from 192.168.0.129 login failed & lock web service
48. 2016-08-23 12:34:33 User from 192.168.0.129 login failed & lock web service
49. 2016-08-23 11:42:34 User from 192.168.0.129 login failed & lock web service
50. 2016-08-23 11:02:52 User from 192.168.0.129 login failed & lock web service
51. 2016-08-23 09:40:19 User from 192.168.0.129 login failed & lock web service
52. 2016-08-23 08:17:44 User from 192.168.0.129 login failed & lock web service
53. 2016-08-23 07:52:04 User from 192.168.0.129 login failed & lock web service
54. 2016-08-23 06:48:43 User from 192.168.0.129 login failed & lock web service
55. 2016-08-23 04:38:02 User from 192.168.0.129 login failed & lock web service
56. 2016-08-23 04:16:29 User from 192.168.0.129 login failed & lock web service
57. 2016-08-23 03:58:28 User from 192.168.0.129 login failed & lock web service
58. 2016-08-23 03:38:28 User from 192.168.0.129 login failed & lock web service
59. 2016-08-23 02:41:52 User from 192.168.0.129 login failed & lock web service
60. 2016-08-23 01:13:33 admin FROM 192.168.0.141 LOGIN OK
Other DCS-2230L cam on DNR-202L
21. 2016-08-23 13:20:20 User from 192.168.0.129 login failed & lock web service
22. 2016-08-23 12:54:40 User from 192.168.0.129 login failed & lock web service
23. 2016-08-23 12:44:47 User from 192.168.0.129 login failed & lock web service
24. 2016-08-23 12:32:28 User from 192.168.0.129 login failed & lock web service
25. 2016-08-23 11:21:28 User from 192.168.0.129 login failed & lock web service
26. 2016-08-23 11:04:45 User from 192.168.0.129 login failed & lock web service
27. 2016-08-23 10:53:49 User from 192.168.0.129 login failed & lock web service
28. 2016-08-23 10:37:20 User from 192.168.0.129 login failed & lock web service
29. 2016-08-23 10:22:43 User from 192.168.0.129 login failed & lock web service
30. 2016-08-23 09:38:00 User from 192.168.0.129 login failed & lock web service
31. 2016-08-23 08:17:41 User from 192.168.0.129 login failed & lock web service
32. 2016-08-23 07:54:11 User from 192.168.0.129 login failed & lock web service
33. 2016-08-23 07:36:48 User from 192.168.0.129 login failed & lock web service
34. 2016-08-23 06:50:29 User from 192.168.0.129 login failed & lock web service
35. 2016-08-23 06:34:32 User from 192.168.0.129 login failed & lock web service
36. 2016-08-23 05:01:05 User from 192.168.0.129 login failed & lock web service
37. 2016-08-23 04:35:48 User from 192.168.0.129 login failed & lock web service
38. 2016-08-23 04:16:19 User from 192.168.0.129 login failed & lock web service
39. 2016-08-23 04:04:19 User from 192.168.0.129 login failed & lock web service
40. 2016-08-23 03:56:20 User from 192.168.0.129 login failed & lock web service
ftp://ftp2.dlink.com/PRODUCTS/DCS-2330L/REVA/DCS-2330L_REVA_RELEASENOTES_1.12.00_EN.PDFV1.10.07
1. Update mydlink agent version to 2.0.19-b23
2. Add the login check mechanism on Web GUI to solve Brute Force Attack
issueIE is crashing, I'll review the video dates later on.