I shall.![]()
Thank thee!
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
I shall.![]()
EDIT: Hi guys. Just want to clear a few things up around this, had a chat with our server team - a torrent tracker is active and running on our network. It's something very, very new - and is only there for testing purposes.
I do need to stress though, that logs are purged every 30 mins and is in no way linked to Afrihost clients. It simply announces peers on the Afrihost network to other Afrihost clients. From what I can see too, only uTorrent supports this feature as it actively looks up trackers. You can disable this feature by un-ticking "Local peer discovery".
This is being done to optimise international links and save traffic. This will in no way breach anyones privacy on our network.
Hi guys
Just want to touch on some thing that popped up in the comments on an article last night
Happy to answer any questions around this.
All good in my opinion! We use them anyway, so having one actively optimizing to offer best results really isn't an issue.
Z![]()
Good Day,
Having regular bursts of high latency that is preventing voip from working properly at home. I am not seeing errors on the line, in durban.
Mode: ADSL_2plus
Type: ATM
Status: Up
Downstream Upstream
Line Coding(Trellis): On On
SNR Margin (dB): 125 122
Attenuation (dB): 65 50
Output Power (dBm): -170 120
Attainable Rate (Kbps): 27696 1296
Rate (Kbps): 10239 1021
D (interleaver depth): 1 1
Delay (msec): 0.19 0.24
HEC Errors: 0 0
OCD Errors: 0 0
LCD Errors: 0 0
Total ES: 0 0
-snip
Very up and down results here
Can run a ping.afrihost.com please?
Looks like the latency is coming in at the exchange.
Hi guys
Just want to touch on some thing that popped up in the comments on an article last night
Happy to answer any questions around this.
Here you go, as you can see the next hop is the big problem. I am going to try a Telkom ADSL account soon to rule that out.
64 bytes from 41.181.185.18: icmp_seq=644 ttl=51 time=20.932 ms
64 bytes from 41.181.185.18: icmp_seq=645 ttl=52 time=21.051 ms
64 bytes from 41.181.185.18: icmp_seq=646 ttl=51 time=20.696 ms
64 bytes from 41.181.185.18: icmp_seq=647 ttl=51 time=20.393 ms
64 bytes from 41.181.185.18: icmp_seq=648 ttl=52 time=20.367 ms
64 bytes from 41.181.185.18: icmp_seq=649 ttl=51 time=20.406 ms
64 bytes from 41.181.185.18: icmp_seq=650 ttl=51 time=21.714 ms
64 bytes from 41.181.185.18: icmp_seq=651 ttl=51 time=21.150 ms
64 bytes from 41.181.185.18: icmp_seq=652 ttl=52 time=20.443 ms
64 bytes from 41.181.185.18: icmp_seq=653 ttl=51 time=20.949 ms
64 bytes from 41.181.185.18: icmp_seq=654 ttl=52 time=132.167 ms
64 bytes from 41.181.185.18: icmp_seq=655 ttl=52 time=643.871 ms
64 bytes from 41.181.185.18: icmp_seq=656 ttl=51 time=601.127 ms
64 bytes from 41.181.185.18: icmp_seq=657 ttl=51 time=20.952 ms
64 bytes from 41.181.185.18: icmp_seq=658 ttl=51 time=924.458 ms
64 bytes from 41.181.185.18: icmp_seq=659 ttl=51 time=2398.657 ms
64 bytes from 41.181.185.18: icmp_seq=660 ttl=51 time=2684.757 ms
64 bytes from 41.181.185.18: icmp_seq=661 ttl=52 time=1733.142 ms
64 bytes from 41.181.185.18: icmp_seq=662 ttl=51 time=781.474 ms
64 bytes from 41.181.185.18: icmp_seq=663 ttl=52 time=84.370 ms
64 bytes from 41.181.185.18: icmp_seq=664 ttl=51 time=20.407 ms
64 bytes from 41.181.185.18: icmp_seq=665 ttl=51 time=20.405 ms
64 bytes from 41.181.185.18: icmp_seq=666 ttl=52 time=21.118 ms
64 bytes from 41.181.185.18: icmp_seq=667 ttl=52 time=20.801 ms
64 bytes from 41.181.185.18: icmp_seq=668 ttl=51 time=1646.823 ms
64 bytes from 41.181.185.18: icmp_seq=669 ttl=51 time=2494.961 ms
64 bytes from 41.181.185.18: icmp_seq=670 ttl=51 time=1531.418 ms
64 bytes from 41.181.185.18: icmp_seq=671 ttl=51 time=538.341 ms
64 bytes from 41.181.185.18: icmp_seq=672 ttl=51 time=21.448 ms
64 bytes from 41.181.185.18: icmp_seq=673 ttl=51 time=20.619 ms
64 bytes from 41.181.185.18: icmp_seq=674 ttl=51 time=21.030 ms
64 bytes from 41.181.185.18: icmp_seq=675 ttl=51 time=20.476 ms
64 bytes from 41.181.185.18: icmp_seq=676 ttl=51 time=20.932 ms
64 bytes from 41.181.185.18: icmp_seq=677 ttl=51 time=21.048 ms
64 bytes from 41.181.185.18: icmp_seq=678 ttl=52 time=20.787 ms
64 bytes from 41.181.185.18: icmp_seq=679 ttl=52 time=1441.974 ms
64 bytes from 41.181.185.18: icmp_seq=680 ttl=52 time=2440.992 ms
64 bytes from 41.181.185.18: icmp_seq=681 ttl=51 time=2012.567 ms
64 bytes from 41.181.185.18: icmp_seq=682 ttl=52 time=1056.319 ms
64 bytes from 41.181.185.18: icmp_seq=683 ttl=51 time=100.232 ms
64 bytes from 41.181.185.18: icmp_seq=684 ttl=51 time=21.936 ms
64 bytes from 41.181.185.18: icmp_seq=685 ttl=52 time=20.778 ms
64 bytes from 41.181.185.18: icmp_seq=686 ttl=52 time=23.807 ms
64 bytes from 41.181.185.18: icmp_seq=687 ttl=51 time=20.872 ms
64 bytes from 41.181.185.18: icmp_seq=688 ttl=52 time=21.100 ms
64 bytes from 41.181.185.18: icmp_seq=689 ttl=52 time=29.605 ms
64 bytes from 41.181.185.18: icmp_seq=690 ttl=51 time=20.631 ms
64 bytes from 41.181.185.18: icmp_seq=691 ttl=52 time=1761.322 ms
64 bytes from 41.181.185.18: icmp_seq=692 ttl=51 time=2687.065 ms
64 bytes from 41.181.185.18: icmp_seq=693 ttl=52 time=1701.615 ms
64 bytes from 41.181.185.18: icmp_seq=694 ttl=51 time=725.644 ms
64 bytes from 41.181.185.18: icmp_seq=695 ttl=52 time=20.756 ms
64 bytes from 41.181.185.18: icmp_seq=696 ttl=51 time=20.815 ms
64 bytes from 41.181.185.18: icmp_seq=697 ttl=52 time=22.106 ms
64 bytes from 41.181.185.18: icmp_seq=698 ttl=52 time=46.502 ms
64 bytes from 41.181.185.18: icmp_seq=699 ttl=51 time=26.961 ms
64 bytes from 41.181.185.18: icmp_seq=700 ttl=51 time=22.774 ms
64 bytes from 41.181.185.18: icmp_seq=701 ttl=52 time=20.664 ms
64 bytes from 41.181.185.18: icmp_seq=702 ttl=51 time=26.878 ms
64 bytes from 41.181.185.18: icmp_seq=703 ttl=51 time=1794.122 ms
64 bytes from 41.181.185.18: icmp_seq=704 ttl=51 time=2690.715 ms
64 bytes from 41.181.185.18: icmp_seq=705 ttl=52 time=1723.318 ms
64 bytes from 41.181.185.18: icmp_seq=706 ttl=52 time=750.861 ms
64 bytes from 41.181.185.18: icmp_seq=707 ttl=51 time=20.423 ms
64 bytes from 41.181.185.18: icmp_seq=708 ttl=51 time=20.560 ms
64 bytes from 41.181.185.18: icmp_seq=709 ttl=51 time=20.877 ms
64 bytes from 41.181.185.18: icmp_seq=710 ttl=51 time=20.900 ms
64 bytes from 41.181.185.18: icmp_seq=711 ttl=51 time=20.967 ms
64 bytes from 41.181.185.18: icmp_seq=712 ttl=51 time=21.324 ms
64 bytes from 41.181.185.18: icmp_seq=713 ttl=52 time=20.649 ms
64 bytes from 41.181.185.18: icmp_seq=714 ttl=52 time=20.853 ms
64 bytes from 41.181.185.18: icmp_seq=715 ttl=52 time=21.309 ms
64 bytes from 41.181.185.18: icmp_seq=716 ttl=52 time=21.011 ms
64 bytes from 41.181.185.18: icmp_seq=717 ttl=51 time=20.884 ms
64 bytes from 41.181.185.18: icmp_seq=718 ttl=52 time=21.004 ms
64 bytes from 41.181.185.18: icmp_seq=719 ttl=52 time=23.259 ms
64 bytes from 41.181.185.18: icmp_seq=720 ttl=52 time=20.899 ms
64 bytes from 41.181.185.18: icmp_seq=721 ttl=51 time=20.564 ms
64 bytes from 41.181.185.18: icmp_seq=722 ttl=52 time=20.735 ms
64 bytes from 41.181.185.18: icmp_seq=723 ttl=52 time=20.718 ms
64 bytes from 41.181.185.18: icmp_seq=724 ttl=52 time=21.116 ms
64 bytes from 41.181.185.18: icmp_seq=725 ttl=51 time=20.826 ms
64 bytes from 41.181.185.18: icmp_seq=726 ttl=52 time=20.950 ms
64 bytes from 41.181.185.18: icmp_seq=727 ttl=52 time=21.082 ms
64 bytes from 41.181.185.18: icmp_seq=728 ttl=51 time=20.752 ms
192.168.10.1 0.0% 731 1.2 1.8 1.1 44.8 2.6
2. 169-0-56-1.ip.afrihost.co.za 0.4% 731 3325. 562.8 7.4 3986. 1025.
3. dbn-up1.ip.adsl.co.za 28.7% 730 24355 24525 22747 28330 992.7
4. dbn-up2.ip.adsl.co.za 0.4% 730 3327. 563.2 9.5 3967. 1021.
5. dbn-in1.ip.adsl.co.za 0.5% 730 3344. 569.5 9.1 4008. 1027.
6. 41.162.84.192 0.5% 730 3358. 568.5 9.4 3968. 1029.
7. 172.18.1.162 0.4% 730 3355. 575.8 17.5 3991. 1030.
8. mtnns-2.jinx.net.za 0.4% 730 3372. 580.9 20.1 4008. 1029.
9. jh-cr-1.za-jh-pr-1.za-a.mtnns.net 0.5% 730 3395. 622.6 20.3 3996. 1029.
10. jh-dca-1.za--jh-cr-1.za-a.mtnns.net 0.7% 730 3349. 588.8 20.1 4045. 1038.
I do find this a bit worrying, as I do game beta testing, most of the updates are large and the developers use P2P to send updates. Last night P2P was bad but no tests showed any problems.
This doesn't have a negative affect on P2P though, and is specific to torrents.
The tracker simply announces itself, improving peer announcements across the network.
Ok, P2P was awful last night, was going through the tests you sent me but none showed any errors. One good thing, my Windows 10 machines updated fast, first timeand it was the big Windows 10 November update
Hi guys
Seen a few queries around P2P not being that hot. For those seeing issues with P2P, please paste the following info so we can nail this trend down.
Location
Account type
Business optimisation on/ off if you're on Business Uncapped
Local speedtest
International speedtest
Torrent speed on http://releases.ubuntu.com/14.04.3/ubuntu-14.04.3-server-amd64.iso.torrent
HTTP speeds on http://releases.ubuntu.com/14.04.3/ubuntu-14.04.3-desktop-amd64.iso
FTP speeds on ftp://ubuntu.mirror.ac.za/ubuntu-release/14.04.3/ubuntu-14.04.3-server-amd64.iso
You obviously don't have to download everything, just let it run for a few mins
This should help narrow down issues.
Thanks guys!
Bittorrent tracker:
Please note this is Still in Beta.
The purpose of a bittorrent tracker is to allow peers to find other peers that are participating in a torrent. The tracker presents a list of peers that have chosen to announce a particular hash to it. The tracker does not have any insight into the nature of the data that it is handling, but only provides a meeting point for peers. We are running a local bittorrent tracker as a technical measure to introduce bittorrent users on our network to nearby peers that are sharing the content that they are downloading. This encourages efficiency and moves a small amount of traffic away from long-haul links to faster local links. This tracker is made available to bittorrent software on the network with Local Peer Discovery, as per BEP 0022.
If you want to ensure that you use the tracker to improve the bittorrent experience, and share content with other users on the local network, you should check that "Local Peer Discovery" is enabled on your bittorrent software. In most bittorrent software Local Peer Discovery is enabled by default.
The tracker we are running has the following features:
* it is restricted to local network users. If we do not restrict access in this way, the benefit of discovering local users is diluted
* it is running standard tracker software on a regular web server
* for each peer, the peer data is the port and info_hashes
* peer data is considered fresh for 30 minutes and then discarded
* we have disabled request logging for reasons of efficiency (which has the side effect of improving privacy)
Reference information:
* http://bittorrent.org/beps/bep_0022.html
* https://en.wikipedia.org/wiki/BitTorrent_tracker
Bras does not respond to ICMP requests.
Bras does not respond to ICMP requests.
Hhhmm.
Try ping 155.239.255.250
Or Zertop's tool![]()
Ok I'm on the same line as junwin. Check this out:
media@mediapc:~$ ping bras.afrihost.com
PING bras.afrihost.com (155.239.255.250) 56(84) bytes of data.
--- bras.afrihost.com ping statistics ---
1724 packets transmitted, 0 received, 100% packet loss, time 1725071ms
media@mediapc:~$ traceroute bras.afrihost.com
traceroute to bras.afrihost.com (155.239.255.250), 30 hops max, 60 byte packets
1 192.168.10.1 (192.168.10.1) 0.652 ms 0.912 ms 0.900 ms
2 169-0-56-1.ip.afrihost.co.za (169.0.56.1) 7.554 ms 9.067 ms 10.435 ms
3 * * *
4 dbn-up2.ip.adsl.co.za (169.1.5.162) 18.628 ms 18.627 ms 19.484 ms
5 dbn-in1.ip.adsl.co.za (169.1.5.204) 21.477 ms 22.408 ms 23.365 ms
6 41.162.84.192 (41.162.84.192) 24.875 ms 9.383 ms 10.024 ms
7 172.18.1.162 (172.18.1.162) 19.562 ms 20.745 ms 21.715 ms
8 41.160.2.69 (41.160.2.69) 23.703 ms 24.645 ms 25.853 ms
9 rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za (196.43.25.137) 27.114 ms 28.342 ms 29.312 ms
10 * * *
11 * * *
12 * * *
I noticed recently we were never able to ping bras.afrihost.com that everyone seemed to be sharing results on, but didn't think anything of it. Strange, yes?
Ok I'm on the same line as junwin. Check this out:
media@mediapc:~$ ping bras.afrihost.com
PING bras.afrihost.com (155.239.255.250) 56(84) bytes of data.
--- bras.afrihost.com ping statistics ---
1724 packets transmitted, 0 received, 100% packet loss, time 1725071ms
media@mediapc:~$ traceroute bras.afrihost.com
traceroute to bras.afrihost.com (155.239.255.250), 30 hops max, 60 byte packets
1 192.168.10.1 (192.168.10.1) 0.652 ms 0.912 ms 0.900 ms
2 169-0-56-1.ip.afrihost.co.za (169.0.56.1) 7.554 ms 9.067 ms 10.435 ms
3 * * *
4 dbn-up2.ip.adsl.co.za (169.1.5.162) 18.628 ms 18.627 ms 19.484 ms
5 dbn-in1.ip.adsl.co.za (169.1.5.204) 21.477 ms 22.408 ms 23.365 ms
6 41.162.84.192 (41.162.84.192) 24.875 ms 9.383 ms 10.024 ms
7 172.18.1.162 (172.18.1.162) 19.562 ms 20.745 ms 21.715 ms
8 41.160.2.69 (41.160.2.69) 23.703 ms 24.645 ms 25.853 ms
9 rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za (196.43.25.137) 27.114 ms 28.342 ms 29.312 ms
10 * * *
11 * * *
12 * * *
I noticed recently we were never able to ping bras.afrihost.com that everyone seemed to be sharing results on, but didn't think anything of it. Strange, yes?