Fixing the IP to a static value has no effect. I tried it. The problem is not that the unit is jumping to different IP addresses.

I have been watching the A3 on a packet sniffer and what I see is that the A3 simply stops responding to TCP requests. The web page page will repeat a request for SYN about 4 times and then declare the site can’t be reached. That “site” of course is on the very same LAN as my PC. This communication path does not traverse the router. There is no further communication between the A3 and the router until the unit reboots and requests a DHCP assignment – and my router always gives it the same address and refresh time of 1440 minutes.

After watching it for while, what I see is that it runs quite normally for 10-11 minutes, updating the screen every 10 seconds. The watchdog never goes above 60 seconds. Somewhere just before 650 seconds, the A3 simply stops talking on the LAN. Since the watchdog will typically have 520 seconds on it, there is no further activity until the WD times out 520 seconds later and the unit reboots. While it is “incommunicado” on the LAN, it appears that the A3 is still sending data to the WAN side – the LED’s blink and no data is lost on the community server. This communication does not show up on the packet sniffer, so I cannot confirm 100%.

It seems unlikely my router is defective – I have 48 devices on my LAN and the URADMonitor is the only one misbehaving. And the communications passing through the router seem to work OK.

The shut-down of the LAN port is rather sudden but always in a predictable time frame of just under 11 minutes

Reply from 192.168.1.69: bytes=32 time<1ms TTL=64
Reply from 192.168.1.69: bytes=32 time<1ms TTL=64
Reply from 192.168.1.69: bytes=32 time<1ms TTL=64
Reply from 192.168.1.69: bytes=32 time=1ms TTL=64
Reply from 192.168.1.69: bytes=32 time=1ms TTL=64
Reply from 192.168.1.69: bytes=32 time<1ms TTL=64
Reply from 192.168.1.69: bytes=32 time=1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.19: Destination host unreachable.

I think it’s clear that there is some kind of problem with the A3 software. The problem is 100% repeatable.

Ken