Bug#1055978: mtr-tiny: traceroute does not stop on subnet router anycast addresses

  0.0 > 28. 2001:db8:0:2::2                                                           > 0.0%     1    1.2   1.2   1.2   1.2   0.0 > 29. 2001:db8:0:2::2                                                           > 0.0%     1    1.4   1.4   1.4   1.4   0.0 > 30. 2001:db8:0:2::2                                                  

Bug#1055978: mtr-tiny: traceroute does not stop on subnet router anycast addresses

Hi, I'd say this is an unwanted side-effect rather than a bug. I'd say the "end-detection" might also consider three times the same host responding to be considerd as "the end". Originally the TTL, that is now "hop counter" was the "number of seconds in the network". Thus if there was a

Bug#967647: mtr: depends on deprecated GTK 2

For Debian I then need to create a release I think. I'll try to do that soon. Thanks for testing. Roger. On Fri, May 20, 2022 at 12:20:29PM +0200, Jordi Mallach wrote: > Package: mtr > Version: 0.95-1 > Followup-For: Bug #967647 > > Hi, > > I just tested a build for this and I can

Bug#999730: mtr: Fix FTBFS with glib2.0 >= 2.70 and deprecated GTimeVal of gtk+2.0

Hi, I've accepted a patch into upstream that fixes the format errors. Roger. On Mon, Nov 15, 2021 at 05:21:45PM +0100, Lukas Märdian wrote: > Package: mtr > Version: 0.94-2 > Severity: serious > Tags: patch ftbfs > Justification: fails to build from source (but built successfully

Bug#997194: mtr: FTBFS: ../ui/curses.c:435:17: error: format not a string literal and no format arguments [-Werror=format-security]

On Sat, Oct 23, 2021 at 09:07:10PM +0200, Lucas Nussbaum wrote: > Source: mtr > Version: 0.94-2 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs That's an error in your compiler. A printf-like function often has a string litteral specifying the format printf ("a = %d\n",

Bug#918778: closed by Guillem Jover (Re: Bug#918778: dpkg does not report all files to be overwritten.)

Well, in my case, the ARM compiler in the distribution (Ubuntu) stopped working (from 16.04 to 18.04). So I had to install a third party ARM compiler .deb . I was going to argue that packaging error can be avoided if there would be an easy tool that scans an entire repository for duplicate

Bug#839879: mtr FTCBFS: uses build architecture tools

On Sat, Sep 30, 2017 at 10:32:04AM +0200, Manuel A. Fernandez Montecelo wrote: > 2017-09-30 3:39 GMT+02:00 Robert Woodcock : > > On 09/28/2017 06:41 PM, Manuel A. Fernandez Montecelo wrote: > > > > Samuel and I are working on releasing 0.92 - I'll make sure that this is > > in

Bug#840563: mtr: New 0.87 release fixes issue with paths with long gaps

On Sat, Oct 15, 2016 at 01:00:28AM -0400, Matthew Gabeler-Lee wrote: > On Thu, 13 Oct 2016, Rogier Wolff wrote: > > >No! Not a "more reasonable" value! An outrageous value! > > > >You have a network where 5 hops-in-a-row don't conform to IP standards.

Bug#840563: mtr: New 0.87 release fixes issue with paths with long gaps

On Wed, Oct 12, 2016 at 03:29:41PM -0400, Matthew Gabeler-Lee wrote: > Package: mtr > Version: 0.86-1+b1 > Severity: wishlist > > A new upstream release 0.87 has a fix (of sorts) for the problem where MTR > will not trace a successful path that has more than five non-responding > hops. I say fix

Bug#839879: mtr FTCBFS: uses build architecture tools

Hi Helmut, Is there anything I need to do in the upstream sources? As far as I can see you patched just the debian build rules, right? Roger. On Thu, Oct 06, 2016 at 05:44:13AM +0200, Helmut Grohne wrote: > Source: mtr > Version: 0.86-1 > Tags: patch > User: helm...@debian.org >

Bug#824142: mtr 0.86 uses suboptimal colours in curses (patch attached)

or1.patch > --- mtr-0.86/debian/patches/color1.patch 1969-12-31 17:00:00.0 > -0700 > +++ mtr-0.86/debian/patches/color1.patch 2016-05-12 12:58:21.0 > -0600 > @@ -0,0 +1,34 @@ > +commit 63a1f1493bfbaf7e55eb7e20b3791fc8b14cf92d > +Author: Rogier Wolff

