e173 modem bouncing between wcdma and hspa causing problems ?? who do i blame ??

Draconia2

Draconia2

Expert Member
Joined
Oct 25, 2009
Messages
1,675
Reaction score
65
Location
Limpopo
:mad:

had no problems for about 4 weeks, last Monday they did some maintenance on the sat3 cable or something and since then i cant play diablo 3 properly. latency use to be 199-250ms . now its 2000ms when i log in and drops down to 409ms at the least.

and now it keeps bouncing between WCDMA and HSPA which seems to be causing another problem, once it bounces from hspa to wcdma the ping goes from 79ms to 385ms on local sites and the EU server ping goes up from 300ms to 600ms and up.

cod4 works fine as always. pings range from 90-100 since its local.:confused:

signal strength is 99% and DB is 75-80.

below are 2 trace routes. My buddy who uses a dsl 4mb line has trace routed the server as well and his times out at 15 hops. mine goes down at 10 hops.



trace route 1

tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:

1 * * * Request timed out.
2 56 ms 53 ms * 172.16.3.1
3 646 ms 78 ms 69 ms 172.16.3.129
4 49 ms 79 ms 59 ms ndn-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.7.73]
5 308 ms 399 ms 409 ms lon-ip-dir-stacker-pos-4-0-0-5.telkom-ipnet.co.za [196.43.9.102]
6 398 ms 399 ms 399 ms ffm-b10-link.telia.net [195.12.255.217]
7 398 ms 430 ms 418 ms ffm-bb2-link.telia.net [213.155.134.136]
8 437 ms 419 ms 389 ms hbg-bb2-link.telia.net [80.91.245.120]
9 418 ms 420 ms 388 ms adm-bb2-link.telia.net [213.155.130.228]
10 398 ms 410 ms 488 ms adm-b5-link.telia.net [80.91.253.171]
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.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
===========================================

then i noticed it switching between wcdma and hspa while im busy trace routing :


Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:

1 * * * Request timed out.
2 58 ms 69 ms 79 ms 172.16.3.1
3 42 ms * 334 ms 172.16.3.129
4 333 ms 449 ms 439 ms ndn-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.7.7
3]
5 325 ms 269 ms 249 ms lon-ip-dir-stacker-pos-4-0-0-5.telkom-ipnet.co.z
a [196.43.9.102]
6 566 ms 409 ms 419 ms ffm-b10-link.telia.net [195.12.255.217]
7 407 ms 419 ms 419 ms ffm-bb2-link.telia.net [80.91.247.188]
8 547 ms 409 ms 419 ms hbg-bb2-link.telia.net [80.91.245.122]
9 408 ms 419 ms 419 ms adm-bb2-link.telia.net [80.91.245.183]
10 387 ms 450 ms 418 ms adm-b5-link.telia.net [80.91.253.171]
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.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.




who do i blame ??? SAIX ??? blizzard ?? my tower ???
 
Last edited:
Draconia2 said:
:mad:

had no problems for about 4 weeks, last Monday they did some maintenance on the sat3 cable or something and since then i cant play diablo 3 properly. latency use to be 199-250ms . now its 2000ms when i log in and drops down to 409ms at the least.

and now it keeps bouncing between WCDMA and HSPA which seems to be causing another problem, once it bounces from hspa to wcdma the ping goes from 79ms to 385ms on local sites and the EU server ping goes up from 300ms to 600ms and up.

cod4 works fine as always. pings range from 90-100 since its local.:confused:

signal strength is 99% and DB is 75-80.

below are 2 trace routes. My buddy who uses a dsl 4mb line has trace routed the server as well and his times out at 15 hops. mine goes down at 10 hops.



trace route 1

tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:

1 * * * Request timed out.
2 56 ms 53 ms * 172.16.3.1
3 646 ms 78 ms 69 ms 172.16.3.129
4 49 ms 79 ms 59 ms ndn-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.7.73]
5 308 ms 399 ms 409 ms lon-ip-dir-stacker-pos-4-0-0-5.telkom-ipnet.co.za [196.43.9.102]
6 398 ms 399 ms 399 ms ffm-b10-link.telia.net [195.12.255.217]
7 398 ms 430 ms 418 ms ffm-bb2-link.telia.net [213.155.134.136]
8 437 ms 419 ms 389 ms hbg-bb2-link.telia.net [80.91.245.120]
9 418 ms 420 ms 388 ms adm-bb2-link.telia.net [213.155.130.228]
10 398 ms 410 ms 488 ms adm-b5-link.telia.net [80.91.253.171]
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.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
===========================================

then i noticed it switching between wcdma and hspa while im busy trace routing :


Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:

1 * * * Request timed out.
2 58 ms 69 ms 79 ms 172.16.3.1
3 42 ms * 334 ms 172.16.3.129
4 333 ms 449 ms 439 ms ndn-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.7.7
3]
5 325 ms 269 ms 249 ms lon-ip-dir-stacker-pos-4-0-0-5.telkom-ipnet.co.z
a [196.43.9.102]
6 566 ms 409 ms 419 ms ffm-b10-link.telia.net [195.12.255.217]
7 407 ms 419 ms 419 ms ffm-bb2-link.telia.net [80.91.247.188]
8 547 ms 409 ms 419 ms hbg-bb2-link.telia.net [80.91.245.122]
9 408 ms 419 ms 419 ms adm-bb2-link.telia.net [80.91.245.183]
10 387 ms 450 ms 418 ms adm-b5-link.telia.net [80.91.253.171]
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.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.




