Does Sentech Use Incoming Satalite

[loosecannon]

I DONT THINK SO ...

http://www.hotlinks.co.uk/traceroute.cgi?host=66.18.82.197
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote">
1 www-gw (217.14.129.1) 0.327 ms 0.262 ms 0.242 ms
2 217.14.130.65 (217.14.130.65) 0.401 ms 0.364 ms 0.350 ms
3 195.66.224.198 (195.66.224.198) 0.733 ms 0.492 ms 0.431 ms
4 core1b-ldn-dock-gi8-0-0-2.rtr.isnet.net (168.209.246.1) 0.777 ms 0.941 ms 0.749 ms
5 168.209.247.157 (168.209.247.157) 0.854 ms 0.713 ms 1.059 ms
6 core1a-ny-se1-1-1.rtr.isnet.net (168.209.100.46) 99.527 ms 100.590 ms 107.401 ms
7 core1c-rba-se12-1-1.rtr.isnet.net (168.209.0.141) 376.234 ms 360.590 ms *
8 isl.nmszone.is.co.za (196.26.0.3) 352.352 ms 365.537 ms 376.650 ms
9 168.209.18.62 (168.209.18.62) 375.610 ms 369.144 ms *
10 66.18.87.251 (66.18.87.251) 395.735 ms 362.228 ms 382.024 ms
11 66.18.67.26 (66.18.67.26) 389.525 ms 362.602 ms *
12 66.18.67.106 (66.18.67.106) 370.796 ms 388.602 ms 378.928 ms
13 66.18.87.50 (66.18.87.50) 377.351 ms 364.452 ms 354.016 ms
14 myw-stp-66-18-82-197.sentechsa.net (66.18.82.197) 847.832 ms 589.659 ms 657.635 ms
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

http://www.mailbox.net.uk/page.php?pid=37/
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote">
traceroute to 66.18.82.197 (66.18.82.197), 30 hops max, 40 byte packets
1 core.lon-th1.mailbox.net.uk (195.82.125.1) 0.58 ms 0.439 ms 0.41 ms
2 bdr2.lon-th1.mailbox.net.uk (195.82.96.228) 1.524 ms 0.69 ms 1.448 ms
3 lvl3gw.thn.packetexchange.net (212.187.197.193) 1.332 ms 1.498 ms 0.951 ms
4 so-1-2-0.gar1.London1.Level3.net (212.113.0.114) 2.2 ms 1.298 ms 1.492 ms
5 ge-1-2.core2.London1.Level3.net (212.187.131.166) 2.17 ms ge-1-1.core2.London1.Level3.net (212.187.131.134) 2.124 ms 2.788 ms
6 POS3-3.BR1.LND9.ALTER.NET (146.188.68.209) 2.056 ms 1.994 ms 3.162 ms
7 so-0-2-0.TR2.LND9.ALTER.NET (146.188.7.245) 2.412 ms 1.721 ms 1.725 ms
8 so-6-1-0.TR1.LND2.ALTER.NET (146.188.4.81) 2.313 ms 2.731 ms 1.968 ms
9 so-5-0-0.XR2.LND2.ALTER.NET (146.188.7.229) 2.358 ms 3.139 ms 2.983 ms
10 pos3-0.cr2.lnd5.gbb.uk.uu.net (158.43.233.245) 4.552 ms 2.869 ms 2.854 ms
11 fe8-0-0.gw13.lnd5.gbb.uk.uu.net (158.43.157.141) 2.085 ms 2.582 ms 2.951 ms
12 Internet-Solutions-gw.customer.ALTER.NET (146.188.58.162) 6.168 ms 6.114 ms 4.847 ms
13 168.209.247.157 (168.209.247.157) 2.78 ms 3.381 ms 4.543 ms
14 core1a-ny-se1-1-1.rtr.isnet.net (168.209.100.46) 103.675 ms 102.87 ms 101.909 ms
15 core1c-rba-se12-1-1.rtr.isnet.net (168.209.0.141) 349.726 ms 349.819 ms 350.813 ms
16 isl.nmszone.is.co.za (196.26.0.3) 338.815 ms 394.297 ms 353.531 ms
17 168.209.18.62 (168.209.18.62) 377.865 ms 372.987 ms 378.492 ms
18 66.18.87.251 (66.18.87.251) 398.292 ms 386.051 ms 384.707 ms
19 66.18.67.26 (66.18.67.26) 398.988 ms 364.639 ms 383.009 ms
20 66.18.67.106 (66.18.67.106) 807.981 ms 385.614 ms 400.507 ms
21 66.18.87.50 (66.18.87.50) 385.813 ms 378.108 ms 377.281 ms
22 myw-stp-66-18-82-197.sentechsa.net (66.18.82.197) 717.824 ms 976.728 ms 677.84 ms
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

