Reliable channel overflowed

[Nuggs]

I recently moved and now my wifi connection is pretty spotty. I keep running into two dreaded errors, reliable channel overflowed and cl_flushentitypacket

These are my settings right now:

cl_cmdrate "100"
cl_updaterate "85"
rate 14000

If I put my rate any higher than 14000 I start to get reliable channel overflowed and dropped. If I put my rate any lower I start to get cl_flushentitypacket. I also lag a decent amount and HH frag nade jumps are pretty difficult. Lowering cmd and updaterate always gives me relaible channel overflowed

When I ping Battlezone I my connection is all over the place

Pinging 66.151.244.170 with 32 bytes of data:
Request timed out.
Reply from 66.151.244.170: bytes=32 time=210ms TTL=51
Request timed out.
Reply from 66.151.244.170: bytes=32 time=216ms TTL=51

Ping statistics for 66.151.244.170:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 210ms, Maximum = 216ms, Average = 213ms


Pinging 66.151.244.170 with 32 bytes of data:
Reply from 66.151.244.170: bytes=32 time=38ms TTL=51
Reply from 66.151.244.170: bytes=32 time=45ms TTL=51
Reply from 66.151.244.170: bytes=32 time=40ms TTL=51
Reply from 66.151.244.170: bytes=32 time=37ms TTL=51

Ping statistics for 66.151.244.170:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 37ms, Maximum = 45ms, Average = 40ms


Pinging 66.151.244.170 with 32 bytes of data:
Reply from 66.151.244.170: bytes=32 time=37ms TTL=51
Reply from 66.151.244.170: bytes=32 time=36ms TTL=51
Reply from 66.151.244.170: bytes=32 time=38ms TTL=51
Reply from 66.151.244.170: bytes=32 time=43ms TTL=51

Ping statistics for 66.151.244.170:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 43ms, Average = 38ms

Any suggestions? Also I forget how to read the net_graph graph but I included a shot here in case that helps


net graph.jpg

[Bishop]

Can you run a broadband speed test and post your download and upload speeds?Maybe run it a few times to get a sense of consistency. 

[Master]

Can you run a broadband speed test and post your download and upload speeds?Maybe run it a few times to get a sense of consistency. 

You are very much running into network congestion, considering the very low amounts of data required to actually play on a multiplayer videogame from 1999 I would have to suggest you find a better solution.

the RCO error you are talking about, I was under the assumption was mostly due to too many HUD messages, this is most likely due to you having a bad connection, the airshot plugin sends 3 messages in the 'reliable channel' which may very well be getting resent to you due to a spotty connection. :^)

a more accurate test for you might be to send some very mild packets and see how that goes.

win32: ping -n 20 -l 512 -4 dedicated.esclan.net
penguin: ping -c 20 -s 512 -4 dedicated.esclan.net

Still super interested in that speedtest though..

[Nuggs]

 Here are the speed test results from ookla in order, test server is 150 miles away

Ping 24
Download Mbps
10.81
Upload Mbps
11.04


Ping 104
Download Mbps
7.60
Upload Mbps
11.39

Ping 42
Download Mbps
7.48
Upload Mbps
8.05

Ping 40
Download Mbps
7.44
Upload Mbps
7.64

Ping 26
Download Mbps
8.11
Upload Mbps
10.56


Here are the results of the ping tests, again in order of testing

Pinging dedicated.esclan.net [66.151.244.170] with 512 bytes of data:
Reply from 66.151.244.170: bytes=512 time=55ms TTL=51
Reply from 66.151.244.170: bytes=512 time=54ms TTL=51
Reply from 66.151.244.170: bytes=512 time=180ms TTL=51
Reply from 66.151.244.170: bytes=512 time=160ms TTL=51
Reply from 66.151.244.170: bytes=512 time=166ms TTL=51
Reply from 66.151.244.170: bytes=512 time=41ms TTL=51
Reply from 66.151.244.170: bytes=512 time=107ms TTL=51
Reply from 66.151.244.170: bytes=512 time=766ms TTL=51
Reply from 66.151.244.170: bytes=512 time=125ms TTL=51
Reply from 66.151.244.170: bytes=512 time=63ms TTL=51
Reply from 66.151.244.170: bytes=512 time=39ms TTL=51
Reply from 66.151.244.170: bytes=512 time=127ms TTL=51
Reply from 66.151.244.170: bytes=512 time=84ms TTL=51
Reply from 66.151.244.170: bytes=512 time=76ms TTL=51
Reply from 66.151.244.170: bytes=512 time=59ms TTL=51
Reply from 66.151.244.170: bytes=512 time=100ms TTL=51
Reply from 66.151.244.170: bytes=512 time=137ms TTL=51
Reply from 66.151.244.170: bytes=512 time=83ms TTL=51
Reply from 66.151.244.170: bytes=512 time=257ms TTL=51
Reply from 66.151.244.170: bytes=512 time=72ms TTL=51

