TCP client-server applications.
tcpserver and tcpclient conform to UCSPI, the UNIX Client-Server Program
Interface, using the TCP protocol. UCSPI tools are available for several
different networks.
Submitted by: Camiel Dobbelaar <cd@sentia.nl>
proxy ARP. In a nutshell, this lets you proxy-ARP an arbitrary IP
address to an arbitrary MAC address, from any machine on the network.
This is useful if your router doesn't do proxy ARP, or does it only
in an all-or-none fashion.
This code will not work outside of 4.4BSD (it relies on BPF). Furthermore,
it won't run on most 4.4BSD operating systems, because a problem with the
standard BPF implementation (try spoofing your source ethernet frame
address on NetBSD).
See: http://www.enteract.com/~tqbf
--
NmapFE is a frontend for the much loved scanner Nmap.
Nmap is a portscanner that is able to do remote OS
detection via TCP/IP fingerprinting as well. You can
use Nmap to scan a large network, or a single host.
This frontend provides a simple GUI interface to the
complexity of Nmap. The GUI supports color coding for
various services, and enables you to append one scan
to the end of others, to create somewhat of a database
of scans.
mail retrieval from POP3 servers by systems that either:
(a) are behind a firewall or screening router OR
(b) do not have an assigned IP number OR
(c) must share a SLIP/PPP connection on another system
- convert patch-aa to a unified diff
- remove workaround for texinfo install-info bug
- move removal of wget.info* into wget's Makefile just before it gets
re-generated
- ${SH} -> sh
See package cvs.log for details.
This includes fixing an obscure security hole.
Patch to avoid spinning in select on non-blocking descriptors (will
probably be fixed in rsync 2.3.3)
This is needed for inter-operability with other systems, as 3.7.0 and
3.8.0 don't talk together.
Also, 3.8.0 fixes some important bugs, and it compresses bitmaps, which
means it can be used in various situations where it was completely useless
before.
-
tcpflow is a program that captures data transmitted as part of TCP
connections (flows), and stores it in a way that is convenient for
protocol analysis or debugging. A program like 'tcpdump' only shows a
summary of packets seen on the wire, but usually doesn't store the
data that's actually being transmitted. In contrast, tcpflow
reconstructs the actual data streams and stores each flow in a
separate file for later analysis.
tcpflow understands sequence numbers and will correctly reconstruct
data streams regardless of retransmissions or out-of-order delivery.
However, it currently does not understand IP fragments; flows
containing IP fragments will not be recorded properly.
Note: this port includes a small patch that adds the capability of
reading the packets from a tcpdump(1) capture file, using
a new option (-r).
-
tcptrace is a TCP dump file analysis tool written by Shawn Ostermann
at Ohio University. It is NOT a packet capture program. It reads
output dump files in the formats of several popular packet capturing
programs: tcpdump, snoop, etherpeek, and netm
For each connection, it keeps track of elapsed time, bytes/segments
sent and received, retransmissions, round trip times, window
advertisements, throughput, etc. Its output format ranges from
Simple to Long to Very Detailed.
someone is expecting substitution here.
tar: Unable to access bin/%%DISTNAME%% <No such file or directory>
tar: Unable to access lib/%%DISTNAME%%-lib/CHANGES <No such file or directory>
tar: Unable to access lib/%%DISTNAME%%-lib/README <No such file or directory>
tar: Unable to access lib/%%DISTNAME%%-lib/alias.tf <No such file or directory>
