|
Author |
Thread Statistics | Show CCP posts - 3 post(s) |

Siuse
|
Posted - 2008.09.14 08:42:00 -
[1]
Does anyone noticed the forum also lag as with the game itself? atleast thats for me. keep having to refresh so much just to load a page.
i wont blame my isp too much. all other website is fine. even my brother's web voice enabled game is fine.

|

Siuse
|
Posted - 2008.09.14 15:29:00 -
[2]
well this issue been on going since July!
|

Siuse
|
Posted - 2008.09.17 15:11:00 -
[3]
i tried 2 methods that solved my problem. two settings were tweaked in my DSL router which solved the problem where the ping to www.eve-online.com become more stable.
1. off firewall in my router (reduced loss packet to 3%)
or...
2. tweak MTU setting in my router to 1302 (used to be 1492) by following how to estimate best MTU in this link - http://www.dslreports.com/tweaks/MTU . The targeted ping test is to www.eve-online.com and seems '1302' worked best for my router and location.
This reduced my loss packet to 7% (used to be 50% loss recently) for eve. I continue to use this setting as I can enable my router's firewall, and there's no DC problem. Not sure if it will help the rest of you.
|

Siuse
|
Posted - 2008.09.24 16:38:00 -
[4]
Originally by: Siuse i tried 2 methods that solved my problem. two settings were tweaked in my DSL router which solved the problem where the ping to www.eve-online.com become more stable.
1. off firewall in my router (reduced loss packet to 3%)
or...
2. tweak MTU setting in my router to 1302 (used to be 1492) by following how to estimate best MTU in this link - http://www.dslreports.com/tweaks/MTU . The targeted ping test is to www.eve-online.com and seems '1302' worked best for my router and location.
This reduced my loss packet to 7% (used to be 50% loss recently) for eve. I continue to use this setting as I can enable my router's firewall, and there's no DC problem. Not sure if it will help the rest of you.
ok this has been working for me since my last post. however these few days it is back to haunt me again (tested different MTU setting like crazy). however I then read about xbox not compatible with modems with low MTU. at the same time, I discovered there is a "Do not enforce MTU" in my Aztech modem. This seems to have solved the problem for me tonite.
really hope CCP can help resolve/confirm this MTU issue.
|

Siuse
|
Posted - 2008.09.25 16:24:00 -
[5]
Yea. I too have to re-enable my MTU setting and try a different setting tonite. The connection is bad, with lots of loss packets when testing ping.
|

Siuse
|
Posted - 2008.09.30 15:07:00 -
[6]
Pinging www.eve-online.com [87.237.39.199] with 32 bytes of da
Request timed out. Request timed out. Request timed out. Reply from 87.237.39.199: bytes=32 time=316ms TTL=116 Reply from 87.237.39.199: bytes=32 time=318ms TTL=116 Request timed out. Reply from 87.237.39.199: bytes=32 time=348ms TTL=116 Request timed out. Reply from 87.237.39.199: bytes=32 time=316ms TTL=116 Reply from 87.237.39.199: bytes=32 time=318ms TTL=116 Reply from 87.237.39.199: bytes=32 time=316ms TTL=116 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 87.237.39.199: bytes=32 time=235ms TTL=116 Reply from 87.237.39.199: bytes=32 time=235ms TTL=116 Request timed out. Reply from 87.237.39.199: bytes=32 time=284ms TTL=116 Reply from 87.237.39.199: bytes=32 time=292ms TTL=116 Request timed out. Request timed out. Request timed out. Request timed out. Reply from 87.237.39.199: bytes=32 time=341ms TTL=116 Request timed out. Reply from 87.237.39.199: bytes=32 time=321ms TTL=116 Reply from 87.237.39.199: bytes=32 time=324ms TTL=116 Request timed out. Request timed out. Reply from 87.237.39.199: bytes=32 time=321ms TTL=116 Request timed out. Reply from 87.237.39.199: bytes=32 time=319ms TTL=116 Reply from 87.237.39.199: bytes=32 time=327ms TTL=116 Request timed out.
Ping statistics for 87.237.39.199: Packets: Sent = 36, Received = 16, Lost = 20 (55% loss),
|

Siuse
|
Posted - 2008.09.30 15:08:00 -
[7]
Pinging www.euro.yahoo-eu1.akadns.net [87.248.120.129] with 32 bytes of data:
Reply from 87.248.120.129: bytes=32 time=344ms TTL=48 Reply from 87.248.120.129: bytes=32 time=347ms TTL=48 Reply from 87.248.120.129: bytes=32 time=343ms TTL=48 Reply from 87.248.120.129: bytes=32 time=342ms TTL=48 Reply from 87.248.120.129: bytes=32 time=342ms TTL=48 Reply from 87.248.120.129: bytes=32 time=344ms TTL=48 Reply from 87.248.120.129: bytes=32 time=342ms TTL=48 Reply from 87.248.120.129: bytes=32 time=354ms TTL=48 Reply from 87.248.120.129: bytes=32 time=354ms TTL=48 Reply from 87.248.120.129: bytes=32 time=344ms TTL=48 Reply from 87.248.120.129: bytes=32 time=342ms TTL=48 Reply from 87.248.120.129: bytes=32 time=343ms TTL=48 Reply from 87.248.120.129: bytes=32 time=341ms TTL=48 Reply from 87.248.120.129: bytes=32 time=345ms TTL=48 Reply from 87.248.120.129: bytes=32 time=342ms TTL=48 Reply from 87.248.120.129: bytes=32 time=341ms TTL=48 Reply from 87.248.120.129: bytes=32 time=343ms TTL=48 Reply from 87.248.120.129: bytes=32 time=349ms TTL=48 Reply from 87.248.120.129: bytes=32 time=344ms TTL=48 Reply from 87.248.120.129: bytes=32 time=341ms TTL=48 Reply from 87.248.120.129: bytes=32 time=343ms TTL=48 Reply from 87.248.120.129: bytes=32 time=343ms TTL=48 Reply from 87.248.120.129: bytes=32 time=346ms TTL=48 Reply from 87.248.120.129: bytes=32 time=343ms TTL=48 Reply from 87.248.120.129: bytes=32 time=469ms TTL=48 Reply from 87.248.120.129: bytes=32 time=477ms TTL=48 Reply from 87.248.120.129: bytes=32 time=341ms TTL=48 Reply from 87.248.120.129: bytes=32 time=346ms TTL=48 Reply from 87.248.120.129: bytes=32 time=342ms TTL=48 Reply from 87.248.120.129: bytes=32 time=340ms TTL=48 Reply from 87.248.120.129: bytes=32 time=345ms TTL=48 Reply from 87.248.120.129: bytes=32 time=344ms TTL=48 Reply from 87.248.120.129: bytes=32 time=348ms TTL=48
Ping statistics for 87.248.120.129: Packets: Sent = 33, Received = 33, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 340ms, Maximum = 477ms, Average = 351ms
|

Siuse
|
Posted - 2008.10.11 17:35:00 -
[8]
Edited by: Siuse on 11/10/2008 17:38:56 I dont know about you guys. Router MTU resetting seems to work for me for the pass few months. but the tedious effort to tweak mtu everytime having issues are really trouble and lossing play time for me. cant mission at all.
another method which i'm 'trying' lately is changing my ADSL encapsulation to PPOA-VC.
Well, not sure how long will it hold - i start to notice my line's speed to UK are abit bad compare to smooth traffic to US side.
and.... ping stat SOMETIMES dont reflect the game disconnection issue. i got 50% packet losses but no disconnection for 3 hours.
|
|
|
|