mtr uses X and currently does not really work on N900.
It is not optified and is bigger.

mtr-tiny works.

I'm confused what you do with MTR here. It goes 8 hops and stops?

I did a "mtr talk.maemo.org" and the 8th hop is talk.maemo.org.
The reverse name of talk.maemo.org is simply reggiesuplido.com.

Try something else, also do a Traceroute to talk.maemo.org I bet it's more than 8 hops. It seems like MTR is showing just 8 hops for everything, or it just stops at 8 hops wherever it is at. Can you get it to do more than 8 hops. I did a traceroute to talk.maemo.org and it was 15 hops from me. Most folks will have more than 8 hops just to get out of their ISPs network.

And if you're in DE, than I will surely be more than 8 hops to Texas, ehhh?

I tried other destinations, and after 13 hops, the screen is full and everything later is not shown. I also did a traceroute to talk.maemo.org. It doesn't look that much different. Except that the last hop does not send icmp-time-exceeded messages. Firewalls ...

traceroute to forums.internettablettalk.com (74.86.202.247), 64 hops max, 52 byte packets
1 tiny.inferno.nadir.org (192.168.43.1) 2 ms 4 ms 3 ms
2 lo1.br04.asham.de.hansenet.net (213.191.84.203) 21 ms 20 ms 20 ms
3 ae1-104.pr05.asham.de.hansenet.net (62.109.119.10) 20 ms 20 ms 20 ms
4 amb1-hansenet-3.amb.seabone.net (89.221.35.29) 20 ms 41 ms 20 ms
5 te1-2-10G.ar3.HAM1.gblx.net (64.208.110.105) 20 ms 19 ms 20 ms
6 te1-1.cer03.dal01.dallas-datacenter.com (64.215.81.2) 142 ms 141 ms 142 ms
7 po3.dar02.dal01.dallas-datacenter.com (66.228.118.211) 174 ms 140 ms 139 ms
8 po2.fcr03.dal01.dallas-datacenter.com (66.228.118.190) 140 ms 139 ms 140 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *

hop 5 is still hamburg, but hop 6 is already dallas. And these two hops are more than 100ms away. Thats the atlantic :-).

I'm not sure I'm following you here, so let's start over. MTR, if it can't show more than 8 hops is useless to me. I would use traceroute. It's like going to mapquest or google maps and asking for Turn by turn instructions for a destination and only getting 8 out of X turns.

You are right. MTR can currently only show the first 13 rows because the display of the N900 is rather small. But the point is, that mtr can show you much more than a single traceroute. And I usually don't have so many hops. It was hard for me to find some paths that were long enough. But this is just a question of taste I think

who cares about how many Rows? It only can resolve 8 hops. I don't know where you surf to but let me just show a few to you:
C:\Users\les>tracert www.yahoo.com

Tracing route to www-real.wa1.b.yahoo.com [69.147.76.15]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms pfsense.local [192.168.0.1]
2 * * * Request timed out.
3 14 ms 11 ms 7 ms 68.86.161.49
4 9 ms 10 ms 8 ms te-9-4-ur01.stluciewest.fl.pompano.comcast.net [
68.86.165.213]
5 10 ms 8 ms 11 ms te-9-4-ur01.ftpierce.fl.pompano.comcast.net [68.
86.165.205]
6 12 ms 15 ms 9 ms te-8-4-ur01.stuart.fl.pompano.comcast.net [68.86
.165.133]
7 24 ms 22 ms 22 ms 68.86.165.50
8 51 ms 47 ms 48 ms pos-0-10-0-0-cr01.charlotte.nc.ibone.comcast.net
[68.86.90.189]
9 53 ms 51 ms 49 ms pos-2-8-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.85.213]
10 51 ms 45 ms 58 ms pos-0-0-0-0-pe01.56marietta.ga.ibone.comcast.net
[68.86.86.82]
11 56 ms 54 ms 53 ms Vlan502.icore1.A56-Atlanta.as6453.net [209.58.44
.1]
12 45 ms 44 ms 45 ms if-7-0-0-60.har1.A56-Atlanta.as6453.net [64.86.8
.17]
13 61 ms 62 ms 76 ms if-13-0-0-1173.core3.AEQ-Ashburn.as6453.net [64.
86.9.26]
14 61 ms 63 ms 68 ms ix-14-2.core3.AEQ-Ashburn.as6453.net [63.243.149
.110]
15 64 ms 62 ms 61 ms ae-6.pat1.dcp.yahoo.com [216.115.102.174]
16 94 ms 61 ms 66 ms ae2-p170.msr2.re1.yahoo.com [216.115.108.69]
17 61 ms 61 ms 61 ms te-8-1.bas-a1.re1.yahoo.com [66.196.112.205]
18 61 ms 61 ms 66 ms f1.www.vip.re1.yahoo.com [69.147.76.15]

