Camera disconnect after a few days
Hi
I have a few C310 cameras, the one started behaving wierdly, after about 8 months of no issues, it would start blinking orange and not be on the network. I will then power cycle and then it's fine again for 2 to 4 days, then disconnects again. It has full Wi-Fi, about 10m from a AP.
Anyone seen this?
@Wayne-TP The camera is about 5 meters from a Deco M4, and the signal shows full strength. It has been in the same location for 11 months, so I don't understand why this issue started a few weeks ago. DNS is also set to 8.8.8.8 and 8.8.4.4.
<4>2025-02-07 19:17:54[tpssl][15.067]domain: security.iot.i.tplinknbu.com DNS failed, error_type: 1006.
1006
1006 is a reserved value and MUST NOT be set as a status code in a
Close control frame by an endpoint. It is designated for use in
applications expecting a status code to indicate that the
connection was closed abnormally, e.g., without sending or
receiving a Close control frame.
"rfc6455#section-7.4.1"
Local Mac to Camera ping
ping 192.168.0.73
PING 192.168.0.73 (192.168.0.73): 56 data bytes
64 bytes from 192.168.0.73: icmp_seq=0 ttl=64 time=7.497 ms
64 bytes from 192.168.0.73: icmp_seq=1 ttl=64 time=5.446 ms
64 bytes from 192.168.0.73: icmp_seq=2 ttl=64 time=5.442 ms
64 bytes from 192.168.0.73: icmp_seq=3 ttl=64 time=5.525 ms
64 bytes from 192.168.0.73: icmp_seq=4 ttl=64 time=5.052 ms
64 bytes from 192.168.0.73: icmp_seq=5 ttl=64 time=9.132 ms
64 bytes from 192.168.0.73: icmp_seq=6 ttl=64 time=5.388 ms
64 bytes from 192.168.0.73: icmp_seq=7 ttl=64 time=5.426 ms
64 bytes from 192.168.0.73: icmp_seq=8 ttl=64 time=6.523 ms
64 bytes from 192.168.0.73: icmp_seq=9 ttl=64 time=4.200 ms
64 bytes from 192.168.0.73: icmp_seq=10 ttl=64 time=8.014 ms
64 bytes from 192.168.0.73: icmp_seq=11 ttl=64 time=6.573 ms
64 bytes from 192.168.0.73: icmp_seq=12 ttl=64 time=4.828 ms
^C
--- 192.168.0.73 ping statistics ---
13 packets transmitted, 13 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 4.200/6.080/9.132/1.350 ms
Nslookup from Mac
nslookup aps1-relay-dcipc-beta.i.tplinknbu.com
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: aps1-relay-dcipc-beta.i.tplinknbu.com
Address: 13.213.85.116
Name: aps1-relay-dcipc-beta.i.tplinknbu.com
Address: 52.74.101.218
nslookup security.iot.i.tplinknbu.com
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
security.iot.i.tplinknbu.com canonical name = aps1-security.iot.i.tplinknbu.com.
aps1-security.iot.i.tplinknbu.com canonical name = aps1-wap-eks-v2-firewall.i.tplinknbu.com.
Name: aps1-wap-eks-v2-firewall.i.tplinknbu.com
Address: 18.142.188.160
Name: aps1-wap-eks-v2-firewall.i.tplinknbu.com
Address: 3.1.225.169
Name: aps1-wap-eks-v2-firewall.i.tplinknbu.com
Address: 52.76.53.101
Name: aps1-wap-eks-v2-firewall.i.tplinknbu.com
Address: 13.228.46.223
Log File from Camera
<4>2025-02-07 07:10:58[DHCPC]Start dhcp.
<4>2025-02-07 07:10:58[DHCPC]br-wan set ip ********* mask 255.255.255.0 gateway 192.168.0.1 lease time -1
<4>2025-02-07 07:10:58[DHCPC]End dhcp.
<4>2025-02-07 07:10:58[NIFC]Link status: LINK_DOWN -> LINK_UP
<4>2025-02-07 07:10:58[NIFC]IP: *********, mask: 255.255.255.0, gateway: 192.168.0.1, DNS: 8.8.8.8, 8.8.4.4
<4>2025-02-07 07:10:58[SNTPC]link_status change to :1
<4>2025-02-07 07:10:58[RTSP]config changes rtsp_reload
<4>2025-02-07 07:10:58[UPNPC]reload over
<4>2025-02-07 07:10:58[HTTP]config changes http_reload
<4>2025-02-07 07:10:59[tpssl][21.163]domain: aps1-relay-dcipc-beta.i.tplinknbu.com DNS failed, error_type: 1006.
<4>2025-02-07 07:10:59[tpssl][21.613]DNS security.iot.i.tplinknbu.com --> 13.213.181.25
<4>2025-02-07 07:11:00[tpssl][22.014]ip:13.213.181.25 tcp connecting --> tcp connected.
<4>2025-02-07 07:11:00[tpssl][22.051]ip:13.213.181.25 tcp connected --> ssl connecting.
<4>2025-02-07 07:11:01[tpssl][23.473]ip:13.213.181.25 ssl connecting --> ssl connected.
<2>2025-02-07 07:11:02[SNTPC]send svr: 128.138.140.44(ip:747408000)
<2>2025-02-07 07:11:02[SNTPC]recived from 747408000.
<2>2025-02-07 07:11:02[SNTPC]set time: 1738905446
<4>2025-02-07 07:17:26[SYSTEM]System time is calibrated by SNTP.
<4>2025-02-07 07:17:26[STM]record_plan new rec type:(motion)
<4>2025-02-07 07:17:26[CloudIot]recv jwt suc: 1
<4>2025-02-07 07:17:26[tpssl][24.725]DNS euw1-device-cloudgateway.iot.i.tplinknbu.com --> 54.170.92.104
<4>2025-02-07 07:17:26[tpssl][25.026]ip:54.170.92.104 tcp connecting --> tcp connected.
<4>2025-02-07 07:17:26[tpssl][25.027]ip:54.170.92.104 tcp connected --> ssl connecting.
<4>2025-02-07 07:17:27[tpssl][25.875]ip:54.170.92.104 ssl connecting --> ssl connected.
<4>2025-02-07 07:17:27[CloudIot]MQTT conn
<4>2025-02-07 07:17:27[CloudIot]MQTT all topics succ
<4>2025-02-07 07:17:27[CloudIot]req ntp succ
<4>2025-02-07 07:17:27[CloudIot]post IoT onoff: 1
<4>2025-02-07 07:17:28[CloudIot]NTP: DevReq: 27, IoTRecvUtc: 1738905448, IoTRespUtc: 1738905448, DevRecv: 27, Sync: 1738905448
(1312)20250207 19:17:56
<4>2025-02-07 19:17:52[STM]record started
<13>2025-02-07 19:17:52[REMOTE_DEBUGGER]diagnose_log: id(1300), offset(73728)
<4>2025-02-07 19:17:52[SYSTEM]System time is calibrated by SD card.
<4>2025-02-07 19:17:52[STM]record_plan new rec type:(motion)
<4>2025-02-07 19:17:54[tpssl][15.067]domain: security.iot.i.tplinknbu.com DNS failed, error_type: 1006.
<2>2025-02-07 19:17:54[CloudIot]http 0 conn err: 1006.
<4>2025-02-07 19:17:55[tpssl][16.138]domain: aps1-relay-dcipc-beta.i.tplinknbu.com DNS failed, error_type: 1006.
@Wayne-TP Hi, it is in the network range just not dhcp, my network range is 192.168.0.0/24. The ER605 has fixed IP leases for my network equipment and cameras.
Clients
192.168.0.128/25
192.168.0.128-128.168.0.255
128 IPs
DHCP 192.168.0.128 - 192.168.0.199
Fixed IP 192.168.0.200 - 192.168.0.254
Open Range
192.168.0.96/27
192.168.0.96 - 192.168.0.128
IPs 32
Network infra
192.168.0.1/26
192.168.0.1 - 192.168.0.63
64 IPs
Camera's 192.168.0.64/27
192.168.0.64-192.168.0.95
32 IPs
Camera Network Settigns
Network Settings
