TP-Link support, thanks for the private reply, but you don't understand the problem. "Large" ping means large sized ping, not large RTT response times as your reply incorrectly assumes. I also have...

TP-Link router has some bug with number of ip fragements (fragment reassembly) This seems to work (33 fragments): fastping -l:48832 -n:1000 192.168.0.1 This is the point at which things start to...

Also happens when using Windows "ping" command line tool: c:\>ping -l 62500 192.168.0.1 Pinging 192.168.0.1 with 62500 bytes of data: Reply from 192.168.0.1: bytes=62500 time=2ms TTL=64 Request...

setup: TP link router (as a router) behind my main router (at 192.168.1.1). When I connect my laptop Wi-Fi to a TP-Link AXE75 (just two feet away from the laptop) and run fastping (Google "duckware...

@Liverpool20 , yes, my original post stated I was using static ip address, and tp-link was STILL performing DHCP. I solved to switching to a different vendor for that access point.

@Kevin_Z the response is "HTTP/1.1 500 Internal Server Error", but inside the response is "<errorCode>401</errorCode>"