MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
ToxicBunny

ToxicBunny

Oi! Leave me out of this...
Joined
Apr 8, 2006
Messages
113,505
Beyond strange....
hmmmm

well its only a minor irritation at this point in time... I'll build my own damn DNS server in the next few weeks, then i shouldn't have any more issues.
 
D

D34M0n7

Executive Member
Joined
Apr 7, 2008
Messages
6,680
ToxicBunny said:
Beyond strange....
hmmmm

well its only a minor irritation at this point in time... I'll build my own damn DNS server in the next few weeks, then i shouldn't have any more issues.
Click to expand...

What I do sometimes, when I can't reboot my router is use Hide my Ass, just google it, its an online proxy. Its a bit slow but it gets the job done when you need it.
 
P

PeterCH

Honorary Master
Joined
Aug 8, 2005
Messages
18,371
D34M0n7 said:
What I do sometimes, when I can't reboot my router is use Hide my Ass, just google it, its an online proxy. Its a bit slow but it gets the job done when you need it.
Click to expand...

Anonymouse is a bit faster i think :)
 
Gordon_R

Gordon_R

Honorary Master
Joined
Jul 5, 2009
Messages
20,817
SabreWolfy said:
I'm in JHB, but MWeb VP node is still 122ms away from me. Should be about 30ms?
Click to expand...

Its possible that MWeb haven't sorted out your area (yet). Make sure its not your router that's at fault (reboot).

Nowhere in SA should have ping times > 50ms, unless the line is congested. Pre-2010 I used to get 8ms ping times on the SAIX backbone (MWeb SMTP mail server).

Code: 
  1  <10 ms  <10 ms  <10 ms  home.gateway [192.168.1.254]
  2    8 ms    8 ms    8 ms  dsl-245-128-01.telkomadsl.co.za [41.245.128.1]
  3    8 ms    8 ms    8 ms  wblv-ip-lir-1-gig-4-0-0.telkom-ipnet.co.za [196.43.8.190]
  4    9 ms    9 ms    8 ms  196.43.25.206
 
Last edited:
D

D34M0n7

Executive Member
Joined
Apr 7, 2008
Messages
6,680
My connection is getting worse xD

1 <1 ms <1 ms <1 ms home.gateway [192.168.0.1]
2 353 ms 344 ms 385 ms 41-132-30-1.dsl.mweb.co.za [41.132.30.1]
3 359 ms 363 ms 388 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 223 ms 173 ms 189 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]

Got no idea why its so high, my exchange is right down the road and all the stuff is new and fast. I'm in constantia park, one of the areas that are going to get 8mb/s pretty soon so one would think that there wouldn't be much congestion. Unless telkom has not worked its routing out properly.

Anyone else in constantia park that can post a trace route?

*EDIT*

I did a trace route to my IP using traceroute.org

traceroute to 41.132.30.114 (41.132.30.114), 20 hops max, 40 byte packets
1 mk2-svr1-vrrp35-32.p.nwu.ac.za (143.160.35.254) 0.552 ms 0.636 ms 0.667 ms
2 mk2-bb2-10gb-1-25-528.p.nwu.ac.za (143.160.130.228) 1.347 ms 2.079 ms 2.813 ms
3 mk2-fwg02-to-bb.p.nwu.ac.za (143.160.131.252) 0.327 ms 0.338 ms 0.370 ms
4 mk1-igs01-eth0.p.nwu.ac.za (143.160.4.1) 0.633 ms 0.687 ms 0.773 ms
5 saix-gw01.p.nwu.ac.za (143.160.3.204) 0.966 ms 0.970 ms 1.001 ms
6 tpr-ip-esr-3-wan.telkom-ipnet.co.za (196.25.250.249) 8.515 ms 8.369 ms 8.006 ms
7 rrba-ip-hsll-1-gig-6-0-8.telkom-ipnet.co.za (196.43.51.170) 9.145 ms 9.124 ms 9.131 ms
8 mweb-gw.telkom-ipnet.co.za (196.25.8.250) 84.891 ms 84.939 ms 84.941 ms
9 vl-12.vic-hscore-2.mweb.co.za (196.22.169.243) 33.041 ms 33.223 ms 33.255 ms
10 tengig-0-0-0-92.vic-ipc-1.mweb.co.za (196.22.189.17) 33.166 ms 33.159 ms 33.183 ms

As you can see on hop 8, as it hits mweb theres an abnormal spike.
 
Last edited:
S

SabreWolfy

