mythtv at theanthonys
Aug 12, 2012, 3:59 AM
Post #9 of 14
(549 views)
Permalink
|
I think HDHR steams over UDP which is not fault tolerant at the protocol level and I doubt the little box has extra data integrity built in. NFS has data integrity so it will work fine, even if there is packet loss.
I'd stick the HDHR box on its own 100meg cable/nic without a switch straight into the myth backend. You save gig ports and its more robust as you can reboot your switch without affecting recordings. With myth controlling the box, there's little reason to keep it on your main network. Just set your myth box to server dhcp (fix the address) to the HDHR segment and you should be fine.
You could try LACP between your switch and your myth box to stop one other box from flooding the entire link, especially if you are using UDP NFS. The dedicated HDHR segment with no switch has worked well for me so far, even with a really lower-power AMD 1800+ single core and 512Mb ram.
--
On 12/08/2012, at 8:03 PM, Adrian Saul wrote:
>
> 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.
>
> TL;DR - buy a decent quality switch, managed if you can afford it.
>
> On 12/08/2012 4:46 AM, Monkey Pet wrote:
>> 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.
>>
>> My network consisted of unmanaged GigE switches.
>>
>> On Fri, Aug 10, 2012 at 11:15 PM, Joseph Fry <joe [at] thefrys> wrote:
>> Hi, I've seen a few threads on this in the past.
>> I have 0.25-fixes. I have random HDHR fails.
>> 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.
>> I headed here after seeing the log error mentioned multiplexing.
>> It seems to toggle back and forth which setting will work and I've yet to see the pattern.
>> Thought this might save someone some time until the issue is fixed.
>>
>> 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.
>>
>>
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users [at] mythtv
>> http://www.mythtv.org/mailman/listinfo/mythtv-users
>>
>>
>>
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users [at] mythtv
>> http://www.mythtv.org/mailman/listinfo/mythtv-users
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users
|
