Same thing for me too at Lallmatie.
On Sunday, April 19, 2015, chitz <chittra.03_at_gmail.com> wrote:
> Me at lallmatie
>
> I cannot call people with proper range
>
> I had to buy emtel sim
> On 19 Apr 2015 19:53, "Ish Sookun" <ish_at_hacklog.in
> <javascript:_e(%7B%7D,'cvml','ish_at_hacklog.in');>> wrote:
>
>> Hello follks,
>>
>> A Pepsi lorry broke my phone line yesterday. Consequently, I have no fix
>> line, Internet and My.T TV working at home at the moment.
>>
>> I did WiFi tethering using my mobile phone today and had to hang my phone
>> at the window to get a decent 3G signal. I live at Providence (Q.
>> Militaire). Anybody else having 3G issues in "villages"?
>>
>> I obtain the following pings:
>>
>> ++++++++++++++
>> ish_at_spark:~$ ping -c 5 google.com
>> PING google.com (196.27.66.185) 56(84) bytes of data.
>> 64 bytes from 196.27.66.185: icmp_seq=1 ttl=57 time=59.3 ms
>> 64 bytes from 196.27.66.185: icmp_seq=2 ttl=57 time=57.7 ms
>> 64 bytes from 196.27.66.185: icmp_seq=3 ttl=57 time=76.1 ms
>> 64 bytes from 196.27.66.185: icmp_seq=4 ttl=57 time=112 ms
>> 64 bytes from 196.27.66.185: icmp_seq=5 ttl=57 time=53.4 ms
>>
>> --- google.com ping statistics ---
>> 5 packets transmitted, 5 received, 0% packet loss, time 4005ms
>> rtt min/avg/max/mdev = 53.474/71.920/112.877/21.883 ms
>> ish_at_spark:~$ ping -c 5 google.mu
>> PING google.mu (196.27.66.143) 56(84) bytes of data.
>> 64 bytes from 196.27.66.143: icmp_seq=1 ttl=57 time=2221 ms
>> 64 bytes from 196.27.66.143: icmp_seq=2 ttl=57 time=1549 ms
>> 64 bytes from 196.27.66.143: icmp_seq=3 ttl=57 time=1001 ms
>> 64 bytes from 196.27.66.143: icmp_seq=4 ttl=57 time=686 ms
>> 64 bytes from 196.27.66.143: icmp_seq=5 ttl=57 time=505 ms
>>
>> --- google.mu ping statistics ---
>> 5 packets transmitted, 5 received, 0% packet loss, time 3999ms
>> rtt min/avg/max/mdev = 505.542/1192.898/2221.999/624.778 ms, pipe 3
>> ish_at_spark:~$ ping -c 5 youtube.com
>> PING youtube.com (196.27.66.102) 56(84) bytes of data.
>> 64 bytes from 196.27.66.102: icmp_seq=1 ttl=58 time=48.6 ms
>> 64 bytes from 196.27.66.102: icmp_seq=2 ttl=58 time=46.7 ms
>> 64 bytes from 196.27.66.102: icmp_seq=3 ttl=58 time=44.7 ms
>> 64 bytes from 196.27.66.102: icmp_seq=4 ttl=58 time=42.7 ms
>> 64 bytes from 196.27.66.102: icmp_seq=5 ttl=58 time=50.9 ms
>>
>> --- youtube.com ping statistics ---
>> 5 packets transmitted, 5 received, 0% packet loss, time 4007ms
>> rtt min/avg/max/mdev = 42.737/46.768/50.951/2.871 ms
>> ish_at_spark:~$ ping -c 5 lexpress.mu
>> PING lexpress.mu (79.125.117.226) 56(84) bytes of data.
>> 64 bytes from ec2-79-125-117-226.eu-west-1.compute.amazonaws.com
>> (79.125.117.226): icmp_seq=1 ttl=36 time=377 ms
>> 64 bytes from ec2-79-125-117-226.eu-west-1.compute.amazonaws.com
>> (79.125.117.226): icmp_seq=2 ttl=36 time=402 ms
>> 64 bytes from ec2-79-125-117-226.eu-west-1.compute.amazonaws.com
>> (79.125.117.226): icmp_seq=3 ttl=36 time=254 ms
>> 64 bytes from ec2-79-125-117-226.eu-west-1.compute.amazonaws.com
>> (79.125.117.226): icmp_seq=4 ttl=36 time=263 ms
>>
>> --- lexpress.mu ping statistics ---
>> 5 packets transmitted, 4 received, 20% packet loss, time 4004ms
>> rtt min/avg/max/mdev = 254.471/324.438/402.391/66.331 ms
>> ish_at_spark:~$ ping -c 5 defimedia.info
>> PING defimedia.info (198.41.204.74) 56(84) bytes of data.
>> 64 bytes from 198.41.204.74: icmp_seq=1 ttl=52 time=883 ms
>> 64 bytes from 198.41.204.74: icmp_seq=2 ttl=52 time=455 ms
>> 64 bytes from 198.41.204.74: icmp_seq=3 ttl=52 time=595 ms
>> 64 bytes from 198.41.204.74: icmp_seq=4 ttl=52 time=340 ms
>> 64 bytes from 198.41.204.74: icmp_seq=5 ttl=52 time=364 ms
>>
>> --- defimedia.info ping statistics ---
>> 5 packets transmitted, 5 received, 0% packet loss, time 4797ms
>> rtt min/avg/max/mdev = 340.998/528.042/883.963/199.175 ms
>> +++++++++++++
>>
>> Regards,
>>
>> --
>> ​Ish Sookun
>>
>> - Geek by birth, Linux by choice.
>> - I blog at HACKLOG.in.
>>
>> https://twitter.com/IshSookun ^^ Do you tweet?
>>
>
--
Chandan Nuckched
Received on Sun May 17 2015 - 23:40:06 PST