If any of you is using Thomson routers ( speedtouch), would you please post a traceroute to google? Thanks.
Anyone using Speedtouch ?
One of my friends has it i just cant remember who, what ISP is providing it with their adsl service ?
Cyberia and Ogero AFAIK
damn ogero --> my cousin. i would rather kill myself than try to ask of him a traceroute, if i pass by his house today ill post it for ya :)
Hi mark, thanks but it's ok I managed to configure my router correctly. I bought a new Linksys WAG320N and it was driving me crazy. It isworking fine but ping on yahoo was like 15/20 ms more than the old D-link router.
Switching the modulation to g.dmt was a good idea. No probs so far..
Down up
DSL Noise Margin: 38.1 dB 35.7 dB
DSL Attenuation: 12.0 dB 10.6 dB
DSL Transmit Power: 14.6 dBm 8.1 dBm
Switching the modulation to g.dmt was a good idea. No probs so far..
Down up
DSL Noise Margin: 38.1 dB 35.7 dB
DSL Attenuation: 12.0 dB 10.6 dB
DSL Transmit Power: 14.6 dBm 8.1 dBm
Well I have Thompson from IDM in beirut and I have D-Link from Ogero in my placeKareem wroteCyberia and Ogero AFAIK
No probs man!
Flyingwizard i guess ogero gives out thompson aswell cause im certain my cousin has it.
Flyingwizard i guess ogero gives out thompson aswell cause im certain my cousin has it.
Ogero is no longer providing the D-Link 2640U.. they switched now to Thomson speedtouch 585Flyingwizard wroteWell I have Thompson from IDM in beirut and I have D-Link from Ogero in my placeKareem wroteCyberia and Ogero AFAIK
I have Thomson Speedtouch 585i from IDM too.
Well if you can post a traceroute to google ill be thankful.
Ah well, I've been having Ogero for like 8 months or so.. They must have changed since then :)
Sorry for that, I was not aware.
Sorry for that, I was not aware.
Hey Sorry I thought you already solved the issue anyways here is a trace route to google :Kareem wroteWell if you can post a traceroute to google ill be thankful.
D:\Documents and Settings\Administrator>tracert google.com
Tracing route to google.com [74.125.67.100]
over a maximum of 30 hops:
1 7 ms 39 ms 39 ms dsldevice.lan [192.168.1.254]
2 253 ms 262 ms 267 ms 10.151.144.1
3 291 ms 294 ms 295 ms 172.50.1.4
4 275 ms 302 ms 300 ms 10.0.1.26
5 269 ms 260 ms 275 ms 213.175.184.193
6 329 ms 322 ms 298 ms 212.36.211.33
7 * * * Request timed out.
8 517 ms 496 ms 487 ms 12.118.94.61
9 415 ms 419 ms 422 ms cr2.n54ny.ip.att.net [12.122.130.166]
10 401 ms 377 ms 422 ms cr2.wswdc.ip.att.net [12.122.3.38]
11 450 ms * 454 ms 12.122.134.149
12 453 ms 497 ms 458 ms 12.88.155.14
13 444 ms 469 ms 432 ms 216.239.48.108
14 416 ms 487 ms 540 ms 66.249.95.149
15 471 ms * 497 ms 209.85.254.247
16 541 ms 525 ms * 209.85.255.190
17 536 ms 498 ms 478 ms gw-in-f100.1e100.net [74.125.67.100]
Trace complete.Whoooh, already 300ms lag to reach IDM gateway ~!
I was just trying to check if someone is getting less than 35ms on the first hop after the router IP. Couldnt get less than 35ms.
I was just trying to check if someone is getting less than 35ms on the first hop after the router IP. Couldnt get less than 35ms.
My latency with IDM is very unstable take a look at those trace routes to bbc and google that I had some days ago (the day I posted about my weird latencies topic) :
D:\Documents and Settings\Administrator>tracert -d bbc.co.uk
Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:
1 22 ms 30 ms 29 ms 192.168.1.254
2 12 ms 12 ms 12 ms 10.151.144.1
3 14 ms 14 ms 16 ms 172.50.1.4
4 12 ms 12 ms 12 ms 10.0.1.26
5 17 ms 21 ms 17 ms 213.175.184.193
6 14 ms 12 ms 17 ms 212.36.211.33
7 * * * Request timed out.
8 137 ms 131 ms 121 ms 12.118.94.93
9 125 ms 121 ms 125 ms 12.122.130.166
10 130 ms 138 ms 140 ms 12.122.130.29
11 139 ms 135 ms 168 ms 192.205.34.54
12 130 ms 131 ms 127 ms 80.91.248.145
13 124 ms 128 ms 130 ms 80.91.248.202
14 145 ms 143 ms 146 ms 80.91.249.170
15 152 ms 142 ms 129 ms 213.248.104.70
16 130 ms 139 ms 136 ms 212.58.238.133
17 128 ms 143 ms 147 ms 212.58.224.138
Trace complete.
D:\Documents and Settings\Administrator>ping bbc.co.uk
Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=145ms TTL=107
Reply from 212.58.224.138: bytes=32 time=134ms TTL=107
Reply from 212.58.224.138: bytes=32 time=143ms TTL=107
Reply from 212.58.224.138: bytes=32 time=129ms TTL=107
Ping statistics for 212.58.224.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 129ms, Maximum = 145ms, Average = 137ms
D:\Documents and Settings\Administrator>tracert -d google.com
Tracing route to google.com [74.125.53.100]
over a maximum of 30 hops:
1 26 ms 31 ms 30 ms 192.168.1.254
2 14 ms 13 ms 13 ms 10.151.144.1
3 46 ms 38 ms 38 ms 172.50.1.4
4 20 ms 30 ms 34 ms 10.0.1.26
5 46 ms 40 ms 49 ms 213.175.184.193
6 18 ms 20 ms 20 ms 212.36.211.33
7 * * * Request timed out.
8 143 ms 124 ms 150 ms 12.118.94.97
9 156 ms 149 ms 167 ms 12.122.131.166
10 147 ms 150 ms 151 ms 12.122.1.2
11 173 ms 169 ms 150 ms 12.122.31.130
12 173 ms 142 ms 141 ms 12.122.146.153
13 149 ms 153 ms 158 ms 12.89.209.14
14 169 ms 177 ms 173 ms 209.85.249.34
15 173 ms 182 ms 162 ms 209.85.250.126
16 146 ms 145 ms 151 ms 216.239.48.34
17 180 ms * 442 ms 64.233.174.123
18 527 ms 333 ms 160 ms 72.14.232.6
19 165 ms 171 ms 178 ms 74.125.53.100
Trace complete.There must be that they have put you on a FASTPATH channel by mistake as ive been reading about that yesterday. Still not sure. I need to check with you guys the latency on DSL of the first hop after your router IPs.