Any idea what the IBurst settings should be ???

[scavern]

using Dr. TCP


TCP Receive window : 255552
window scaling : yes
time stamping : no
selective acks: yes
dial up (RAS) MTU : 1352
path MTU discovery : Yes
black hole detection : no
Max duplicate acks: 2
ttl : 64

downloads for me are pretty fast... but i do have to reconnect often

 

[native]

TCP Receive = 17136
Dial up (RAS) MTU = 1352
Adapter Settings = 1352 (Depending on your connection, if it is USB go for iBurst Terminal, if Ethernet chose your network Card.)
Window Scaling = Default
Time Stamping = Default
Selective acks = Default

path MTU discovery = Default
Black hole = Default
black hole= leave it empty
ttl= leave it empty

 

[Gatecrasher]

There's no "should be", "right" or "wrong."

But setting dial up (RAS) MTU will do nothing.

You need to set the MTU for the NIC (if using ethernet) or
Local area network (USB) that your modem connects to.

My current settings are:

TCP Receive window : 97440
window scaling : yes
time stamping : yes
selective acks: yes
dial up (RAS) MTU : 1500
path MTU discovery : Yes
black hole detection : Yes
Max duplicate acks: 2
ttl : 128
Realtek NIC MTU: 1432.

But you should do the ping test to see what MTU your BS is set to. It
appears that not all base stations are configured the same.

The wrong MTU has the potential to cause disconnects and other problems. But none of the other setting should have too great an effect.

 

[TheYak]

I don't know what these settings are supposed to be, but Tsepo (upon getting a call from me, complaining about k@k speed) told me earlier tonight to change it to 1352 from 1392 - it was fine for a few minutes - and now my connection is BUGGERED again... I'm getting pings between 1500ms and 2400ms!!! LOCAL! To iBurst's site!

Best I start getting that ADSL application ready...

 

[ic]

My advice: apply some irony to the situation...

...
Best I start getting that ADSL application ready...

Use your Burst-i connection to apply online at the Telkomonopoly website...

 

[Gatecrasher]

Here's my current ping test, showing cutoff of 1404. Wherever it cuts off add 28. Hence MTU of 1432. Your base station may be different.

C:\Documents and Settings\...>ping -f -l 1404 [url]www.iburst.co.za[/url]

Pinging [url]www.iburst.co.za[/url] [196.30.31.120] with 1404 bytes of data:

Reply from 196.30.31.120: bytes=1404 time=248ms TTL=126
Reply from 196.30.31.120: bytes=1404 time=202ms TTL=126
Reply from 196.30.31.120: bytes=1404 time=296ms TTL=126
Reply from 196.30.31.120: bytes=1404 time=249ms TTL=126

Ping statistics for 196.30.31.120:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 202ms, Maximum = 296ms, Average = 248ms

C:\Documents and Settings\...>ping -f -l 1405 [url]www.iburst.co.za[/url]

Pinging [url]www.iburst.co.za[/url] [196.30.31.120] with 1405 bytes of data:

Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 196.30.31.120:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),