router blocking SE IPs for ping flooding

[RAIST]

if you can't whitelist SE's IP range in your router's security to enable/allow the DNS pings, you could try changing the security setting for respond to DNS and/or ping requests to see if it helps. Wording/options will vary, but may be options about replying to either one or both of them. Also might have to specify port 53 or DNS if whitelisting IP's, not just TCP/UDP. Opening up reply to DNS or ping isn't a perfect scenario (can open you up to DoS from ping flood and such), but it might keep you from getting drop-kicked from SE's servers because it thinks you lost connection. If toggling those works, I would test it after a while with the setting back on the stronger security options...just in case SE fixes the network behavior down the line.

[poodlehat]

Thanks for the response. The router is a DIR-865. I have "Enabled WAN Ping", and in the firewall I have all ports open to the following blocks of addresses, which I know to be owned by SE:

202.67.48.1 -202.67.63.254
124.150.152.1 -124.150.159.254
61.195.48.1 -61.195.55.254
219.117.144.1 -219.117.159.254

Now, if there is some game traffic that is being sourced from some other IP that doesn't belong to SE (like a cloud service or something) then it may be the culprit. I'm not comfortable opening all the ports SE says to open to all IP addresses. I'd rather limit it to just ones owned by SE.