MWEB Uncapped ADSL - Official Q & A

Status
Not open for further replies.
<snip>

16 * 80-239-182-6.customer.teliacarrier.com [80.239.182.6] reports: Destination net unreachable.

Trace complete.

Its so bad! Why mweb, WHY!?

Not sure if it will help, but someone (forgot who) suggested in an earlier post that I restart my router to improve my (local) ping results. Worked for me.
 
@SabreWolfy - Agreed, I will certainly monitor it over a longer period before I decide which service is best... Just surprised that so far Afrihost is the clear winner, currently getting full 512kbps from Afrihost and at best 384kbps from Mweb and its now 1:30am in the morning. Surely out of priority shaping?!?

@D34M0n7 - lets hope we made the right decision :) I will keep an eye on it and let you all know which is the more consistent of the two, well for me anyhow.
 
MWEB

What static DNS should I have in my router.(Linksys WAG160N)
I was using the google ones(8.8.8.8/8.8.4.4) but they were slow.

I have set it to autodetect but nothing appears in my router and its affecting my browsing.
Thanks

PS I would prefer a local one to use all the stuff on the AKAIMAI mirrors and such
 
Tracing route to 80-239-181-76.customer.teliacarrier.com [80.239.181.76]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.0.1]
2 601 ms 303 ms 352 ms 41-132-30-1.dsl.mweb.co.za [41.132.30.1]
3 311 ms 184 ms 375 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]

<<snip>>

Its so bad! Why mweb, WHY!?

Not sure if it will help, but someone (forgot who) suggested in an earlier post that I restart my router to improve my (local) ping results. Worked for me.

Duh, the first 2 hops on tracert tells you that your router or ADSL line is clogged up, so rebooting is the obvious answer!

The first 2-3 hops should never exceed 10ms (30ms for CT MWeb users). If you check the ADSL line statistics the CRC errors are probably in the tens of thousands to get those poor ping times.

I should have figured that, but I was thinking you were doing other downloads or something. Definitely not an upstream MWeb problem...
 
Last edited:
MWEB

What static DNS should I have in my router.(Linksys WAG160N)
I was using the google ones(8.8.8.8/8.8.4.4) but they were slow.

I have set it to autodetect but nothing appears in my router and its affecting my browsing.
Thanks

PS I would prefer a local one to use all the stuff on the AKAIMAI mirrors and such


I see my router picks up the following two dns server from mweb... latency much better than google dns servers.

196.28.80.140
196.28.80.139
 
Downloads Stall

Reposting to see if anyone has any suggestions.

Podcast mp3s downloaded from two different computers over the last two or three days via HTTP from local and international sites run at maximum speed (38Kbps) for some time (say 70% or 90%) and then just stall to 0Kbps but don't time out.

I've tried downloading with wget and via Firefox -- same problem. I've restarted both machines and my router. I tried downloading a .deb file and it too stalled after 2MB, but it resumed after wget reported "Connection reset by peer". I could usually resume broken downloads. If I try to now, wget just hangs trying to connect to the HTTP site. I've actually watched the download stall many times to see what happens -- the download speed just drops from 38Kbps to 0 in a matter of 1 or 2 seconds. I've tried downloading with the "no-cache", but this had no effect.

Browsing and email and YouTube "streaming" seem to be fine.

Effectively I'm no longer able to download anything. I've used 6.5GB this month. I'm seriously confused on this one.
 
Thanks I've put it in, lets see what happens:)
2 more questions. What range ip address should i be getting. Mweb is in the 196xxxx... range if i remember correctly.
And what router would you recommend to set up a a decent wifi network at home. The range should hopefully be between between 12m and 25m but there are a few falls and such between. I know netgear has some good routers. Is there anything else that i should look out for. Just need the routing part, already have a modem.

Thanks
 
Thanks I've put it in, lets see what happens:)
2 more questions. What range ip address should i be getting. Mweb is in the 196xxxx... range if i remember correctly.
And what router would you recommend to set up a a decent wifi network at home. The range should hopefully be between between 12m and 25m but there are a few falls and such between. I know netgear has some good routers. Is there anything else that i should look out for. Just need the routing part, already have a modem.

Thanks

MWeb.co.za is 196.XXX, but your own ADSL IP gateway should be 41.13X.XX. (SAIX/Telkom uses 41.24X.XX)

A bit off off topic: Your home network will be inside the router firewall, so the ISP is irrelevant. Most ADSL modem/routers should have a DHCP function to allocate local addresses (subnets/masks), typically 192.168.XX.

I see my router picks up the following two dns server from mweb... latency much better than google dns servers.

196.28.80.140
196.28.80.139

A tracert from Cape Town to google is 16 hops (300ms), so using that DNS makes no sense (as long as the MWeb DNS is working properly).
 
Last edited:
Thanks I've put it in, lets see what happens:)
2 more questions. What range ip address should i be getting. Mweb is in the 196xxxx... range if i remember correctly.
And what router would you recommend to set up a a decent wifi network at home. The range should hopefully be between between 12m and 25m but there are a few falls and such between. I know netgear has some good routers. Is there anything else that i should look out for. Just need the routing part, already have a modem.

