EyezOn Forum

Hi,

Envisalink 3 and DSC user for years with no networking changes in at least 3 years. It has all worked flawlessly.

yesterday we had a power outage for about an hour. I noticed the envisalink was not reachable on the LAN but the DSC was working. I tried power-cycling my router/switch, but that did not make the EVL3 reachable. Tried unplugging/replugging EVL3 ethernet, no luck.

This morning I completely power-cycled the DSC including removing the battery. It now works fine.

Any suggestions or ideas as to why the EVL3 did not come back online after a power outage? This is not normal, as we routinely have short outages.

Don't know if this will help but in envisalink setup have you checked "Make Network Settings Static?"

If not then when power was restored to the router it may have issued the envisalink IP to another device. When you cycled the Envisalink it was issued a new IP.

I was thinking something similar, but not exactly. I've seen the dd-wrt router not route Envisalerts packets if it was rebooted as the Envisalink wasn't in its DHCP table. I guess this is part of the packet inspection firewall.

If the Envisalink is on a long DHCP lease, say 2 weeks, and the router reboots due to a power failure, the Envisalink won't ask for a lease renewal until 50% of the time has expired, which is 1 week. So you can imagine a scenario where the router won't route the packets, but the Envisalink won't ask for a new lease.

This supposedly changed in 1.12.15X but I haven't had a chance to test it on my home dd-wrt. If the router, or any other piece of Ethernet equipment, goes down for 5 seconds or more the Envisalink we ask for a lease renewal.

@Flyct brings up a good point and we see this quite often in tech support. Customers make their Envisalinks static within the allocated dynamic range of the DHCP server. I good router will first "ping" a new IP address before assigning it to a DHCP client but not always. In that scenario you can get two devices with the same IP address on the network and the packets will not route correctly. So if you have a DHCP range of say 192.168.0.100 - 192.168.0.199, don't stick your Envisalink in that range. Put it down in the 192.168.0.0XX range to be safe.