C:\Users\les>tracert www.newegg.com

Tracing route to www.newegg.com [216.52.208.185]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms pfsense.local [192.168.0.1]
2 * * * Request timed out.
3 9 ms 12 ms 11 ms 68.86.161.49
4 10 ms 7 ms 8 ms te-9-4-ur01.stluciewest.fl.pompano.comcast.net [
68.86.165.213]
5 20 ms 10 ms 13 ms te-9-4-ur01.ftpierce.fl.pompano.comcast.net [68.
86.165.205]
6 9 ms 8 ms 9 ms te-8-4-ur01.stuart.fl.pompano.comcast.net [68.86
.165.133]
7 23 ms 22 ms 22 ms 68.86.165.50
8 65 ms 60 ms 45 ms pos-0-10-0-0-cr01.charlotte.nc.ibone.comcast.net
[68.86.90.189]
9 46 ms 56 ms 45 ms pos-2-9-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.85.225]
10 46 ms 47 ms 46 ms te-4-3.car1.Atlanta2.Level3.net [4.71.252.25]
11 181 ms 47 ms 52 ms ae-62-51.ebr2.Atlanta2.Level3.net [4.68.103.29]

12 57 ms 50 ms 53 ms ae-73-70.ebr3.Atlanta2.Level3.net [4.69.138.20]

13 68 ms 72 ms 72 ms ae-7.ebr3.Dallas1.Level3.net [4.69.134.21]
14 155 ms 107 ms 109 ms ae-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]
15 155 ms 99 ms 100 ms ae-31-80.car1.LosAngeles1.Level3.net [4.69.144.1
31]
16 101 ms 99 ms 106 ms INTERNAP-NE.car1.LosAngeles1.Level3.net [4.71.14
0.54]
17 315 ms 109 ms 199 ms border2.po1-4g-bbnet1.ext1a.lax.pnap.net [216.52
.255.32]

C:\Users\les>tracert www.mozilla.org

Tracing route to www-mozilla-org.glb.mozilla.net [63.245.209.11]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms pfsense.local [192.168.0.1]
2 * * * Request timed out.
3 10 ms 14 ms 8 ms 68.86.161.49
4 9 ms 9 ms 10 ms te-9-4-ur01.stluciewest.fl.pompano.comcast.net [
68.86.165.213]
5 119 ms 9 ms 9 ms te-9-4-ur01.ftpierce.fl.pompano.comcast.net [68.
86.165.205]
6 159 ms 9 ms 10 ms te-8-4-ur01.stuart.fl.pompano.comcast.net [68.86
.165.133]
7 24 ms 31 ms 22 ms ge-3-1-0-ar03.augusta.ga.augusta.comcast.net [68
.86.165.54]
8 85 ms 46 ms 47 ms pos-0-10-0-0-cr01.charlotte.nc.ibone.comcast.net
[68.86.90.189]
9 46 ms 47 ms 46 ms pos-2-9-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.85.225]
10 95 ms 45 ms 47 ms te-3-3.car1.Atlanta2.Level3.net [4.71.252.1]
11 186 ms 52 ms 54 ms ae-63-51.ebr3.Atlanta2.Level3.net [4.68.103.30]

12 175 ms 72 ms 70 ms ae-7.ebr3.Dallas1.Level3.net [4.69.134.21]
13 112 ms 107 ms 111 ms ae-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]
14 * 113 ms 110 ms ae-2.ebr2.SanJose1.Level3.net [4.69.132.13]
15 119 ms 110 ms 109 ms ae-82-82.csw3.SanJose1.Level3.net [4.69.134.218]

16 116 ms 110 ms 109 ms ae-3-89.edge8.SanJose1.Level3.net [4.68.18.148]

17 112 ms 112 ms 111 ms CWIE-LLC.edge8.SanJose1.Level3.net [4.53.30.86]

18 114 ms 113 ms 112 ms v9.core2.sj.mozilla.com [63.245.208.58]
19 111 ms 112 ms 120 ms moz.org01.nslb.sj.mozilla.com [63.245.209.11]

There is basically nothing that is anywhere near only 8 hops away. I use traceroute as a diagnostic tool and only seeing 30-50% of the Hops is useless, no matter how pretty it is. I didn't parse for routes that were long, I don't have to. I'll BET that if I give you ten random websites to trace, that they all come up with an average of around 15-20 hops.

There isn't a way to run all the lines out so you can scroll through them?

how do i get tracert to work on my n900`?

thx

You could try spelling it properly. It is called traceroute on sensible operating systems