D-Link Forums
The Graveyard - Products No Longer Supported => IP Cameras => DCS-935L => Topic started by: FurryNutz on January 25, 2017, 11:11:50 AM
-
Firmware: v1.10 B01 01/25/2017 NA Region!
Revision Info:
Problems Fixed:
1. Wireless - AP Mode - fixed beacon broadcast issue when turn off AP mode.
Do a Factory reset and set up from scratch after FW has been loaded.
New Features:
1. mydlink agent upgrade to 2.1.0-b45.
2. Added UID support
D-Link posted DCS-935L Rev A firmware version v1.10 Build 01, which can be downloaded here: DCS-935L - Firmware v1.10.01 Download (http://support.dlink.com/productinfo.aspx?m=DCS-935L).
NOTE: Be sure that your wireless signal on the main host router is good and signal is strong with the camera if it's connected wirelessly. If your confident in this, upgrade via wireless with the camera can proceed. If your not confident in the wireless signal, use a wired LAN cable connection to the camera before upgrading the camera. This would help avoid any wireless FW upgrade problems.
- Network Cameras - Important Posts & Information (http://forums.dlink.com/index.php?topic=58121.0)
- Network Cameras - Beta Firmware Terms and Conditions (http://forums.dlink.com/index.php?topic=47672.0)
- Network Cameras - Why Have Multiple Hardware Versions for the Same Model? (http://forums.dlink.com/index.php?topic=57627.0)
Please post your comments and observations as a reply to this thread.
:) ;) :)
-
Failed update. Such a pain with these cameras because you then have to reset them and reprogram from scratch.
-
What browser are you using to update the FW? I recommend using IE11 or FF only and be sure to clear all browser caches before and after sending the FW file.
Also temporarily disable any PC security software while upgrading FW.
I think there is a save camera configuration to file that you can do then re-load after FW is updated...
-
I did it from the app. The problem with these being wireless only is once they die, there is no way to communicate. You have to reset them and the only way to set them up is by direct connecting with a smartphone. It is a very painful design.
-
So were you able to get it updated or is the camera not working at all now?
-
Nope. Seems to be bricked. The hard reset does not work. No way to connect to the camera.
-
Finally got it setup with a weird array of reset and reboots before the ad-hoc came to life and worked. It came up with the new firmware installed. Somehow the new firmware is preventing a hard reset back to original firmware, which is really scary.
-
I did it from the app. The problem with these being wireless only is once they die, there is no way to communicate. You have to reset them and the only way to set them up is by direct connecting with a smartphone. It is a very painful design.
Or a laptop... Or a wireless device for your PC...
-
Resets don't revert back to any prior version of FW. FW should be updated and kept up to date to maintain security and connection with the mydlink services.
Finally got it setup with a weird array of reset and reboots before the ad-hoc came to life and worked. It came up with the new firmware installed. Somehow the new firmware is preventing a hard reset back to original firmware, which is really scary.
-
Resets don't revert back to any prior version of FW. FW should be updated and kept up to date to maintain security and connection with the mydlink services.
??? Hard resets have always reverted to the original firmware in the past.
-
:o It shouldn't, factory reset should only clear camera configurations...
-
http://forums.dlink.com/index.php?topic=65474.msg278743#msg278743
SSID still visible on my side after updating several cameras.
***update****
Resetting to factory appears the only way to implement this fix. After doing this procedure the ssids are no longer visible.
-
Yes a factory reset is needed to ensure the previous FW and settings have been cleared out.
Glad the issue is resolved now.
Enjoy. ;)
-
Anyone else having trouble after this firmware? It is losing the network daily on mine. Now it won't connect at all and when put in ad-hoc mode, it does not broadcast an SSID, so there is no way to connect and fix. Painful.
-
Was a factory reset performed after the FW was updated? One should be as it seemed to fix this users issues after upgrading.
-
Was a factory reset performed after the FW was updated? One should be as it seemed to fix this users issues after upgrading.
Yes.
-
Need to try a factory reset and use the latest SW or app to get it setup. I thing it should broadcast it's own set up wifi so you can get it set up and choose your main host routers SSID name and PW.
What wireless modes are you using? 2.4 or 5Ghz?
Mixed modes or single N?
WPA2 and AES is recommended.
Manual channel 1, 6 or 11 on 2.4Ghz if there not busy.
-
Need to try a factory reset and use the latest SW or app to get it setup. I thing it should broadcast it's own set up wifi so you can get it set up and choose your main host routers SSID name and PW.
What wireless modes are you using? 2.4 or 5Ghz?
Mixed modes or single N?
WPA2 and AES is recommended.
Manual channel 1, 6 or 11 on 2.4Ghz if there not busy.
I have reset it. There is no way to connect to it and change settings or update anything. It is not broadcasting when in adhoc mode and without that it can't be connected to.
-
I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. We find that phone contact has better immediate results over using email.
Let us know how it goes please.
-
See this for potential solution: http://forums.dlink.com/index.php?topic=62708.45
-
Glad it worked for you. Thanks for posting.
See this for potential solution: http://forums.dlink.com/index.php?topic=62708.45
-
See this for potential solution: http://forums.dlink.com/index.php?topic=62708.45
Can't downgrade without being able to connect to the camera.
-
Can get the camera to connect to the main host router at all?
See this for potential solution: http://forums.dlink.com/index.php?topic=62708.45
Can't downgrade without being able to connect to the camera.
-
Can get the camera to connect to the main host router at all?
At all. It was explained above. Do you understand how this model works? If it will not connect to a router on its own, you must put it in "ad-hoc" mode, which allows you to connect directly to the camera and change settings. There is a button labelled "direct" on the camera, which is supposed to put it in this mode. It also is supposed to go there after a hard reset. Since installing this firmware version, the ad-hoc mode does not work and thus there is no way to communicate with the camera and change any settings. Basically updating to this firmware killed my camera.
-
I just got my 936L and 960L Monday. I see the process now.
I presume if you can't get the camera back to factory and it's wifi is not seen then, I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. We find that phone contact has better immediate results over using email.
Let us know how it goes please.
Can get the camera to connect to the main host router at all?
At all. It was explained above. Do you understand how this model works? If it will not connect to a router on its own, you must put it in "ad-hoc" mode, which allows you to connect directly to the camera and change settings. There is a button labelled "direct" on the camera, which is supposed to put it in this mode. It also is supposed to go there after a hard reset. Since installing this firmware version, the ad-hoc mode does not work and thus there is no way to communicate with the camera and change any settings. Basically updating to this firmware killed my camera.
-
Unfortunately it appears the SSID broadcasting issue has returned after several weeks. What is odd is that I did get them to not appear by factory resetting after updating the firmware, but now they are visible even after a power cycle.
They are still accessible via mydlink, and local browser connections, when they are in this state. However, it does appear to cause other cascading wireless issues since they are using the same broadcast channel as the router.
All Qty: 6 of these devices that were updated at the same time are now exhibiting the same behavior. As mentioned previously, all were factory reset after the 1.10 bios, and reconfigured through the mydlink app (ie I did not import any previous configurations). I pulled the power, and recycle the router, with no change in behavior. So it appears somehow that SSID setting to become visible is getting reset with time.
Other Environment Settings:
1) Netgear R7500V2, 2.4 and 5GHz enabled.
2) DCS-935L linked on 2.4, channel 2
3) DCS-935L will show SSID visible (DCS-935-XXXX) also on channel 2, 2.4 GHZ
4) SSID Would not display originally after factory reset (Aftern local network connection), but would become visible after a length of time.
The SSID now remains visible even after power reset.
5) ***Only setting that was manipulated outside of the Dlink app to install, was setting a static ip for each camera. I'm wondering if this is the source of the SSID becoming enabled.***
***Update******
Confirmed setting IP back to DHCP would hide the SSID, setting to manual IP would re-enable SSID with fw1.10. It appears to be a bug that will need to be reviewed.
-
So if you set a static IP address ON the camera, the cameras SSID would be enabled to broadcast after a period of time? So using DCHP auto assigned IP address seems to prevent this?
-
I have recently upgraded my firware. Now on my DCS-935L it says 1.10. But since my update I do not get any push messages when movement is there. Same goes for my DCH-Z110.
With the camera it's setup in my network (2.4G) WPA2 with DCHP. Access via APP and browser is flawless. But no e-mails to my account when movement should be detected and no push messages in my app. Hardware is A1
I opened a ticket at D-Link Benelux but the best thing they suggested was to erase notification rules.... as you can understand I hope to find more help here on the forums.
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)
- What region are you located?
Was the camera notifications working before the update?
Try removing the configuration from the camera then set up again or do a factory reset on the camera and set up from scratch and set up the email notifications and see what happens.
I have recently upgraded my firware. Now on my DCS-935L it says 1.10. But since my update I do not get any push messages when movement is there. Same goes for my DCH-Z110.
With the camera it's setup in my network (2.4G) WPA2 with DCHP. Access via APP and browser is flawless. But no e-mails to my account when movement should be detected and no push messages in my app. Hardware is A1
I opened a ticket at D-Link Benelux but the best thing they suggested was to erase notification rules.... as you can understand I hope to find more help here on the forums.
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)
- What region are you located?
Was the camera email notifications working before the update?
Try removing the configuration from the camera then set up again or do a factory reset on the camera and set up from scratch and set up the email notifications and see what happens.
I have recently upgraded my firware. Now on my DCS-935L it says 1.10. But since my update I do not get any push messages when movement is there. Same goes for my DCH-Z110.
With the camera it's setup in my network (2.4G) WPA2 with DCHP. Access via APP and browser is flawless. But no e-mails to my account when movement should be detected and no push messages in my app. Hardware is A1
I opened a ticket at D-Link Benelux but the best thing they suggested was to erase notification rules.... as you can understand I hope to find more help here on the forums.
Region is the Netherlands/Benelux.
Regarding e-mail notifications I didn't have that option on. I tried this after reading on this forum, as I have just found out I made a typo. Mail notification is working now.
1st attempt
- unplug power
- power on
- camera started and was accessible but no push notifications
2nd attempt
- Removed device via APP
- New install (with QR-code etc)
- Camera working again on Wifi and 3g/4g
- No push notification
3nd attempt
- Hard reset with needle in the back of camera
- No luck on push messages
-
So email notifications is working however mobile app push notifications is not working?
Did you load FW from this site?
http://www.dlink.com/nl/nl/support/product/dcs-935l-monitor-hd (http://www.dlink.com/nl/nl/support/product/dcs-935l-monitor-hd)
-
So email notifications is working however mobile app push notifications is not working?
Correct. And the mailnotifications is the one configured via www.mydlink.com (not via direct access on camera).
I've also downloaded the mydlink Lite app, but no difference no push messages.
-
What mobile platform are you using?
Might try downgrading to v1.09 and see if push notifications come back at all.
-
What mobile platform are you using?
Might try downgrading to v1.09 and see if push notifications come back at all.
The 935L does not have an UTP/RJ45 access. Is it without risk to downgrade?
Downgrade would be;
1) downloading other firmware
2) upload firmware via direct access on camera
3) execute
4) restart?
thanks so far for your help.
-
Be sure your PC is LAN wired to the main host router and that the camera has a good wireless signal.
Yes, you can send the FW file using it's web page UI. I would do a factory reset after the update and set up from scratch using the mydlink Lite app.
One thing you could do, give it a day and see if the push notifications come back. I've seen it where sometimes the notifications don't get fully enabled for a bit.
What mobile platform are you using?
Might try downgrading to v1.09 and see if push notifications come back at all.
The 935L does not have an UTP/RJ45 access. Is it without risk to downgrade?
Downgrade would be;
1) downloading other firmware
2) upload firmware via direct access on camera
3) execute
4) restart?
thanks so far for your help.
-
Be sure your PC is LAN wired to the main host router and that the camera has a good wireless signal.
Yes, you can send the FW file using it's web page UI. I would do a factory reset after the update and set up from scratch using the mydlink Lite app.
One thing you could do, give it a day and see if the push notifications come back. I've seen it where sometimes the notifications don't get fully enabled for a bit.
What mobile platform are you using?
Might try downgrading to v1.09 and see if push notifications come back at all.
The 935L does not have an UTP/RJ45 access. Is it without risk to downgrade?
Downgrade would be;
1) downloading other firmware
2) upload firmware via direct access on camera
3) execute
4) restart?
thanks so far for your help.
Thanks I will try and get back to you with the result.
-
;)
-
;)
Reset the firmware but no luck. So far my whole home security set is uselless. The camera now isn't connecting via the app (direct acces onn wifi is possible).
Just received my smoke detector today, sadly enough this one isn't working either on the system. No luck in adding it via the app.
Do you have direct phone number for support?
-
Try this page:
http://www.dlink.com/nl/nl/support/contact?product=DCS-935L&description=email+notifications (http://www.dlink.com/nl/nl/support/contact?product=DCS-935L&description=email+notifications)
AT the bottom of the page, select Telefoon tab.
-
Try this page:
http://www.dlink.com/nl/nl/support/contact?product=DCS-935L&description=email+notifications (http://www.dlink.com/nl/nl/support/contact?product=DCS-935L&description=email+notifications)
AT the bottom of the page, select Telefoon tab.
Thanks I will call them.
-
;)
-
Well, I did the upgrade in the hopes that it would fix the issue with the SSID being visible, as well as the numerous blackouts that are interpreted as motion.
Well, the blackouts might be fixed but I wouldn't know - I don't get any email notifications anymore. I upgraded the firmware last Friday. I noticed I hadn't received any motion alerts yesterday, so I took a look at things. I can get live video through the webpage and the MyDlink app, but I'm not getting any notifications. Looking at the logs, it's not registering motion at all. I tried turning up the sensitivity to 100%, but waving something in front of the camera does nothing. I rebooted the camera, and it took almost 15 minutes (!) to come back. Hurray! Email notifications were coming through! Two of them. Now it's not registering motion again.
I have 5 different models of Dlink cameras, this being the newest. _None_ of them have been particularly reliable, but this one is by far the worst. It's extremely frustrating and a waste of time. I looks like it's time to bin them and look for a new solution.
Thanks,
Brian
-
Did you phone contact your regional D-Link support office yet?
Try this page:
http://www.dlink.com/nl/nl/support/contact?product=DCS-935L&description=email+notifications (http://www.dlink.com/nl/nl/support/contact?product=DCS-935L&description=email+notifications)
AT the bottom of the page, select Telefoon tab.
Thanks I will call them.
-
Hi,
Since upgrade to v1.10.01, my DCS-935L have errors to send email notifications.
When I reboot cam, email notifications are ok one or two times but after there no more notifications and I have this system error :
eMail: upload /tmp/event/eventrec20170709_121927.mp4 failed: -10
Test send email video clip and instant are ok.
Version matériel A1
Version de l'agent 2.1.0-b45
Do you see the problem ?
Al thanks
Fred
-
Has a factory reset been performed then set up from scratch? Might try this first.
If not, try downgrading back to previous version of FW to see if any changes.
-
Hi!
I have also problems since upgrade to v1.10.01... is more instable - the cam hangs at all and only a hard reset help to get it back working.
Since the ping was disabled by firmeware, I had to move on to http request to check if cam is still online. checking it whole day long, the cam is dieing, not every day, but often...
Anyone has also this problem? I think this must be a mem leak in webserver on the cam...
how can I downgrade to old firmware version? where to download?
thanks, raimund
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=49573.0)
- What region are you located?
What Mfr and model is the main host router?
What wireless modes are you using?
What is the distance between the Camera and the main host router?
How many other wireless devices do you have connected to the main host router?
- Any 2.4Ghz or 5Ghz cordless house phones or WiFi APs near by that maybe causing interferences?
- Any other WiFi routers in the area that maybe causing interferences? Link> Use a WiFi Scanner (http://forums.dlink.com/index.php?topic=48327.0) to find out. How many?
I recommend setting a static IP address ON the cameras outside of the main host routers default DHCP IP address pool as a troubleshooting step: 192.168.#.93 DHCP (http://forums.dlink.com/index.php?topic=58017.0)
Test cameras with uPnP and uPnP Port Forwarding both enabled on ALL cameras: DCS Cloud (L) Series Camera Configuration and Mydlink.com (http://forums.dlink.com/index.php?topic=62395.0)
Hi!
I have also problems since upgrade to v1.10.01... is more instable - the cam hangs at all and only a hard reset help to get it back working.
Since the ping was disabled by firmeware, I had to move on to http request to check if cam is still online. checking it whole day long, the cam is dieing, not every day, but often...
Anyone has also this problem? I think this must be a mem leak in webserver on the cam...
how can I downgrade to old firmware version? where to download?
thanks, raimund
-
Hi!
My DCS-935L keeps trying to connect to several outbound ip addresses for example 52.8.86.161, 54.193.41.31, 52.17.177.126, 54.169.242.162, 216.146.43.71. Is there a way to disable this?
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)
- What region are you located?
What Mfr and model is the main host router?
Use www.domaintools.com (http://www.domaintools.com) whois look up tool to see where those IP addresses are going first:
Of of them points to Amazon:
NetRange: 52.0.0.0 - 52.31.255.255
CIDR: 52.0.0.0/11
NetName: AT-88-Z
NetHandle: NET-52-0-0-0-1
Parent: NET52 (NET-52-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Amazon Technologies Inc. (AT-88-Z)
Hi!
My DCS-935L keeps trying to connect to several outbound ip addresses for example 52.8.86.161, 54.193.41.31, 52.17.177.126, 54.169.242.162, 216.146.43.71. Is there a way to disable this?
-
The first two are Amazon in California, the second two are Amazon in Ireland, and the last one is Dynamic Network Services Inc (DYN.com - DDNS service).
The Amazon IPs are most likely for the mydlink services.
-
Thanks for the info. Figured as much. ::)
-
Thanks for the info.
- What region are you located?
The Netherlands
The first two are Amazon in California, the second two are Amazon in Ireland, and the last one is Dynamic Network Services Inc (DYN.com - DDNS service).
The Amazon IPs are most likely for the mydlink services.
DDNS was already disabled but still outbound connections to 216.146.43.71? That's weird. Any idea why this is happening? How can I disable the mydlink services?
-
Are you using or needing Mydlink services at all? If not then you can do a factory reset on the camera and just not set up mydlink features. This should stop all services from being accessed. I would remove the device from the mydlink service site as well.
-
Hi FurryNutz,
Are you using or needing Mydlink services at all?
No.
If not then you can do a factory reset on the camera and just not set up mydlink features.
Did that.
This should stop all services from being accessed.
No, still the same as you can see here:
Mar 9 21:50:20 debian kernel: [86435.855387] loc-net DROP IN=eth1 OUT=eth0 MAC=e8:94:f6:02:6b:08:b0:c5:54:24:f8:02:08:00 SRC=192.168.168.117
DST=54.254.189.209 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=31446 DF PROTO=TCP SPT=40435 DPT=443 WINDOW=5840 RES=0x00 SYN URGP=0
Mar 9 21:50:20 debian kernel: [86436.585960] loc-net DROP IN=eth1 OUT=eth0 MAC=e8:94:f6:02:6b:08:b0:c5:54:24:f8:02:08:00 SRC=192.168.168.117
DST=216.146.38.70 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=28547 DF PROTO=TCP SPT=40277 DPT=80 WINDOW=5840 RES=0x00 SYN URGP=0
Mar 9 21:50:23 debian kernel: [86438.851655] loc-net DROP IN=eth1 OUT=eth0 MAC=e8:94:f6:02:6b:08:b0:c5:54:24:f8:02:08:00 SRC=192.168.168.117
DST=54.254.189.209 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=31447 DF PROTO=TCP SPT=40435 DPT=443 WINDOW=5840 RES=0x00 SYN URGP=0
Mar 9 21:50:23 debian kernel: [86439.581671] loc-net DROP IN=eth1 OUT=eth0 MAC=e8:94:f6:02:6b:08:b0:c5:54:24:f8:02:08:00 SRC=192.168.168.117
DST=216.146.38.70 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=28548 DF PROTO=TCP SPT=40277 DPT=80 WINDOW=5840 RES=0x00 SYN URGP=0
Mar 9 21:50:29 debian kernel: [86444.851662] loc-net DROP IN=eth1 OUT=eth0 MAC=e8:94:f6:02:6b:08:b0:c5:54:24:f8:02:08:00 SRC=192.168.168.117
DST=54.254.189.209 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=31448 DF PROTO=TCP SPT=40435 DPT=443 WINDOW=5840 RES=0x00 SYN URGP=0
Mar 9 21:50:29 debian kernel: [86445.581980] loc-net DROP IN=eth1 OUT=eth0 MAC=e8:94:f6:02:6b:08:b0:c5:54:24:f8:02:08:00 SRC=192.168.168.117
DST=216.146.38.70 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=28549 DF PROTO=TCP SPT=40277 DPT=80 WINDOW=5840 RES=0x00 SYN URGP=0
Mar 9 21:50:41 debian kernel: [86457.582187] loc-net DROP IN=eth1 OUT=eth0 MAC=e8:94:f6:02:6b:08:b0:c5:54:24:f8:02:08:00 SRC=192.168.168.117
DST=216.146.38.70 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=28550 DF PROTO=TCP SPT=40277 DPT=80 WINDOW=5840 RES=0x00 SYN URGP=0
Mar 9 21:51:05 debian kernel: [86481.066298] loc-net DROP IN=eth1 OUT=eth0 MAC=e8:94:f6:02:6b:08:b0:c5:54:24:f8:02:08:00 SRC=192.168.168.117
DST=54.229.64.81 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=10744 DF PROTO=TCP SPT=36108 DPT=443 WINDOW=5840 RES=0x00 SYN URGP=0
Mar 9 21:51:05 debian kernel: [86481.581999] loc-net DROP IN=eth1 OUT=eth0 MAC=e8:94:f6:02:6b:08:b0:c5:54:24:f8:02:08:00 SRC=192.168.168.117
DST=216.146.38.70 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=28551 DF PROTO=TCP SPT=40277 DPT=80 WINDOW=5840 RES=0x00 SYN URGP=0
Mar 9 21:51:08 debian kernel: [86484.062194] loc-net DROP IN=eth1 OUT=eth0 MAC=e8:94:f6:02:6b:08:b0:c5:54:24:f8:02:08:00 SRC=192.168.168.117
DST=54.229.64.81 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=10745 DF PROTO=TCP SPT=36108 DPT=443 WINDOW=5840 RES=0x00 SYN URGP=0
Mar 9 21:51:14 debian kernel: [86490.062106] loc-net DROP IN=eth1 OUT=eth0 MAC=e8:94:f6:02:6b:08:b0:c5:54:24:f8:02:08:00 SRC=192.168.168.117
DST=54.229.64.81 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=10746 DF PROTO=TCP SPT=36108 DPT=443 WINDOW=5840 RES=0x00 SYN URGP=0
Mar 9 21:51:35 debian kernel: [86511.104770] loc-net DROP IN=eth1 OUT=eth0 MAC=e8:94:f6:02:6b:08:b0:c5:54:24:f8:02:08:00 SRC=192.168.168.117
DST=54.194.162.25 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=15102 DF PROTO=TCP SPT=34379 DPT=443 WINDOW=5840 RES=0x00 SYN URGP=0
Mar 9 21:51:38 debian kernel: [86514.102218] loc-net DROP IN=eth1 OUT=eth0 MAC=e8:94:f6:02:6b:08:b0:c5:54:24:f8:02:08:00 SRC=192.168.168.117
DST=54.194.162.25 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=15103 DF PROTO=TCP SPT=34379 DPT=443 WINDOW=5840 RES=0x00 SYN URGP=0
Mar 9 21:51:44 debian kernel: [86520.102245] loc-net DROP IN=eth1 OUT=eth0 MAC=e8:94:f6:02:6b:08:b0:c5:54:24:f8:02:08:00 SRC=192.168.168.117
DST=54.194.162.25 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=15104 DF PROTO=TCP SPT=34379 DPT=443 WINDOW=5840 RES=0x00 SYN URGP=0
Mar 9 21:51:53 debian kernel: [86529.582418] loc-net DROP IN=eth1 OUT=eth0 MAC=e8:94:f6:02:6b:08:b0:c5:54:24:f8:02:08:00 SRC=192.168.168.117
DST=216.146.38.70 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=28552 DF PROTO=TCP SPT=40277 DPT=80 WINDOW=5840 RES=0x00 SYN URGP=0
I would remove the device from the mydlink service site as well.
Did that too.
Do you have any other ideas?
-
mydlink cameras will broadcast to mydlink servers regardless if you sign up for it or not.
-
Thanks for this info.