Afrihost Uncapped ADSL Feedback (Pt3)

Status
Not open for further replies.
AfriMan said:
If you're running a clean system (i.e. no contention) that would prove if gaming is shaped if you can see you're not bursting above a certain amount (the percentage mentioned in ClientZone shaping) on BitMeter OS.
Click to expand...

I'll install bitmeter OS and check it out.

My NNTP runs on another machine, I can start it up while the gaming is going on to see if there's a difference in gaming throughput with it enabled/disabled. Valid test?
 
NightowlZA said:
So I just tested ( using netlimiter)

Capped 1gb: during gameplay it goes along at around 16-18kB/s DL, jumping to 25kB/s when there's a lot going on.

Uncapped 1mb: Never went over 7kB/s regardless of what was going on in the game.


and yes, my latency was jumping over 2500ms on my uncapped. No issues on the capped.
Click to expand...

Can you show me those results and also give me your username and contact details. Just drop them in a mail to [email protected]. Let's see if we can figure this :(
 
Sinbad said:
I'll install bitmeter OS and check it out.

My NNTP runs on another machine, I can start it up while the gaming is going on to see if there's a difference in gaming throughput with it enabled/disabled. Valid test?
Click to expand...

I think for now, just run the game and let's see what your throughput is like. Even gaming should burst above the shaped limit, and we'll see it hit a ceiling if the traffic is being shaped.
 
AfriMan said:
I think for now, just run the game and let's see what your throughput is like. Even gaming should burst above the shaped limit, and we'll see it hit a ceiling if the traffic is being shaped.
Click to expand...

OK here we go, with YELLOW latency in D3 - so above 300ms


Capture.jpg
 
Then for lols I started NNTP up.
Unable to even retrieve my character list in D3.

Capture.PNG


Request timed out.


So something D3 is doing is contending for the p2p bandwidth that the shaper is restricting.

Screenshot026.jpg
 

Attachments

  • Screenshot 2014-06-03 17.48.06.jpg
    Screenshot 2014-06-03 17.48.06.jpg
    28 KB · Views: 232
Last edited:
Sinbad said:
Then for lols I started NNTP up.
Unable to even retrieve my character list in D3.

View attachment 122799


Request timed out.


So something D3 is doing is contending for the p2p bandwidth that the shaper is restricting.

View attachment 122803
Click to expand...

Could the same thing be happening on capped? My 10Meg capped account is unplayable on D3 tonight, switched to my backup 2 Meg with another ISP and is humming along green all the way.
 
Ol' Mean Bastid said:
Could the same thing be happening on capped? My 10Meg capped account is unplayable on D3 tonight, switched to my backup 2 Meg with another ISP and is humming along green all the way.
Click to expand...

Capped should not have the same issue.
I think the latency thing and the p2p thing are two separate issues. I think there's *** with MTN somewhere along the line. (My FNB Connect account was also poked)
 
I am going to capture traffic as soon as wireshark finishes downloading. 40KB/sec... on a 10 meg line.

Then we can see latencies in packet acks as well as capturing ALL the servers/ports that D3 tries to connect to.
 
