<br><br><div class="gmail_quote">On Mon, Mar 1, 2010 at 11:12 AM, Lennart Poettering <span dir="ltr"><<a href="mailto:lennart@poettering.net" target="_blank">lennart@poettering.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div><br> </div>Make sure you don't have a firewall blocking these thins.<br></blockquote><div><br></div><div>Done, both urw and iptables show nothing being firewalled.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Don't use the old ifconfig/route tools. They are compat kludges that are<br> misleading in many ways. use iproute (i.e. "ip addr" and suchlike) instead.<br></blockquote><div><br></div><div>Done, I've switched to 'ip route' etc.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Use wireshark to verify what's going on on the network.</blockquote><div><br></div><div>So it was obvious from the tsharking that 'hdhomerun_config discover' was only broadcasting to the private 192.168.x.x network. It turns out, it will only broadcast to the addresses for configured interfaces. So the solution ended up being adding a virtual interface on the zeroconf network, and then everything worked.</div> <div><br></div><div>Thanks for the help!</div><div>J</div> </div>