Smart Home Community > Tapo Smart Camera > C520WS and Tapo app on device with different vlan issues
< Tapo Smart Camera

C520WS and Tapo app on device with different vlan issues

C520WS and Tapo app on device with different vlan issues

C520WS and Tapo app on device with different vlan issues
C520WS and Tapo app on device with different vlan issues
2025-06-26 06:09:40 - last edited 2025-06-26 06:16:52
Model: Tapo C520WS  
Hardware Version: V1
Firmware Version: Version:1.3.2 Build 250228 Rel.53151n

 

When phone and camera are on different subnets/vlans Tapo app image freezes 5 secondes in and its on and off like this all the time disconnects reconnects(firewall rules are open at the moment) . Multicast is working but seems like since devices are on seprate subnets its causing issues.

 

When i go to the same ssid/subnet, its perfect.

 

Sorry for the time stamps but i had to copy paste portions of the dump. It seems like communication is working but ping ponging between local requests and fall back to web and back and forth. 

 

01:28:12.579699 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 40

01:28:12.733120 IP ec2-44-196-194-88.compute-1.amazonaws.com.https > c520ws.m1.lan.37514: Flags [P.], seq 27988:28311, ack 49087, win 502, options [nop,nop,TS val 321148080 ecr 4017915495], length 323

01:28:12.739095 IP c520ws.m1.lan.37514 > ec2-44-196-194-88.compute-1.amazonaws.com.https: Flags [.], ack 28311, win 16462, options [nop,nop,TS val 4017930492 ecr 321148080], length 0

01:28:12.802157 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 40

01:28:12.802164 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 282

01:28:12.802165 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 48

01:28:12.981390 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 40

01:28:13.183483 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 40

01:28:13.384282 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 40

01:28:13.584360 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 40

01:28:13.787761 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 40

01:27:59.543288 IP c520ws.m1.lan.42502 > bober-s-z-fold5.m1.lan.33255: UDP, length 64

01:27:59.720000 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 40

01:27:59.730449 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 282

01:27:59.730464 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 48

01:27:59.802192 IP c520ws.m1.lan.42502 > bober-s-z-fold5.m1.lan.33255: UDP, length 64

01:27:59.923081 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 40

01:28:00.065267 IP c520ws.m1.lan.42502 > bober-s-z-fold5.m1.lan.33255: UDP, length 64

01:28:00.143118 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 40

01:28:00.322384 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 40

01:28:00.552824 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 40

01:28:00.758936 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 40

01:28:00.758958 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 282

01:27:48.042928 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2303488:2304916, ack 4259, win 7920, options [nop,nop,TS val 3547900947 ecr 1256908911], length 1428

01:27:48.042929 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2304916:2306344, ack 4259, win 7920, options [nop,nop,TS val 3547900947 ecr 1256908911], length 1428

01:27:48.044359 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2306344:2307772, ack 4259, win 7920, options [nop,nop,TS val 3547900947 ecr 1256908911], length 1428

01:27:48.044361 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2307772:2309200, ack 4259, win 7920, options [nop,nop,TS val 3547900948 ecr 1256908912], length 1428

01:27:48.044362 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2309200:2310628, ack 4259, win 7920, options [nop,nop,TS val 3547900948 ecr 1256908912], length 1428

01:27:48.053683 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2293492, win 68, options [nop,nop,TS val 1256908925 ecr 3547900942], length 0

01:27:48.054823 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2296348, win 68, options [nop,nop,TS val 1256908926 ecr 3547900943], length 0

01:27:48.054838 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2299204, win 68, options [nop,nop,TS val 1256908926 ecr 3547900944], length 0

01:27:48.056563 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2302060, win 68, options [nop,nop,TS val 1256908928 ecr 3547900945], length 0

01:27:48.057965 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2306344, win 68, options [nop,nop,TS val 1256908929 ecr 3547900947], length 0

01:27:48.059472 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2310628, win 68, options [nop,nop,TS val 1256908931 ecr 3547900947], length 0

01:27:48.060348 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2310628:2312056, ack 4259, win 7920, options [nop,nop,TS val 3547900964 ecr 1256908925], length 1428

01:27:48.060350 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2312056:2313484, ack 4259, win 7920, options [nop,nop,TS val 3547900964 ecr 1256908925], length 1428

01:27:48.061870 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2313484:2314912, ack 4259, win 7920, options [nop,nop,TS val 3547900965 ecr 1256908926], length 1428

01:27:48.061890 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2314912:2316340, ack 4259, win 7920, options [nop,nop,TS val 3547900965 ecr 1256908926], length 1428

