Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=174032.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2005-11-23T23:00:36+00:00 Ian wrote:

>From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 
Fedora/1.7.12-1.5.1

Description of problem:
In some cases, tracepath continues tracing although it has already reached the 
intended destination host.  For example:

[vaj4088@coyote ~]$ tracepath 24.221.130.104
 1:  192.168.0.241 (192.168.0.241)                          0.314ms pmtu 1500
 1:  firewall (192.168.0.250)                               0.578ms
 2:  10.253.1.1 (10.253.1.1)                              asymm  3  84.814ms
 3:  aztutmrt01.az.sprintbbd.net (24.221.129.1)           asymm  2  93.968ms
 4:  <deleted> (24.221.130.104)                       asymm  5 162.687ms
 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
[vaj4088@coyote ~]$  

tracepath should have stopped at the line labeled "4:", but continued
on.

<deleted> is a name from my /etc/hosts file that has been deleted to
protect the name of an innocent bystander.

Version-Release number of selected component (if applicable):
iputils-20020927-22

How reproducible:
Always

Steps to Reproduce:
My example shows how I reproduce the problem.  Networks being what they are, I 
don't know how to reproduce it in your circumstances.
  

Actual Results:  See description.

Expected Results:  Should have looked something like:

[vaj4088@coyote ~]$ tracepath 24.221.130.104
 1:  192.168.0.241 (192.168.0.241)                          0.314ms pmtu 1500
 1:  firewall (192.168.0.250)                               0.578ms
 2:  10.253.1.1 (10.253.1.1)                              asymm  3  84.814ms
 3:  aztutmrt01.az.sprintbbd.net (24.221.129.1)           asymm  2  93.968ms
 4:  <deleted> (24.221.130.104)                       asymm  5 162.687ms
     Resume: pmtu 1500 hops 4 back 3
[vaj4088@coyote ~]$  


Additional info:

Note that the following works fine:

[vaj4088@coyote ~]$ tracepath 24.221.129.1
 1:  192.168.0.241 (192.168.0.241)                          0.342ms pmtu 1500
 1:  firewall (192.168.0.250)                               0.581ms
 2:  10.253.1.1 (10.253.1.1)                              asymm  3 121.557ms
 3:  aztutmrt01.az.sprintbbd.net (24.221.129.1)           asymm  2 223.267ms 
reached
     Resume: pmtu 1500 hops 3 back 2
[vaj4088@coyote ~]$

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/416150/comments/0

------------------------------------------------------------------------
On 2006-06-27T18:38:36+00:00 Daniel wrote:

Created attachment 131624
This patch changes the default destination port number to 33434 (which was 
assigned by IANA for tracerouting) and fixes the bug in a simple but functional 
way :]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/416150/comments/1

------------------------------------------------------------------------
On 2006-07-02T23:06:31+00:00 Ian wrote:

(In reply to comment #1)
> This patch changes the default destination port number to 33434 (which was
> assigned by IANA for tracerouting) and fixes the bug in a simple but 
> functional
> way :]
> 

Dan -
Thanks for the effort, but I can set the port number on the command line and I
still get the same result if I choose 33434 as the port number.
This is using Fedora Core 5, which takes the command as
tracepath 24.221.130.104/33434

I think that the root cause needs to be understood and corrected.
Thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/416150/comments/2

------------------------------------------------------------------------
On 2006-07-03T10:41:13+00:00 Daniel wrote:

(In reply to comment #2)
> (In reply to comment #1)
> > This patch changes the default destination port number to 33434 (which was
> > assigned by IANA for tracerouting) and fixes the bug in a simple but 
functional
> > way :]
> > 
> 
> Dan -
> Thanks for the effort, but I can set the port number on the command line and I
> still get the same result if I choose 33434 as the port number.
> This is using Fedora Core 5, which takes the command as
> tracepath 24.221.130.104/33434
> 
> I think that the root cause needs to be understood and corrected.
> Thanks!

Yes, I know that the port number is not a solution to your problem. It's only 
another bug that the patch fixes. The patch makes more changes in the code of 
tracepath. Please apply the patch first and then test it again.
It works for me:

mildew> patch -p1 < ../iputils-20020927-trace_stop.patch
patching file tracepath.c
...
mildew> ./tracepath 24.221.130.104
...
...
20:  sl-bb22-stk-15-0.sprintlink.net (144.232.4.242)      asymm 16 218.962ms
21:  sl-bb22-stk-15-0.sprintlink.net (144.232.4.242)      asymm 16 217.624ms
22:  sl-bb23-sj-10-0.sprintlink.net (144.232.20.113)      asymm 15 216.131ms
23:  sl-bbwl-4-0-0.sprintlink.net (144.228.111.42)        asymm 16 252.138ms
24:  cpe-24-221-130-104.az.sprintbbd.net (24.221.130.104) asymm 19 274.079ms 
reached
     Resume: pmtu 1500 hops 24 back 19

I think the root cause is not in tracepaht but in the reply from 24.221.130.104 
(it sends "host unreachable" instead of "connection refused")
btw. traceroute has the same problem with this machine.


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/416150/comments/3

------------------------------------------------------------------------
On 2006-07-10T07:29:07+00:00 Radek wrote:

Patch applied on rawhide, thanks a lot

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/416150/comments/4

------------------------------------------------------------------------
On 2006-08-13T14:29:27+00:00 Daniel wrote:

Created attachment 134099
New option -c, default UDP port change

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/416150/comments/5

------------------------------------------------------------------------
On 2006-08-22T02:47:52+00:00 Ian wrote:

The addition of an option to control stopping makes sense to me (but why 'c'?).
I do not have a development environment for testing the patch, so I am unable to
confirm or deny its correctness.
Thanks for your efforts!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/416150/comments/6

------------------------------------------------------------------------
On 2006-08-22T07:37:49+00:00 Martin wrote:

I applied this patch, tested it, and it works nice. Thank you Dan.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/416150/comments/7

------------------------------------------------------------------------
On 2006-08-23T22:09:38+00:00 Daniel wrote:

(In reply to comment #6)
> The addition of an option to control stopping makes sense to me (but why 
> 'c'?).
> I do not have a development environment for testing the patch, so I am unable 
> to
> confirm or deny its correctness.
> Thanks for your efforts!

c -> compare :]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/416150/comments/8


** Changed in: iputils (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/416150

Title:
  [enhancement] change default port

Status in iputils package in Ubuntu:
  New
Status in iputils package in Fedora:
  Fix Released

Bug description:
  Not really a bug, but I found tracepath's output to be pretty
  inaccurate, with lots of "no reply"-replies.

  This led me to the bug-report on
  https://bugzilla.redhat.com/show_bug.cgi?id=174032 which states that
  changing the port for tracepath to 33434 because it "...was assigned
  by IANA for tracerouting..." fixed this behaviour.

  I'd suggest to incorporate the patches from this report if possible,
  though I made one _very_ unobtrusive that just changes the default
  port, which worked for me.

  Please either update this package for karmic (if that fixes this) or
  add this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/416150/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to