Free network ups software for linux

Network Ustadi is a Web interface for managing network services. It provides firewall management, routing table management, NAT configuration, DHCP server configuration, interface configuration, etc.
To ease the task of network administration, decrease the likelihood of erronous command execution and to maintain all network services from a central point, EnderUNIX SDT anounces the availability of its 9th open-source tool, netUstad.
The tool, designed and coded by one of our developers Ozkan KIRIK, has the capability to generate FreeBSD IPFW and Linux Iptables rulesets. It has been written in C language and includes its own HTTP server.
The newly anounced version provides a web interface for system administrators to add/delete/update IPFW and Iptables rulesets, manage routing table and network interfaces. You can manage your firewall via a TCP/IP connected remote PC, easily.
Enhancements:
- Problems that causes the process to terminate, solved.
- Virtual Server configuration problem fixed.
- Some fixes in nat management module.

Network FIFO project is a network object that provides data transfering tunnel across network in first in/first out manner.

Simply put,

fifo server file is: monotech_fifo.pl
This script require Net::Server::NonBlocking at least 4.1(you can grab from CPAN)

% perl monotech_fifo.pl < address > < port >

and itll show up like this:

[root@WongWai monotech_fifo]# perl monotech_fifo.pl 192.168.3.52 12000
Listen on 192.168.3.52:20005
Listen on 192.168.3.52:12000

12000 is the port in which the fifo resides.
20005 is the port in which backoffice management resides.

--------------------------------------------------

port 20005 in which the management control resides can be accessed by "admin.pl"

% perl admin.pl < address >

for example

perl admin.pl 192.168.3.52

itll show something like this:

message>

where you can type some commands and press enter

the commands are:

message>readers
message>flush

(flush is the command that read all socket buffer of the admin client socket)

to show all reader in the fifo, it is very useful when some reader is connection disconnected by his ISP or readers machine hangs, the fifo will hold his connection forever (It is because the monotech_fifo.pl doesnt set SO_KEEPALIVE and TCP_KEEPALIVE which will be fixed in the future)

and

message>kill_reader[tab]< fifo name >

to kill any connection of < fifo name >

This package is heavily used by my company, so it is likely reliable.

Java Network Stack provides a Java library for research oriented network programming.

Java Network Stack is a library used by the DIMES project to create new internet measurements. It provides a clean API for packet manipulation, send, receive, filter, and analysis. It is a unification of raw socket capabilities, MAC level networkingm, and IPv6 capabilities.

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.

poker-network project includes a poker server, a client library, an abstract user interface library, and a client based on it.

The server deals the cards and checks the user actions using a poker game engine (poker-engine). It listens on a TCP/IP port and understands its own specific protocol. The persistent information is stored in a MySQL database.

The client library implements the poker-network protocol for the client. The abstract user interface library provides a framework based on the client library and suited to implement a user friendly client.

Noname Network provides a powerful file-sharing network.

The Noname network is a gnutella-based network that features a different and more flexible protocol. The client and network currently support filesharing, but the protocol can be extended to support more features.