Traceroute in Network Tools not functioning

[Aviv]

Binary package hint: gnome-nettool

In Jaunty, when doing "Traceroute" in System-->Administration-->Network Tools, tracing the route to a given IP takes infinite time (application is responsive, though), whereas browsing to same IP is OK.
In conclusion: Traceroute fails to trace.

[Pedro Villavicencio (pedro)]

I've traced google.com and that works ok for me, which ip are you testing?

[Aviv (ademorga)]

Any IP, incl. google.com will not respond.

Aviv.

Quoting Pedro Villavicencio <email address hidden>:

> I've traced google.com and that works ok for me, which ip are you
> testing?
>
> ** Changed in: gnome-nettool (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: gnome-nettool (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: gnome-nettool (Ubuntu)
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
>
> --
> Traceroute in Network Tools not functioning
> https://bugs.launchpad.net/bugs/369993
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
"Whereof one cannot speak, thereof one must be silent."

Aviv de Morgan
Laboratory of Computational Biology and Bioinformatics
The Institute of Evolution
Department of Evolutionary Biology and Ecology
University of Haifa, Mt. Carmel
Haifa 31905, Israel
Tel: [phone] (home)
     [phone] (mobile)
     [phone] (lab)
     [phone] (fax)
E-mail: <email address hidden>

------------------------------------------------------------------------
This message was sent using IMP, the Webmail Program of Haifa University

[Antono Vasiljev (antono)]

It fails because of patch changing default tcptraceroute to tracepath for ubuntu (and porobably debian).

And tracepaths seems broken:

$ traceroute github.com

traceroute to github.com (207.97.227.239), 30 hops max, 60 byte packets
 1 192.168.1.1 (192.168.1.1) 1.349 ms 5.258 ms 5.175 ms
 2 178.126.128.1 (178.126.128.1) 57.997 ms 59.468 ms 61.402 ms
 3 mm-123-80-84-93.dynamic.pppoe.mgts.by (93.84.80.123) 64.205 ms 65.643 ms 67.261 ms
 4 10.240.8.129 (10.240.8.129) 68.825 ms 70.642 ms 72.560 ms
 5 core.10g.net.belpak.by (93.84.122.41) 74.976 ms 76.786 ms 78.258 ms
 6 te2-4.l3-core-2.mck.net.belpak.by (93.84.125.2) 80.437 ms 56.155 ms 56.428 ms
 7 po31.l3-gw-2.mck.net.belpak.by (193.232.249.76) 59.123 ms 60.627 ms 62.336 ms
 8 83.229.241.121 (83.229.241.121) 95.582 ms 97.420 ms 100.002 ms
 9 83.229.226.101 (83.229.226.101) 100.714 ms 96.211 ms msk-b4-hq-ae0.main.synterra.ru (83.229.225.5) 98.077 ms
10 ae7.RT.MR.MSK.RU.retn.net (87.245.253.169) 109.185 ms 110.601 ms 112.515 ms
11 xe000-8.RT.EQX.ASH.US.retn.net (87.245.233.118) 249.085 ms 249.955 ms 249.832 ms
12 * * *
13 edge3.iad.rackspace.net (207.235.17.129) 219.433 ms 220.859 ms 223.582 ms
14 vlan905.core5.iad2.rackspace.net (72.4.122.10) 224.971 ms 226.626 ms 227.579 ms
15 aggr301a-1-core5.iad2.rackspace.net (72.4.122.121) 229.892 ms 235.406 ms 235.425 ms
16 github.com (207.97.227.239) 235.836 ms 217.763 ms 219.882 ms

tracepath github.com
 1: 192.168.1.11 0.188ms pmtu 1500
 1: 192.168.1.1 2.015ms asymm 2
 1: 192.168.1.1 1.604ms asymm 2
 2: no reply
 3: no reply
 4: no reply
 5: no reply
 6: no reply
 7: no reply
 8: no reply
 9: no reply
10: no reply
11: no reply
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
31: no reply
     Too many hops: pmtu 1500
     Resume: pmtu 1500

[Antono Vasiljev (antono)]

It seems related to iputils-tracepath but:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/586256

[Antono Vasiljev (antono)]

It can be fixed by dropping tracepath patch and usage of simple tracepath witch seems to work from non root accounts.

[Antono Vasiljev (antono)]

Another option (according to bug#586256) is decreasing package size via tracepath command line:

tracepath -l 1000 github.com
 1: 192.168.1.1 1.550ms asymm 2
 2: 178.126.128.1 68.094ms
 3: mm-123-80-84-93.dynamic.pppoe.mgts.by 68.589ms
 4: 10.240.8.129 68.310ms
 5: core.10g.net.belpak.by 68.788ms
 6: te2-4.l3-core-2.mck.net.belpak.by 69.150ms
 7: po31.l3-gw-2.mck.net.belpak.by 83.705ms asymm 6
 8: 83.229.241.121 110.549ms asymm 6
 9: 83.229.226.101 93.560ms asymm 6
10: ae7.RT.MR.MSK.RU.retn.net 102.780ms asymm 6
11: xe000-8.RT.EQX.ASH.US.retn.net 230.745ms asymm 6
12: no reply
13: edge3.iad.rackspace.net 229.209ms asymm 6
14: vlan905.core5.iad2.rackspace.net 229.259ms asymm 6
15: aggr301a-1-core5.iad2.rackspace.net 230.991ms asymm 6
16: github.com 233.131ms reached
     Resume: pmtu 1000 hops 16 back 250

[Antono Vasiljev (antono)]

working on patch

[Antono Vasiljev (antono)]

Updated 03_use_tracepath.patch

[Antono Vasiljev (antono)]

someone please test this patch

[Antono Vasiljev (antono)]

You can take improved package from my PPA

https://launchpad.net/~antono/+archive/fixes

[Aviv (ademorga)]

Thanks, I'll do that!

On Fri, Feb 11, 2011 at 12:54 AM, Antono Vasiljev <<email address hidden>
> wrote:

> You can take improved package from my PPA
>
> https://launchpad.net/~antono/+archive/fixes<https://launchpad.net/%7Eantono/+archive/fixes>
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/369993
>
> Title:
> Traceroute in Network Tools not functioning
>

[john morimore (paradigmshifter1)]

It is actually very important as I am quite sure it has been manipulated..(it has occured before.....

[Antono Vasiljev (antono)]

Whell. It's still an issue in Oneiric. Someone from Desktop Team should apply my patch.
Anyone?

[Antono Vasiljev (antono)]

I provided patch but need someone from Desktop Team to apply it to the package.

[Rodrigo Moya (rodrigo-moya)]

This doesn't work for me, ditto if I run in the command line:

$ /usr/bin/tracepath -l 1000 www.google.com
 1: 192.168.0.1 1.896ms
 2: no reply
 3: no reply
....

[Rodrigo Moya (rodrigo-moya)]

Note that with the previous patch, it failed also, so yes, we need a fix.

[Antono Vasiljev (antono)]

Not sure what was wrong with native traceroute. Probably it will work without tracepath patch?

[Rodrigo Moya (rodrigo-moya)]

it's not installed by default, so there's a reason why we have to patch it. Not sure though why, anyone knows?

[Antono Vasiljev (antono)]

man of tracepath mentions that in contrast with traceroute it does NOT require
root privilegies. Probably at some point in time it was true, but
currently i use
traceroute without root privilegies.
The patch was introduced by Dan Holbach on Mon, 12 Jun 2006 15:17:53 +0200
https://launchpad.net/ubuntu/+source/gnome-nettool/+changelog
Dan mentions distro decision about tracepath but google says nothing
about why tracepath
was chosen. And tracepath is broken currently. At least 2 releases
Natty and Oneiric.

On Fri, Sep 23, 2011 at 14:29, Rodrigo Moya <email address hidden> wrote:
>
> it's not installed by default, so there's a reason why we have to patch
> it. Not sure though why, anyone knows?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/369993
>
> Title:
>  Traceroute in Network Tools not functioning
>
> Status in “gnome-nettool” package in Ubuntu:
>  In Progress
>
> Bug description:
>  Binary package hint: gnome-nettool
>
>  In Jaunty, when doing "Traceroute" in System-->Administration-->Network Tools, tracing the route to a given IP takes infinite time (application is responsive, though), whereas browsing to same IP is OK.
>  In conclusion: Traceroute fails to trace.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/369993/+subscriptions

--
http://antono.info/