Bug#789083: mtr_0.85.orig.tar.gz contains .o files

If I remember correctly I once noticed this, fixed it and promptly had the somedistribution guys in my neck: They store a hash of the original distrobuted source in their build-system to make sure that changing the source without changing the version number is detected (or a malicious injection of

Bug#731799: Do not work with IPv4 only anymore

On Sun, Apr 27, 2014 at 04:29:18PM +0200, Jeroen Massar wrote: This seems completely unrelated to mtr or let alone Debian... If your tunnel is broken, then report that to SixXS, there is a nice ticket system at https://www.sixxs.net/tickets/. Do provide actual details instead of making

Bug#731799: Do not work with IPv4 only anymore

configuration. I fully agree with the decisions upstream in debian to enable IPV6. But you should respect those that may have reasons to disable it. On 2014-04-28 09:08, Rogier Wolff wrote: I personally have a good understanding of IPV4 and how I've secured my network against attacks from

Bug#731799: Do not work with IPv4 only anymore

explcitly told to do IPV4 only. I disagree with closing the bug as user-error. Roger. -- +-- Rogier Wolff -- www.harddisk-recovery.nl -- 0800 220 20 20 -- - Datarecovery Services Nederland B.V. Delft. KVK: 30160549 - | Files foetsie, bestanden kwijt, alle data weg?! | Blijf kalm en neem

Bug#731799: Do not work with IPv4 only anymore

, so now we're stuck in mtr with a separate name-resolving code-block which is buggy and difficult to maintain. Roger. -- +-- Rogier Wolff -- www.harddisk-recovery.nl -- 0800 220 20 20 -- - Datarecovery Services Nederland B.V. Delft. KVK: 30160549 - | Files foetsie, bestanden kwijt, alle data weg

Bug#725222: mtr invoked by command line does nothing

On Thu, Oct 03, 2013 at 02:03:08AM -0300, Rogério Brito wrote: I'm attaching (as compressed files) the output of running both `sudo strace mtr` and `sudo strace mtr --curses`. That works. strace shows: // from mtr.c: if ( ( net_preopen_result = net_preopen () ) ) {

Bug#725222: mtr invoked by command line does nothing

On Thu, Oct 03, 2013 at 06:07:42AM -0300, Rogério Brito wrote: It is a common method, indeed. I don't know how/why mtr uses a pseudo-random generator, though, without having read the code (will read that later, if I still have sufficient interest). mtr sends out (crafted, non-regular) packets

Bug#721792: mtr fails without IPv6 socket

Hi James, Yes. This bug is fix committed in the git repository. But I haven't released the next version yet. You can do apt-get build-deps mtr and then clone the git repository and compile: git clone https://github.com/traviscross/mtr.git cd mtr sh bootstrap.sh ; ./configure ; make

Bug#706816: mtr: new upstream version 0.84 available

You mean you want to see a tarball of 0.84 on ftp.bitwizard.nl or do you want oseome else to package the 0.84 from ftp.bitwizard\.nl? Roge On Sun, May 05, 2013 at 11:04:56AM +0200, Johann AMSELLEM wrote: Package: mtr Severity: wishlist Dear Maintainer, MTR 0.84 is available, please

Bug#696060: mtr: StDev overflowed to negative

Hi, The variance, which is used to calculate the stdev, is stored in a 64-bit integer. However, what we store there are the squares of the difference from the average. So if you have 70 second ping time (sometimes), the square of 7 miliseconds becomes 4900 million! Quite a lot, but

Bug#662583: FTBFS

On Mon, Mar 05, 2012 at 08:11:52AM +0100, Moritz Muehlenhoff wrote: Package: mtr Version: 0.82-2 Severity: serious (cd mtr;aclocal;automake --foreign --include-deps Makefile;autoconf) This is the required commandline to satisfy automake. Automake is intended to make the buildprocess of

Bug#654117: Please enabled hardened build flags

Hi, I don't have a debian/rules in my upstream distribution. Should I grab a copy somewhere and start distributing it? Rogier. On Mon, Jan 02, 2012 at 02:31:30AM +0100, Moritz Muehlenhoff wrote: Package: mtr Version: 0.82-1 Severity: important Tags: patch Please enabled

Bug#528992: mtr: No DNS resolution in trace, when only IPv6 transport used (no v4 dns hosts in /etc/resolv.conf

I expect that this is very difficult to fix: mtr implements its own name resolving. It has its own code to contact name servers and such. This is bad software engineering. I've been thinking about a next generation mtr. It will use multiple processes to handle different parts of the mtr

Bug#416567: mostly fixed

On Tue, May 12, 2009 at 12:52:21AM -0700, Ryan Niebur wrote: retitle 416567 make .deb match override quit this bug is already fixed in the override, which is what really matters. however the package needs to be updated to match that. You mean you're changing copyright notices in the debian

Bug#416567: mostly fixed

On Tue, May 12, 2009 at 08:14:44AM -0700, Ryan Niebur wrote: this has nothing to do with copyright at all. the problem is that this I somehow got a link to a page saying that there was a problem with some packages claiming to have Copyright You may copy according to GPL which is

Bug#98482: text dump of current data

On Thu, Mar 05, 2009 at 08:44:45AM +, George B. wrote: Hello, Any chance this feature can be implemented? The report function is not sufficient - need to see stats real time and yet have the option of grabbing a copy of the data - neither the curses interface, nor the GTK one allow

Bug#500141: mtr-tiny: Repeatable error

On Wed, Dec 17, 2008 at 07:46:12AM -0600, Ron Johnson wrote: On 12/17/08 07:35, Rogier Wolff wrote: what message? The same message that the creator of this bug complains about. Well then I have the same answer for you as I had for him. Roger. -- ** r.e.wo...@bitwizard.nl

Bug#500141: mtr-tiny: Repeatable error

what message? This was possibly fixed in the next version. You're having a kenrel withou IPV6? Rogier. On Wed, Dec 17, 2008 at 07:21:22AM -0600, Ron Johnson wrote: Package: mtr-tiny Version: 0.75-2 Followup-For: Bug #500141 I get that same message, too. -- System

Bug#500141: mtr-tiny: Couldn't get fd's flags: Bad file descriptor

On Thu, Sep 25, 2008 at 10:27:14AM -0300, Nelson A. de Oliveira wrote: Package: mtr-tiny Version: 0.75-2 Severity: minor Hi! Probably inoffensive, but with version 0.75 I get this message when using mtr-tiny: Couldn't get fd's flags: Bad file descriptor Hi, This is new code,

Bug#499789: FTBFS: clean target fails: rm: cannot remove `mtr': No such file or directory

Hi, It works here. Maybe you are trying to do make clean within 3 seconds after a make distclean? Roger. On Mon, Sep 22, 2008 at 01:29:48PM +0200, Christoph Berg wrote: Package: mtr Version: 0.75-1 Severity: serious Justification: FTBFS The debian/rules 'clean' target

Bug#499789: FTBFS: clean target fails: rm: cannot remove `mtr': No such file or directory

On Mon, Sep 22, 2008 at 02:16:18PM +0200, Julien Cristau wrote: On Mon, Sep 22, 2008 at 14:09:57 +0200, Rogier Wolff wrote: Hi, It works here. Maybe you are trying to do make clean within 3 seconds after a make distclean? Or maybe you want rm -f. Mine does include the -f

Bug#495840: gqview doesn't display images larger than 32k horizontal pixels correctly

Package: gqview Version: 2.0.1-1 Severity: important When displaying images with a width greater than 32k pixels gqview messes up a bit. I'm stitching panoramas and they sometimes have over 60k horizontal pixels. This happens when zoomed out all the way. It doesn't happen when zoomed in. (I'm

Bug#495840: gqview doesn't display images larger than 32k horizontal pixels correctly

On Wed, Aug 20, 2008 at 11:15:13PM +0200, Daniel Baumann wrote: severity 495840 normal Indeed the severity I set sounded a bit hefty, but the description matched exactly with the situation. tags 495840 +moreinfo thanks Rogier Wolff wrote: Package: gqview Version: 2.0.1-1

Bug#472509: mtr: UDP patch

On Tue, Apr 15, 2008 at 04:41:15PM +0200, Martin Pels wrote: Depending on whether IP_HDRINCL is defined net_preopen() creates an icmp and udp socket, or a single raw socket. If we have two sockets it is trivial to close them in net_selectsocket(). This is actually what I did in the first

Bug#472509: mtr: UDP patch

On Tue, Apr 15, 2008 at 05:56:36PM +0200, Martin Pels wrote: On Tue, 15 Apr 2008 17:15:18 +0200 Rogier Wolff [EMAIL PROTECTED] wrote: On Tue, Apr 15, 2008 at 04:41:15PM +0200, Martin Pels wrote: Depending on whether IP_HDRINCL is defined net_preopen() creates an icmp and udp socket

Bug#472509: mtr: UDP patch

On Tue, Apr 15, 2008 at 05:56:36PM +0200, Martin Pels wrote: On Tue, 15 Apr 2008 17:15:18 +0200 Rogier Wolff [EMAIL PROTECTED] wrote: On Tue, Apr 15, 2008 at 04:41:15PM +0200, Martin Pels wrote: Depending on whether IP_HDRINCL is defined net_preopen() creates an icmp and udp socket

Bug#472509: mtr: UDP patch

Hi guys, Looks nice. One problem I have with this is that the amount of code that is exposed to security problems has gone up a factor of ten... How much work would it be to open both the new UDP port and the old ICMP port, and discard the one we don't need? How can the program switch (with

Bug#472511: mtr: Sub-second interval patch

Applied. Will go out in the next version when it comes out. Rogier On Mon, Mar 24, 2008 at 07:03:04PM +0100, Martin Pels wrote: Subject: mtr: Sub-second interval patch Package: mtr Version: 0.72 Severity: wishlist Tags: patch Hi, In the current version of mtr, intervals

Bug#461049: coreutils: dd no longer reports xx+yy records in|out after sigpipe.

On Mon, Jan 28, 2008 at 10:50:23PM -0700, Bob Proulx wrote: Michael Stone wrote: Rogier Wolff wrote: dd if=somebigfile | dd count=100 of=/dev/null both dd's should report that they copied 100 records. This worked in debian sarge. Debian Etch, the first dd stopped reporting

Bug#461049: coreutils: dd no longer reports xx+yy records in|out after sigpipe.

On Tue, Jan 29, 2008 at 03:12:24PM +0100, Jim Meyering wrote: Rogier Wolff [EMAIL PROTECTED] wrote: On Tue, Jan 29, 2008 at 08:01:45AM -0500, Michael Stone wrote: I figured there'd be some piece of posix at the bottom of it. :) I wonder if the documentation should better reflect

Bug#461049: dd's reaction to a close of the output. (Bug#461049)

Hi, In the past, the dd program would report the number of records copied when it stopped. dd stopping can of course be caused by several things: Running out of input, input IO error, output io error, or the case of interest here, the output pipe getting closed. Someone has quoted the

Bug#461049: coreutils: dd no longer reports xx+yy records in|out after sigpipe.

+and when @command{dd} completes normally or is killed by the [EMAIL PROTECTED] signal, it outputs the final statistics. Which is not correct, as the stats are also printed upon write error, like ENOSPC. (as we all agree the standards require). Roger. -- ** [EMAIL PROTECTED] **

Bug#461049: coreutils: dd no longer reports xx+yy records in|out after sigpipe.

On Tue, Jan 29, 2008 at 08:01:45AM -0500, Michael Stone wrote: I figured there'd be some piece of posix at the bottom of it. :) I wonder if the documentation should better reflect that. (The info page says only that when dd completes it outputs the final statistics; maybe something like

Bug#461049: coreutils: dd no longer reports xx+yy records in|out after sigpipe.

On Tue, Jan 29, 2008 at 01:27:57PM +0100, Jim Meyering wrote: Rogier Wolff [EMAIL PROTECTED] wrote: ... Let me reiterate: It is the first dd that is misbehaving, when it recieves a write error and SIGPIPE, it simply exits instead of reporting the stats. Thanks for the report

Bug#461049: coreutils: dd no longer reports xx+yy records in|out after sigpipe.

On Tue, Jan 29, 2008 at 03:33:01PM +0100, Jim Meyering wrote: Rogier Wolff [EMAIL PROTECTED] wrote: On Tue, Jan 29, 2008 at 01:27:57PM +0100, Jim Meyering wrote: Rogier Wolff [EMAIL PROTECTED] wrote: ... Let me reiterate: It is the first dd that is misbehaving, when it recieves

Bug#461049: coreutils: dd no longer reports xx+yy records in|out after sigpipe.

Package: coreutils Version: 5.97-5.3 Severity: normal -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.22bm Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Bug#457638: confused by router that always responds as the destination host

On Mon, Dec 24, 2007 at 03:46:02PM -0500, Joey Hess wrote: Robert Woodcock wrote: On Mon, Dec 24, 2007 at 10:07:47AM -0500, Joey Hess wrote: ICMP (-I) works, TCP SYN (-T) doesn't. First, This router is completely broken. It foges packets from the destination. As everybody else does it

Bug#384926: mtr: Broken IPv6 reverse lookup

Hi Bernhard, The patch was already in my source, 0.72 will have this, I just haven't released it yet. Roger. On Mon, Aug 28, 2006 at 01:11:59AM +0200, Bernhard Schmidt wrote: Package: mtr Severity: normal Tags: patch mtr 0.71 breaks on certain conditions when composing the

Bug#384444: mtr in sarge eats 100% cpu with -n

Hi, It is also already in my tree. Roger. On Thu, Aug 24, 2006 at 11:11:30AM +0200, Peter Palfrader wrote: Package: mtr-tiny Version: 0.67-1 Hi, mtr in sarge eats 100% CPU when called with -n (don't resolve IP addresses to hostnames). It turns out there is a small bug in

Bug#329745: mtr-tiny: Contradictory output when there is a failure in name resolution

On Sun, Oct 02, 2005 at 08:54:49AM -0700, Robert Woodcock wrote: On Sun, Oct 02, 2005 at 01:32:48AM -0300, Nelson A. de Oliveira wrote: On 9/27/05, Rogier Wolff [EMAIL PROTECTED] wrote: Yes, somehow, it calls a function that fails, but the errno variable indicates no specification

Bug#327043: [sane-devel] LiDE 25 issues

On Thu, Sep 08, 2005 at 04:30:40PM +0200, Julien BLACHE wrote: Gerhard Jaeger [EMAIL PROTECTED] wrote: Hi, well that what I was afraid of. The driver needs some tweaking either at the overall clock-divider settings or the motor-speed stuff. I have no possibility to check as I don't

Bug#327044: Libsane: Extra noise on lide25 scanner.

Package: libsane Version: 1.0.16 Severity: minor The Canoscan LiDE25 scanner makes more noise using the Linux driver than when used under Windows. This might impact longlivety of the hardware? (Driver: plustek) -- ** [EMAIL PROTECTED] ** http://www.BitWizard.nl/ ** +31-15-2600998 ** *--

Bug#327043: Libsane doesn't scan at 75dpi (or lower?) on Lide25.

Package: libsane Version: 1.0.16 When I scan with scanimage at 75 DPI, the scan-element doesn't move. It scans the black part of the enclosure. resulting images are quite black and useless. I've decided I don't want any 75 DPI scans, so for me this is a very low-priority bug. I've compiled

Bug#319968: mtr-tiny: TTL of 30 is insufficient for some routes

Hi, How about -m maxttl or --max-ttl maxttl . Roger. On Tue, Jul 26, 2005 at 11:24:35AM +1000, Konstantin Seiler wrote: Package: mtr-tiny Version: 0.67-1 Severity: normal mtr uses a maxTTL of 30 hops. However, today there are longer routes on the net. Today linux's default

Bug#291850: Ogle gets screen aspect ratio wrong.

Package: Ogle Version 0.9.2-2 Ogle gets my screen aspect ratio completely wrong. It results in a very skinny ogle window. I have 3 1024x768 monitors configured side-by-side, so the widht of my screen is 90.6 cm, and the height about 23.2 cm That's correct. But if you reason that way, the

Bug#291850: Ogle gets screen aspect ratio wrong.

On Mon, Jan 24, 2005 at 12:02:11AM +0100, Martin Norb?ck wrote: On Sun, Jan 23, 2005 at 05:49:27PM +0100, Rogier Wolff wrote: I have 3 1024x768 monitors configured side-by-side, so the widht of my screen is 90.6 cm, and the height about 23.2 cm That's correct. But if you reason that way

Bug#290215: Improper copyright file

On Wed, Jan 12, 2005 at 07:19:57PM -0500, Justin Pryzby wrote: Package: mtr-tiny Version: 0.67-1 Severity: normal The copyright file of this package seems to use the *license*, instead of the copyright holder in the style of Copyright (C) 2005 by Justin Pryzby. Where did you find this