Thanks

Here is a tracert to google.co.za on the 196.28.80.140 DNS
looks like there is a problem somewhere. notably the 7th and 15th hop. any ideas. Browsing has become a pain
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

tracert google.co.za

Tracing route to google.co.za [209.85.229.104]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 9 ms 11 ms 41-132-16-1.dsl.mweb.co.za [41.132.16.1]
3 10 ms 10 ms 10 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
4 11 ms 10 ms 10 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 41 ms 53 ms 40 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 30 ms 26 ms 28 ms tengig-0-2-0-0.mid-1.mweb.co.za [196.22.169.219]

7 272 ms 271 ms 272 ms ap2522-1-s7-smg.mweb.net [196.22.163.230]
8 267 ms 265 ms 269 ms 130.117.136.1
9 273 ms 261 ms 256 ms te1-2.ccr02.lon02.atlas.cogentco.com [130.117.50
.117]
10 265 ms 268 ms 270 ms te7-2.mpd02.lon01.atlas.cogentco.com [130.117.0.
97]
11 277 ms 300 ms 285 ms google.lon01.atlas.cogentco.com [130.117.14.90]

12 274 ms 270 ms 285 ms 64.233.175.25
13 386 ms 325 ms 338 ms 72.14.232.134
14 275 ms 272 ms 273 ms 209.85.252.83
15 * * * Request timed out.
16 319 ms 275 ms 272 ms ww-in-f104.1e100.net [209.85.229.104]

Trace complete.

C:\Documents and Settings\Kids>
 
Last edited:
An update on my 512k account:



:D

Was getting 30 kB/s from Astraweb, getting max speed using Flashget. Don't worry guys (you know who), I haven't forgotten about your PM and will send it today :)
 
Unable to Download

Apologies for cross/re/posting, but this is driving me crazy and I need to determine if anyone else is experiencing this.

Since Wednesday, all mp3 podcast downloads (and other "large" files I think) all stall after several MB at 0kbps and never finish; they all download at 38Kbps until they stall at 0kbps. I've tried on different computers and from different sites; all downloads are standard HTTP, not P2P or torrent or anything like that. I've reset router and restarted computers and called Tech Support who reset the port, checked DNS on router etc.

Browsing, email, streaming is all fine. Any "large" file download just stalls after several MB and cannot be resumed. I download via command-line 'wget' (so no browser cache) but the same problem happens via Firefox. I have no proxies or anti-virus running. Before Wednesday evening, all downloads were running fine. Trying to resume with 'wget' hangs sending the HTTP request, despite the fact that starting the download from scratch works. Sometimes 'wget' reports Connection reset by peer or Connection timed out, despite downloading at 38Kbps.

I've downloaded one of the 'problem' files via my AlwaysOn/MWeb 5 hours wireless access and it downloads to completion so the file itself is fine at the source.

Downloaded a mp3 podcast over an SSH connection works fine -- it downloads to completion.

It seems as though there is something wrong with some transparent HTTP proxy somewhere? Tech support said I was the first call about this issue though...
 
Last edited:
@MWEB: Is there any particular issue in the Durban Area? I am currently getting speedtests of 0.34mbits down to NY on speedtest.net. I have been on the 4meg uncapped option since the day you released it, and this is the first severe degredation of service that i have experienced. I have checked my connection and my line is syncing fine with plenty of noise margin so i can only assume its an MWEB specific issue?
 
I was using the google ones(8.8.8.8/8.8.4.4) but they were slow.

PS I would prefer a local one to use all the stuff on the AKAIMAI mirrors and such
Hi Guantanamo,

One of the reasons you should be using the MWEB DNS servers (auto learnt) is so that you can benefit from locally cached Akamai content e.g. ...

C:\>ping www.nvidia.com

Pinging a1650.g.akamai.net [165.165.39.210] with 32 bytes of data:
Reply from 165.165.39.210: bytes=32 time=21ms TTL=55
Reply from 165.165.39.210: bytes=32 time=18ms TTL=55
Reply from 165.165.39.210: bytes=32 time=20ms TTL=55
Reply from 165.165.39.210: bytes=32 time=22ms TTL=55

MWB.
 
Hi Guantanamo,

One of the reasons you should be using the MWEB DNS servers (auto learnt) is so that you can benefit from locally cached Akamai content e.g. ...

<<snip>>

MWB.

Also NASA!

Code:
ping www.nasa.gov

Pinging a1718.x.akamai.net [165.165.39.200] with 32 bytes of data:

Reply from 165.165.39.200: bytes=32 time=29ms TTL=55
Reply from 165.165.39.200: bytes=32 time=30ms TTL=55
Reply from 165.165.39.200: bytes=32 time=29ms TTL=55
Reply from 165.165.39.200: bytes=32 time=29ms TTL=55
 
Hi MWeb welcome back

I’d like to ask once more:

What do you consider reasonable shaping on non-priority downloads on a 384 connection?
I think we all agree that less than dialup speed is unacceptable. So what should it be?
It’s a fair question from paying customers.

Thanks
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X