Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[jackthesmack]

When I look at the log for Namebench, I only see response time. That seems to be the only metric for determining which DNS is better.

Here is my results: http://i.imgur.com/ol1Ugt2.png

The only thing that was enabled during this test was DNS Relay, not Automatic DNS Service (which was what slowed everything down). The DNS Relay address (Boxed in blue) and the fasted DNS (Boxed in green, which also happens to be my modem's default DNS, lead to the same WAN address.

I just did a test where I set the router's DNS to Google's DNS servers ( 8.8.8.8 ), then saved settings and did the required router reboot. Without changing any settings from my computer's automatic IP address settings, it was able to get the new DNS address when it reconnected. Setting the router back to 0.0.0.0, and rebooting it, changed my computer back to the Comcast DNS server. So any DNS changes can be propagated through the network, automatically, without even using DNS Relay. For anyone who uses DHCP only, which I assume is 99% of people out there, the DNS Relay offers no advantage I see. It's really silly for D-Link to have this enabled by default, as anyone running a network without DHCP must already know what they're doing and can enable it themselves.

[FurryNutz]

Nice results. I think I need to check mine as well. 

[jackthesmack]

OK, so I was able to download 200 torrents fine. But then I started getting more and more...and at 400+ torrents I started noticing problems. After doing some research, it appears the bottleneck is simply the RAM and CPU of the router. But I can't see the load on it at all.

However, I did have an old Dell computer lying around. And people on torrent sites were telling me to install pfSense. So now I have pfSense installed and I'm using a Dell computer as a router, and it's running much better. I have 1500 torrents currently running and the router is saying only 20% RAM is used (out of 512MB) and I can see the CPU usage spiking to 10% sometimes. I'm gonna assume that the RAM and CPU on the D-Link were far worse, and I was clogging both up. Disabling QOS, DNS Relay, etc reduced the load, but I was still adding more load with more torrents.

I guess I would have seen this issue from the beginning if there was a way to see the load on the router. Here's an example of what I'm seeing right now with pfSense: http://i.imgur.com/mjhHGr8.png

Thanks for all your help though.

[FurryNutz]

Ya, probably having that many torrents going on these routers isn't probably good. Routers are only designed to so so much. Torrent moderation is needed. 

Glad you found a work around.

Enjoy.