Expert Member
Joined
Sep 7, 2009
Messages
2,228
@Gordon_R
Restarted router. Pings still at 122ms so I guess not all areas have been resolved yet.
 
Gordon_R

Gordon_R

Honorary Master
Joined
Jul 5, 2009
Messages
20,817
D34M0n7 said:
My connection is getting worse xD

1 <1 ms <1 ms <1 ms home.gateway [192.168.0.1]
2 353 ms 344 ms 385 ms 41-132-30-1.dsl.mweb.co.za [41.132.30.1]
3 359 ms 363 ms 388 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 223 ms 173 ms 189 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]

Got no idea why its so high, my exchange is right down the road and all the stuff is new and fast. I'm in constantia park, one of the areas that are going to get 8mb/s pretty soon so one would think that there wouldn't be much congestion. Unless telkom has not worked its routing out properly.

Anyone else in constantia park that can post a trace route?
Click to expand...

I think its your line, either bad copper, or the exchange being messed around. Make sure your CRC errors aren't going though the roof, if your modem is not synching properly on ADSL2+.

I can now ping your DSLAM (41.132.30.1) in 30ms flat (from Cape Town!)

SabreWolfy said:
@Gordon_R
Restarted router. Pings still at 122ms so I guess not all areas have been resolved yet.
Click to expand...

Sorry to hear that. I think MWeb bought a big chunk of connectivity on the CT-Jhb leg, but Jhb is a whole different matter (more than one hub, etc).

Tracert should confirm if its the 2nd hop (DSLAM), or 3rd hop (ISP). If I recall, your tracert doesn't show 2nd hop times (weird??)

SabreWolfy said:
Seems to be the case:

Code: 
 2:  home.gateway (192.168.1.254)                           0.519ms pmtu 1492
 2:  *****.dsl.mweb.co.za (*****)             118.932ms 
 3:  tengig-0-0-0-110.vic-ipc-1.mweb.co.za (196.22.169.170) 120.574ms asymm  4
Click to expand...

Edit: Your tracert doesn't show the 2nd hop IP address (TonyA & hambone's tracert don't show 2nd hop IP or time). It does show the 2nd hop times of 120ms. Probably an exchange problem (not MWeb...)
 
Last edited:
C

calvincoetzee

Well-Known Member
Joined
Oct 11, 2008
Messages
318
D34M0n7 said:
My connection is getting worse xD

1 <1 ms <1 ms <1 ms home.gateway [192.168.0.1]
2 353 ms 344 ms 385 ms 41-132-30-1.dsl.mweb.co.za [41.132.30.1]
3 359 ms 363 ms 388 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 223 ms 173 ms 189 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]

Got no idea why its so high, my exchange is right down the road and all the stuff is new and fast. I'm in constantia park, one of the areas that are going to get 8mb/s pretty soon so one would think that there wouldn't be much congestion. Unless telkom has not worked its routing out properly.

Anyone else in constantia park that can post a trace route?

*EDIT*

I did a trace route to my IP using traceroute.org

traceroute to 41.132.30.114 (41.132.30.114), 20 hops max, 40 byte packets
1 mk2-svr1-vrrp35-32.p.nwu.ac.za (143.160.35.254) 0.552 ms 0.636 ms 0.667 ms
2 mk2-bb2-10gb-1-25-528.p.nwu.ac.za (143.160.130.228) 1.347 ms 2.079 ms 2.813 ms
3 mk2-fwg02-to-bb.p.nwu.ac.za (143.160.131.252) 0.327 ms 0.338 ms 0.370 ms
4 mk1-igs01-eth0.p.nwu.ac.za (143.160.4.1) 0.633 ms 0.687 ms 0.773 ms
5 saix-gw01.p.nwu.ac.za (143.160.3.204) 0.966 ms 0.970 ms 1.001 ms
6 tpr-ip-esr-3-wan.telkom-ipnet.co.za (196.25.250.249) 8.515 ms 8.369 ms 8.006 ms
7 rrba-ip-hsll-1-gig-6-0-8.telkom-ipnet.co.za (196.43.51.170) 9.145 ms 9.124 ms 9.131 ms
8 mweb-gw.telkom-ipnet.co.za (196.25.8.250) 84.891 ms 84.939 ms 84.941 ms
9 vl-12.vic-hscore-2.mweb.co.za (196.22.169.243) 33.041 ms 33.223 ms 33.255 ms
10 tengig-0-0-0-92.vic-ipc-1.mweb.co.za (196.22.189.17) 33.166 ms 33.159 ms 33.183 ms

