<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div>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.</div>
</div></blockquote><div><br></div><div>Yes, direct cabling the HDHR to a cheap PCI nic works great. </div><div><br></div><div>However, you do NOT need to have the backend serve DHCP to the HDHR. Just set the dedicated NIC to a static 169.254.x.x address with a 255.255.0.0 netmask (no gateway or dns). The HDHR gets a link local address (169.254.x.x) almost immediately after it boots. Sure it pulls a different address on every boot, but you should never configure the backend to connect it by IP anyway, so it doesn't matter if it changes every time the HDHR starts.</div>
<div><br></div><div>My /etc/network/interfaces file looks like this, no other config necessary for the HDHR segment:</div><div><br></div><div>--------------------------------------------------</div><div># primary NIC</div>
<div>auto eth0</div><div>iface eth0 inet static</div><div> address 192.168.15.100</div><div> gateway 192.168.15.1</div><div> netmask 255.255.255.0</div><div><br></div><div># HDHR</div><div>auto eth1</div><div>iface eth1 inet static</div>
<div> address 169.254.15.100</div><div> netmask 255.255.0.0</div><div>--------------------------------------------------</div><div><br></div></div>