TCP/IP settings

[DukeOFprunes]

After doing everything I could with the MTU etc settings, I've been playing around with some protocol/adapter/TCP/IP settings last night, some combinations got better results than others (tip: don't enable "Software compression")

Do you guys know which settings are best supported by iBurst, or which settings do you know make the most difference?
(i.e. En/Disable LCP controls; IP Header compression; Negotiate Multilink...;DNS settings, WINS settings etc etc etc)

 

[FireFLi]

Only thing I know is that the MTU should be set to 1352.

 

[DukeOFprunes]

Thanks, I've done a lot of playing around with that too, and my packet loss issues haven't abated since January. That's a pity since December, when I signed up, saw me playing CoH with 0 packet loss, ~300ms ping, perfect conditions all round, but no longer.

That's why I'm trying to fiddle with other bits now, but I don't know these things well enough. It's driving me up the wall.

 

[FireFLi]

It's not you, it's iburst. I am in a similar position, was quite happily playing WoW with an average in game latency ~700. Since mid/late January it's become unplayable. Don't have packet loss but the latency is very unstable.

Which tower are you on?

Tonights pings... all over the place
Pinging www.iburst.co.za [196.30.31.120] with 32 bytes of da

Reply from 196.30.31.120: bytes=32 time=51ms TTL=124
Reply from 196.30.31.120: bytes=32 time=320ms TTL=124
Reply from 196.30.31.120: bytes=32 time=459ms TTL=124
Reply from 196.30.31.120: bytes=32 time=94ms TTL=124
Reply from 196.30.31.120: bytes=32 time=238ms TTL=124
Reply from 196.30.31.120: bytes=32 time=248ms TTL=124
Reply from 196.30.31.120: bytes=32 time=367ms TTL=124
Reply from 196.30.31.120: bytes=32 time=156ms TTL=124
Reply from 196.30.31.120: bytes=32 time=131ms TTL=124
Reply from 196.30.31.120: bytes=32 time=241ms TTL=124
Reply from 196.30.31.120: bytes=32 time=160ms TTL=124
Reply from 196.30.31.120: bytes=32 time=189ms TTL=124
Reply from 196.30.31.120: bytes=32 time=173ms TTL=124
Reply from 196.30.31.120: bytes=32 time=97ms TTL=124
Reply from 196.30.31.120: bytes=32 time=307ms TTL=124
Reply from 196.30.31.120: bytes=32 time=228ms TTL=124
Reply from 196.30.31.120: bytes=32 time=92ms TTL=124
Reply from 196.30.31.120: bytes=32 time=271ms TTL=124
Reply from 196.30.31.120: bytes=32 time=189ms TTL=124
Reply from 196.30.31.120: bytes=32 time=383ms TTL=124
Reply from 196.30.31.120: bytes=32 time=233ms TTL=124
Reply from 196.30.31.120: bytes=32 time=72ms TTL=124
Reply from 196.30.31.120: bytes=32 time=402ms TTL=124
Reply from 196.30.31.120: bytes=32 time=186ms TTL=124
Reply from 196.30.31.120: bytes=32 time=100ms TTL=124
Reply from 196.30.31.120: bytes=32 time=90ms TTL=124
Reply from 196.30.31.120: bytes=32 time=118ms TTL=124
Reply from 196.30.31.120: bytes=32 time=56ms TTL=124
Reply from 196.30.31.120: bytes=32 time=156ms TTL=124
Reply from 196.30.31.120: bytes=32 time=111ms TTL=124
Reply from 196.30.31.120: bytes=32 time=299ms TTL=124

Ping statistics for 196.30.31.120:
Packets: Sent = 31, Received = 31, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 459ms, Average = 200ms

 

[Jaco82]

Northcliff is the best!!

Look at my pings...can't beat that!


>ping iburst.co.za -n 30 -w 700

Pinging iburst.co.za [196.30.31.120] with 32 bytes of data:

Request timed out.
Reply from 196.30.31.120: bytes=32 time=812ms TTL=125
Reply from 196.30.31.120: bytes=32 time=93ms TTL=125
Request timed out.
Request timed out.
Reply from 196.30.31.120: bytes=32 time=265ms TTL=125
Reply from 196.30.31.120: bytes=32 time=828ms TTL=125
Reply from 196.30.31.120: bytes=32 time=312ms TTL=125
Reply from 196.30.31.120: bytes=32 time=687ms TTL=125
Reply from 196.30.31.120: bytes=32 time=359ms TTL=125
Request timed out.
Reply from 196.30.31.120: bytes=32 time=312ms TTL=125
Reply from 196.30.31.120: bytes=32 time=203ms TTL=125
Reply from 196.30.31.120: bytes=32 time=296ms TTL=125
Reply from 196.30.31.120: bytes=32 time=656ms TTL=125
Reply from 196.30.31.120: bytes=32 time=343ms TTL=125
Reply from 196.30.31.120: bytes=32 time=437ms TTL=125
Request timed out.
Request timed out.
Reply from 196.30.31.120: bytes=32 time=562ms TTL=125
Reply from 196.30.31.120: bytes=32 time=359ms TTL=125
Reply from 196.30.31.120: bytes=32 time=578ms TTL=125
Reply from 196.30.31.120: bytes=32 time=328ms TTL=125
Reply from 196.30.31.120: bytes=32 time=500ms TTL=125
Reply from 196.30.31.120: bytes=32 time=375ms TTL=125
Reply from 196.30.31.120: bytes=32 time=250ms TTL=125
Reply from 196.30.31.120: bytes=32 time=453ms TTL=125
Reply from 196.30.31.120: bytes=32 time=734ms TTL=125
Request timed out.
Reply from 196.30.31.120: bytes=32 time=562ms TTL=125

Ping statistics for 196.30.31.120:
Packets: Sent = 30, Received = 23, Lost = 7 (23% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 828ms, Average = 448ms


Can anyone plz recommend settings...

 

[FireFLi]

you win but I doubt any network tweaks are going to improve those