As you can see on hop 8, as it hits mweb theres an abnormal spike.
Click to expand...

hmmmm not cool, but nevermind that, is it working for wow? that's all that matters, even if it's just the logged in screen..
 
S

SabreWolfy

Expert Member
Joined
Sep 7, 2009
Messages
2,228
A tracepath to www.mweb.co.za doesn't finish and is now going via Telkom:

Code: 
 2:  home.gateway (192.168.1.254)                           0.512ms pmtu 1492
 2:  *.dsl.mweb.co.za (*.*.*.*)             118.973ms 
 3:  tengig-0-0-0-100.vic-ipc-2.mweb.co.za (196.22.163.206) 119.776ms asymm  4 
 4:  vl-92.vic-hscore-1.mweb.co.za (196.22.189.2)         118.512ms asymm  5 
 5:  tengig-0-0-0-0-11.vic-up-1.mweb.co.za (196.22.169.225) 163.274ms asymm  6 
 6:  rrba-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.8.249) 126.149ms asymm  7 
 7:  196.43.39.58 (196.43.39.58)                          145.843ms asymm 10 
 8:  tiscali-gw.telkom-ipnet.co.za (196.25.55.178)        148.790ms asymm 10 
 9:  no reply
10:  no reply
11:  no reply
12:  no reply
 
D

D34M0n7

Executive Member
Joined
Apr 7, 2008
Messages
6,680
I'll phone telkom tomorrow and ask for a line reset... sigh, if that doesn't work dunno what I'm gonna do. Don't know how telkom is going to pull off 8mb/s here with this kind of shiz.
 
D

D34M0n7

Executive Member
Joined
Apr 7, 2008
Messages
6,680
calvincoetzee said:
hmmmm not cool, but nevermind that, is it working for wow? that's all that matters, even if it's just the logged in screen..
Click to expand...

+1

I have been there lol, loggin in just to see the screen xD

*EDIT*

OMFG ITS YOU CALVIN!

HELLO! I iz goin to pm chu!
 
Gordon_R

Gordon_R

Honorary Master
Joined
Jul 5, 2009
Messages
20,817
SabreWolfy said:
A tracepath to www.mweb.co.za doesn't finish and is now going via Telkom:

Code: 
 2:  home.gateway (192.168.1.254)                           0.512ms pmtu 1492
 2:  *.dsl.mweb.co.za (*.*.*.*)             118.973ms 
 3:  tengig-0-0-0-100.vic-ipc-2.mweb.co.za (196.22.163.206) 119.776ms asymm  4 
 4:  vl-92.vic-hscore-1.mweb.co.za (196.22.189.2)         118.512ms asymm  5 
 5:  tengig-0-0-0-0-11.vic-up-1.mweb.co.za (196.22.169.225) 163.274ms asymm  6 
 6:  rrba-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.8.249) 126.149ms asymm  7 
 7:  196.43.39.58 (196.43.39.58)                          145.843ms asymm 10 
 8:  tiscali-gw.telkom-ipnet.co.za (196.25.55.178)        148.790ms asymm 10 
 9:  no reply
10:  no reply
11:  no reply
12:  no reply
Click to expand...

That is funny, but not unusual. Mweb.co.za is hosted by MTN Business, so the traffic has to go via Telkom.

The fact that the tracert doesn't finish, is because the site host has turned off ping responses. The website works fine, but is not useful for ping testing. Try mweb.com instead!
 
S

SabreWolfy

Expert Member
Joined
Sep 7, 2009
Messages
2,228
Gordon_R said:
That is funny, but not unusual. Mweb.co.za is hosted by MTN Business, so the traffic has to go via Telkom.

The fact that the tracert doesn't finish, is because the site host has turned off ping responses. The website works fine, but is not useful for ping testing. Try mweb.com instead!
Click to expand...

Ok so MWeb ADSL runs over Seacom for customers but www.mweb.co.za sits on MTN Business/Telkom. mweb.com also doesn't reply. No matter.

Why are pings to www.mweb.co.za ~ 45ms but tracepaths ~ 125ms?
 
Gordon_R

Gordon_R

Honorary Master
Joined
Jul 5, 2009
Messages
20,817
SabreWolfy said:
Ok so MWeb ADSL runs over Seacom for customers but www.mweb.co.za sits on MTN Business/Telkom. mweb.com also doesn't reply. No matter.

