<br><br><div class="gmail_quote">On Dec 30, 2007 1:20 AM, Max Palatnik <<a href="mailto:mmpalatn@artsci.wustl.edu">mmpalatn@artsci.wustl.edu</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Sean,<br><br> Which router is it? What's firmware is it running?<br><br>Have you tried changing it back to see if the problem continues?<br><font color="#888888"><br>Max<br></font><div><div></div><div class="Wj3C7c"><br>
Sean Goodpasture wrote:<br>> running mythdora FWIW.<br>><br>> I've got a linksys router and got the wild hair to install DD-WRT on<br>> it today. One of the things you can do is static DHCP. This allows<br>
> you to make sure that a given box always gets the same IP. I guess<br>> that it also does something with DNS? I didn't change the hostname,<br>> just the way that the IP is assigned. The hostname actually stayed
<br>> the same, but now I can reach the backend by name rather than only by<br>> IP.<br>><br>> In any case, since doing this, I get all sorts of instability with my<br>> main backend. When watching live TV (on a remote frontend) I get
<br>> random crashes when changing the channel. Sometimes the crash happens<br>> when I'm playing around in recordings or recording settings.<br>><br>> I did watch most of the football 2nd half this evening, but right
<br>> after it borked when I went to check the score of the college game on<br>> ESPN.<br>><br>> The bad thing is that there is nothing in the log at all. Just a<br>> changing to Live TV on my tuner and then the restart stuff from when I
<br>> restart the backend.<br>></div></div></blockquote><div><snip><br>I bet it changed your FQDN for the box - For example it went from
<a href="http://yourmom.belkin.com">yourmom.belkin.com</a> to <a href="http://yourmom.somethingelse.com">yourmom.somethingelse.com</a> - Some routers pull the
DNS suffix from their WAN router and some don't. If your FQDN changed, the frontend may be doing some weird DNS query and freaking out. Run a reverse dns query (fire up nslookup, plop in the IP address and see what name it spits at you), and see if it matches the name you get when typing hostname on the backend.
</div></div><br>