I am seeing a problem arise from the lack of static IP capabilities with the EISY, and hoping there is a workaround. I know that static IP addresses are not enabled and that topic has been beaten to death... hear is what I am facing:

I use EISY in a residential setting, and I get occasional power outages. I have found that when power is restored, my EISY reboots and looks for a DHCP address faster than my router can startup DHCP services. The EISY times out, and then remains without connectivity until I cycle the power on the EISY.

Is there any way to make the EISY delay / extend the dhcp window?

Any other workarounds I should try?

Thanks

I think a UPS on sensitive equipment like that is a good idea. It won't always solve the problem if it is a prolonged outage but I have them even though I have full home battery backup because it does not switch fast enough. Maybe a script could be written that checks to see if eisy has an ip address and if not it makes it look for one. I had AI help with a direct connection for my powerwalls to stream the data and the powerwall kept dropping the connection, now the computer will reestablish the connection on it's own.

The usual workaround is to reserve a DHCP address in your router for the eisy's MAC address.

Another workaround is to set a second, fixed IP address in your eisy as an alias. This is copied from another post I did a while back:

FreeBSD allows you to set more than one IP address for a network interface. The idea here is to let DHCP do it's thing, which keeps UDI happy because the correct default gateway, nameserver, etc settings are acquired. Then you define a second IP address that can be static, as an alias. It only takes one line added to the /etc/rc.conf file. The line is (for a eisy) :

ifconfig re0 <fixed IP address> netmask <netmask> alias

The terminating "alias" is of utmost importance! For whatever reason it is suggested that the netmask be different than the default one, so I made it smaller.

Only thing is that this can sometimes get deleted after a udx upgrade, so you might need to redo it if that happens.