Guest Guest_Mizerie_* Posted February 20, 2006 Report Posted February 20, 2006 !@#$%^&*o Mizerie here.I am one of the head sysops for SSCX Chaos/League Zone SVS and for the first time ever I am having difficulties with my connection to subspace. I have done everything I know how to do and have checked with everyone I know that might be able to find a solution for me.view my trace info here:trace info As you can see, after 100 or so cycles I am having pretty much 100% packetloss at hops 7 and 8. These servers/routers appear to be somewhere in Minnesota. This has been going on for over 3 weeks now and its starting to upset me a little bit. My cable company has been out to run some tests and since nothing is wrong on their end they obviously wont help me to restore my connection to little ol subspace.SS biller has been reset, my routers and modem have been reset. I have done everything I know how to do to try and get my connection to re-route and byp!@#$%^&* these servers in Minnesota, but to no avail. The cable company recommended that I use a proxy to byp!@#$%^&* them and !@#$%^&* that is worth a shot to me but I dont know of any proxy servers that can help me here. A proxy is probably goign to put my ping way to high to play anyway (if it has high traffic). Every free proxy server I attempt to use comes back with a "Socks error 4, check proxy configuration" anyway. I am looking for any advice you guys may have to help me fix this unfortunate connection issue. -MizerieData Manager and AML Sysop
★ SOS Posted February 20, 2006 Report Posted February 20, 2006 Those two hops are not a problem. Call them a measurement error, that would be most fitting. Aside from that non-error, the trace looks great. What problems are you having?
Guest Guest_Mizerie_* Posted February 20, 2006 Report Posted February 20, 2006 in game stats0.0% S2C packetloss.10%+ C2S packetloss.pings are good. My internet connection is excellent to everything but subspace. how are those hops not a problem if I am getting 100% packetloss from them and a regular ping to either hop is "request timed out"? Its almost like those servers/routers are purposly blocking my connection. As far as I know when routers are down you are supposed to be re-routed. isnt that how the internet works? I have been told by some of my IT friends at work that the only way to really solve this issue might be to contact that administrators of the servers in question, but I wouldnt know how to begin in that quest. -Miz
★ SOS Posted February 21, 2006 Report Posted February 21, 2006 Your IT friends are idiots The routers are not down nor are they giving you any packetloss, that's just what I would call a "measurement error". The trace shows 0% packetloss. C2S packetloss, hmm? Well, I assume you're not doing any insane uploading that would eat up your upstream? Could be that your ISP is giving UDP packets (which Continuum uses, normal internet consists of TCP packets) special low-priority treatment. Happened to me once, for a few months UDP was totally screwed. I guess enough people complained and it got fixed for me. Are you having this problem with every SS zone? Try some random small-time zones. Oh yeah, have you tried another computer on the same connection? What kind of a connection are you on? Have a router? Try without it. Let me know how the small zones work and talk about the network configuration. If that doesn't give any insight into the issue, I'll whip together some UDP testing program that might provide some.
Guest Guest_Mizerie_* Posted February 21, 2006 Report Posted February 21, 2006 I am guessing it may be my connection in general. I get the same issue in every zone. The UDP point that you bring up may be right on the money. No matter what zone I connect to I get the same C2S packetloss, however there is no consistancy to it. Sometimes I can log into a zone and hold a connection for 15 minutes before getting disconnected. Other times its every minute.I notice that If I just start up the continuum main menu and watch my zone list for long enough then I see every zone go red for a couple of seconds.To answer all of your questions:- I do not run any programs when I play SS beside maybe the occasional browser window while I am alt-tabbed.- I tried my laptop on the same connection and still had the same results.- I use comcast high speed internet and running tests on that internet connection come out with great results. - I had a router, I eliminated it to see what difference it may make and it had no effect.- I have also experimented with turning off my firewall. What surprises me the most is that I have a friend that lives only a few miles away and he uses comcast as well, however he is not having these same issues. His connection does NOT go through the same servers/routers that mine do (the 12.123.#.# ones) -Miz
★ SOS Posted February 21, 2006 Report Posted February 21, 2006 Alright, time to give good old UDP a test then. I'll try to throw together some simple UDP test program by tomorrow evening.
★ SOS Posted February 22, 2006 Report Posted February 22, 2006 Ok, here is the test program.You'll need .Net Framework 2.0 to run it (you can get it from Windows Update if you do not have it). Let it send a few thousand packets and post the statistics it gives. Try with different sizes, see if you notice any changes in the packetloss depending on packet size. Play around with it and let me know what it shows.Tester.zip
Guest Guest_Mizerie_* Posted February 23, 2006 Report Posted February 23, 2006 SOS thank you for all of your !@#$%^&*istance and help so far, its great to have people like you around.Test results are as follows. I tried to run these tests during my own peak subspace playing times. I of course did not run ss while running these test, only the occasional brower window. please let me know if you need any more testing. ================================================(restarted computer before first test only)1st test ~3000 packets (size: 400) @ 10 packets per second. 6:17pmS2C: 0% C2S: 0.23% Sent: 3014 Received: 3007 Remotely received: 3007 2nd test ~2000 packets (size: 800) @ 10 packets per second. 6:32pmS2C: 0.05% C2S: 4.26% Sent: 2018 Received: 1931 Remotely received: 1932 3rd Test ~2250 packets (size: 200) @ 10 packets per second. 7:02pmS2C: 0% C2S: 2.94% Sent: 2242 Received: 2176 Remotely received: 2176 4th Test ~2000 packets (size: 400) @ 5 packets per second. 7:17pmS2C: 0% C2S: 0.05% Sent: 2015 Received: 2014 Remotely received: 2014 5th Test ~3500 packets (size: 1000) @ 10 packets per second. 7:48pmS2C: 0% C2S: 0.06% Sent: 3588 Received: 3586 Remotely received: 3586 6th Test ~3500 packets (size 800) @ 10 packets per second. 8:13pmS2C: 0.03% C2S: 5.53% Sent: 3505 Received: 3310 Remotely received: 3311 7th Test ~2000 packets (size 1200) @ 5 packets per second. 8:24pmS2C: 0.05% C2S: 2.9% Sent: 2033 Received: 1973 Remotely received: 1974 8th Test ~2000 packets (size 800) @ 10 packets per second. 9:05pmS2C: 0% C2S: 5.24% Sent: 2003 Received: 1898 Remotely received: 1898 9th Test ~2000 pacekts (size 1000) @ 10 packets per second. 9:19pmS2C: 0.05% C2S: 0.1% Sent: 2002 Received: 1999 Remotely received: 2000 10th Test ~2000 packets (size 100) @ 10 packets per second. 9:24pmS2C: 0% C2S: 6.18% Sent: 2005 Received: 1881 Remotely received: 1881======================================================= -Miz
★ SOS Posted February 23, 2006 Report Posted February 23, 2006 Hmm... well, looks like you do indeed have some UDP packetloss that occurs from time to time. Some tests show near zero, some show quite a bit. I'm afraid this is bad news. This indicates that most likely there is a faulty/super-congested router somewhere along the line. There is really only one thing you can do: bug the ISP. Try to get a technician on the phone, not just some customer service rep. Of course that's difficult with a big ISP... The ISP probably did not test UDP, since it is a rarely-used protocol. Most likely they just tested the raw data stream between your computer (or router) and the next immediate hop. This problem could come from any of those hops. Perhaps not even a hop under your ISPs control. But still, letting a technician know should speed up the fix, even if it is some router in the middle of nowhere. These things do get fixed when they're noticed but it's just that most people don't know how to notice this, so the tech support call centres aren't really equipped to handle these reports... You could try calling a tech over and explaining the issue to him (or showing him this thread) but I'm not sure whether he would be able to help you... at least over here the technicians don't know anything about internet, they just hook up wires to modems...
Recommended Posts