<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 8/15/2011 02:22, Jason Long wrote:
<blockquote cite="mid:4E48BB13.4050407@jasonlong.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
On 8/14/11 10:36 PM, Raymond Wagner wrote:
<blockquote cite="mid:4E48B07B.6010208@wagnerrp.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 8/15/2011 00:16, Jason Long wrote:
<blockquote cite="mid:4E489D82.8090507@jasonlong.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<tt>| 1 | 192.168.1.31-0 | HDHOMERUN | MPEG2TS |
mythtv |</tt><br>
</blockquote>
<br>
Is there any reason you're using the IP address rather than the
device ID?<br>
</blockquote>
<br>
Not particularly (but it's a static IP). Any advantage to using
the device ID? I guess I could re-IP the tuner and not screw up
myth?<br>
</blockquote>
<br>
Device ID just seems to be Silicon Dust's preferred method of
accessing the HDHomeRun. Until a few months ago, there was an
upstream bug in the libraries that prevented access to the second
tuner when using the IP address. Note that in order for use of the
Device ID to work, both the HDHomeRun and the backend must be on the
same logical subnet with the same broadcast address.<br>
</body>
</html>