![]() If the ratio is much above 0.5, torrenting might not be the only issue at hand. In each file, find the line that looks like total entries = Īnd divide the number in the baseline file by the number in the post-test file. Right now we're just interested in measuring the ratio between a typical number of NAT entries (the baseline) and the maximum possible number of NAT entries (the post-test). The natlist-baseline.txt and natlist-post-test.txt files are plain-text dumps of the NAT table and some associated diagnostics. Otherwise, the NAT table probably isn't your issue - sorry. If you saw "Out of NAT buffer" messages in step 6, it's time to compare the two files you've downloaded. Restart the router (or wait about 15 min.) to clear the NAT table.Any "Out of NAT buffer" messages indicate that the router is filling up its NAT table.ĭownload and save it as natlist-post-test.txt. Go to Status -> Log and look through all the log entries. Use the wired machine to log into the router's web administration interface. You can stop torrenting once the router is unresponsive. On the wired machine, find an active torrent that is likely to cause the router to seize up (an Ubuntu distribution works well) and begin torrenting. On the wireless machine, ping the router continuously, so it'll be obvious when the router is unresponsive. ![]() ![]() Stress the router until it's unresponsive to the wireless machine.Go back to Status -> Log and remove all the current log entries by clicking "Clear". Use the wired machine to log into the router's web administration interface at Go to Status -> Log -> Log Settings, and make sure that "Dropped Packets" is checked. Connect two machines to the network - one with a wired connection, the other wirelessly.This file will serve as a point of comparision later on. To check if torrenting is clogging the NAT table:ĭownload and save it as natlist-baseline.txt. Though torrenting is probably what's causing your problems, torrenting may actually just aggravate an underlying condition. It seems likely that the NAT table is filling up the DI-524 only has about 8 MB of memory, so the NAT table is relatively small. (Right now this answer is diagnostic only: if the first part is accurate, I'm planning to edit this with a solution.)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |