diff options
Diffstat (limited to 'net-analyzer/lft')
| -rw-r--r-- | net-analyzer/lft/Manifest | 2 | ||||
| -rw-r--r-- | net-analyzer/lft/metadata.xml | 44 |
2 files changed, 43 insertions, 3 deletions
diff --git a/net-analyzer/lft/Manifest b/net-analyzer/lft/Manifest index a58b886d3a08..5cf9ef7dd3d1 100644 --- a/net-analyzer/lft/Manifest +++ b/net-analyzer/lft/Manifest @@ -4,4 +4,4 @@ DIST lft-3.8.tar.gz 376731 BLAKE2B e78e6d32cdaff8864e13477522dac92953d7ba44cb7d6 EBUILD lft-3.77.ebuild 493 BLAKE2B 49e6ddad7656e1c01304a464eb4c092f1f2e7e423732397645cbc3ed1ce2ada675f59d7668368d6f0e067e39ee875823f4f2f979c34000ddacdfae57449b5e36 SHA512 7d921ace43680f2ead6e1e9a1cd45d8e3a3a505b2b9293ad2940dbe117a3339e1a80ff04b15831459b80a214beaf27efaac57c9696642d4a58933516756c7164 EBUILD lft-3.79.ebuild 496 BLAKE2B a473d61c76ee7692a243e5fc8bfe20300879aec259336d161ea64c0f62c7ad6b266a3e00e6aa1b84d74e838f3f060265f753c720edbd1f38c6401971f50b68b8 SHA512 763ac7adc467f1517e7dc682ee179f9e8a58b94f67c871a898c55f4545c66219764bef441aece29a575675b54e899bcc59b408f4c755188f176694852c374c89 EBUILD lft-3.80.ebuild 518 BLAKE2B aa43152e115169c697369770cc9ab04deecafc9e8e35bd7ba59b322fd1fe02349c539acfe7a2ad45ce237de954b65739598cfb9455b2ff5fe60c2b900c150f19 SHA512 1ac97a059e628e16ed8f1bdf2b87a66b8d7d377298ea2cdf502486599c8f332b813629d6fc5eabf90a34f0c47672dd9f36d590c28199fe7b25146b20f4e528e6 -MISC metadata.xml 276 BLAKE2B e21811549278e73aa9a14acfe242fd022106a39ac1300caa00615772d7f54d08a433052659a271f9ac0d453c7776fc2b9e8d86e6d3f637817c214174dde52cb2 SHA512 f0e6c6bc89659e01e157d9bf30d0a2f3fd2d71bc26c8d12489c4a44fc5237159946e25b46e7295ab4676aea63559194977a0b1e76aced31d81cf6387dd0f4250 +MISC metadata.xml 2868 BLAKE2B 8ae5df11623eb04065537a289d1565a1ad766d93ebaff9b4fc8e326991331edfd7efa712387633a0edc5436445a1f3748425b7d93191ffb61a36c944cfd32b99 SHA512 13fa9fcdcc8c7e75a9a195d9463fc0456a81cc124302ab06f4caba6f20af0a1551ca76c7a6dc77a2551f0a02fbf29fd1087e9b14d674c1f9e661e52fc298b64a diff --git a/net-analyzer/lft/metadata.xml b/net-analyzer/lft/metadata.xml index 74c2baebb4ec..2fd58454386f 100644 --- a/net-analyzer/lft/metadata.xml +++ b/net-analyzer/lft/metadata.xml @@ -2,7 +2,47 @@ <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> <pkgmetadata> <maintainer type="project"> - <email>netmon@gentoo.org</email> - <name>Gentoo network monitoring and analysis project</name> +<email>netmon@gentoo.org</email> +<name>Gentoo network monitoring and analysis project</name> </maintainer> +<longdescription> +(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. +</longdescription> </pkgmetadata> |