![]() |
tracert on xterminal?
i found that ping and nslookup there but traceroute not. is it different command or not exist on maemo5.
also what are the other usefull commands? thanks |
Re: tracert on xterminal?
I think you need to install it, can't remember which repo it was in, but the command to invoke it is the full "traceroute foo.com".
|
Re: tracert on xterminal?
|
Re: tracert on xterminal?
Quote:
|
Re: tracert on xterminal?
You need to activate another repo, I think.
See the links in my post here: http://talk.maemo.org/showthread.php...473#post433473 for how to do that. Edit: actually, it's best to do this where you can, because install via dpkg doesn't apply the rules that delete stuff installed into /usr/share/doc/ as apt-get and the package manager do. If you do install via dpkg, take a look at /var/lib/dpkg/info/<package>.list and see what's been put where. With rootfs space so critical, it pays to be very careful.. Anyway, if you install the tools repo, I think you should see stuff like traceroute returned from apt-cache search. |
Re: tracert on xterminal?
Just for lolz, try to copy over the tracert program from a desktop distro
I'll upload one if you don't have it |
Re: tracert on xterminal?
Quote:
|
Re: tracert on xterminal?
if you enable tools repo http://wiki.maemo.org/Documentation/devtools/maemo5 you should be able to see it with apt-cache search and install it with apt-get
|
Re: tracert on xterminal?
Quote:
|
Re: tracert on xterminal?
hav a look at http://maemo.kluenter.de
there is mtr-tiny in that repository which is far better than traceroute. I built it and it works great. But be careful. This is my personal repository. Ther is some crap in there too. |
Re: tracert on xterminal?
Quote:
|
Re: tracert on xterminal?
Yeah, I noticed that too.
Never mind! apt-cache search <pkg> and apt-get install <pkg> work fine in the terminal. |
Re: tracert on xterminal?
Quote:
|
Re: tracert on xterminal?
1 Attachment(s)
Quote:
"apt-get install mtr-tiny" I don't know what to do to make them show up in HAM Attachment 5146 |
Re: tracert on xterminal?
i have installed mtr-tiny but how do you call it? mrt-tiny says not found on xterminal
up: got it just mtr |
Re: tracert on xterminal?
Quote:
|
Re: tracert on xterminal?
I found out how to make packages which show up in the application manager. mtr-tiny and iproute can now be installed with your thumb
|
Re: tracert on xterminal?
Quote:
in the fremantle/sdk repository. Add this to your apt/sources.list: deb http://repository.maemo.org/ fremantle/sdk free non-free Update: I tried this, and it does _NOT_ work. Don't use this on your device. It is only useful in your SDK |
Re: tracert on xterminal?
Quote:
|
Re: tracert on xterminal?
Quote:
EDIT: Too bad, I would really like Locate! |
Re: tracert on xterminal?
Quote:
It is not optified and is bigger. mtr-tiny works. |
Re: tracert on xterminal?
Quote:
|
Re: tracert on xterminal?
Quote:
The reverse name of talk.maemo.org is simply reggiesuplido.com. |
Re: tracert on xterminal?
Quote:
And if you're in DE, than I will surely be more than 8 hops to Texas, ehhh? |
Re: tracert on xterminal?
Quote:
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 :-). |
Re: tracert on xterminal?
Quote:
|
Re: tracert on xterminal?
Quote:
|
Re: tracert on xterminal?
Quote:
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? |
Re: tracert on xterminal?
how do i get tracert to work on my n900`?
thx |
Re: tracert on xterminal?
You could try spelling it properly. It is called traceroute on sensible operating systems :)
|
Re: tracert on xterminal?
Quote:
sh: traceroute: not found please help.... thx |
Re: tracert on xterminal?
bump
someone? |
Re: tracert on xterminal?
the package is in the tools-repository. You can install it via terminal. Become root an type: "apt-get install traceroute"
Before, you have to be sure to have the tools-repository enabled. Catalog Name: fremantle-tools Web Address: http://repository.maemo.org Distribution: fremantle/tools Components: free non-free |
Re: tracert on xterminal?
Quote:
|
Re: tracert on xterminal?
Tanks a lot so far for this thread.
I installed now several tracerouting applications. Including traceroute and mtr-tiny. But I have a problem: I'm trying to get the IP Adress of my WiFi Router using such a traceroute tool. But for me is only the local IP Adress of my Router (192.168.0.1) visible and not the IP Adress my Router has from the outside. The one I got from my Provider. :confused: In the traceroute utility is this IP Adress simply not listed. Hmm... I guess this is correct and I have simply not understand how my router works before I began trying to get this IP. So, is there a way to see this IP Adress of my Router without logging into the webcontrol? I want to access via SSH to my N900 while it is connected to a different W-Lan. But I need the IP adress before. :D |
Re: tracert on xterminal?
Quote:
1) Click this linkhttp://www.whatismyip.com/ 2) Come back here and hit the Thanks button! |
Re: tracert on xterminal?
Quote:
Sometimes my way of thinking is simply to complicated. Thanks a lot! :D |
Re: tracert on xterminal?
Quote:
Your Ethernet interface on your Router has an inner and an outer interface(as well as inner and outer IP addresses). If the packets originate inside your network, they will only see the inner interface on the way out, not the outer interface. That's why Traceroute was not your answer. |
Re: tracert on xterminal?
I added this to my ~/.bashrc (or ~/.profile depending):
netip() { curl -s checkip.dyndns.com | grep -o "[[:digit:].]\+"; } Then I can just run: $ netip :P |
All times are GMT. The time now is 01:08. |
vBulletin® Version 3.8.8