I'm new(ish) to networking and have been setting up a home server. Part of making sure the server is good and healthy is of course making sure I have a solid connection.
Unfortunately, our DD WRT router needs to be reset at least weekly. No one uses P2P on our network, at most there are only a few standard machines doing basic web browsing at any given moment.
Last night was the first time that I ever had a chance to get to the route of the problem, and to try a less aggressive method to repair connection rather than resetting the whole machine.
So I ping(ed) 220.127.116.11 but received no response. I was then forced to fix the issue immediately by one of the other LAN users; however, rather than resetting the router, I released and renewed the DHCP lease and connection was restored.
Leaving the routers WAN port, the next machine down the line is the modem and then off to Comcast it goes. We seem to have had problems with the same symptoms for the last three routers, all of which were Netgear/Broadcom machines, the last two ran DD WRT.
So I have three questions:
Who is at fault? ISP or DDWRT?
What tools can I use to more intelligently diagnose the problem than checking if a known server like Google's DNS is reachable?
How can I make sure DD WRT takes care of this problem itself, even if I cant fix the route cause. For example, I have considered writing a script that pings a known server, such as 18.104.22.168, at regular intervals. If no response, a log is made of how far the machine makes it (using tools like question 2), and then the DHCP is released/renewed. I feel as though a more elegant solution should exist.