nahoR
Well-Known Member
Its not entirely like wireshark. It is a proxy for web traffic. How ever you are able to decrypt SSL traffic.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Its not entirely like wireshark. It is a proxy for web traffic. How ever you are able to decrypt SSL traffic.
Does your browser not give you an untrusted cert warning?
Having the same problem as yesterday, my ping online is high but throughout the day it was fine.
And this is the result after "Magically Fixed My Line"
Last Result:
Download Speed: 256 kbps (32 KB/sec transfer rate)
Upload Speed: 471 kbps (58.9 KB/sec transfer rate)
Latency: 163 ms
21/05/2014 19:08
Ping Test:
ping 197.242.144.102
64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=74 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=35 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=88 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=38 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=43 ms
ping 8.8.8.8
64 bytes from 8.8.8.8: icmp_req=1 ttl=43 time=217 ms
Request timeout for icmp_seq 2
64 bytes from 8.8.8.8: icmp_req=3 ttl=43 time=230 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Trace Test:
traceroute -n 197.242.144.102
1 192.168.0.1 20 ms 30 ms
2 105.236.234.6 12 ms 9 ms
3 41.181.53.1 11 ms 30 ms
4 41.181.198.1 12 ms 10 ms
5 196.44.18.2 15 ms 33 ms
6 196.44.31.1 34 ms 13 ms
7 196.44.0.2 60 ms
196.44.31.9 32 ms
8 196.31.220.1 49 ms 34 ms
9 196.31.220.2 38 ms 35 ms
10 196.31.63.2 33 ms 38 ms
11 196.30.42.1 37 ms
197.242.144.1 40 ms
12 197.242.144.1 42 ms
traceroute -n 8.8.8.8
1 192.168.0.1 14 ms 99 ms 34 ms
2 105.236.234.6 11 ms 32 ms 12 ms
3 41.181.53.1 29 ms 18 ms 12 ms
4 41.181.198.1 95 ms 16 ms 38 ms
5 196.44.18.2 15 ms 16 ms
196.44.31.1 27 ms
6 196.44.31.1 17 ms 38 ms
196.44.31.6 70 ms
7 196.44.31.6 42 ms
41.181.139.1 53 ms 49 ms
8 41.181.139.1 57 ms
72.14.194.7 39 ms
209.85.253.1 200 ms
9 Request timed out * * *
10 Request timed out *
11 Request timed out *
12 Request timed out *
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.34.116
Name: www.google.com
Address: 173.194.34.114
Name: www.google.com
Address: 173.194.34.112
Name: www.google.com
Address: 173.194.34.113
Name: www.google.com
Address: 173.194.34.115
nslookup thishouldfail.afrihost.com
** server can't find thisshouldfail.com: NXDOMAIN
Hell yeah, gotta love that shaping at 9:30PM. On the FULLY upgraded East IPC.
AFriman...tell AFriguy to check his messages![]()
Dialup line?Finished at 2014-05-22 10:10:02
Downloaded 159 MB
Results of the job:
Stage Download
Downloaded in 1 hour 28 minutes 45 seconds at an average of 30 KB/s
Less than 3 percent of line capacity :-(
Dialup line?
AfriMan, you didn't reply to my post, so I'll ask again. Is there something going on in PTA East?
From the above posts I'm assuming that you're shaping everyone because of capacity constraints?
I am likewise finding that shaping is too heavy.
My German streaming is working again.
@Afriman: I too use tagging to shape my data. I am familiar with the routing, though likely don't use heuristics, DPI and such fancy methods to tag my packets. It is however clear that "real-time service"s aren't adequately profiled yet because when I relay them over VPS instances in different locations I get differing throughput.
Work related data now goes over 3G for the last months. CellC far outperforms Afrihost's deemed 12%/6% shaping for a low utilization 10 meg uncapped user.
Do you allow multiple DSL accounts over one line? Perhaps go down to a 2 meg uncapped business line and have a capped account for work use and browsing (cannot download updates and the like at 12% and 6% of line speed)? Mikrotik doesn't care if the modem is a bridge device.