It is an hdhomerun. It can be a dhcp client, but I'm not running a dhcp server on the NAT'd side of the network -- that would have been another solution. Once you are able to connect to it, you can also manually set its IP address.<div> <br></div><div>It's a great little device, despite my flailing to talk to it outside of a zeroconf network.<br><div><br></div><div>J<br><br><div class="gmail_quote">On Mon, Mar 1, 2010 at 6:11 PM, Robin Perkins <span dir="ltr"><<a href="mailto:robin.perkins@internode.on.net">robin.perkins@internode.on.net</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br> On 01/03/2010, at 8:53 AM, j2u4 j2u4 wrote:<br> <br> > 狢 have a device that only exposes a zerconf 169.254.0.0 interface.<br> <br> </div>Out of interest what is this device ? It sounds like it is broken if it cannot be a dhcp client or have a manually assigned IP address.<br> <br> Rob<br> <div><div></div><div class="h5">_______________________________________________<br> avahi mailing list<br> <a href="mailto:avahi@lists.freedesktop.org">avahi@lists.freedesktop.org</a><br> <a href="http://lists.freedesktop.org/mailman/listinfo/avahi" target="_blank">http://lists.freedesktop.org/mailman/listinfo/avahi</a><br> </div></div></blockquote></div><br></div></div>