http://www.ook.co.uk/cgi-bin/traceroute
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote">
traceroute to myw-stp-66-18-82-197.sentechsa.net (66.18.82.197): 1-30 hops, 38 byte packets
1 hsrp-gw.gloucester.ook.co.uk (212.125.76.254) 1.79 ms 1.10 ms 1.10 ms
2 fe4-2.bar003.star.net.uk (212.125.76.78) 1.28 ms 1.67 ms 1.48 ms
3 lon008-f60.metrocore-vlan51.star.net.uk (212.125.78.146) 6.81 ms (ttl=252!) 6.07 ms (ttl=252!) 6.47 ms (ttl=252!)
4 ge3-0.br1.lnd6.gbb.uk.uu.net (195.66.224.16) 7.96 ms 7.10 ms 6.46 ms
5 srp4-0.cr1.lnd6.uk.gbb.uu.net (158.43.194.233) 7.36 ms (ttl=252!) 7.65 ms (ttl=252!) 7.00 ms (ttl=252!)
6 pos4-0.cr1.lnd5.gbb.uk.uu.net (158.43.253.130) 10.1 ms (ttl=248!) 8.65 ms (ttl=248!) 8.44 ms (ttl=248!)
7 fe0-0-0.gw13.lnd5.gbb.uk.uu.net (158.43.157.13) 8.74 ms (ttl=250!) 8.58 ms (ttl=250!) 8.59 ms (ttl=250!)
8 Internet-Solutions-gw.customer.ALTER.NET (146.188.58.162) 10.4 ms 10.0 ms 9.88 ms
9 168.209.247.157 (168.209.247.157) 11.2 ms (ttl=248!) 11.3 ms (ttl=248!) 11.0 ms (ttl=248!)
10 core1a-ny-se1-1-1.rtr.isnet.net (168.209.100.46) 109 ms (ttl=247!) 108 ms (ttl=247!) 111 ms (ttl=247!)
11 core1c-rba-se12-1-1.rtr.isnet.net (168.209.0.141) 384 ms (ttl=246!) * 383 ms (ttl=246!)
12 196.26.0.3 (196.26.0.3) * 362 ms (ttl=245!) 361 ms (ttl=245!)
13 168.209.18.62 (168.209.18.62) 385 ms (ttl=244!) 376 ms (ttl=244!) 390 ms (ttl=244!)
14 66.18.87.251 (66.18.87.251) 376 ms (ttl=240!) 373 ms (ttl=240!) 389 ms (ttl=240!)
15 66.18.67.26 (66.18.67.26) 379 ms (ttl=48!) * 395 ms (ttl=48!)
16 66.18.67.106 (66.18.67.106) 364 ms (ttl=238!) 583 ms (ttl=238!) 360 ms (ttl=238!)
17 66.18.87.50 (66.18.87.50) 396 ms (ttl=237!) 394 ms (ttl=237!) 371 ms (ttl=237!)
18 myw-stp-66-18-82-197.sentechsa.net (66.18.82.197) 698 ms (ttl=236!) 619 ms (ttl=236!) 769 ms (ttl=236!)
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

http://cgi.cs.wisc.edu/scripts/condor/netmon/traceroute.pl?66.18.82.197
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote">
traceroute to 66.18.82.197 (66.18.82.197) from ns2.acadia.net (142.167.1.1), 40 hops max, 40 byte packets
1 ip142167001252.acadia.net (142.167.1.252) 0.671 ms 0.588 ms 0.493 ms
2 500.Serial3-11.GW8.BOS1.ALTER.NET (63.111.121.197) 8.616 ms 8.640 ms 8.570 ms
3 196.at-1-0-0.CL1.BOS1.ALTER.NET (152.63.25.122) 8.981 ms 9.197 ms 9.110 ms
4 0.so-1-1-0.XL1.NYC4.ALTER.NET (152.63.21.22) 15.314 ms 15.371 ms 15.371 ms
5 0.so-7-0-0.XR3.NYC4.ALTER.NET (152.63.17.30) 15.354 ms 15.814 ms 15.397 ms
6 509.ATM7-0.IG2.NYC4.ALTER.NET (152.63.22.1) 15.661 ms 15.485 ms 15.754 ms
7 iscoza-oc3-gw.customer.alter.net (208.192.177.206) 204.590 ms 195.259 ms 198.377 ms
8 168.209.247.30 (168.209.247.30) 18.134 ms 18.199 ms 17.023 ms
9 core2b-rba-se12-1-0.rtr.isnet.net (168.209.0.85) 291.197 ms * 294.925 ms
10 isl.nmszone.is.co.za (196.26.0.3) 292.945 ms 289.333 ms 293.222 ms
11 168.209.18.62 (168.209.18.62) 288.872 ms 287.781 ms 295.834 ms
12 66.18.87.251 (66.18.87.251) 303.542 ms 289.684 ms 302.021 ms
13 66.18.67.26 (66.18.67.26) 294.947 ms 290.113 ms 312.517 ms
14 66.18.67.106 (66.18.67.106) 297.395 ms * 303.055 ms
15 66.18.87.50 (66.18.87.50) 304.891 ms 279.801 ms 297.143 ms
16 myw-stp-66-18-82-197.sentechsa.net (66.18.82.197) 456.377 ms 685.568 ms 496.010 ms
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

 

