MTN blocking ICMP ping?

[w1z4rd]

So I want to test my latency and I see (only) while using a MTN sim card in my modem. I am unable to ping anything. Is this normal?

My traceroute looks something like this:

Tracing route to ftp.is.co.za [196.4.160.12]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.68
  2   277 ms   449 ms   339 ms  10.210.32.113
  3   275 ms   329 ms   338 ms  10.210.32.126
  4   330 ms   609 ms   399 ms  10.210.70.33
  5   324 ms   359 ms   399 ms  10.210.70.33
  6   355 ms   639 ms   339 ms  10.210.70.61
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.

Is something wrong with my connection or is it normal for MTN to kill an important protocol like ICMP?

I can see I can ping IP`s before the filtering

 ping 10.210.70.33
PING 10.210.70.33 (10.210.70.33): 56 data bytes
64 bytes from 10.210.70.33: icmp_seq=0 ttl=252 time=333 ms
64 bytes from 10.210.70.33: icmp_seq=1 ttl=252 time=372 ms
64 bytes from 10.210.70.33: icmp_seq=2 ttl=252 time=332 ms
64 bytes from 10.210.70.33: icmp_seq=3 ttl=252 time=352 ms

Are MTN really this mentally challenged that they would block ping?

 

[ShawnStar]

What's up with all those 10.*.*.* IP's? Or does MTN give out private IP's it due to limited number of public IP's?
Would not be very clever of them to block icmp etc
Edit: Do you always hop over 10.*.*.* IP range's when doing trace routes over the MTN connection? And can you browse?

 

[pgs]

traceroute to ftp.is.co.za (196.4.160.12), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 7.221 ms 7.298 ms 7.672 ms
2 105-236-8-65-esr-lo.mtnbusiness.co.za (105.236.8.65) 223.054 ms 224.992 ms *
3 * * *
4 * * *
5 jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95) 260.503 ms * *
6 * qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115) 165.627 ms *
7 * * *
8 * * *
9 ar2-rba-tnr-gi0-2.ip.isnet.net (168.209.1.132) 243.363 ms * *
10 * * 196.34.7.196 (196.34.7.196) 243.834 ms
11 ftp.is.co.za (196.4.160.12) 245.092 ms !X * *


and I have p2p running.

From Cpt

 

[w1z4rd]

traceroute to ftp.is.co.za (196.4.160.12), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 7.221 ms 7.298 ms 7.672 ms
2 105-236-8-65-esr-lo.mtnbusiness.co.za (105.236.8.65) 223.054 ms 224.992 ms *
3 * * *
4 * * *
5 jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95) 260.503 ms * *
6 * qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115) 165.627 ms *
7 * * *
8 * * *
9 ar2-rba-tnr-gi0-2.ip.isnet.net (168.209.1.132) 243.363 ms * *
10 * * 196.34.7.196 (196.34.7.196) 243.834 ms
11 ftp.is.co.za (196.4.160.12) 245.092 ms !X * *


and I have p2p running.

From Cpt

What APN you using?

 

[w1z4rd]

What's up with all those 10.*.*.* IP's? Or does MTN give out private IP's it due to limited number of public IP's?
Would not be very clever of them to block icmp etc
Edit: Do you always hop over 10.*.*.* IP range's when doing trace routes over the MTN connection? And can you browse?

I can browse fine and ssh into servers of mine. ICMP is blocked :/

 

[Centronix]

It's not abnormal to block ICMP. I work for an ISP and we block ICMP to our Session Border Controllers. It's just another security mechanism to prevent DoS attacks

 

[bruce_the_loon]

It's not abnormal to block ICMP. I work for an ISP and we block ICMP to our Session Border Controllers. It's just another security mechanism to prevent DoS attacks

You just block some or all ICMP? I ask this because a couple of ISPs cause my network problems because they block the MTU discovery system by blocking all ICMP messages. There's a reason they called it Internet Control Message Protocol.

 

[w1z4rd]

It's not abnormal to block ICMP. I work for an ISP and we block ICMP to our Session Border Controllers. It's just another security mechanism to prevent DoS attacks

It hardly protects against dos attacks. ssyn and udp dont care. Its stupid. Especially on a wireless connection where you want to find the best signal for lower latency.

 

[Centronix]

You just block some or all ICMP? I ask this because a couple of ISPs cause my network problems because they block the MTU discovery system by blocking all ICMP messages. There's a reason they called it Internet Control Message Protocol.

All. I know we allow ping to routers but our BU restricts it to our SBCs. I guess it depends on the team policy. I'm against it

 

[Centronix]

It hardly protects against dos attacks. ssyn and udp dont care. Its stupid. Especially on a wireless connection where you want to find the best signal for lower latency.

Its just one of the mechanisms. It's not a 'the buck stops here' type of protection