IP Stack Integrity Checker
Its purpose is to test the stability of an IP Stack and its component stacks
(TCP, UDP, ICMP et. al.) It does this be generating random packets of the
desired protocol. The packets can have tendencies. ie by default all packets
have a 50% chance of having IP Options. The packets are then sent against the
target machine to either penetrate its firewall rules or find bugs in the IP
stack.
This program is a lightweight access- and prefix-list generator
for Cisco routers and GateD/Zebra. Access lists are generated
based on RADB/RIPE data.
This tool is not so powerful as RAToolSet, but has some
features missing in RAToolSet, such as optional filtering
of more specific routes in the same AS or acl string aggregation;
also, it does not requires Tcl/Tk to be installed.
Packit is a network auditing tool. Its value is derived from
its ability to customize, inject, monitor, and manipulate IP
traffic. By allowing you to define (spoof) nearly all TCP, UDP,
ICMP, IP, ARP, RARP, and Ethernet header options, Packit can be
useful in testing firewalls, intrusion detection systems, port
scanning, simulating network traffic, and general TCP/IP
auditing. Packit is also an excellent tool for learning TCP/IP.
hidentd is a simple and secure GPLed ident (RFC1413) server. It
requires either inetd, xinetd or ucspi-tcp to run. Basic
features:
* small and simple - around 300 lines of code
* secure - runs without root priviledges
* easy - no complicated configuration file syntax to learn.
* hidentd is entirely controlled with command line options.
* can be configured to provide fake usernames, protecting your privacy
* limited masqueraded/NAT connections support.
__ _ __
_ __ ___| /_ ___ ___ _ __(_)_ __ | /_ (portable/multi-platform) lightwei-
| '_ \./ _ \ __/ __)/ __| '__| | '_ \| __) ght TCP socket scripting. Intende-
| | | | ._/ |_(__ \ (__| | | | |_) ) |_ d for (non-)experienced persons to
|_| |_|\___|\__|___/\___|_| |_| .__/ \__) be able to use to automate situati-
[TCP socket scripting program] |_| [1.6.0] ons, built on a word-to-word rules-
et response system. includes wild-
card support, character replacement, random replacement, argument inclusion,
server timeout, initial send, display altering, multiple character dump forma-
ts, telnet protocol support, logging, program to socket dumping, executable
ruleset support, reverse binding, and module support among other things.
Geo::IP::PurePerl uses a file based database. This database simply contains
IP blocks as keys, and countries as values. This database is more complete
and accurate than reverse DNS lookups.
Geo::IP::PurePerl can be used to automatically select the geographically
closest mirror, to analyze your web server logs to determine the countries
of your visiters, for credit card fraud detection, and for software export
controls.
The IO::Socket::Multicast6 module subclasses IO::Socket::INET6 to enable you to
manipulate multicast groups. With this module you will be able to receive
incoming multicast transmissions and generate your own outgoing multicast
packets.
This module uses the same API as IO::Socket::Multicast, but with added support
for IPv6 (IPv4 is still supported). Unlike IO::Socket::Multicast, this is a
pure-perl module.
This is a snapshot release of the NIS interface to Perl 5. There are
three parts to the interface: the raw component (Net::NIS), the
object-oriented component (Net::NIS::Table), and the tied interface
(Net::NIS).
Unless someone provides strong reason to support the raw or OO
components, they will be marked as deprecated and not documented or
enhanced (but still supported for backward compatibility).
POE::Component::Client::Whois provides a lightweight one shot non-blocking
RFC 812 WHOIS query to other POE sessions and components. The component will
attempt to guess the appropriate whois server to connect to based on the
query string passed.
If no guess can be made it will connect to whois.internic.net for domains,
whois.arin.net for IPv4 addresses and whois.6bone.net for IPv6 addresses.
Panoptis is a project started some time ago,
with the aim to stop the Denial of Service
and Distributed Denial of Service attacks that
have been torturing the Internet for the last
few years.
It is based on real-time processing of Cisco (R)
NetFlow (TM) data, since this seems to be the
most efficient approach as it is router-centric,
allowing for automated central response without
intervention from the affected organizations'
network administrators.