Route Sentry Fail

M

MrG

Executive Member
Joined
Feb 12, 2005
Messages
6,007
Reaction score
21
kk Setup:
International: AfriHost IS Capped Account
Local: TelkomInternet Local Only

Cant get to news24.com :( M-Web stuff gotta do with this?
 
Mweb wants open peering. Telkom wants Mweb to pay again for the traffic you have already paid for. Telkom clients could reach news24 locally if Telkom were not so greedy.
 
FlatspinZA said:
Could be something to do with Mweb & Telkom not peering locally anymore?
Click to expand...

Surely that would just mean a delay? I doubt that some websites stop working all together. You can game on sgs just have a higher ping so why would the website be blocked?
 
Because Route sentry is trying to access news24 using your local only account from Telkom. To access news24 from Telkom you need to use international bandwidth.
 
killadoob said:
Surely that would just mean a delay? I doubt that some websites stop working all together. You can game on sgs just have a higher ping so why would the website be blocked?
Click to expand...

The thing is that the route sentry routing tables cannot keep up with all the telscum et al routing shena****ns (probably censored ... she nan iga ns) . It sees news24.com [196.28.41.200] as a local ip and thus routes it via the localonly account. Klaar oor en uit. For me 196.28.41.200 seems to be located on some unpeered network and is thus being routed via the international links. International links being loaded on a capped localonly account leads to ...fail/blocked website.

Although even a tracert to 196.28.41.200 from my webafrica account leads to some interesting pings and results:

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

  1    19 ms    19 ms    19 ms  wblv-ip-esr-3.ipnet.wa.co.za [41.185.83.1]
  2    22 ms    22 ms    19 ms  vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
  3    23 ms    22 ms    23 ms  vl33.er.gw.cpt.za.wa.co.za [41.185.0.30]
  4    22 ms    22 ms    20 ms  upstream.vl102.gw.cpt.za.wa.co.za [196.220.59.23
0]
  5   188 ms   187 ms   188 ms  lon-ip-dir-telecity-pos-1-1-0.telkom-ipnet.co.za
 [196.43.9.50]
  6   190 ms   188 ms   188 ms  45-254-167-89.packetexchange.net [89.167.254.45]

  7   183 ms   181 ms   183 ms  17-255-167-89.packetexchange.net [89.167.255.17]

  8   220 ms   190 ms   192 ms  195.66.226.149
  9   410 ms   410 ms   410 ms  196.22.175.209
 10   416 ms   416 ms   416 ms  tengig-0-0-0-0-41.vic-up-2.mweb.co.za [196.22.16
9.210]
 11   413 ms   414 ms   418 ms  vl-12.vic-hscore-2.mweb.co.za [196.22.169.243]
 12   411 ms   409 ms   474 ms  tengig-3-2.vic-core-sw2.mweb.co.za [196.22.169.7
0]
 13   418 ms   417 ms   416 ms  opt-65-1.optinet.net [196.22.163.22]
 14   409 ms   409 ms   408 ms  200.41.28.196.netactive.net [196.28.41.200]

Trace complete.

89.167.254.45? ... that is in the UK, right? But why?

Could someone please ping News24.com to see if I got the right IP? Am I right in assuming that 196.28.41.200 is a local ip?
 
Non-Mweb-Peering Routes List

To those who are using Route Sentry and are affected by the routing issues experienced by ISPs not peering with Mweb, there are two options I could suggest.

1. Manually update your local routes list (localroutes.dat) with the following list for "non-peering" ISPs http://developers.locality.co.za/routes-nonpeered-rs.txt
2. Switch to Traffic Splitter (which is far more automated than Route Sentry and already includes the list) http://mybroadband.co.za/vb/showthr...-RouteSentry?p=5021553&viewfull=1#post5021553
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X