Found my problem. Fedora Core 12 enables firewall by default (installed from Live CD). Once I shut it down everything works.<div><br></div><div>I couldn't run "hdhomerun_config discover" from that machine.</div>
<div><br></div><div>Not sure if there is special firewall rules I could enable for the hdhomerun to work with firewall enabled.</div><div><br><div class="gmail_quote">On Tue, Jan 5, 2010 at 1:07 PM, Steve Malenfant <span dir="ltr"><<a href="mailto:smalenfant@gmail.com">smalenfant@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I tried to search and find this problem that could have been experienced by other users, but can't find any fixes for it.<div>
<br></div><div>I'm building another mythbackend and trying to scan all the channels using HD homerun and myth. I did shutdown my existing backend (different machine) and tried to scan to see if it would work.</div>
<div><br></div><div>I can get a lock no problem, I can tune using TS Reader, I can record from my old backend...</div><div><br></div><div>But retrying on scan on .21 and .22 just plain doesn't work.</div><div><br></div>
<div>The result is "Timed out, no channels" when I get a lock. Increased the timeout a bit, same result.</div><div><br></div><div>Is this because I'm running the latest 20091024 version on the HD Homerun? Seems like the TS is coming out just fine.</div>
<div><br></div><div>Is there anything changed in the broadcast line up (tables) that could cause this? I know my Voom receiver reboots on some of the channels now.</div><div><br></div><div>Any pointers would help. I'll try downgrading the firmware for now.</div>
<div><br></div><font color="#888888"><div>Steve</div>
</font></blockquote></div><br></div>