Ping statistics for 66.151.244.170:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 39ms, Maximum = 766ms, Average = 137ms

Pinging dedicated.esclan.net [66.151.244.170] with 512 bytes of data:
Reply from 66.151.244.170: bytes=512 time=233ms TTL=51
Reply from 66.151.244.170: bytes=512 time=127ms TTL=51
Reply from 66.151.244.170: bytes=512 time=61ms TTL=51
Reply from 66.151.244.170: bytes=512 time=78ms TTL=51
Reply from 66.151.244.170: bytes=512 time=113ms TTL=51
Reply from 66.151.244.170: bytes=512 time=55ms TTL=51
Reply from 66.151.244.170: bytes=512 time=63ms TTL=51
Reply from 66.151.244.170: bytes=512 time=62ms TTL=51
Reply from 66.151.244.170: bytes=512 time=43ms TTL=51
Reply from 66.151.244.170: bytes=512 time=135ms TTL=51
Reply from 66.151.244.170: bytes=512 time=88ms TTL=51
Reply from 66.151.244.170: bytes=512 time=296ms TTL=51
Reply from 66.151.244.170: bytes=512 time=138ms TTL=51
Reply from 66.151.244.170: bytes=512 time=131ms TTL=51
Reply from 66.151.244.170: bytes=512 time=192ms TTL=51
Reply from 66.151.244.170: bytes=512 time=84ms TTL=51
Reply from 66.151.244.170: bytes=512 time=135ms TTL=51
Reply from 66.151.244.170: bytes=512 time=79ms TTL=51
Reply from 66.151.244.170: bytes=512 time=49ms TTL=51
Reply from 66.151.244.170: bytes=512 time=276ms TTL=51

Ping statistics for 66.151.244.170:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 43ms, Maximum = 296ms, Average = 121ms

Pinging dedicated.esclan.net [66.151.244.170] with 512 bytes of data:
Reply from 66.151.244.170: bytes=512 time=145ms TTL=51
Reply from 66.151.244.170: bytes=512 time=133ms TTL=51
Reply from 66.151.244.170: bytes=512 time=168ms TTL=51
Reply from 66.151.244.170: bytes=512 time=238ms TTL=51
Reply from 66.151.244.170: bytes=512 time=53ms TTL=51
Reply from 66.151.244.170: bytes=512 time=40ms TTL=51
Reply from 66.151.244.170: bytes=512 time=108ms TTL=51
Reply from 66.151.244.170: bytes=512 time=53ms TTL=51
Reply from 66.151.244.170: bytes=512 time=61ms TTL=51
Reply from 66.151.244.170: bytes=512 time=40ms TTL=51
Reply from 66.151.244.170: bytes=512 time=36ms TTL=51
Reply from 66.151.244.170: bytes=512 time=51ms TTL=51
Reply from 66.151.244.170: bytes=512 time=36ms TTL=51
Reply from 66.151.244.170: bytes=512 time=50ms TTL=51
Reply from 66.151.244.170: bytes=512 time=42ms TTL=51
Reply from 66.151.244.170: bytes=512 time=38ms TTL=51
Reply from 66.151.244.170: bytes=512 time=40ms TTL=51
Reply from 66.151.244.170: bytes=512 time=37ms TTL=51
Reply from 66.151.244.170: bytes=512 time=39ms TTL=51
Reply from 66.151.244.170: bytes=512 time=49ms TTL=51

Ping statistics for 66.151.244.170:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 238ms, Average = 72ms

Pinging dedicated.esclan.net [66.151.244.170] with 512 bytes of data:
Reply from 66.151.244.170: bytes=512 time=36ms TTL=51
Reply from 66.151.244.170: bytes=512 time=40ms TTL=51
Reply from 66.151.244.170: bytes=512 time=71ms TTL=51
Reply from 66.151.244.170: bytes=512 time=40ms TTL=51
Reply from 66.151.244.170: bytes=512 time=39ms TTL=51
Reply from 66.151.244.170: bytes=512 time=38ms TTL=51
Reply from 66.151.244.170: bytes=512 time=37ms TTL=51
Reply from 66.151.244.170: bytes=512 time=44ms TTL=51
Reply from 66.151.244.170: bytes=512 time=37ms TTL=51
Reply from 66.151.244.170: bytes=512 time=46ms TTL=51
Reply from 66.151.244.170: bytes=512 time=47ms TTL=51
Reply from 66.151.244.170: bytes=512 time=45ms TTL=51
Reply from 66.151.244.170: bytes=512 time=38ms TTL=51
Reply from 66.151.244.170: bytes=512 time=38ms TTL=51
Reply from 66.151.244.170: bytes=512 time=40ms TTL=51
Reply from 66.151.244.170: bytes=512 time=47ms TTL=51
Reply from 66.151.244.170: bytes=512 time=40ms TTL=51
Reply from 66.151.244.170: bytes=512 time=37ms TTL=51
Reply from 66.151.244.170: bytes=512 time=43ms TTL=51
Reply from 66.151.244.170: bytes=512 time=36ms TTL=51

