SaToon wrote:
Pie I can't believe you are here instead of in bed. But since your up do you think this a router issue?
Hey its spring break man! Lol.
From what I can tell and from talking with gunm4n and Cobalt, I don't think its an issues with anybody's personal router, but a hop that certain players have to make. Gunm4n identified a hop that was timing out for him, as he was having connection troubles that day. It was a hop that he had to make, but I didn't. Me, gunm4n, and Cobalt all pinged the IP of that hop with 20 packets. We both got 2 timeout, which is a 10% packetloss. This could account for hanging on edges and skipped frames. However, Sarah's problem is slightly different (I think). It is related though from what I can tell. She may be going through multiple hops that are bad, cause legacy engines, such as ProQuake to totally drop the connection. This, I think, is why she can stay connected with Darkplaces. Darkplaces handles 'blips' in connection loss much better. I have seen her ping spike to 1000+ which indicates temporary connection loss (such as a bad hop, or hop time out).
So here's what you can both do: Open up cmd and type 'tracert quake.shmack.net' (without the quotes). Give cmd some time to ping each hop. This will allow you to see what hops your connection has to make to get to shmack.
Important: Do not spam a server with ping requests. I would suggest no more than two rounds of 20 pings before waiting significant time, as in some cases pings can be mistaken for DOS attacksNow, excluding local IPs (like you modem/router) you can send packets to each hop to check for packet loss. I would put this in CMD: ping -n 20 'insert ip'
So for example: ping -n 20 204.93.204.153 (this is a hop I make on the way to shmack) and this is what I got:
Pinging 204.93.204.153 with 32 bytes of data:
Reply from 204.93.204.153: bytes=32 time=33ms TTL=52
Reply from 204.93.204.153: bytes=32 time=33ms TTL=52
Reply from 204.93.204.153: bytes=32 time=32ms TTL=52
Reply from 204.93.204.153: bytes=32 time=34ms TTL=52
Reply from 204.93.204.153: bytes=32 time=32ms TTL=52
Reply from 204.93.204.153: bytes=32 time=34ms TTL=52
Reply from 204.93.204.153: bytes=32 time=33ms TTL=52
Reply from 204.93.204.153: bytes=32 time=31ms TTL=52
Reply from 204.93.204.153: bytes=32 time=34ms TTL=52
Reply from 204.93.204.153: bytes=32 time=32ms TTL=52
Reply from 204.93.204.153: bytes=32 time=34ms TTL=52
Reply from 204.93.204.153: bytes=32 time=33ms TTL=52
Reply from 204.93.204.153: bytes=32 time=32ms TTL=52
Reply from 204.93.204.153: bytes=32 time=32ms TTL=52
Reply from 204.93.204.153: bytes=32 time=66ms TTL=52
Reply from 204.93.204.153: bytes=32 time=34ms TTL=52
Reply from 204.93.204.153: bytes=32 time=33ms TTL=52
Reply from 204.93.204.153: bytes=32 time=31ms TTL=52
Reply from 204.93.204.153: bytes=32 time=31ms TTL=52
Reply from 204.93.204.153: bytes=32 time=33ms TTL=52
Reply from 204.93.204.153: bytes=32 time=33ms TTL=52
Reply from 204.93.204.153: bytes=32 time=32ms TTL=52
(there will be more info in cmd like avg ping etc.) I make the txt file of my ping results by doing this in cmd: ping -n 20 204.93.204.153>> c:\users\Username\Desktop\Test.txt -t
If y'all want to ping all your hops with: 'ping -n 20 'insert ip'>> c:\users\username\Desktop\'filname'.txt -t' (without quotes) you could post anything that times out here and I could ping it (as I am not having theses issues) and we could see if theres a bad hop.
Hope we can get this sorted!