Afrihost - Pure Fibre Feedback Thread

Status
Not open for further replies.
Hey guys

Sorry I've been AWOL for a couple of days, been hitting the books (though I think these books hit back!)

Gonna answer as much as I can. If I miss anything (or skip a post I think may no longer be relevant) please PM me so I can make sure I help out.
 
@AfriMan does AH plan on offering the connection speed combos for OpenServe that MWEB is currently offering?

The 40/10 and 100/20 combos are quite nice options.

I'm not aware of any new products for the moment - I guess it really depends on our Fibre Ops team letting us know that there is a lot of demand for those products. Will certainly mention it next time I have a chance.
 
@AfriMan

I downgraded to 100/100 on the 15th of October. My line's still at 200/200 and my AH clientzone says the package is 200/200. I don't know if it just hasn't been actioned yet or what, but I don't want to be billed for 200/200 when I downgraded in time.

Yo, thought for some reason we chatted about this on PM, but was chatting to someone else about a similar issue.

Please PM me about this. We may have had an issue submitting the downgrade to the provider, but that's on our side and we need to fix.
 
No internet since yesterday afternoon TTConnect Bedfordview area.
Network status page didn't indicate any maintenance / outages.

Please drop me a PM so I can ensure that we've logged a fault for you and check for any progress for you :(
 
Correct, Openserve. Just resent request to release the line. I will also get hold of AH to send me the details as soon as possible to try your suggestion. Thank you.

No issues with you using your Afrihost PPPoE details - just bear in mind that when we see you on the network we "Activate" your package and billing. So if you're cool with that :)

Give me a shout if you need me to follow up on anything :)
 
I followed the WA support staffs guide and uploaded the firmware from the .co.za site and it said invalid firmware. The point was not how smart I am but rather that their support should know giving out Russian DIR-825s that the co.za firmware doesn't work.

At least you got *a* quip in about how smart -you- are. :)

[edit] https://prnt.sc/pq7nav -- there's me being a real smart ass, getting kicks out of being the brainy one, nothing to do with trying to point out to AH that they have the wrong info of course.

ftp://ftp.d-link.co.za/DIR/dir825%20(new)/firmware/G1_BlueWhiteGui/ welcome to show me where the RevR1 russian firmware is on that link

Just a little concerned about different firmware versions running around. Our routers are manufactured to order in Russia for this region, so whatever firmware they pull automatically should be the correct firmware.

Latest routers should be on v1.0.0 and older models on v3.0.6
 
2 month's in and still very happy with my move, I saw my old isp brought their prices more in line with some of the other Openserve providers recently and even with that I have zero desire to move back to them. :)

My line has been for the most part flawless and while I'm not a heavy downloader, it's reallllly nice to have the extra speed when you need to do an update or want to watch something.

That said, I do have one or two queries @AfriMan

Firstly, is it possible Openserve is throttling international downloads? I've noticed this on a couple of occasions lately when updating games which I assume have their patches served from international servers.

For example, I am busy updating Battlefield V at the moment, on a 100mb line it starts at around 12MB/s which is correct, however halfway through and its down to 6MB/s, almost exactly half... if I pause and resume it goes back up to 12MB/s and then slowly drops back down to 6MB/s.. hmm.

Almost exactly the same thing happened when I reinstalled Rainbow Six Siege, which suggests to me that it's not a line issue or a server issue, but rather that the line is being artificially limited... if I immediately switch to a download served from local servers, IE from Steam (JHB/CPT), I get the full line speed for the duration of the download.

Secondly, on the whole topic of routing and online games, I know you must be sick of these already and I know you guys are working on it, but is there any way it could be stressed to whoever does the routing through Europe that even though on paper 20-30ms is a very insignificant number, in practice, when you are already pushing the limits by playing on international servers, 20-30ms is a huge number that is definitely noticeable.

Throw into that random packet loss or other players with spotty connections and a game quickly goes from enjoyable to unplayable.

With my old ISP thew best ping I could get to Rainbow Six servers in London was around 190ms, now with Afrihost, I'm averaging around 160ms, so using that as an example, the difference is literally night and day.

While I'm sure Ubisoft has made netcode improvements since I last played, at 160ms the game is highly playable to me and if I didn't know I was on an EU server it would be hard for me to tell.

Contrast that to another game I play with servers in Amsterdam, which I used to get a ping of around 160ms to, I now average 220ms... I tried it over the weekend, it was awful, I'm not exaggerating when I say I needed to lead targets a full bodies width at point-blank range to get hit markers and even then, with a weapon that's usually a 3 hit kill, I had to use an entire magazine to get the kill because 90% of shot's didn't register...

A similar thing happens in Overwatch, where with hitscan heroes I can see my aim is solid, but the shot's get dusted and enemies take no damage.

I'm not sure if you've ever seen any of the Battle(non)sense netcode video's on youtube, but he explains perfectly in one of his videos, how for example, Battlefield doesn't allow shot's coming from a user with very high ping, the difference between a shot being counted and disallowed, for local players can sometimes be just 20 or 30ms.

