Short Iburst Rant

S1ght

Expert Member
Joined
Jan 23, 2006
Messages
3,301
Reaction score
27
Location
Berlin
K, on 1 gig package with 64k throttle and somehow the cap decided to disappear (I suspect my brother or parents were doing some of their own downloading) so now we at the throttled speed and yet its barely enough to stay on mxit pc or google talk or msn so obviously browsing with any of these running cause them to disconnect and reconnect a million times. If i try do a simple download it downloads at like 2 and all browsing seems to not be an option...

And they call this a service?!

*Rant over :)
 
K, on 1 gig package with 64k throttle and somehow the cap decided to disappear (I suspect my brother or parents were doing some of their own downloading) so now we at the throttled speed and yet its barely enough to stay on mxit pc or google talk or msn so obviously browsing with any of these running cause them to disconnect and reconnect a million times. If i try do a simple download it downloads at like 2 and all browsing seems to not be an option...

And they call this a service?!

*Rant over :)

Maybe its your setup. The 64k throttle while not quite giving me 64k speeds
does give me up to about 56-60k. I can download gigabytes of stuff
at that speed, obviously it takes a long time but leaving a PC downloading
overnight yields 300MB in the morning. I'm also able to browse
the web while running Skype and MSN. I can do VOIP on Skype and VoipCheap, in fact I can do both (not at the same time) while on dialup, on the 64k throttled
service the speed is just a bit faster - 2-3000 bytes per second.

So maybe your MTU setting is wrong, or your signal is poor or
maybe iBurst is screwing people over now, but even last month
the 64k speed on iBurst while never maxing out at 8192 bytes
per second gave me a consistent 7000-7600 bytes per
sec throughout.
 
I'm not too sure about the MTU (dunno how to check it) but my signal is fine cause I'm pretty close to a tower
 
I'm not too sure about the MTU (dunno how to check it) but my signal is fine cause I'm pretty close to a tower

I just checked by pinging the JHB DNS server and my packets were not fragmented

C:\Documents and Settings\iBurst connection>ping 196.30.31.193 -f -l 1352

Pinging 196.30.31.193 with 1352 bytes of data:

Reply from 196.30.31.193: bytes=1352 time=17ms TTL=125
Reply from 196.30.31.193: bytes=1352 time=18ms TTL=125
Reply from 196.30.31.193: bytes=1352 time=18ms TTL=125
Reply from 196.30.31.193: bytes=1352 time=18ms TTL=125
 
C:\Documents and Settings\>ping 192.30.31.193 -f -l 1352

Pinging 192.30.31.193 with 1352 bytes of data:

Reply from 192.168.1.254: 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 192.30.31.193:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Ok, is the default MTU 1352? cause maybe this could be the problem then? Cause on my router the MTU is set to 1352 and I connect through wireless to the router
 
C:\Documents and Settings\>ping 192.30.31.193 -f -l 1352

Pinging 192.30.31.193 with 1352 bytes of data:

Reply from 192.168.1.254: 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 192.30.31.193:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Ok, is the default MTU 1352? cause maybe this could be the problem then? Cause on my router the MTU is set to 1352 and I connect through wireless to the router

Hi there,

I have a similar setup as you, i.e. I have a wireless/Ethernet router hooked up to an iBurst desktop modem. Router's MTU is set to the recommended iBurst setting of 1352.

If I understand it correctly, you also have to set the MTU to 1352 in Windows; see following on how to do that: http://support.microsoft.com/default.aspx?scid=kb;en-us;283165

Then, to test using the ping utility, you have to use a data size of MTU - 28, that is 1324 for testing, NOT the full MTU of 1352. This is because ping adds it's own 28 bytes overhead. See http://support.microsoft.com/kb/159211/

Cheers
 
Thanx, I tried what the link suggested and still same reply when I ping. I also tried it from a pc directly plugged into the router but same result, if i ping with a mtu of around 1320 I start getting a reply but only when I use the pc plugged directly into the router so the problem could also then be in my wireless..hmm
 
Ya,got nod32 installed & tried on vista and xp & same thing
 
I also have the exact same issue when downloading files browsing of any sort grinds to a halt...
 
Top
Sign up to the MyBroadband newsletter
X