Free network deepscan 2.6 software for linux

network jack is an Internet troubleshooting and information gathering tool. It provides a Web interface to several common command-line tools, including ping, traceroute, dig, and whois, as well as a subnet mask and CIDR block calculator.
Current Modules which you can find in the application:
Pinger
- Ping a host on the internet (currently only IPv4)
Tracer
- Traceroute to a host on the internet from the web server (currently only IPv4)
Digger
- Do a DNS Dig of a hostname or IP address (for reverse lookups)
Drooler
- block list lookup (aka RBL query, blackhole lookup)
Whoser
- lookup for domain names and IP addresses / blocks
Netter
- Mask / CIDR calculator
Linker
- Front" page for the tools, provides spot for links
Main features:
- It is intended to be easy to add new modules
- Seperates html code into its own file so can be customized without modifying the program files

Network Simulator (Ns) is a discrete event simulator targeted at networking research. Ns provides substantial support for simulation of TCP, routing, and multicast protocols over wired and wireless (local and satellite) networks.
Ns began as a variant of the REAL network simulator in 1989 and has evolved substantially over the past few years. In 1995 ns development was supported by DARPA through the VINT project at LBL, Xerox PARC, UCB, and USC/ISI.
Currently ns development is support through DARPA with SAMAN and through NSF with CONSER, both in collaboration with other researchers including ACIRI. Ns has always included substantal contributions from other researchers, including wireless code from the UCB Daedelus and CMU Monarch projects and Sun Microsystems.
Enhancements:
- Major updates were made to the PackMime-HTTP HTTP/1.1 and WPAN modules.
- Solaris/Sun C compilation bugs were fixed.

Network UPS Tools is a collection of programs which provide a common interface for monitoring and administering UPS hardware. Network UPS Tools uses a layered approach to connect all of the parts.
Drivers are provided for a wide assortment of equipment. They understand the specific language of each UPS and map it back to a compatibility layer.
This means both an expensive "smart" protocol UPS and a simple "power strip" model can be handled transparently.
This information is cached by the network server upsd, which then answers queries from the clients. upsd contains a number of access control features to limit the abilities of the clients. Only authorized hosts may monitor or control your UPS hardware if you wish.
Since the notion of monitoring over the network is built into the software, you can hang many systems off one large UPS and they will all shut down together.
Clients such as upsmon check on the status of the hardware and do things when necessary. The most important task is shutting down the operating system cleanly before the UPS runs out of power.
Other programs are also provided to log UPS status regularly, monitor status through your web browser, and more.
Enhancements:
- HAL support. IPv6 support.
- Support for many new devices.
- Many driver improvements.
- This release uses automake.

network-config is a simple network configuration tool.

Network-config is a simple and easy to use program that helps configuring the network interfaces for linux-based operating systems. It allows to have multiple configurations for the same computer and to easy configure NAT for internet sharing.

It can also be used to scan for wireless networks. It is written in perl and uses gtk2+, but also works as a command line program.

Parallel Network Scanner provides a fast network services scanner.
pnscan is a scanner for TCP network services. It uses multithreading to increase its speed.
pnscan tries to be smart as to how many threads to start - it will dynamically start only as many as is needed to make progress in the scan - up to a maximum either as specified with the "-n" command line option, or 8 minus the maximum number of available file descriptors (pnscan tries to increase
it to the max limit automatically) - or any internal limit on the system (Linux normally only allows 256 threads).
Host ranges can be specified both as a CIDR - network name or IP address / mask bit length and as a range. When using CIDR notation - the first and last address is ignored (normally used for broadcasts)
Some examples:
192.168.0.0/24
192.160.0.1:192.160.0.254
arpanet/8
USAGE - EXAMPLES
# Scan network 192.168.0.0/24 for SSH daemons on port 22
pnscan 192.168.0.0/24 22
pnscan 192.168.0.1:192.168.0.254 ssh
# Scan hosts 192.168.10.34 ... 98 for IDENT servers, max 8 threads
pnscan -n8 -w"VERSION" 192.168.10.34:192.168.10.98 113
# Scan host 127.0.0.1 for WWW servers on all ports
pnscan -w"HEAD / HTTP/1.0rnrn" -r"Server:" 192.168.0.32 1:65525
pnscan -w"HEAD / HTTP/1.0rnrn" -r"Server:" localhost 1:65525
# Send binary data and expect the binary sequence FF 00 FF on port 145.
pnscan -W"05 5A 37" -R"FF 00 FF" 192.168.0.32 145
# Scan for Roxen servers and print the whole Server-line
pnscan -l -w"HEAD / HTTP/1.0rnrn" -r"Roxen" localhost 1:65525
# Scan for pidentd servers and try to locate the version
pnscan -w"VERSION" 192.160.0.0/24 113
# Scan network arpanet/24 for daytime servers and sort them IP-numerically
pnscan arpanet/10 daytime | ipsort
# Read host (&port) lines from stdin and scan the selected hosts for SSH
echo 192.160.10.11 ssh | pnscan -v
echo 192.160.10.12 | pnscan 22
Enhancements:
- pnscan.sgml Added the other options implemented in pnscan.c.
- pnscan.c: Modified the threads startup code to dynamically only start as many threads as is needed.