Why are pings to www.mweb.co.za ~ 45ms but tracepaths ~ 125ms?
Click to expand...

I don't know how tracepath works for you, proxy perhaps? Routing still seems to be a bit unstable at present.

The MWeb representative said www.dstv.com is a good test, since it is hosted very close to the VIC data center. (I get 28-30ms from Cape Town).

Code: 
Tracing route to www.dstv.com [196.28.65.142]
over a maximum of 30 hops:

  1   <10 ms   <10 ms   <10 ms  home.gateway [192.168.1.254]
  2     8 ms     8 ms     8 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
  3    28 ms    28 ms    30 ms  196.22.169.134
  4    28 ms    28 ms    29 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5    29 ms    30 ms    29 ms  tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.66]
  6    34 ms    30 ms    30 ms  135.75.28.196.netactive.net [196.28.75.135]
  7    30 ms    29 ms    29 ms  192.168.196.17
  8    30 ms    29 ms    30 ms  www.dstv.com [196.28.65.142]

Trace complete.

Edit: As I have noted before, the 'worst' tracert for me is www.iol.co.za, which is hosted by MTN Business, and is located in Cape Town. It takes 14 hops, even though it is located in the same city as me. Despite this, ping times are consistent around 50ms (when the network is not congested).
 
Last edited:
D

D34M0n7

Executive Member
Joined
Apr 7, 2008
Messages
6,680
A trace route to www.dstv.com

1 <1 ms <1 ms <1 ms home.gateway [192.168.0.1]
2 935 ms 1042 ms 962 ms 41-132-30-1.dsl.mweb.co.za [41.132.30.1]
3 818 ms 856 ms 721 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 629 ms 749 ms 829 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]

Its not pretty, is there anyone else in constantia park that can also do a traceroute pls, I need to find out exactly where the problem is before I try call MWEB/Shizkom
 
M

MWEB

Well-Known Member
Joined
Aug 31, 2009
Messages
349
D34M0n7 said:
1 <1 ms <1 ms <1 ms home.gateway [192.168.0.1]
2 353 ms 344 ms 385 ms 41-132-30-1.dsl.mweb.co.za [41.132.30.1]
3 359 ms 363 ms 388 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 223 ms 173 ms 189 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
Click to expand...
Hi D34M0n7,

Definately something amiss here, assuming there was no other backround traffic utilising your line and the line itself is healthy (not running excessive errors).

Some backround technical info first; each (local copper loop) line on the national ADSL access network is connected to a DSLAM located at the closest (local) exchange. All the DSLAMs within the exchanges in a particular region are aggregated to one or more large routers refered to as ESRs (Edge Services Routers). The aggregated traffic from each ESR is then routed between regions to the point of interconnect (IPC links) with the respective ISP and handed over for onward routing to the Internet.

Now for the relevant part; the first hop (after your router) in the above traceroute is the MWEB assigned IP addr for the ESR you use (within the MWEB 'vlan'). Therefore, by virtue of the high latency on this first hop, your issue seems to be occuring before you have even reached the MWEB network (2nd hop).

While the national ADSL access network is beyond our sphere of control, we can certainly bring any issues to Telkom's attention and work with them to resolve. With this in mind can I ask any others experiencing poor overall performance to post/PM me so that we can try to identify any patterns which can be escalate to Telkom. The two important pieces of information would be a traceroute (to say smtp.mweb.co.za) and the first 6 digits of the telephone number associated to your ADSL line.

So D34M0n7, let me see if I can get any more feedback to provide Telkom with a more substantiated case.

EDIT: D34M0n7 see from another post your issues have been resolved by resetting your session. None the less, the request still stands for any others having problems.

MWB.
 
Last edited:
T

Tanya35

Senior Member
Joined
Apr 16, 2010
Messages
717
Tracing route to www.dstv.com [196.28.65.142]
over a maximum of 30 hops:

1 107 ms 123 ms 182 ms 41-132-48-1.dsl.mweb.co.za [41.132.48.1]
2 44 ms 143 ms 354 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.16
9.134]
3 149 ms 109 ms 76 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
4 85 ms 45 ms 57 ms tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.6
6]
5 99 ms 66 ms 41 ms 135.75.28.196.netactive.net [196.28.75.135]
6 88 ms 96 ms 48 ms 192.168.196.17
7 48 ms 78 ms 43 ms CL2www2.m-net.co.za [196.28.65.142]

Trace complete.

Why is there such a high gap between two MWEB servers?
 
Status
Not open for further replies.
Top