Free virtual network computing software for linux

The "Virtual Universe" is a 3D cyberspace which offers more possibilities than just chat: it is a combination of the Web, chat, and instant messaging within a realistic, three-dimensional cyberspace.
The "Virtual Universe" is a virtual reality environment which runs on top of the Internet.
Main features:
- chat with each other
- see the chat-partner as a virtual, three-dimensional person
- interact and communicate
- be creative in many ways
- create own worlds for any desired subject
Enhancements:
- A lighting bug in .COB/.SCN loader has been fixed.

Virtual Tomcat project is a set of scripts designed to ease administration tasks involved with hosting multiple JVM instances and domains using Apache Tomcat and HTTPd.

The system (which uses jsvc to spawn instances) allows users to deploy their own applets from within their home directories, as well as allowing full access to /manager and /admin applets.

My Network Catalog is an indexing engine that allows Windows shares (or Samba shares) to be bound together over a local network.

My Network Catalog allows an easy centralized search of all the files available over the network.

Pinger Network Tools is a simple frontend for ping, netstat, traceroute and whois.

My first ever Kommander script that I did in an effort to learn the Kommander scripting engine/style and to have something useful.

Built with Kommander Editor 1.2

Network Configurator is a network configuration tool.
Network Configurator is user-level tool that aims to make network configuration more easy. It have command line and GTK+ interface.
Supported network types:
- Ethernet
- PPPoE
- PPTP
- Wi-Fi (no WEP and WPA for now)
- dialup

Ruby Iptables NEtwork Displayer project draws an SVG from a Linux IP table generated by "iptables-save".

KNetworkManager is the KDE front end for NetworkManager. KNetworkManager project provides a sophisticated and intuitive user interface which enables users easily to switch their network environment.

The range of functions encompasses the features implemented by NetworkManager daemon. Up until now NetworkManager supports:

Wired Ethernet Devices (IEEE 802.3)
Wireless Ethernet Devices (IEEE 802.11): Unencrypted, WEP, WPA Personal, WPA Enterprise
Virtual Private Network (VPN): OpenVPN, VPNC
Dial-Up (PPP)

How does it work?

For both, Wireless LAN and Wired LAN, NetworkManager supports devices known to HAL. Unless working in offline mode, NetworkManager tries to keep the system connected at any time. For this, NetworkManager follows the following policy.

Once started, NetworkManager asks HAL about available network interfaces. If a wired network interface with a carrier is found, NetworkManager connects to this. Either by DHCP (default) or by setting up previously defined static configuration. Later on, when KNetworkManager starts up, NetworkManager will expose its information about network devices and wireless networks found by scanning to the applet.

At this point, if a user decides to unplug the wired connection, NetworkManager will not connect to an arbitrary wireless network. By default all available networks are untrusted. Only if a user decides to connect to a network manually once, this specific network n henceforth being marked as trusted.

n = { ESSID, Hardware address or addresses of the access point}

The trusted networks are stored individually for each user. KNetworkManager stores them and informs NetworkManager about the known, trusted networks. If a wired connection drops due to unplugging the cable NetworkManager will automatically connect to a trusted network. As this step was done without user interaction, NetworkManager will reconnect to the wired connection once it has a carrier.

If a user joins a wireless network by manual intervention (e.g. user clicks on a network listed in the context menu of KNetworkManager or connects to a hidden wireless network), NetworkManager will take down any previous connection. If one unplugs the wired connection after such a step, NetworkManager will not connect to the wired connection once it has a carrier.

The Linux Virtual Server is a highly scalable and highly available server built on a cluster of real servers, with the load balancer running on the Linux operating system.

The architecture of the server cluster is fully transparent to end users, and the users interact as if it were a single high-performance virtual server.

The basic goal of the Linux Virtual Server Project is to:
- Build a high-performance and highly available server for Linux using clustering technology, which provides good scalability, reliability and serviceability.