Best posts made by Frank_442401001791671

Well, it's no Wireshark log, but the E1 cameras do not respond to ping or tracert from the main LAN (192.168.1.0/24):

C:Usersfrank>ping 192.168.10.139

Pinging 192.168.10.139 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.10.139:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:Usersfrank>tracert 192.168.10.139

Tracing route to 192.168.10.139 over a maximum of 30 hops

  1     1 ms    <1 ms     2 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.

Other devices on the IoT VLAN reponds as expected.

Thickening of the plot:
Another problem I experience and may play into this as a separate or combined issue, is basic router/DHCP connectivity at times. Sometimes, the E1 cameras have persistent ARP and DNS timeouts, which I can solve be powercycling them (unplug, wait 10 seconds and replug the power cable). I have given the E1s fixed IPs, in order to reduce/eliminate DHCP issues, due to this, which seems to have alleviated some of the problem - some of the time. Unfortunately, not entirely, and this might be another candidate as contributing culprit in the cause of no connectivity across subnets, as only the E1 cameras keep getting DHCPOFFER every 6 minutes, with a a DHCPDISCOVER thrown in every now and then, too (see screen shot).

When the E1s show this behavior, I cannot externally connect to them either. At this stage, it is both across subnets and from the internet side, as well, that the connectivity is nonexistent. But joining the same subnet still gives access to the cameras (Android app), even under these circumstances. No other ARP/DNS timeouts reported for other devices on the IoT VLAN, although some TCP latency every now and then. So, I can't really see it should be a router issue from the Unifi Dream Machine Pro. Something fishy is going on, indeed, but it is across E1s, so I can't see how it should be a malfunctioning camera I have, as the batch of E1s show the same (unwanted) and identical behavior.
DHCP-Reolink-E1.jpeg

I made a firewall rule to log any and all traffic (including ICMP) to the E1 cameras (see screen shot), which is then logged to Papertrail. Then I started pinging the E1s. Nothing in the logs. So even though they seems online in the router, they might be "off" the network, in some way that is beyond me. See screen shot.

The IPs for the E1s are done on the router side by MAC addresses. The E1s do not have a onption for setting a fixed IP, at least to my knowledge and experience with them.
IoT-devices-router-status.jpeg
logging-E1s-console-and-papertrail.jpeg

I am unsure of that, too. Anyway, I decided to bite the bullet and crawled into the low-height attic to connect an E1 by wire, to eliminate potential issues. I can cross VLANs when the camera has hardwired IP (by RJ45). So, it seems the connectivity issue is with E1s and wifi. When the same E1 is connected to the same IoT VLAN by cable, it acts as any other IoT device I have (although, they are all connected by wifi). That rules out the Unifi Dream Machine Pro, at least. And leaves the AC Lite and the E1s as the potential troublemakers, it seems.
attic-crawl-back-pain-legs-burning.jpg