Ping statistics for 66.151.244.170:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 71ms, Average = 41ms

Pinging dedicated.esclan.net [66.151.244.170] with 512 bytes of data:
Reply from 66.151.244.170: bytes=512 time=46ms TTL=51
Reply from 66.151.244.170: bytes=512 time=41ms TTL=51
Reply from 66.151.244.170: bytes=512 time=39ms TTL=51
Reply from 66.151.244.170: bytes=512 time=44ms TTL=51
Reply from 66.151.244.170: bytes=512 time=36ms TTL=51
Reply from 66.151.244.170: bytes=512 time=41ms TTL=51
Reply from 66.151.244.170: bytes=512 time=39ms TTL=51
Reply from 66.151.244.170: bytes=512 time=40ms TTL=51
Reply from 66.151.244.170: bytes=512 time=48ms TTL=51
Reply from 66.151.244.170: bytes=512 time=37ms TTL=51
Reply from 66.151.244.170: bytes=512 time=38ms TTL=51
Reply from 66.151.244.170: bytes=512 time=38ms TTL=51
Reply from 66.151.244.170: bytes=512 time=37ms TTL=51
Reply from 66.151.244.170: bytes=512 time=36ms TTL=51
Reply from 66.151.244.170: bytes=512 time=42ms TTL=51
Reply from 66.151.244.170: bytes=512 time=40ms TTL=51
Reply from 66.151.244.170: bytes=512 time=38ms TTL=51
Reply from 66.151.244.170: bytes=512 time=37ms TTL=51
Reply from 66.151.244.170: bytes=512 time=37ms TTL=51
Reply from 66.151.244.170: bytes=512 time=39ms TTL=51

Ping statistics for 66.151.244.170:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 48ms, Average = 39ms

[Nuggs]

Does this look like something that might be mitigated with different rate settings or is my connection just FUBAR?

[Bishop]

The jumps in ping to 200+ highlight a problem with your connection that won't be mitigated by tfc rate settings.  Also you had packet loss in your first post which is very bad.  That being said, when your connection is working you should be able to handle these settings:

rate 25000
cl_cmdrate set to fps+50
cl_updaterate 100

[Nuggs]

Thanks for the info Bishop

I'm using my desktop PC onboard WiFi right now. I found an old USB WiFi dongle so I'll give that a shot and rerun the tests to see if it makes things better or worse

[Master]

Thanks for the info Bishop

I'm using my desktop PC onboard WiFi right now. I found an old USB WiFi dongle so I'll give that a shot and rerun the tests to see if it makes things better or worse

trying to solve your network congestion issue by doing literally nothing.. I like it, please let me know how it works out.

[Nuggs]

Ah so you're telling me the issue is the actual ISP and not my WiFi connection stenghth? Too many users sucking up bandwidth?

I moved about 100 yards away to a different condo in the same community. Internet is provided by spectrum to every building via 4 access points per building. 12 units per building. So if I was getting a solid connection in the last building and a shit one here, probably means too many users on the network??

Any suggestions? Complain to the POA maybe? Ask them to send Spectrum out and verify speeds? Every unit is supposed to receive "up to 100/100mbps" but I guess that's just weasel words. Maybe try using LTE and my iPhone as a WiFi hotspot? How much data do you think a 1hr session of TFC uses

[M1LO]

I have no idea if this is any help or even related to the issues Nuggs is having.
But it wouldn't be unknown for me to receive over a dozen RCO errors during one match on BZ on a daily basis. My ping averages on a good day between 135-150 but more often than not hovering around 160-180. A lot of the time I would just drop out completely and have to rejoin whilst also restarting the router just for a little extra hope of a prolonged uninterrupted connection. Speaking with an engineer for some other connection related issue they suggested that I was currently using a "static connection" which meant that any time I restarted the router or had a drop out the router was set to only reconnect to the one I.P address. Removing this setting meant that the router would now connect to the first available I.P it found,  and from that moment I now very rarely receive an RCO error, I mean the difference now is like night and day to what it was.
Again technically I have no offerings other than just about knowing what "PC" stands for but this change certainly made a huge difference to the issues I was having.         

[Master]

https://www.youtube.com/watch?v=vLjVSMjQYFc

use ethernet

[Nuggs]

So to update, Yosh sent me a message and suggested to remove the sparkys commands in my autoexec.cfg for flag location, timers and bhop meter and since then I haven't experienced the reliable channel overflow.

Still running into cl_flushentitypacket on occasion and some weird FPS drops but at least it's somewhat playable now