mxmaniac wrote:I have seem to have a lot of trouble with LAN transfers going slow. Especially FTP. I can often download files off the net, faster than I can transfer them between PC's on the LAN.
Now I realize where some of the bottlenecks could be. Software firewall(s), router, wireless connections, etc.
But what I'm wondering, is there an efficient way (that's beginner/intermediate friendly) to find out exactly where the bottlenecks are? Rather than a haphazard trial and error approach of disabling firewalls, swapping routers, replacing wireless connections with wired, etc?
I know over the web there is the "tracert" command which traces a packets path to its destination, telling the delay between each connection. Is there any similar command, or software tool that can trace packets across a LAN to determine the bottleneck? Or some other efficient way to troubleshoot?
mxmaniac wrote:I looked up iperf and like what I see. A simple lightweight tool for windows, linux, and android. I will plan on trying this out soon, seems like a great tool. From what I can tell though it seems to primarily measure throughput and quality, but doesn't tell exactly where the bottleneck is (unsure if this is possible though).
As far as a network map, its a pretty simple typical home setup. Router is a Buffalo (I believe wrt54g) flashed with Tomato, although I am already replacing this very soon with a much more powerful (cpu / ram wise), wireless n, gigabit router, as I suspect its the weak point, and I sometimes have to reboot it. Then there are a small number of laptops, phones, IP cameras hooked up. 4 devices are wired using the router ports, rest wireless.
I'm not yet familiar with SNTP traps, netflow, or PRTG. Rather than ask a ton of questions on here, I'll plan to set aside some google/youtube time later this weekend to try to learn about them. How would I know if my equipment is compatible? Can they actually identify the bottleneck? Like trace the packet through its journey across the lan, and find out where it slows down, such as the router, the wireless connection, etc?
notfred wrote:I thought the idea here was to find the performance bottleneck rather than to practice for a CCIE.
The idea with running iperf tests between all the different devices is that hopefully you'll notice a pattern that if a particular device is involved then that is the cause of the slowdown. If these all show good throughput but the file transfers still show bad throughput then you need to start doing the same thing at that level. Don't condemn the router yet, it could all just be a bad cable somewhere!
Users browsing this forum: Hz so good and 7 guests