01:27:48.062546 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2316340:2317768, ack 4259, win 7920, options [nop,nop,TS val 3547900966 ecr 1256908926], length 1428

01:27:48.062548 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2317768:2319196, ack 4259, win 7920, options [nop,nop,TS val 3547900966 ecr 1256908926], length 1428

01:27:48.062549 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2319196:2320624, ack 4259, win 7920, options [nop,nop,TS val 3547900966 ecr 1256908928], length 1428

01:27:48.062606 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2320624:2322052, ack 4259, win 7920, options [nop,nop,TS val 3547900966 ecr 1256908928], length 1428

01:27:48.063496 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2322052:2323480, ack 4259, win 7920, options [nop,nop,TS val 3547900967 ecr 1256908929], length 1428

01:27:48.063541 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2323480:2324908, ack 4259, win 7920, options [nop,nop,TS val 3547900967 ecr 1256908929], length 1428

01:27:48.063542 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2324908:2326336, ack 4259, win 7920, options [nop,nop,TS val 3547900967 ecr 1256908929], length 1428

01:27:48.063543 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2326336:2327764, ack 4259, win 7920, options [nop,nop,TS val 3547900967 ecr 1256908929], length 1428

01:27:48.064228 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2327764:2329192, ack 4259, win 7920, options [nop,nop,TS val 3547900967 ecr 1256908931], length 1428

01:27:48.064230 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2329192:2330620, ack 4259, win 7920, options [nop,nop,TS val 3547900967 ecr 1256908931], length 1428

01:27:48.064231 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2330620:2332048, ack 4259, win 7920, options [nop,nop,TS val 3547900968 ecr 1256908931], length 1428

01:27:48.072866 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 40

01:27:48.075488 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2313484, win 68, options [nop,nop,TS val 1256908947 ecr 3547900964], length 0

01:27:48.077074 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2316340, win 68, options [nop,nop,TS val 1256908948 ecr 3547900965], length 0

01:27:48.077594 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2319196, win 68, options [nop,nop,TS val 1256908949 ecr 3547900966], length 0

01:27:48.077596 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2322052, win 68, options [nop,nop,TS val 1256908949 ecr 3547900966], length 0

01:27:48.078804 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2327764, win 68, options [nop,nop,TS val 1256908950 ecr 3547900967], length 0

01:27:48.079362 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2330620, win 68, options [nop,nop,TS val 1256908951 ecr 3547900967], length 0

01:27:48.042928 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2303488:2304916, ack 4259, win 7920, options [nop,nop,TS val 3547900947 ecr 1256908911], length 1428

01:27:48.042929 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2304916:2306344, ack 4259, win 7920, options [nop,nop,TS val 3547900947 ecr 1256908911], length 1428

01:27:48.044359 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2306344:2307772, ack 4259, win 7920, options [nop,nop,TS val 3547900947 ecr 1256908911], length 1428

01:27:48.044361 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2307772:2309200, ack 4259, win 7920, options [nop,nop,TS val 3547900948 ecr 1256908912], length 1428

01:27:48.044362 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2309200:2310628, ack 4259, win 7920, options [nop,nop,TS val 3547900948 ecr 1256908912], length 1428

01:27:48.053683 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2293492, win 68, options [nop,nop,TS val 1256908925 ecr 3547900942], length 0

01:27:48.054823 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2296348, win 68, options [nop,nop,TS val 1256908926 ecr 3547900943], length 0

01:27:48.054838 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2299204, win 68, options [nop,nop,TS val 1256908926 ecr 3547900944], length 0

01:27:48.056563 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2302060, win 68, options [nop,nop,TS val 1256908928 ecr 3547900945], length 0

01:27:48.057965 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2306344, win 68, options [nop,nop,TS val 1256908929 ecr 3547900947], length 0

01:27:48.059472 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2310628, win 68, options [nop,nop,TS val 1256908931 ecr 3547900947], length 0

01:27:48.060348 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2310628:2312056, ack 4259, win 7920, options [nop,nop,TS val 3547900964 ecr 1256908925], length 1428

01:27:48.060350 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2312056:2313484, ack 4259, win 7920, options [nop,nop,TS val 3547900964 ecr 1256908925], length 1428

01:27:48.061870 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2313484:2314912, ack 4259, win 7920, options [nop,nop,TS val 3547900965 ecr 1256908926], length 1428

01:27:48.061890 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2314912:2316340, ack 4259, win 7920, options [nop,nop,TS val 3547900965 ecr 1256908926], length 1428

