<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
In my experience not all GigE switches are equal. I had a no-name
brand GigE switch that would choke once you tried to push any more
than 30MB/s between machines (the only two on the switch). I
replaced that with a 5 port Netgear and could benchmark 100MB/s over
NFS with no other changes. Down the track I started getting
networking issues that appeared to be packet drops under load and
after trying a few NIC changes was about to blame my home cabling
job until I thought to take the switch out of the mix. Somehow the
switch was dropping packets but being unmanaged I had no stats to
tell me that other than what appeared on the hosts.<br>
<br>
TL;DR - buy a decent quality switch, managed if you can afford it.<br>
<br>
<div class="moz-cite-prefix">On 12/08/2012 4:46 AM, Monkey Pet
wrote:<br>
</div>
<blockquote
cite="mid:CADXZuRxBwE2xVGnAaC3A7WFgveUak6mZBOCwWM-a2Bg_Ly3pVQ@mail.gmail.com"
type="cite">I solved my random HDHR issues when I moved my 2 HD
homeruns to its own dedicated network. For some reason (very
strange), it was causing lots of issues including: crashing my
cable modem, stuttering while playing livetv on remote frontends,
and some failed recordings. When i isolated the HD homeruns to
its own network which was connected to the backend, it solved all
the issues. Maybe it was luck with the fixes in 0.25/fixes coming
at the same time? I have no idea. However, i did some issues
that people reported with the HD homeruns and networking stuff
awhile back also.
<div>
<br>
</div>
<div>My network consisted of unmanaged GigE switches.<br>
<br>
<div class="gmail_quote">On Fri, Aug 10, 2012 at 11:15 PM,
Joseph Fry <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:joe@thefrys.com" target="_blank">joe@thefrys.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote">
<div>
<div class="h5">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi, I've seen a few threads on this in the past.
<div>I have 0.25-fixes. I have random HDHR fails.</div>
<div>I have found the only way to fix them is to go
into the setup cards advanced tab and change the
number of tuners from 1-2 or from 2-1.</div>
<div>I headed here after seeing the log error
mentioned multiplexing.</div>
<div>It seems to toggle back and forth which setting
will work and I've yet to see the pattern.</div>
<div>Thought this might save someone some time until
the issue is fixed.</div>
</blockquote>
<div><br>
</div>
</div>
</div>
<div>Sounds like your talking about the HDHR prime. If
that's the case then yes, you cannot use multiplexes
when using a cable card. If your using QAM, or ATSC (on
a non-prime HDHR) then you can set this as high as you
think your system will handle/need. I have each tuner
in my 1st Gen HDHR set to 4 virtual tuners as my cable
provider puts all my favorite QAM channels on the same
multiplex.</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a moz-do-not-send="true"
href="http://www.mythtv.org/mailman/listinfo/mythtv-users"
target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
mythtv-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>
<a class="moz-txt-link-freetext" href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a>
</pre>
</blockquote>
<br>
</body>
</html>