Vodacom Problems: Slow Throughput, trying to Connect, DNS, High Latency

Status
Not open for further replies.
At last something positive

Symptoms: Exactly as described in V3G's first post in the thread.
Area: Pretoria Moreleta Park (1km north of NIA)
Type: Merlin U70 (HW REV [0:56]
EMEI: 358661000648029
Firmware: 15.4-15.4-00
APN: internet

Hope all of this leads to a solution! Will try the pings and report on that later.
 
area: Cape Town - Plumstead
modem: Option card CE 0700
IMEI: 351969005573804
firmware: 3.1.2
apn: internet

ping -t smtp.vodacom.co.za gives me these results:
bytes: 32
time: averages about 290ms
TTL: 247

ping -t -l 500 smtp.vodacom.co.za
bytes: 500
time: averages about 310ms
TTL: 247

ping -t -l 1000 smtp.vodacom.co.za
bytes: 1000
time: averages about 500ms
TTL: 247

The pings do time out every now and then and sometimes go as high as 1500ms. The highest I saw was 3794ms.

My "disappearing connection" problem is as I and others have explained before, but for the sake of completion, I'll repeat it here.

I connect, no problem and then the connection just dies even though the dashboard shows that I still have a 3G connection and the light on the modem is still flashing. I then disconnect, shut down the dashboard, pop the card out, put the card back in, wait for it to acquire, and reconnect. This usually works for me.
 
Area: Sydenham, Jo'burg and during the last few days Cape Town (central) where I experienced exactly the same problem.
Modem: Huawei E620
IMEI: 357130001369663
Firmware: 11.16.09.06.19
Apn: Internet

The dashboard doesn't show a disconnection, but the connection itself just dies. Disconnecting and reconnecting (without closing the dashboard) usually solves the problem but, tonight for example, I've had to do this almost every time that I move to another page or website!
 
When you guys get the slow throughput issue, if you completely reboot the modem (i.e. power it down by unplugging it and re-inserting it), do you get the throughput back again?

I'm trying to establish if a full modem reset helps. One thing we're trying to find is if certain modem types get their knickers in a knot with certain towers.
 
vodacom3g said:
When you guys get the slow throughput issue, if you completely reboot the modem (i.e. power it down by unplugging it and re-inserting it), do you get the throughput back again?

I'm trying to establish if a full modem reset helps. One thing we're trying to find is if certain modem types get their knickers in a knot with certain towers.
Click to expand...

I reboot my laptop and that usually does the trick.
 
Oddly enough, its happened to me a few times this evening, but just leaving it for a few minutes and it rights itself and all is happiness and light again...
 
vodacom3g said:
When you guys get the slow throughput issue, if you completely reboot the modem (i.e. power it down by unplugging it and re-inserting it), do you get the throughput back again?

I'm trying to establish if a full modem reset helps. One thing we're trying to find is if certain modem types get their knickers in a knot with certain towers.
Click to expand...

Using the wrt54g3g router: a poweroff does not necessarily solve it, did not in the last instance I reported above. Will test further.

BTW: noticed nothing today.

ryts
 
The problem is usually fixed by disconnecting, exiting dashboard, re-executing dashboard & reconnecting. If I do exit the dashboard and try to reconnect, I get an error 692. Sometimes the throughput rights itself if you wait long enough. I have never had to power down the 3G card or to reboot my machine.
 
at 21h23, Groot Brak, Mossel Bay area (an edifying spectacle NOT)

Code: 
~$ ping smtp.vodacom.co.za
PING smtp.vodacom.co.za (196.11.146.148) 56(84) bytes of data.
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=1 ttl=246 time=748 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=2 ttl=246 time=152 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=4 ttl=246 time=339 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=5 ttl=246 time=1390 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=7 ttl=246 time=1040 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=8 ttl=246 time=291 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=9 ttl=246 time=2240 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=12 ttl=246 time=880 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=13 ttl=246 time=477 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=14 ttl=246 time=149 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=17 ttl=246 time=540 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=18 ttl=246 time=1160 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=23 ttl=246 time=159 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=25 ttl=246 time=4561 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=28 ttl=246 time=2250 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=29 ttl=246 time=1980 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=34 ttl=246 time=2870 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=39 ttl=246 time=2099 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=40 ttl=246 time=2239 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=43 ttl=246 time=2429 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=49 ttl=246 time=939 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=50 ttl=246 time=286 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=51 ttl=246 time=626 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=52 ttl=246 time=1628 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=54 ttl=246 time=679 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=55 ttl=246 time=169 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=56 ttl=246 time=676 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=57 ttl=246 time=179 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=58 ttl=246 time=195 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=60 ttl=246 time=169 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=62 ttl=246 time=169 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=63 ttl=246 time=179 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=64 ttl=246 time=219 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=65 ttl=246 time=1669 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=69 ttl=246 time=1369 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=70 ttl=246 time=1099 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=72 ttl=246 time=1809 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=78 ttl=246 time=1238 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=79 ttl=246 time=618 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=83 ttl=246 time=2189 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=84 ttl=246 time=1980 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=85 ttl=246 time=1198 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=86 ttl=246 time=1392 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=89 ttl=246 time=731 ms
64 bytes from mx1.vodamail.co.za (196.11.146.148): icmp_seq=90 ttl=246 time=200 ms

--- smtp.vodacom.co.za ping statistics ---
91 packets transmitted, 45 received, 50% packet loss, time 90014ms
rtt min/avg/max/mdev = 149.918/1102.730/4561.153/931.466 ms, pipe 5
 
Having major problems today .. can't stay connected for even a minute at a time :(

area: Cape Town - Plumstead
modem: Option card CE 0700
IMEI: 351969005573804
firmware: 3.1.2
apn: internet
 
In Ramsgate 3G is missing - who stole it?
GPRS is painfully slow I think I would be better going back to dialup.

As vodacoms 3g speed is getting slower and slower we finally ordered ADSL a couple of months ago but true to form Telkom has not delivered!

Our 3g contracts only expire at the end of the year so I guess we have to pay for this painful service until then!
 
Hi V3G,

thanks for the update (in another thread). As you wrote, the route to the problem it is ironic.

ryts
 
Anyone seeing those slow-downs / link freeze events in the recent past now noticing a rise in discos?

ryts
 
lights are flashing here at my disco .. but nobody's dancing!!

I have had major problems again with this "disappearing" connection today .. same thing as before .. it shows that I am connected .. but nothing happens and when I ping the request just times out .. I have tried keeping the connection warm by having the ping running constantly in the background .. still no joy.
 
gypsy said:
lights are flashing here at my disco .. but nobody's dancing!!

I have had major problems again with this "disappearing" connection today .. same thing as before .. it shows that I am connected .. but nothing happens and when I ping the request just times out .. I have tried keeping the connection warm by having the ping running constantly in the background .. still no joy.
Click to expand...

The first fix for this should roll out tonight, up in JHB and will be tested there. Then it should roll out in the rest of the country if Gauteng did not blow up completely.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X