Bug#7111: marked as done (tkined omnibus)
Your message dated Tue, 13 Jan 2004 10:51:33 +0000
with message-id <20040113105133.GA3883@deprecation.cyrius.com>
and subject line Removed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 4 Feb 1997 18:56:17 +0000
Received: (qmail 10763 invoked from network); 4 Feb 1997 18:56:16 -0000
Received: from rdm.legislate.com (HELO test.legislate.com) (198.80.98.13)
by master.debian.org with SMTP; 4 Feb 1997 18:56:06 -0000
Received: (qmail 2018 invoked by uid 1000); 4 Feb 1997 19:51:23 -0000
Date: 4 Feb 1997 19:51:23 -0000
Message-ID: <19970204195123.2017.qmail@test.legislate.com>
From: Raul Miller <rdm@tad.micro.umn.edu>
To: submit@bugs.debian.org
Subject: tkined omnibus
Package: tkined
Version: 1.3.4-2
tkined is neat, but it's got lots of quirks and sometimes feels
clumsy.
What I'd like to be able to do with it is hand it a list of network
addresses, and have it go out and poll those networks and come back
with the topology of the network, with emphasis on the network
devices, and icons assigned based on some kind of signatures
(e.g. windows machines tend to only respond on port 139, snmp will
sometimes give you system information, sunrpc sometimes is useful..).
tkined is tantalizing, but has a long way to go before it can tackle
this kind of thing.
Perhaps the best option would be some kind of documented mechanism for
importing a database, with some well defined tables, and using tkined
only as presentation software. Then, I would go in with scotty, and
maybe tools I've written myself, build up the database over a period
of days and use tkined to take snapshots of this.
(1) it will sometimes put graphics "off the page", but won't let you
scroll to see them (or even select them). I'd prefer if the page
boundaries were advisory (something like the way an expanded group is
displayed, but maybe different line weight or color?).
(2) it misses opportunities for information. For example, I'd like to
be able to have it automatically color nodes that have erroroneous
behavior (e.g. byte swapped ports).
(3) it occasionally spits stack traces out at me. [I'll try to file
these as I come across them.]
(4) it sometimes creates duplicate representations for the same ip
address or network, and I don't understand why.
(5) it doesn't have a way of representing subnets smaller than class
C. [Or, presumably, larger than class C but not class A or B -- then
again, I don't have any way of testing that out.]
(6) it doesn't have any way (other than slow manual work) of
integrating information from snmp (e.g. which ip addresses does a
cisco router use, what type of network is on each, what does arp
indicate about brand of network device, ...). It would be nice to (a)
have a way of automatically propagating this information into
attributes, and (b) have a mechanism to automatically set icon details
based on attributes.
(7) choice icons are very limited, and no obvious way of extending
them.
(8) nested groups are kind of nice but extremely quirky. [You can put
a group inside another group, but under some circumstances the
contents of the groups will be tossed out of the original group -- I
just had a bunch of networks tossed out of a three level deep
hierarchy I'd built to represent a router.]
(9) snmp queries against a number of systems will frequently give up
if there's a few that aren't responding in the current community.
(10) selection by address sometimes gets the wrong node (especially
with patterns).
(11) TCP Services under IP-Trouble tends to hang for a long period of
time under not-uncommon circumstances (e.g. some ports behind packet
filter).
(12) The IP-Layout parameters are overly optimistic about the minimum
number of nodes in a row (10). Why can't I set this lower?
(13) IP-Discover's text view tells me about querying snmp agents, but
there's no apparent way of getting at these specific machines for
further interaction (see also #6, and #9).
(14) There's no way to set the default icon for IP-Discover (this is
basically an ultra simplified variant on #6).
(15) There's no display abstraction for a machine with multiple ip
addresses. For example, if I use "groups", I wind up with a bunch of
disconnected networks.
--
Raul
---------------------------------------
Received: (at 7111-done) by bugs.debian.org; 13 Jan 2004 11:52:27 +0000
>From tbm@cyrius.com Tue Jan 13 05:51:22 2004
Return-path: <tbm@cyrius.com>
Received: from bangpath.uucico.de [195.71.9.197]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AgM9P-000270-00; Tue, 13 Jan 2004 04:51:59 -0600
Received: by bangpath.uucico.de (Postfix, from userid 10)
id 77F8E26B9A; Tue, 13 Jan 2004 11:51:58 +0100 (CET)
Received: by deprecation.cyrius.com (Postfix, from userid 1000)
id C7A2FFEEB; Tue, 13 Jan 2004 10:51:33 +0000 (GMT)
Date: Tue, 13 Jan 2004 10:51:33 +0000
From: Martin Michlmayr <tbm@cyrius.com>
To: 7111-done@bugs.debian.org, 13226-done@bugs.debian.org,
14186-done@bugs.debian.org, 28688-done@bugs.debian.org,
50532-done@bugs.debian.org, 50743-done@bugs.debian.org,
67469-done@bugs.debian.org, 166057-done@bugs.debian.org
Subject: Removed
Message-ID: <20040113105133.GA3883@deprecation.cyrius.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
Delivered-To: 7111-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin
2.60-master.debian.org_2003_11_25-bugs.debian.org_2004_1_5
(1.212-2003-09-23-exp) on master.debian.org
X-Spam-Status: No, hits=0.0 required=4.0 tests=none autolearn=no
version=2.60-master.debian.org_2003_11_25-bugs.debian.org_2004_1_5
X-Spam-Level:
This package has been removed from Debian unstable because it has not
been maintained in Debian (orphaned for over 130 days) and is also no
longer being developed upstream.
--
Martin Michlmayr
tbm@cyrius.com
Reply to: