Public bug reported:
Binary package hint: tcptraceroute
When you upgrade (In my case from Gutsy to Hardy) tcptraceroute is not
installed. A replacement script (follow the symlinks time)
[EMAIL PROTECTED]:~$ which tcptraceroute
/usr/bin/tcptraceroute
[EMAIL PROTECTED]:~$ ls -l /usr/bin/tcptraceroute
lrwxrwxrwx 1 root root 31 2008-06-18 15:48 /usr/bin/tcptraceroute ->
/etc/alternatives/tcptraceroute
[EMAIL PROTECTED]:~$ ls -l /etc/alternatives/tcptraceroute
lrwxrwxrwx 1 root root 25 2008-06-18 15:48 /etc/alternatives/tcptraceroute ->
/usr/bin/tcptraceroute.db
If I do an 'aptitude reinstall tcptraceroute' I get the proper working
version:
[EMAIL PROTECTED]:~$ ls -l /usr/bin/tcptraceroute
-rwsr-xr-x 1 root root 28156 2007-04-30 04:47 /usr/bin/tcptraceroute
The format of the command in the /usr/bin/tcptraceroute.db command for a
tcptraceroute does *not* follow correct tcptraceroute format either so
it's not currently safe to swap in. First off the upgrade script
(/usr/bin/tcptraceroute.db) requires root, full tcptraceroute does not
as it's setuid.
Also trying to run a command similar to tcptraceroute host port
does not correspond to how they are calling it within the
/usr/bin/tcptraceroute.db script: Something which should be similar (based on
limited testing)
sudo /usr/bin/traceroute.db -T 10.0.28.2 30 -n -P tcp -p 311
But this result sin a lot of this:
[EMAIL PROTECTED]:~$ sudo /usr/bin/traceroute.db -T 10.0.28.2 30 -P tcp -p 311
traceroute to 10.0.28.2 (10.0.28.2), 30 hops max, 30 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 *
Which just ends up timing out and still does not seem to use (in this case)
port 311. I think if people are calling tcptraceroute from scripts or command
line they are expecting same and *working* functionality from the tool.
I don't want to come of pretty harsh or ungreatful in this but it really
doesn't do what it says on the tin. Running the same command which times
out above after perfomring a reinstall to the *real* version of
tcptraceroute gives this(An far faster too):
[EMAIL PROTECTED]:~$ tcptraceroute 10.0.28.2 311
Selected device eth0, address 10.255.50.242, port 38490 for outgoing packets
Tracing the path to 10.0.28.2 on TCP port 311, 30 hops max
1 10.255.50.1 0.477 ms 0.419 ms 0.402 ms
2 172.29.5.145 1.307 ms 1.292 ms 0.788 ms
3 172.34.2.181 1.029 ms 1.064 ms 1.004 ms
4 10.254.28.2 3.686 ms 10.001 ms 9.999 ms
5 10.0.28.2 [open] 1.072 ms 1.445 ms 1.060 ms
And it finishes perfectly...
Odd thing when you do a reinstall it says it's installed, but clearly
it's not, so not sure if it's some sort of meta-placeholder
(terminology?) pretending to be the same version.
Preparing to replace tcptraceroute 1.5beta6-2 (using
.../tcptraceroute_1.5beta6-2_amd64.deb) ...
Unpacking replacement tcptraceroute ...
Setting up tcptraceroute (1.5beta6-2) ...
Anyway, apologies if this is long or rambling and I do appreciate the
efforts by you folks.
Thanks,
Félim
** Affects: tcptraceroute (Ubuntu)
Importance: Undecided
Status: New
--
tcptraceroute in Hardy is not "The Real Thing"
https://bugs.launchpad.net/bugs/241586
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