I love you guy's, Im not going anywhere, but please, as someone who use's their line mostly for gaming, better routing would be a huge improvement, even if it's just prioritizing routing of game traffic, I don't mind waiting an extra 20ms for my Netflix movie to load. Thanks in advance :)

Really appreciate this heartfelt message and the detail you've gone into - I promise it's very much appreciated on all fronts.

I don't think it's a question of our network people not thinking this is a significant latency different - we have many gamers in the team. I think it's about trying to achieve those improvements without having to significantly alter our network routing - which would be a major infrastructure overhaul and possible affect other services that are now working perfectly. I said in the beginning it could take time, becuase I'm pretty sure we're looking at any possible options available right now.

With regard to throttling, I am pretty confident that Openserve is not doing this. It would be fairly complex to do anyway, but I don't think it's in anyone's best interests. BUt remember that Openserve uses PPPoE and not DHCP, so our traffic has to go through all their local points of presence to IPC (much like ADSL) before we route that traffic locally or internationally. We would need to run some tests to see if local congestion or demand might be affecting performance.

It's also possible that the overseas server may manage downloads.

We'd have to do some testing and troubleshooting to see what could be happening.
 
I'm not aware of any new products for the moment - I guess it really depends on our Fibre Ops team letting us know that there is a lot of demand for those products. Will certainly mention it next time I have a chance.
Maybe AH should have a poll?
 
Me in 8 days:

3a46a17397.png


Afrihost:

736515
 
I don't think it's a question of our network people not thinking this is a significant latency different - we have many gamers in the team. I think it's about trying to achieve those improvements without having to significantly alter our network routing

I don't really understand how it all works internally, but there are instances where the routing does go via london outbound, to say amsterdam, but then it returns via the east coast (its asymmetric). Surely that wouldn't require a major overhaul to change?

Code:
E.g. Routing to blizzard eu
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |   28 |   28 |    0 |    0 |    1 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   cpt-rx2.ip.adsl.co.za -    0 |   28 |   28 |    3 |    3 |   13 |    3 |
|                  cpt-net1.ip.adsl.co.za -    0 |   28 |   28 |    2 |    2 |    4 |    3 |
|     be-22.lza-pe1-cpt.liquidtelecom.net -    0 |   28 |   28 |    2 |    3 |    4 |    4 |
|te-0-0-0-12.luk-p1-tho.liquidtelecom.net -    0 |   28 |   28 |  150 |  150 |  152 |  150 |
|      be-3.luk-pe1-tho.liquidtelecom.net -    0 |   28 |   28 |  146 |  147 |  148 |  146 |
|            5.11.8.145.liquidtelecom.net -    0 |   28 |   28 |  151 |  153 |  203 |  151 |
|                          195.66.226.234 -    0 |   28 |   28 |  148 |  157 |  196 |  151 |
|              ae1-br01-eqld5.as57976.net -    0 |   28 |   28 |  181 |  182 |  202 |  181 |
|         et-0-0-2-br02-eqam1.as57976.net -    0 |   28 |   28 |  180 |  180 |  190 |  184 |
|        et-0-0-67-pe01-eqam1.as57976.net -    0 |   28 |   28 |  179 |  184 |  230 |  224 |
|                           137.221.66.43 -    0 |   28 |   28 |  179 |  180 |  182 |  180 |
|                             37.244.24.2 -    0 |   28 |   28 |  180 |  180 |  184 |  184 |
|________________________________________________|______|______|______|______|______|______|

TRACEROUTE:
traceroute to 169.0.108.* (169.0.108.*), 15 hops max, 60 byte packets
1  Blizzard Blizzard  0.295 ms  0.267 ms  0.265 ms
2  37.244.24.2 (37.244.24.2)  0.518 ms  0.581 ms  0.658 ms
3  Blizzard Blizzard  1.020 ms  1.074 ms  1.150 ms
4  137.221.66.42 (137.221.66.42)  2.562 ms  2.566 ms  2.565 ms
5  137.221.78.66 (137.221.78.66)  1.097 ms  1.096 ms  1.095 ms
6  137.221.78.32 (137.221.78.32)  1.036 ms  1.191 ms  1.159 ms
7  ams-ix.teng0-1-0-6.lfr-pe1-mrs.liquidtelecom.net (80.249.211.45)  28.227 ms  27.885 ms  27.933 ms
8  5.11.10.251.liquidtelecom.net (5.11.10.251)  173.950 ms * *
9  * * *
10  77.246.59.85.liquidtelecom.net (77.246.59.85)  173.559 ms * *
11  * * *
12  * * *
13  * 169-0-108-*.ip.afrihost.co.za (169.0.108.*)  176.539 ms  176.941 ms
 
I don't really understand how it all works internally, but there are instances where the routing does go via london outbound, to say amsterdam, but then it returns via the east coast (its asymmetric). Surely that wouldn't require a major overhaul to change?

