[SOLVED] Getting DCed after a couple minutes of gameplay?

[boxes]

 hello tastyfriends,

  i recently got my dad back into playing quake 2 as per request, i set him up with his old config, got him a functional modern client, and showed him the server list. everything works fine, except after generally no matter what happens, after about a match and a half we'll /both/ get forcibly disconnected. i thought it might have been something with our configs, or something in the router- but i've extensively exhausted all possibilities and came here to explore if it was a common occurrence. i figured if we both get DCed in around the same time frame on different computers, configs, and even OSes that our IP must be getting blocked/was banned for some reason or another.

the names we go by are 'boxes' (me) and 'springgreens'. i've tested this on rails,dm,wodx you name it, all the same thing. any way anyone can check this out for me?

SOLUTION:

  I have a Netgear router and it wasn't playing nice with Quake 2, in most servers. The solution was to enable QoS, get rid of all the default rules, and make Quake 2 the highest priority on the router. Was able to play railz for an hour with zero disconnects, whereas previously it would take about 10-12 minutes (about a match and a half) to get disconnected. I'm going to post this in the OP as well for any future people who have this same problem.

[quadz]

Hi,

after about a match and a half we'll /both/ get forcibly disconnected. i thought it might have been something with our configs, or something in the router- but i've extensively exhausted all possibilities and came here to explore if it was a common occurrence.

From the server logs, there indeed appears to be a network error.

Lots of this sort of thing:

[2017-05-15 02:11] springgreens[173.170.xxx.xxx:56749]: protocol 35: "q2pro r1504~924ff39 Dec 3 2014 Win32 x86"
[2017-05-15 02:11] springgreens[173.170.xxx.xxx:56749] changed name to SpRiNgGrEeNs.
[2017-05-15 02:16] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:16] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:16] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:16] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:16] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:16] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:16] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:16] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:16] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:16] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:16] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:16] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:17] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:17] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:17] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:17] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:17] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749
[2017-05-15 02:17] NET_GetPacket: No route to host from 173.170.xxx.xxx:56749


Not sure where along the route this would be likely to occur. (Makes me wonder if your router's NAT is timing out incorrectly and dropping the mapping from that port to your internal network IP. But, dunno.)

[boxes]

snip

snip

snip

i might have worded that incorrectly and maybe you misunderstood. i didn't mean "both" at the exact same time, just that we both run into those conditions from which we get disconnected. (after for playing for a match or so we get DCed)

edit: fiddled with my nat being open and closed with no results, also forwarded the port i saw in the logs to my sub ip to see if it would help- nada.

[quadz]

i might have worded that incorrectly and maybe you misunderstood. i didn't mean "both" at the exact same time, just that we both run into those conditions from which we get disconnected. (after for playing for a match or so we get DCed)

I don't feel like a misunderstanding occurred.

I'm simply reporting what's in the server logs.

And what it seems to indicate, is that packets suddenly begin to be bounced at your router with a "no route to host" error.

I didn't say anything about "both".

The logs I posted refer to a specific IP/port combination.

It's quite possible for your router to begin bouncing packets destined for one port and yet continue to accept packets for another, if its NAT has gotten confused.

That said, this is an uncommon occurrence, so I'm only speculating as to the cause.

The single fact we seem to have (from the server logs) is that your router is (after some time period) suddenly deciding to begin bouncing packets to an IP/port that it was previously accepting.

Perhaps there are network tools we could use to probe the issue in more detail? (Though I'm not sure which, offhand.)

[boxes]

i might have worded that incorrectly and maybe you misunderstood. i didn't mean "both" at the exact same time, just that we both run into those conditions from which we get disconnected. (after for playing for a match or so we get DCed)

snip

ah i am the misunderstandee(er?)

im going to do a hard reset on my router and see if it plays nice on a default configuration.

[boxes]

Doubleposting for the sake of solving my own problem:

 I have a Netgear router and it wasn't playing nice with Quake 2, in most servers. The solution was to enable QoS, get rid of all the default rules, and make Quake 2 the highest priority on the router. Was able to play railz for an hour with zero disconnects, whereas previously it would take about 10-12 minutes (about a match and a half) to get disconnected. I'm going to post this in the OP as well for any future people who have this same problem.

[Sgt. Dick]

I glad to see you got it fixed.

See you in the arena