Afrihost New Network Feedback

Status
Not open for further replies.
AfriGuy said:
You mentioned the host uses a 169 IP range as internal traffic, which in turn blocks or implements port knocking from internal requests.

Either way, the issue is fixed. Whether it was a fix from our team reaching our, a change on our end or theirs - it's working.
Click to expand...

Nope... I said no such thing. I made reference to an IP range that is used as internal, but both you and savage corrected me. I would also like to know what you mean by "On top of this, our network team reached out to the hosts."? What was asked on your side, and what was their response?

The point is, you responded to my comment about SMTP errors (among other issues in the SOUTH) that was a bit of a brush-off. The fact that it is now working is besides the point... the fact that others are too having SMTP errors tells me that my issue is not an anomaly, nor does it have anything to do with my host/VPS/firewall settings/etc.

SIMPLIFICATION:
"if the error only occurs on the AH network, then there something not working correctly on the AH network.
 
cortexenslaver said:
Nope... I said no such thing. I made reference to an IP range that is used as internal, but both you and savage corrected me. I would also like to know what you mean by "On top of this, our network team reached out to the hosts."? What was asked on your side, and what was their response?

The point is, you responded to my comment about SMTP errors (among other issues in the SOUTH) that was a bit of a brush-off. The fact that it is now working is besides the point... the fact that others are too having SMTP errors tells me that my issue is not an anomaly, nor does it have anything to do with my host/VPS/firewall settings/etc.

SIMPLIFICATION:
"if the error only occurs on the AH network, then there something not working correctly on the AH network.
Click to expand...

I'm sorry if I mis-understood the PM - I think we both need to review what was discussed there though. SMTP errors was for our SMTP server, which looks to be resolved now.

Again, relaying mail via port 587 isn't an issue on our network - only in this case. Could have been a case of port knocking, as I mentioned in the PM.
If our team reached out, we would have said we're seeing issues relaying mail, please update x.
 
AfriGuy said:
Are there auto-assigned DNS servers?
Maybe try the following if not:

169.1.2.1
169.1.2.2

Do any other sites route internationally for you?
Click to expand...

To do so my router also needs a static IP address. Is there a particular one I should use, or how do I find out which one?
 
al4bb said:
To do so my router also needs a static IP address. Is there a particular one I should use, or how do I find out which one?
Click to expand...

That's pretty weird. DNS and Static IPs are very different services.
I assume you're using automatically assigned DNS then?
 
AfriGuy said:
That's pretty weird. DNS and Static IPs are very different services.
I assume you're using automatically assigned DNS then?
Click to expand...

Talking to a guy who just knows the basics.
Using a Huawei router and the only option I see to manually enter DNS is to also enter a static IP. I presume the DNS settings are automatic.

I also assume your exchange congestion scenario is partly correct as we now have a power outage and speeds have greatly improved but still getting the international hops of some of the local sites.
 
al4bb said:
Talking to a guy who just knows the basics.
Using a Huawei router and the only option I see to manually enter DNS is to also enter a static IP. I presume the DNS settings are automatic.

I also assume your exchange congestion scenario is partly correct as we now have a power outage and speeds have greatly improved but still getting the international hops of some of the local sites.
Click to expand...

As default DNS will be automatically assigned.
Congestion can be seen when pinging bras.afrihost.com - that's the local Telkom equipment.

Any other sites routing internationally for you though?
 
AfriGuy said:
Latency looks mostly OK, keep me posted tonight :)
Click to expand...

Decided to switch to Afrihost account as my cap on web africa account was reached.

Did test on Afrihost Business Account. Looks to be performing much worse than Web Africa account

http://netgauge.ookla.com/share/307744207.png

