This is already in the standard version of emplode. It discovers empegs by broadcasting a UDP discovery packet to the local subnet. Most routers and bridges won't forward these discovery packets. If the unit is assigned a static IP, and emplode finds it, then this is working.

If the DHCP server is assigning an IP address on a different subnet, then emplode won't find it. This is not likely to be the case with one of these home/office router boxes. If this is the problem, we've got a fix to emplode which allows you to provide a specific IP address on which to find the empeg. It'll be in the next maintenance release.

I suspect, however, that this problem is caused by a, shall we say, "difference in interpretation" of the DHCP specification between your router and the empeg. If you could capture the serial output of the empeg when it's starting up, this would be a great help when diagnosing the problem.



Roger - not necessarily speaking for empeg