OK, port 1119 connections to the following IPs:
178.79.194.187
62.115.244.84
80.239.208.193 (seeing quite a few DUP ACKS to this and TCP Retransmission, along with packet loss (TCP previous segment not captured) <---- this accounts for the latency and spikes IMHO

Then HTTP connections to:
87.248.210.254 and 80.239.186.26
 
HELP : All looks good but my D/L speed is awful and in-game ping 300ms+ (4MB line)

Data Statistics
Data Used: 4.98 GB Average
Daily Usage: 1.66 GB
Projected Monthly Usage: 49.76 GB

Shaping Policy: 18.8% Download/ 6.25% P2P

Last Result:
Download Speed: 416 kbps (52 KB/sec transfer rate)
Upload Speed: 413 kbps (51.6 KB/sec transfer rate)
Latency: 171 ms
‎03‎/‎06‎/‎2014‎ ‎20‎:‎12

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=33 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=38 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=40 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=33 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=34 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=45 time=179 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=45 time=189 ms
Request timeout for icmp_seq 3
64 bytes from 8.8.8.8: icmp_req=4 ttl=45 time=179 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=45 time=189 ms


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 24 ms 2 ms
2 105.236.234.6 16 ms 9 ms
3 41.181.221.2 66 ms 13 ms
4 41.181.198.1 12 ms 12 ms
5 196.44.18.2 16 ms 16 ms
6 196.44.31.6 46 ms
196.44.31.1 18 ms
7 196.44.31.9 34 ms
196.44.31.6 39 ms
8 196.30.1.5 55 ms
196.44.31.9 56 ms
9 196.31.220.2 37 ms
196.30.1.5 60 ms
10 196.30.42.1 41 ms
196.31.63.2 32 ms
11 197.242.144.1 34 ms
196.30.42.1 33 ms
12 197.242.144.1 43 ms


traceroute -n 8.8.8.8

1 192.168.0.1 70 ms
2 105.236.234.6 17 ms
3 41.181.51.1 12 ms
4 41.181.198.1 11 ms
5 196.44.18.2 14 ms
6 196.44.31.1 14 ms
7 196.44.31.6 42 ms
8 41.181.139.1 34 ms
9 72.14.194.7 36 ms
10 66.249.95.8 209 ms
11 8.8.8.8 180 ms


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name: www.google.com
Address: 173.194.41.178
Name: www.google.com
Address: 173.194.41.177
Name: www.google.com
Address: 173.194.41.176
Name: www.google.com
Address: 173.194.41.180
Name: www.google.com
Address: 173.194.41.179


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
Zertop said:
Please would you run my second app (in the link below) :)

Z
Click to expand...

I gave Zertop's app a go and this the results

Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 48ms
Your maximum ping was 57ms

Looking at your average ping, your line seems to be a bit dodgy :/ This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (ie... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice

Detailed Report
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)

Pinging 105.236.0.193 with 32 bytes of data:
Reply from 105.236.0.193: bytes=32 time=50ms TTL=254
Reply from 105.236.0.193: bytes=32 time=57ms TTL=254
Reply from 105.236.0.193: bytes=32 time=42ms TTL=254
Reply from 105.236.0.193: bytes=32 time=49ms TTL=254
Reply from 105.236.0.193: bytes=32 time=52ms TTL=254
Reply from 105.236.0.193: bytes=32 time=44ms TTL=254
Reply from 105.236.0.193: bytes=32 time=43ms TTL=254
Reply from 105.236.0.193: bytes=32 time=50ms TTL=254
Reply from 105.236.0.193: bytes=32 time=51ms TTL=254
Request timed out.
Reply from 105.236.0.193: bytes=32 time=44ms TTL=254
Reply from 105.236.0.193: bytes=32 time=45ms TTL=254
Request timed out.
Reply from 105.236.0.193: bytes=32 time=46ms TTL=254
Reply from 105.236.0.193: bytes=32 time=54ms TTL=254
Reply from 105.236.0.193: bytes=32 time=56ms TTL=254
Request timed out.
Reply from 105.236.0.193: bytes=32 time=56ms TTL=254
Reply from 105.236.0.193: bytes=32 time=47ms TTL=254
Reply from 105.236.0.193: bytes=32 time=43ms TTL=254
Reply from 105.236.0.193: bytes=32 time=50ms TTL=254
Reply from 105.236.0.193: bytes=32 time=42ms TTL=254
Reply from 105.236.0.193: bytes=32 time=44ms TTL=254
Reply from 105.236.0.193: bytes=32 time=52ms TTL=254
Reply from 105.236.0.193: bytes=32 time=47ms TTL=254
Reply from 105.236.0.193: bytes=32 time=43ms TTL=254
Reply from 105.236.0.193: bytes=32 time=42ms TTL=254
Reply from 105.236.0.193: bytes=32 time=49ms TTL=254
Reply from 105.236.0.193: bytes=32 time=43ms TTL=254
Reply from 105.236.0.193: bytes=32 time=56ms TTL=254