Network Tracker application is a user (MAC) tracker daemon, for big LANs (campus).
The Network Trackerd builds a table which records which user is connected on which port of a switch by scanning the devices with SNMP in your inventory which is in a MySQL database. Trackerd keeps that table up-to-date by scanning the network regularly.
Thus, you will have the opportunity to know exactly where a user (MAC, IP, UID) is connected on your network !
Your devices are also checked with ping and SNMP, and you are informed with e-mail when any of the devices is not alive.
More over, you may produce various reports about your network infrastructure on the web (cgi) or by using other tools.
Network tracker eases especially to find and shutdown the switch port of the users, when their PCs on the network start to spread viruses or warms using lots of bandwith; so you are able to stop that kind harmfull traffic on the network.
Main features:
- Collects all the MAC addresses and port numbers from CAM tables of the switches.
- Finds IP addresses of the MACs from ARP tables of the routers.
- Finds LDAP uid of the user.
- Check devices on the network with both ping and SNMP for better reliability.
- The daemon sends 2 self check e-mail per day.
- Developped with C.
Enhancements:
- trackerd is now multi-threaded and works very quickly because a new thread is created for each network device.
- MAC tracking code has been reimplemented for multi-threaded use.
- Wireless access point support has been added.
- gnuplot graphics are prepared, showing the active number of users like MRTG graphs.
- tracker now accepts MAC addresses in free format.

Network Device Change Control (NDCC) is a system that monitors and records changes to the configurations of network equipment.

Network Device Change Control can store configuration snapshots for any text-based configs. It has been used to store configurations from Unix and Linux systems, Cisco routers, switches, load balancers, and firewalls, Foundry, NetScreen, Juniper, NetScaler, and others.

It only took a while to realize that router changes should be tracked. I rewrote the system to give a current and once-back system of configurations. Since I was using diff, I decided to leave the diff information in the system. Those diffs were emailed to a group so everyone knew when something was changed, along with what was changed.

Some time later, a bank needed to track configuration files, and the system was upgraded for use within a database. The first implementation was using perl as a CGI script against a PostgreSQL database. The company wanted many changes made for their auditing needs and most of those changes enhanced NDCC. Upgrades to their environment moved things to PHP and MySQL, and the system was rewritten for that environment and the old perl code has since been lost.

Netleak is a collection of small perlscripts that detects connectivity between network segments. It is mostly useful to detect "leaks" in large organizations that have private networks physically separated from the Internet.


Imagine some large corporation which has an internal development LAN were all sorts of sensitive information is flowing around. This corporation would likely have some very strict rules as to how its employees access the internet or other partner branches in order to
protect its information. For the systemadinistrator this is a daunting task - as the corporate LAN grows keeping track of all the routes through the network becomes extremely difficult. Some routers might simply have been forgotten over time or an employee might have gone wise and connected his own adsl-router or something alike.

Network Leak Finder tries to detect this in a centralized manner by sending out spoofed packets into the internal network and if any packets finds a way onto the external network, a "leak" has been detected. As an anology it works the same way you would find a hole in
a bucket: fill it with water and see if anything leaks.

In most scenarios the external network would be the Internet since everybody should be afraid of what their corporate LANs are leaking to it!