Zertop's "Is it my Line" Results
Date/Time: Wed Oct 28 17:43:54 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 54ms.
Your maximum ping was 111ms.

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 (eg... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice!

Detailed Report:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=52ms TTL=63
Reply from 155.239.255.250: bytes=32 time=95ms TTL=63
Reply from 155.239.255.250: bytes=32 time=77ms TTL=63
Reply from 155.239.255.250: bytes=32 time=96ms TTL=63
Reply from 155.239.255.250: bytes=32 time=44ms TTL=63
Reply from 155.239.255.250: bytes=32 time=59ms TTL=63
Reply from 155.239.255.250: bytes=32 time=66ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=57ms TTL=63
Reply from 155.239.255.250: bytes=32 time=76ms TTL=63
Reply from 155.239.255.250: bytes=32 time=67ms TTL=63
Reply from 155.239.255.250: bytes=32 time=82ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=83ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=111ms TTL=63
Reply from 155.239.255.250: bytes=32 time=96ms TTL=63
Reply from 155.239.255.250: bytes=32 time=103ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=77ms TTL=63
Reply from 155.239.255.250: bytes=32 time=28ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=83ms TTL=63
Reply from 155.239.255.250: bytes=32 time=71ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 111ms, Average = 54ms
 
KoolDaffy said:
Decided to switch to Afrihost account as my cap on web africa account was reached.

Did test on Afrihost Business Account. Looks to be performing much worse than Web Africa account

http://netgauge.ookla.com/share/307744207.png

Zertop's "Is it my Line" Results
Date/Time: Wed Oct 28 17:43:54 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 54ms.
Your maximum ping was 111ms.

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 (eg... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice!

Detailed Report:

-snip
Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 111ms, Average = 54ms
Click to expand...

The latency is very up and down here though :(
Anything over 40ms (as a maximum) is an issue on ping here.

How does your ping differ on your other account?
 
AfriGuy said:
The latency is very up and down here though :(
Anything over 40ms (as a maximum) is an issue on ping here.

How does your ping differ on your other account?
Click to expand...

I posted ping with my other account on previous page.

Definitely nowhere near as high as with Afrihost account. Average on Web Africa account was 11ms While Afrihost one is showing Average as 54ms.
 
AfriGuy said:
Again, relaying mail via port 587 isn't an issue on our network - only in this case. Could have been a case of port knocking, as I mentioned in the PM.
If our team reached out, we would have said we're seeing issues relaying mail, please update x.
Click to expand...

You say that, but the problem was not there before, and is STILL not there on ANY other ISP's network. That in itself means there something was not working correctly on AH's NEW network. It does not make sense to sight "port knocking" as the reason for AH's network not being able to telnet in and see the port as "open". It is also ludicrous for me to have go and check/change rules on the firewall that STILL work PERFECTLY with EVERY OTHER ISP - again, this was proved by me, and in your subsequent tests.

I understand that there is still "tweaking" going on (that is why I brought it to your attention), but seeing as I did troubleshoot with my provider FIRST, and verified where the issue lies, does not diminish, or detract from the validity of my (and now other clients') current issues. The only way that using the telnet command would start working, is if AH's team refined/changed settings in one of their tweaks. The rules on my VPS have not changed, nor should they have to.
 
KoolDaffy said:
I posted ping with my other account on previous page.

Definitely nowhere near as high as with Afrihost account. Average on Web Africa account was 11ms While Afrihost one is showing Average as 54ms.
Click to expand...

Not sure how the results would differ to your exchange though.
I thought you'd let one account run for the day though as a comparison?
 
cortexenslaver said:
You say that, but the problem was not there before, and is STILL not there on ANY other ISP's network. That in itself means there something was not working correctly on AH's NEW network. It does not make sense to sight "port knocking" as the reason for AH's network not being able to telnet in and see the port as "open". It is also ludicrous for me to have go and check/change rules on the firewall that STILL work PERFECTLY with EVERY OTHER ISP - again, this was proved by me, and in your subsequent tests.

I understand that there is still "tweaking" going on (that is why I brought it to your attention), but seeing as I did troubleshoot with my provider FIRST, and verified where the issue lies, does not diminish, or detract from the validity of my (and now other clients') current issues. The only way that using the telnet command would start working, is if AH's team refined/changed settings in one of their tweaks. The rules on my VPS have not changed, nor should they have to.
Click to expand...

I really do feel that all of this has already been discussed via PM though.
Again, as I mentioned earlier, if our team has reached out to your hosts and changes made on either side - then there's progress there.

I'm able to telnet into the box on 587 without a problem.
If you are still having issues relaying mail please PM me the details and I can look at this with our team again.
 
LaraC said:
Why does "traceroute -n 197.242.144.102" have more than one IP at hop #10, 12,13 and 14?
Click to expand...
Never mind. Google told me that it is used in Multi-route and load balancing situations. :)
 
AfriGuy said:
Not sure how the results would differ to your exchange though.
I thought you'd let one account run for the day though as a comparison?
Click to expand...

Reached my cap on previous account. Little low on funds this month so didn't want to spend to buy more.

I did let it run for about half the day and seen no degradation on Web Africa account.

I only switched back to Afrihost account now and did a quick test and above is the results of it.
 
LaraC said:
Never mind. Google told me that it is used in Multi-route and load balancing situations. :)
Click to expand...

Sorry if I missed your last post. Basically just how the routers are configured to talk to each other :)
Happy reading, all this network stuff is really interesting!
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X