Ping statistics for 105.236.0.193:
Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 57ms, Average = 48ms

2014-06-03 21:30:32,37
 
AfriGuy said:
Was this locally or on international?
Maybe download our network test app and paste up the results here - should give us a better idea of what's happening.

www.afrihost.com/site/page/afrihost_network_test
Click to expand...


did this too:
Ping Test:

ping 197.242.144.102

Request timeout for icmp_seq 1
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=56 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=43 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=47 ms
Request timeout for icmp_seq 5


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=42 time=211 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=42 time=215 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=42 time=216 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=42 time=211 ms
Request timeout for icmp_seq 5


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms
2 41.181.221.2 51 ms
105.236.0.1 33 ms
3 41.181.165.1 44 ms
41.181.221.2 43 ms
4 196.44.31.1 44 ms
41.181.165.1 86 ms
5 196.30.1.5 42 ms
196.44.31.1 55 ms
6 196.31.220.2 47 ms
196.44.31.9 44 ms
7 196.30.42.1 46 ms
196.31.220.2 45 ms
8 197.242.144.1 43 ms
196.31.63.2 50 ms
9 196.30.42.1 52 ms
10 197.242.144.1 43 ms


traceroute -n 8.8.8.8

1 192.168.0.1 1 ms 1 ms 1 ms
2 105.236.0.1 33 ms 33 ms 47 ms
3 41.181.221.2 55 ms 53 ms
41.181.165.1 78 ms
4 41.181.165.1 56 ms 46 ms
41.181.139.9 45 ms
5 41.181.139.9 44 ms
196.44.0.1 43 ms
72.14.194.7 50 ms
6 72.14.194.7 45 ms
41.181.139.9 45 ms
72.14.242.2 212 ms
7 8.8.8.8 210 ms


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

** server can't find thisshouldfail.com: NXDOMAIN


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
I see it's not just me then. I sent some emails to Afrihost trying to get an explanation for all the shaping. My NNTP downloads are DEAD at 0KB/s. Only after 1am now did I see it coming alive again at acceptable speeds. But every day now for 3 days my NNTP downloads stop completely during the day and night up to 1am. Also my torrents don't run over 15KB/s. Is this shaping or some general issue? I also experienced latency spikes during online gaming tonight. It should be known I am a new uncapped subscriber with AH, so I don't know how my experience compares to that of other users. Do you all get shaped like this?
 
BLIXEMPIE said:
I see it's not just me then. I sent some emails to Afrihost trying to get an explanation for all the shaping. My NNTP downloads are DEAD at 0KB/s. Only after 1am now did I see it coming alive again at acceptable speeds. But every day now for 3 days my NNTP downloads stop completely during the day and night up to 1am. Also my torrents don't run over 15KB/s. Is this shaping or some general issue? I also experienced latency spikes during online gaming tonight. It should be known I am a new uncapped subscriber with AH, so I don't know how my experience compares to that of other users. Do you all get shaped like this?
Click to expand...

Jip.
 
Sinbad said:
Capped should not have the same issue.
I think the latency thing and the p2p thing are two separate issues. I think there's *** with MTN somewhere along the line. (My FNB Connect account was also poked)
Click to expand...

I think it happening on Capped and Uncapped would mean it's not a shaping issue. Probably relates to contention, it would be unlikely that we're having two separate issues at the same time :(
 
AfriMan said:
I think it happening on Capped and Uncapped would mean it's not a shaping issue. Probably relates to contention, it would be unlikely that we're having two separate issues at the same time :(
Click to expand...

You're having two separate issues at the same time, promise.
The packet loss issue is an MTN thing - as I get it on FNB Connect as well.
The shaping thing is definitely your shaper messing with D3 traffic. 30KB/sec of NNTP traffic should not prevent D3 from working, unless the D3 traffic is being classed the same as the NNTP traffic.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X