[regardtv]

I have done quite a few tests along similar lines ....

Problem is that protocol routing could be comming into play. If I ran an ISP and had no scruples I'd run my ICMP/UDP traceroute/ping traffic via the cable and move bulk traffic over the satellite....

This would imply planning and foresight to achieve this approach....As Sentech have been doing the satellite return path thingy for a while .. this may well be the case.

Some straight answers on this one would be nice...

 

[loosecannon]

i think you could be wrong here for a couple simple reason ...

1)this type of routing gets done with BGP and BGP is not protocol dependant [yes you can remap protocols but this is not carried by BGP]
2)to do this protocol rerouting the equipment at the satalite transmiter must have a route map ... as they claim BT is the uplink provider all traffic must go VIA UK/BT this is not apparent
3)what is possible is if IS is better peered at a point than Sentechs provider ie fewer hops ... AS prepending will circumvebt this and is unlikely in most cases ... and the one route above shows this unlikely .... concidering it was a UK based route and did not go via the magic satalite provider there is no proof of this ...

 

[regardtv]

I agree cannon ... but if you use one primary BGP peer and then make a routing decision AFTER that router the above is feasible.

Also, it may be that a "proxy" address is specified as the source address. The data heading for that source/dst address is then routed via the satellite. Sentech can make the routing decision locally in that case. As I recall this is somewhat along the lines of what they do for the Infosat/mweb sat service.

 

[loosecannon]

doing it on a session scheme makes no sense remember siyanda/infosat had large amounts of bandwidth to there proxy and the IP need not have been externaly routed so the send out via link recive VIA sat worked very well and would only work this way but incoming via satalite will not be able to work in the same way where the endpoint is not local

as satalite BW will be the cheaper (by far) sentech will have set it up to be used as much as possible ... and traceroutes will deffinately show this up ...

how will a server in the states know this session must be routed via satalite or not ... he will send all traffic following routing paths pre determined ... the traffic will need to come to a router that will pass the traffic either via satalite or via copper ... there is also no proof of this conciderig BT was quoted as uplink i dont see this happening as there would need to be a router with a link to BT and IS at some point and this router will be advertising there AS i just dont see it and why go to the expense of setting this router up ... overseas when it costs more for the copper anyway ...

the uplink for siyanda/infosat was in south africa in the same server room as the copper so this was possible ... ... SPI and the like became practical

to save money you would want p2p and the like to run on the cheeper link in this case satalite ... if all they doing is what siyanda/infosat did the only BW via satalite will be web traffic ... this does not make sense and would love it cleared up ...

or am i missing somthing ...

 

[regardtv]

I hope you're right and I'm wrong ... but if that's the case one question BEGS to be asked ... where IS all this amazing satellite bandwidth then ?

 

[dbnnet]

Of one thing I know for sure... MW is NOT using Sentech's satellite infrastructure.
I seem to recall that basically ALL their satellite infrastructure was being
used for their commercial Corporate and Government(education) customers.


<font size="1"><font color="black">Bay of Plenty :</font id="black"><font color="blue"> Signal 48% - SNL 17 - ber 71% :</font id="blue"><font color="green"> D-Link DI-604 - PPPoE :</font id="green"><font color="orange"> 8dBi Patch Antenna :</font id="orange"> Firmware 5.0.1.60</font id="size1">

 

[regardtv]

Just remember to differentiate between their local downlink offerings and their international backhaul sat services ....

Guess the spewing of BS (by Sentech) should not be a surprise at all.

 

[Luke7777]

dbnnet :
and, I suppose, a little bit for their residential ex-infosat customers (like me)

128K|21%|13SNL|36 Menlopark 2530

 

[dbnnet]

Luke7+ .... I'm not too sure about that anymore. (It was the case yes)!
When I last heard... they were all suffering like the rest of us
on the IS backbone. ????

<font size="1"><font color="black">Bay of Plenty :</font id="black"><font color="blue"> Signal 48% - SNL 17 - ber 71% :</font id="blue"><font color="green"> D-Link DI-604 - PPPoE :</font id="green"><font color="orange"> 8dBi Patch Antenna :</font id="orange"> Firmware 5.0.1.60</font id="size1">

 

[Luke7777]

Could very well be. I think the only SAT comms currently is between MW and my dish via their VPN connection. Since it's not too stable (drops often) when used in conjunction with MyWi, I haven't used it for a while. Since the "move" to MW, I've never seen the 1mb+ bursts during quiet hours as I did with Infosat, but could still have 16 d/l coming in at an acceptable rate (200-300kb total)

128K|21%|13SNL|36 Menlopark 2530