01:27:48.062546 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2316340:2317768, ack 4259, win 7920, options [nop,nop,TS val 3547900966 ecr 1256908926], length 1428

01:27:48.062548 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2317768:2319196, ack 4259, win 7920, options [nop,nop,TS val 3547900966 ecr 1256908926], length 1428

01:27:48.062549 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2319196:2320624, ack 4259, win 7920, options [nop,nop,TS val 3547900966 ecr 1256908928], length 1428

01:27:48.062606 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2320624:2322052, ack 4259, win 7920, options [nop,nop,TS val 3547900966 ecr 1256908928], length 1428

01:27:48.063496 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2322052:2323480, ack 4259, win 7920, options [nop,nop,TS val 3547900967 ecr 1256908929], length 1428

01:27:48.063541 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2323480:2324908, ack 4259, win 7920, options [nop,nop,TS val 3547900967 ecr 1256908929], length 1428

01:27:48.063542 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2324908:2326336, ack 4259, win 7920, options [nop,nop,TS val 3547900967 ecr 1256908929], length 1428

01:27:48.063543 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2326336:2327764, ack 4259, win 7920, options [nop,nop,TS val 3547900967 ecr 1256908929], length 1428

01:27:48.064228 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2327764:2329192, ack 4259, win 7920, options [nop,nop,TS val 3547900967 ecr 1256908931], length 1428

01:27:48.064230 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2329192:2330620, ack 4259, win 7920, options [nop,nop,TS val 3547900967 ecr 1256908931], length 1428

01:27:48.064231 IP c520ws.m1.lan.49612 > 158.101.96.128.https: Flags [.], seq 2330620:2332048, ack 4259, win 7920, options [nop,nop,TS val 3547900968 ecr 1256908931], length 1428

01:27:48.072866 IP bober-s-z-fold5.m1.lan.60526 > c520ws.m1.lan.57296: UDP, length 40

01:27:48.075488 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2313484, win 68, options [nop,nop,TS val 1256908947 ecr 3547900964], length 0

01:27:48.077074 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2316340, win 68, options [nop,nop,TS val 1256908948 ecr 3547900965], length 0

01:27:48.077594 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2319196, win 68, options [nop,nop,TS val 1256908949 ecr 3547900966], length 0

01:27:48.077596 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2322052, win 68, options [nop,nop,TS val 1256908949 ecr 3547900966], length 0

01:27:48.078804 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2327764, win 68, options [nop,nop,TS val 1256908950 ecr 3547900967], length 0

01:27:48.079362 IP 158.101.96.128.https > c520ws.m1.lan.49612: Flags [.], ack 2330620, win 68, options [nop,nop,TS val 1256908951 ecr 3547900967], length 0

 

  0      
 
  0      
 
#1
Options
4 Reply
Re:C520WS and Tapo app on device with different vlan issues
2025-06-26 06:42:08 - last edited 2025-06-26 06:45:44

Here is an othere where host names arent resolved..

10.10.2.103 = phone

192.168.30.38 = camera 

 

02:38:58.784718 IP 150.230.187.62.443 > 192.168.30.38.51484: Flags [.], ack 410243, win 425, options [nop,nop,TS val 3992361215 ecr 3040890530], length 0

02:38:58.792219 IP 192.168.30.38.51484 > 150.230.187.62.443: Flags [.], seq 413099:414527, ack 4267, win 7918, options [nop,nop,TS val 3040890554 ecr 3992361214], length 1428

02:38:58.792236 IP 192.168.30.38.51484 > 150.230.187.62.443: Flags [.], seq 414527:415955, ack 4267, win 7918, options [nop,nop,TS val 3040890554 ecr 3992361214], length 1428

02:38:58.792802 IP 150.230.187.62.443 > 192.168.30.38.51484: Flags [.], ack 413099, win 433, options [nop,nop,TS val 3992361223 ecr 3040890539], length 0

02:38:58.793804 IP 10.10.2.103.60434 > 192.168.30.38.46115: UDP, length 40

02:38:58.809108 IP 150.230.187.62.443 > 192.168.30.38.51484: Flags [.], ack 415955, win 433, options [nop,nop,TS val 3992361239 ecr 3040890554], length 0

02:38:58.855121 IP 192.168.30.38.51484 > 150.230.187.62.443: Flags [.], seq 416969:418397, ack 4267, win 7918, options [nop,nop,TS val 3040890617 ecr 3992361239], length 1428

