Free network deepscan 2.2 software for linux

Network technology evolves quickly, but available bandwidths are still not sufficient for fast transfers of big files to a bunch of clients (for example populating operating systems installation images).

This paper describes Multicasting Master-Slave Network Filesystem (mmsnfs) -- a new method of distributing entire filesystem among several client-machines simultaneously and efficiently.

Moreover it provides mechanisms for modifying distibuted filesystem structure reliably and securing it against introducing inconsistencies. It is designed to be used in small networks of similarly-configured machines, for instance university labs or internet cafes.

Samba Commander is a text mode SMB network commander. In SMBC, you can browse the local network or you can use the search function to find the files.
You can also download/upload files and directories or create them both locally and remotely. SMBC has a resume function and supports UTF-8 characters.
Enhancements:
- fixed bug in function to retrying connection
- fixed bug in bookmark menu
- fixed bug in function to set username, password and workgroup

Komba2 is a windows network administration tool for the K Desktop Environment.

Our target is to make administration beautiful and intuitive without sacrificing power.

GNOME Network is a set of client network-oriented tools, which currently contains a network information tool, a remote shell and desktop clients and a personal web server and a desktop sharing tool.
GNOME Network is Free Software distributed under the terms of the GNU GPL.
Enhancements:
Updated translations:
- gl (Ignacio)
- it (Alessio)

Network Tracker and Management is a Web-based network management application.
Network Tracker and Management can store information about all of your network devices, and allows you to track all changes and updates made to the device.
Having this information readily available will enhance your ability to troubleshoot network problems.
Enhancements:
- The documentation was updated to include more details on the setup of the database for the network tracking system.

Deep Network Analyzer is an flexible, open and extensible deep network analyzer (software server) and architecture for gathering and analyzing network packets, network sessions and applications protocols, passively off enterprise class networks.
DNA is designed to be used for Internet Security, Intrusion detection, Network Management, Protocol and Network Analysis, Information Gathering, Network Monitoring applications.
DNA runs as a distributed application under a Java Virtual Machine (JVM) environment and is portable across many OS environments, including: Network appliances, Switches and Routers.
Main features:
- Deep packet and session processing (layers 2-7)
- Configurable processing and output:
- Layer 4 Packet flows
- Layer 4-7 Stateful Sessions flows (client/server flow pairs)
- Layer 7 Packet and Session Application protocol Parsing (HTTP, DNS, P2P, VoIP, etc)
- Application protocol parsing toolkit enables easy devlopment of new new protocol parsers.
- Support for both symmetric and asymmetric routing links.
- Targeting based full session capture facility, like a real time targeted TCPDump.
- Flexible targeting from IP address, port tuple to application sensitive targeting.
- Configurable and extensible output adaptor utilizing OpenAdaptor able to send output to a varity of resources including: Flat file, Oracle, MySQL, MSSQL, Sybase, Sockets, JMS, RMI, WebService.
- Extensible real time collection engine portable across many OS/Packet processing environment :
- Specialized linux drivers mechanisms
- Network Appliances
- Network Switches / Routers
- Highly paralleliszed for increased performance over multi processor environment
- System metadata dictionary externalizes processing type definition
Enhancements:
- Adoption of OpenAdaptor(tm) as the Output Adapter mechanism.
- Support for local-only administration.
- A new targeted packet capture parser, new run scripts, and a new install mechanism.
- Many bugfixes.

Jimsim Network Simulator project can emulate several routers connected via virutal networks. You can connect to the routers with your own favorite telnet program.
Connecting to the Virtual Routers
Use your favorite telnet program to connect to each of the virtual routers. For example:
For router 1 type:
C:>telnet localhost 10000
For router 2 type:
C:>telnet localhost 10001
For router 3 type:
C:>telnet localhost 10002
Network Layout
Currently the network is configured like this:
access-list [1-99] [permit/deny] [ ip wildcard-mask | host a.b.c.d | any ]
ip acccess-list [standard] [name]
ip access-group
show access-list
show ip interface
show ip interface brief
debug interface
encapsulation [hdlc,ppp] (serial interfaces only)
bandwidth
clock rate (serial interfaces)
interface loopback0
User commands:
?
enable
exit
ping ip
show cdp
show cdp neigh
show cdp neigh detail
show interface
show interface e0,eth0,etc
show ip route
show version
Enable commands:
clear counters
clear counters interface
config terminal
copy running startup
copy startup running
debug all
debug ip routing
debug ip eigrp
debug cdp
disable
exit
reload
show run
show startup
show ip eigrp neighbors
show ip eigrp topology
traceroute ip
undebug all
undebug ip routing
undebug ip eigrp
undebug cdp
Config commands:
cdp run
enable password password
end
hostname
banner motd delimiter
banner exec delimiter
banner login delimiter
ip route network netmask dest
interface e0,eth0,etc
bandwidth value
ip address addr netmask
description
cdp enable
shutdown
line con0, console0, console 0
login
login local
password passwd
router eigrp number
network a.b.c.d
service password-encryption
user username password password
Version restrictions:
- The EIGRP support is very basic. Just the network command for now. (Neighbors dont expire.) You can disable EIGRP with "no router eigrp process_id"
- The routing table isnt 100% correct. It doesnt summarize subnets. Nor does it understand multiple routes to the same destination. This will be fixed in the next version.
- Traceroute seems to count extra hops. Its counting each remote interface on a router as a hop. So, when you traceroute from router1 to router3, it counts router2 twice (once for 192.168.1.2 and 10.1.1.1)