Networking – ASUS RT-N66U how to identify source of traffic spike

debugdiagnosticnetworkingrouter

I have an ASUS RT-N66U as my home router. We are experiencing some traffic spikes in downloading over WiFi that slow all other activity to a crawl.

Is there a way to identify the source (ip/host) of the traffic spike from the router's web interface?

My next step would be to disconnect that host.

I'm fairly noob in this area – any help appreciated, thanks! 🙂

Best Answer

Contrary to a widespread myth, saturating one’s bandwidth with a big download or upload should NEVER cause a latency spike for everything else. If it does, you’re probably hitting a widespread and well known router bug called bufferbloat.

Use http://dslreports.com/speedtest (note: this is NOT Ookla speedtest.net) to get your bufferbloat grade. If you get a bad grade, look into enabling FQ-CoDel (or any later smart queueing algorithms to come from the bufferbloat research community) on your router. You may need to install open source firmware such as OpenWrt on your router in order to enable FQ-CoDel. Enabling Explicit Congestion Notification (ECN) is helpful as well. Also consider adjusting traffic shaping on your router to make your CoDel router a slight bottleneck so that FQ-CoDel can kick in before bloated buffer queues build up anywhere else.

Or look at purchasing a turn-key solution such as EvenRoute’s IQrouter.

Related Solutions

Linux – script to add port forwarding rule in home router

MiniUPnP is a command line UPnP client that allows you to enable port forwarding. The source is available so you should be able to compile it to the Pi.

I think this is the syntax you need, but I don't have a machine to test it on. You would just put the following in a script that would set up the uPnP ports for you

upnpc -a `ifconfig wlan0 | grep "inet addr" | cut -d : -f 2 | cut -d " " -f 1` 22 22 TCP
upnpc -a `ifconfig wlan0 | grep "inet addr" | cut -d : -f 2 | cut -d " " -f 1` 5900 5900 TCP
upnpc -a `ifconfig wlan0 | grep "inet addr" | cut -d : -f 2 | cut -d " " -f 1` 9091 9091 TCP

Networking – How to forward traffic between Tun device and eth0

Your main mistake is: assumption that such kind of traffic will be forwarded. This is not that case. This is outgoing, not forwarded traffic for VM perspective. ICMP replies come to eth0 and go up to protocol stack, thus, you can not see them on tun0 device. For futher details you can look here: https://serverfault.com/questions/554477/tap0-not-receiving-traffic/554698

Best Answer

Related Solutions

Linux – script to add port forwarding rule in home router

Networking – How to forward traffic between Tun device and eth0

Related Question