<div class="gmail_quote">On Mon, Aug 13, 2012 at 4:35 PM, Raymond Wagner <span dir="ltr"><<a href="mailto:raymond@wagnerrp.com" target="_blank">raymond@wagnerrp.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="im">On 8/13/2012 17:26, Phill Edwards wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have read some posts about UDP traffic potentially flooding the<br>
switch if the Homerun is plugged into the switch rather than the<br>
Mythbackend itself. As it's a VM it's not really possible to plug<br>
it into a NIC dedicated to the Mythbackend VM so how are you dealing<br>
with that issue?<br>
</blockquote>
<br></div>
Can't say I've ever heard of such issues. Perhaps the person using it was using all 10/100 gear, and thus much closer to the collision limit?</blockquote><div><br></div><div>I have an HP ProCurve 1800-24G switch. The ESXi host is plugged into it for now. I've thought about link aggregating it's NICs, but haven't done it yet. The HDHR is also in the gig switch. So far, it's been working perfectly. No issues to report (except the obvious Leap Second Bug). Before the leap second, it was working great.</div>
</div>