Not so much a bug as an interesting tidbit.
I plugged the empeg in and it was assigned an IP from my DHCP server. I then went and changed the config on my domain name and DHCP servers to give the empeg a fixed IP address.
When the lease ran out and the empeg requested a new IP, the server attempted to give it a different one. This caused the empeg to reboot.
Log follows...
Aug 31 17:02:00 proteus dhcpd: DHCPREQUEST for 192.168.0.137 from 00:02:d7:10:00:62 via eth0
Aug 31 17:02:00 proteus dhcpd: DHCPNAK on 192.168.0.137 to 00:02:d7:10:00:62 via eth0
Aug 31 17:02:10 proteus dhcpd: DHCPDISCOVER from 00:02:d7:10:00:62 via eth0
Aug 31 17:02:10 proteus dhcpd: DHCPOFFER on 192.168.0.7 to 00:02:d7:10:00:62 via eth0
Aug 31 17:02:10 proteus dhcpd: DHCPREQUEST for 192.168.0.7 from 00:02:d7:10:00:62 via eth0
Aug 31 17:02:10 proteus dhcpd: DHCPACK on 192.168.0.7 to 00:02:d7:10:00:62 via eth0