Getting bad packet loss when large numbers of sessions are running through the router. LAN connectivity stays up fine, but WAN goes bonkers. Ping output (google.com):
Code: Select all
Reply from 74.125.237.51: bytes=32 time=72ms TTL=56
Reply from 74.125.237.51: bytes=32 time=209ms TTL=56
Reply from 74.125.237.51: bytes=32 time=77ms TTL=56
Reply from 74.125.237.51: bytes=32 time=81ms TTL=56
Reply from 74.125.237.51: bytes=32 time=130ms TTL=56
Reply from 74.125.237.51: bytes=32 time=97ms TTL=56
Reply from 74.125.237.51: bytes=32 time=78ms TTL=56
Reply from 74.125.237.51: bytes=32 time=150ms TTL=56
Request timed out.
Reply from 74.125.237.51: bytes=32 time=107ms TTL=56
Reply from 74.125.237.51: bytes=32 time=124ms TTL=56
Reply from 74.125.237.51: bytes=32 time=102ms TTL=56
Reply from 74.125.237.51: bytes=32 time=142ms TTL=56
Reply from 74.125.237.51: bytes=32 time=142ms TTL=56
Request timed out.
Reply from 74.125.237.51: bytes=32 time=137ms TTL=56
Reply from 74.125.237.51: bytes=32 time=190ms TTL=56
Reply from 74.125.237.51: bytes=32 time=234ms TTL=56
Reply from 74.125.237.51: bytes=32 time=91ms TTL=56
Reply from 74.125.237.51: bytes=32 time=48ms TTL=56
Request timed out.
Reply from 74.125.237.51: bytes=32 time=106ms TTL=56
Reply from 74.125.237.51: bytes=32 time=273ms TTL=56
Reply from 74.125.237.51: bytes=32 time=146ms TTL=56
Reply from 74.125.237.51: bytes=32 time=170ms TTL=56
Reply from 74.125.237.51: bytes=32 time=119ms TTL=56
Reply from 74.125.237.51: bytes=32 time=140ms TTL=56
Reply from 74.125.237.51: bytes=32 time=77ms TTL=56
Reply from 74.125.237.51: bytes=32 time=173ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.237.51: bytes=32 time=130ms TTL=56
Reply from 74.125.237.51: bytes=32 time=112ms TTL=56
Reply from 74.125.237.51: bytes=32 time=252ms TTL=56
Reply from 74.125.237.51: bytes=32 time=101ms TTL=56
Reply from 74.125.237.51: bytes=32 time=214ms TTL=56
Reply from 74.125.237.51: bytes=32 time=118ms TTL=56
Request timed out.
Reply from 74.125.237.51: bytes=32 time=208ms TTL=56
Reply from 74.125.237.51: bytes=32 time=131ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.237.51: bytes=32 time=241ms TTL=56
Reply from 74.125.237.51: bytes=32 time=172ms TTL=56
Request timed out.
Request timed out.
Reply from 74.125.237.51: bytes=32 time=107ms TTL=56
Reply from 74.125.237.51: bytes=32 time=156ms TTL=56
Reply from 74.125.237.51: bytes=32 time=180ms TTL=56
Request timed out.
Reply from 74.125.237.51: bytes=32 time=152ms TTL=56
Reply from 74.125.237.51: bytes=32 time=44ms TTL=56
Request timed out.
Reply from 74.125.237.51: bytes=32 time=140ms TTL=56
Reply from 74.125.237.51: bytes=32 time=93ms TTL=56
Request timed out.
Reply from 74.125.237.51: bytes=32 time=181ms TTL=56
Reply from 74.125.237.51: bytes=32 time=154ms TTL=56
Request timed out.
Request timed out.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination net unreachable.
Reply from 192.168.1.251: Destination port unreachable.
Reply from 74.125.237.51: bytes=32 time=26ms TTL=56
Reply from 74.125.237.51: bytes=32 time=25ms TTL=56
Reply from 74.125.237.51: bytes=32 time=23ms TTL=56
Reply from 74.125.237.51: bytes=32 time=27ms TTL=56
Reply from 74.125.237.51: bytes=32 time=74ms TTL=56
Reply from 74.125.237.51: bytes=32 time=29ms TTL=56
Reply from 74.125.237.51: bytes=32 time=25ms TTL=56
Reply from 74.125.237.51: bytes=32 time=23ms TTL=56
Takes a little while for this to start happening after hitting start in Transmission (running on a PC, not the router). Happens before the link is anywhere near capacity though, so it doesn't seem to be an issue with that. Sessions is set to 500 in Transmission, so it's not a stupidly large number either (though not that small). Using PPPoE to connect. Have seen issues like this before when using the modem to connect, but when modem is bridged and using PPPoE with Gargoyle, it used to work fine. Have been away for a while, so not sure which version this issue appeared with. Has anyone else seen similar?
Oh, btw, I changed the IP of Gargoyle to 192.168.1.251...
Edit: Other useful information I probably should have included before:
* Router is a Netgear WNDR3700 (v1).
* QoS is disabled (but I've also seen this happen when enabled with default settings).
* I saw the router reboot once when I was doing this, but haven't been able to reproduce that since.
* New flash of Gargoyle...only settings changed: IP address, Internet connected using PPPoE, MTU to 1454, wireless enabled with WPA2...everything else is default.