02:38:58.855139 IP 192.168.30.38.51484 > 150.230.187.62.443: Flags [.], seq 418397:419825, ack 4267, win 7918, options [nop,nop,TS val 3040890617 ecr 3992361239], length 1428

02:38:58.855142 IP 192.168.30.38.51484 > 150.230.187.62.443: Flags [.], seq 419825:421253, ack 4267, win 7918, options [nop,nop,TS val 3040890617 ecr 3992361239], length 1428

02:38:58.855293 IP 192.168.30.38.51484 > 150.230.187.62.443: Flags [.], seq 421253:422681, ack 4267, win 7918, options [nop,nop,TS val 3040890617 ecr 3992361239], length 1428

02:38:58.855296 IP 192.168.30.38.51484 > 150.230.187.62.443: Flags [.], seq 422681:424109, ack 4267, win 7918, options [nop,nop,TS val 3040890617 ecr 3992361239], length 1428

02:38:58.872197 IP 150.230.187.62.443 > 192.168.30.38.51484: Flags [.], ack 415955, win 433, options [nop,nop,TS val 3992361302 ecr 3040890554,nop,nop,sack 1 {416969:419825}], length 0

02:38:58.872204 IP 150.230.187.62.443 > 192.168.30.38.51484: Flags [.], ack 415955, win 433, options [nop,nop,TS val 3992361302 ecr 3040890554,nop,nop,sack 1 {416969:421253}], length 0

02:38:58.872205 IP 150.230.187.62.443 > 192.168.30.38.51484: Flags [.], ack 415955, win 433, options [nop,nop,TS val 3992361302 ecr 3040890554,nop,nop,sack 1 {416969:424109}], length 0

02:38:58.875945 IP 192.168.30.38.51484 > 150.230.187.62.443: Flags [P.], seq 415955:416969, ack 4267, win 7918, options [nop,nop,TS val 3040890639 ecr 3992361302], length 1014

02:38:58.893084 IP 150.230.187.62.443 > 192.168.30.38.51484: Flags [.], ack 424109, win 427, options [nop,nop,TS val 3992361323 ecr 3040890639], length 0

02:38:58.894900 IP 192.168.30.38.46115 > 10.10.2.103.60434: UDP, length 64

02:38:58.896758 IP 192.168.30.38.51484 > 150.230.187.62.443: Flags [P.], seq 424109:424844, ack 4267, win 7918, options [nop,nop,TS val 3040890660 ecr 3992361323], length 735

02:38:58.914180 IP 150.230.187.62.443 > 192.168.30.38.51484: Flags [.], ack 424844, win 436, options [nop,nop,TS val 3992361344 ecr 3040890660], length 0

  0  
  0  
#2
Options
Re:C520WS and Tapo app on device with different vlan issues
2025-07-01 09:26:26

  @b101 

 

Is there any problem when watching camera through cellular data, or from a remote WiFi network?

 

Can you share your network topology here?

▶ Tapo P110M Matter 1.3 Release Energy Monitoring through Matter ▶ Smart HomeBase Tapo H500 - Even More Powerful Smart Hub ▶ First Smart Switch Module! Tapo S112 Smart Switch Module with Roller and Switch Dual Modes ▶ Tapo Camera Image Style & Image Brightness Try out a different image style for your camera!
  0  
  0  
#3
Options
Re:C520WS and Tapo app on device with different vlan issues
2025-07-01 18:37:29

  @Wayne-TP no since there is no local multicast subnet to respond,  connection is stable. The issue is that:  multicast is working across subnets/vlans but its as if the Tapo app is having issues with the video feed if the multicast responses are from an other local subnet than the camera is on.

 

 

 

  0  
  0  
#4
Options
Re:C520WS and Tapo app on device with different vlan issues
2025-07-04 08:59:18

  @b101 

 

Thank you for your testing and feedback. I'll forward your report to our relevant department for review. However, when faced with a complex network topology and lacking the means to replicate it, pinpointing the source of the issue can be quite challenging. I'm unsure if I will receive comments from the relevant department on this case. This situation seems can be resolved by simplying the network topology -- connecting all devices under the same subnet. For a better use experience, I recommend using them in a simpler network environment.

▶ Tapo P110M Matter 1.3 Release Energy Monitoring through Matter ▶ Smart HomeBase Tapo H500 - Even More Powerful Smart Hub ▶ First Smart Switch Module! Tapo S112 Smart Switch Module with Roller and Switch Dual Modes ▶ Tapo Camera Image Style & Image Brightness Try out a different image style for your camera!
  0  
  0  
#5
Options

Information

Helpful: 0

Views: 204

Replies: 4

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.