Code:
E.g. Routing to blizzard eu
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |   28 |   28 |    0 |    0 |    1 |    0 |
|                   No response from host -  100 |    6 |    0 |    0 |    0 |    0 |    0 |
|                   cpt-rx2.ip.adsl.co.za -    0 |   28 |   28 |    3 |    3 |   13 |    3 |
|                  cpt-net1.ip.adsl.co.za -    0 |   28 |   28 |    2 |    2 |    4 |    3 |
|     be-22.lza-pe1-cpt.liquidtelecom.net -    0 |   28 |   28 |    2 |    3 |    4 |    4 |
|te-0-0-0-12.luk-p1-tho.liquidtelecom.net -    0 |   28 |   28 |  150 |  150 |  152 |  150 |
|      be-3.luk-pe1-tho.liquidtelecom.net -    0 |   28 |   28 |  146 |  147 |  148 |  146 |
|            5.11.8.145.liquidtelecom.net -    0 |   28 |   28 |  151 |  153 |  203 |  151 |
|                          195.66.226.234 -    0 |   28 |   28 |  148 |  157 |  196 |  151 |
|              ae1-br01-eqld5.as57976.net -    0 |   28 |   28 |  181 |  182 |  202 |  181 |
|         et-0-0-2-br02-eqam1.as57976.net -    0 |   28 |   28 |  180 |  180 |  190 |  184 |
|        et-0-0-67-pe01-eqam1.as57976.net -    0 |   28 |   28 |  179 |  184 |  230 |  224 |
|                           137.221.66.43 -    0 |   28 |   28 |  179 |  180 |  182 |  180 |
|                             37.244.24.2 -    0 |   28 |   28 |  180 |  180 |  184 |  184 |
|________________________________________________|______|______|______|______|______|______|

TRACEROUTE:
traceroute to 169.0.108.* (169.0.108.*), 15 hops max, 60 byte packets
1  Blizzard Blizzard  0.295 ms  0.267 ms  0.265 ms
2  37.244.24.2 (37.244.24.2)  0.518 ms  0.581 ms  0.658 ms
3  Blizzard Blizzard  1.020 ms  1.074 ms  1.150 ms
4  137.221.66.42 (137.221.66.42)  2.562 ms  2.566 ms  2.565 ms
5  137.221.78.66 (137.221.78.66)  1.097 ms  1.096 ms  1.095 ms
6  137.221.78.32 (137.221.78.32)  1.036 ms  1.191 ms  1.159 ms
7  ams-ix.teng0-1-0-6.lfr-pe1-mrs.liquidtelecom.net (80.249.211.45)  28.227 ms  27.885 ms  27.933 ms
8  5.11.10.251.liquidtelecom.net (5.11.10.251)  173.950 ms * *
9  * * *
10  77.246.59.85.liquidtelecom.net (77.246.59.85)  173.559 ms * *
11  * * *
12  * * *
13  * 169-0-108-*.ip.afrihost.co.za (169.0.108.*)  176.539 ms  176.941 ms

I couldn't say what it would entail - really am not qualified enough on the networking side. I know our team do pretty complex things, so when they tell me it's difficult, I'm inclined to believe them :)
 
No issues with you using your Afrihost PPPoE details - just bear in mind that when we see you on the network we "Activate" your package and billing. So if you're cool with that :)

Give me a shout if you need me to follow up on anything :)
Thanks Afriman. Was all sorted Quick/Sharp. I do however want to check how long it takes for Afrihost to "Take ownership" of the Line, as I have increased the package on the Clientzone.
 
Quick update: after getting frustrated with regular 5ghz dropouts, about a week ago I flashed a nightly build onto my R1. To date I have not had a single dropout (and have not noticed any other issues), so as far as I'm concerned this fw is a vast improvement on the afrihost-supplied factory build.
I've now just updated to most recent nightly (2019/11/04), for those that may be interested click here to give it a try.
NB! This is a test build so its entirely possible that there may be bugs that I simply havent stumbled upon. Use at your own risk!
 
Quick update: after getting frustrated with regular 5ghz dropouts, about a week ago I flashed a nightly build onto my R1. To date I have not had a single dropout (and have not noticed any other issues), so as far as I'm concerned this fw is a vast improvement on the afrihost-supplied factory build.
I've now just updated to most recent nightly (2019/11/04), for those that may be interested click here to give it a try.
NB! This is a test build so its entirely possible that there may be bugs that I simply havent stumbled upon. Use at your own risk!

Great advice!

You can always roll back if you experience problems :)
 
Thanks Afriman. Was all sorted Quick/Sharp. I do however want to check how long it takes for Afrihost to "Take ownership" of the Line, as I have increased the package on the Clientzone.

It can sometimes go through in a couple of hours, but best to allow a couple of days.
 
Noob...



:)

I wonder if you can tell when I upgraded to unlimited Google Drive....

Top job AH! Really satisfied and I promise I won't keep the network pinned like this for much longer!!!
I've only got a 20/20 line which is shared throughout the house. Can't go balls crazy else they will complain.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X