who do i blame ??? SAIX ??? blizzard ?? my tower ???
Click to expand...

Your dongle goes into idle mode when you are not downloading or uploading data. All dongle should do that. the problem isnt with your dongle but with 8ta ... I have the same experience in the evenings mostly... nothing can really be done from your side.
 
Nitrate said:
Your dongle goes into idle mode when you are not downloading or uploading data. All dongle should do that. the problem isnt with your dongle but with 8ta ... I have the same experience in the evenings mostly... nothing can really be done from your side.
Click to expand...

the idle side of things i understand, but shouldn't it be in hspa mode while doing tracert or pings ? saturday night my dashboard showed hsdpa for like 30 seconds, i couldn't believe it !!
 
Re traceroute:
The first one in Telkom (telkom-ipnet.co.za)
The second one shows somewhere between 8ta and Telkom.

Re: WCDMA/HSPA bouncing.
Yip, it is normal. With HSPA+ modem transition is faster, as modem will use high speed control channels and HSPA+ transition protocol (while still displays WCDMA). But don't expect significant improvements in your case. See above.
 
Last edited:
sajunky said:
Re traceroute:
The first one in Telkom (telkom-ipnet.co.za)
The second one shows somewhere between 8ta and Telkom.

Re: WCDMA/HSPA bouncing.
Yip, it is normal. With HSPA+ modem transition is faster, as modem will use high speed control channels and HSPA+ transition protocol (while still displays WCDMA). But don't expect significant improvements in your case. See above.
Click to expand...

the problem lies with the fact that my tower could be screwed ?


today i lost signal about three times just slapping that confirmation even further .... sigh ... sigh ... sigh
 
Yip, it seems multiple problems. PM 8ta using MyBB sticky template and include link to this thread.
 
Ho3n3r said:
I have exactly the same issue. Is there any way to force it to HSUPA without touching normal 3G?
Click to expand...
That wouldn't help. Switching between HSUPA and 3G is not the cause of the problem.

Because no data is being transferred, the connection drops from HSUPA down to 3G, not because the connection dropped from HSUPA down to 3G, no data is being transferred.
 
ginggs said:
That wouldn't help. Switching between HSUPA and 3G is not the cause of the problem.

Because no data is being transferred, the connection drops from HSUPA down to 3G, not because the connection dropped from HSUPA down to 3G, no data is being transferred.
Click to expand...

On mine, if MDMA shows that it's 3G, nothing happens, i.e. pings time out, pages don't load etc. and as soon as it switches to HSUPA, stuff happens. So if there is a way to keep it on HSUPA it will definitely help. a Bypass of sorts. But according to my limited research, there is none.
 
Ho3n3r said:
On mine, if MDMA shows that it's 3G, nothing happens, i.e. pings time out, pages don't load etc. and as soon as it switches to HSUPA, stuff happens.
Click to expand...
No, it is switching to HSUPA because stuff is happening.
 
ginggs said:
No, it is switching to HSUPA because stuff is happening.
Click to expand...

OK, so how do you force it to 'realise that stuff is happening'? Sometimes it takes about 30 seconds to make this switch...

EDIT: My biggest problem is that it's switching off the HSUPA during online gaming, which surely it shouldn't, since 'stuff is happening', right? It ups my latency heavily, which is not what I'd call ideal. How do I prevent this?
 
Last edited:
Ho3n3r said:
OK, so how do you force it to 'realise that stuff is happening'? Sometimes it takes about 30 seconds to make this switch...

EDIT: My biggest problem is that it's switching off the HSUPA during online gaming, which surely it shouldn't, since 'stuff is happening', right? It ups my latency heavily, which is not what I'd call ideal. How do I prevent this?
Click to expand...
If your base station is congested stuff stops happening.
 
ginggs said:
If your base station is congested stuff stops happening.
Click to expand...

telkom techy just popped in to check my trace routes / pings and rsi, says everything is fine my side they would need to investigate the base station and took down some details. as soon as it switches to WCDMA the pings jump. ie local ping = 60 on hspa, wcdma pings are 400. Same thing happens with international hence the reason i cant play d3 properly :/


+4 to 8ta customer service ! :D you handled this one really well and speedy


are you telling me a bunch of elderly people are harassing the tower with their 3g dongles because it is highly plausible :P
 
google HSPA locker & give that a try,should hold it in HSPA
 
Hi all!

As per the other threads:
We are currently experiencing a higher than normal customer data usage which will affect throughput during busy hours. Network optimization is in progress which will address the issue. A resolve is expected by next week Wednesday (18/07/2012).

Apologies for the inconvenience

Regards,
Social Media Team
 
Draconia2 said:
had no problems for about 4 weeks, last Monday they did some maintenance on the sat3 cable or something and since then i cant play diablo 3 properly. latency use to be 199-250ms . now its 2000ms when i log in and drops down to 409ms at the least.

and now it keeps bouncing between WCDMA and HSPA which seems to be causing another problem, once it bounces from hspa to wcdma the ping goes from 79ms to 385ms on local sites and the EU server ping goes up from 300ms to 600ms and up.
Click to expand...
Let us know how things improve on the 18th.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X