From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id CC99D1382C5 for ; Fri, 20 Apr 2018 13:09:17 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CF071E07F2; Fri, 20 Apr 2018 13:09:16 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 99492E07F2 for ; Fri, 20 Apr 2018 13:09:16 +0000 (UTC) Received: from oystercatcher.gentoo.org (unknown [IPv6:2a01:4f8:202:4333:225:90ff:fed9:fc84]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 83FCD335C06 for ; Fri, 20 Apr 2018 13:09:13 +0000 (UTC) Received: from localhost.localdomain (localhost [IPv6:::1]) by oystercatcher.gentoo.org (Postfix) with ESMTP id EE48E257 for ; Fri, 20 Apr 2018 13:09:11 +0000 (UTC) From: "Jeroen Roovers" To: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "Jeroen Roovers" Message-ID: <1524229750.a606b7134e3f8743b8236ecac463491549f9e895.jer@gentoo> Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/lft/ X-VCS-Repository: repo/gentoo X-VCS-Files: net-analyzer/lft/metadata.xml X-VCS-Directories: net-analyzer/lft/ X-VCS-Committer: jer X-VCS-Committer-Name: Jeroen Roovers X-VCS-Revision: a606b7134e3f8743b8236ecac463491549f9e895 X-VCS-Branch: master Date: Fri, 20 Apr 2018 13:09:11 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org X-Archives-Salt: a1c6895c-f4ec-4eb2-8e75-5ef607721608 X-Archives-Hash: 28a63a17c3492a73217cba4c3517237d commit: a606b7134e3f8743b8236ecac463491549f9e895 Author: Jeroen Roovers gentoo org> AuthorDate: Fri Apr 20 13:08:29 2018 +0000 Commit: Jeroen Roovers gentoo org> CommitDate: Fri Apr 20 13:09:10 2018 +0000 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a606b713 net-analyzer/lft: Add . Package-Manager: Portage-2.3.31, Repoman-2.3.9 net-analyzer/lft/metadata.xml | 44 +++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 42 insertions(+), 2 deletions(-) diff --git a/net-analyzer/lft/metadata.xml b/net-analyzer/lft/metadata.xml index 74c2baebb4e..2fd58454386 100644 --- a/net-analyzer/lft/metadata.xml +++ b/net-analyzer/lft/metadata.xml @@ -2,7 +2,47 @@ - netmon@gentoo.org - Gentoo network monitoring and analysis project +netmon@gentoo.org +Gentoo network monitoring and analysis project + +(Note that version 3.80 is really 3.8, but released after 3.79.) + +LFT, short for Layer Four Traceroute, is a sort of 'traceroute' that often +works much faster (than the commonly-used Van Jacobson method) and goes through +many configurations of packet-filters (firewalls). More importantly, LFT +implements numerous other features including AS number lookups through several +reliable sources, loose source routing, netblock name lookups, et al. What +makes LFT unique? LFT is the all-in-one traceroute tool because it can launch a +variety of different probes using ICMP, UDP, and TCP protocols, or the RFC1393 +trace method. For example, rather than only launching UDP probes in an attempt +to elicit ICMP "TTL exceeded" from hosts in the path, LFT can send TCP SYN or +FIN probes to target arbitrary services. Then, LFT listens for "TTL exceeded" +messages, TCP RST (reset), and various other interesting heuristics from +firewalls or other gateways in the path. LFT also distinguishes between +TCP-based protocols (source and destination), which make its statistics +slightly more realistic, and gives a savvy user the ability to trace protocol +routes, not just layer-3 (IP) hops. With LFT's verbose output, much can be +discovered about a target network. + +WhoB is a likable whois client (see whois(1)) designed to provide everything a +network engineer needs to know about a routed IP address by typing one line and +reading one line. But even so, it's worth typing a few more lines because WhoB +can do lots of other cool things for you! It can display the origin-ASN based +on the global routing table at that time (according to Prefix WhoIs, RIPE NCC, +or Cymru), the 'origin' ASN registered in the RADB (IRR), the netname and +orgname, etc. By querying pWhoIs, WhoB can even show you all prefixes being +announced by a specific Origin-ASN. WhoB performs the lookups quickly, the +output is easily parsed by automated programs, and it's included as part of the +Layer Four Traceroute (LFT) software package. LFT uses WhoB as a framework (and +you can too, quite easily--see whois.h). Recent LFT releases (as of version +2.5) include WhoB functionality through a standalone "whob" client/command +placed in the LFT binary directory. + + LFT and WhoB continue to evolve and provide more and more useful data to + network engineers and to anyone else that cares how IP datagrams are being + routed. With the advent of smarter firewalls, traffic engineering, QoS, and + per-protocol packet forwarding, LFT and WhoB have become invaluable tools for + many network managers worldwide. +