Free miniupnp client daemon 1.0 rc7 software for linux

MiniUPnP Client and Daemon is an UPnP IGD client lightweight library and UPnP IGD daemon.
The UPnP protocol is supported by most home adsl/cable routers and Windows 2K/XP. The aim of the MiniUpnp project is to bring a free software solution to support the "Internet Gateway Device" part of the protocol.
The Linux SDK for UPnP devices (libupnp) seems too heavy for me. I want the simplest library possible, with the smallest footprint and no dependencies to other libraries such as XML parsers or HTTP implementations. All the code is pure ANSI C.
Compiled on a x86 PC, the miniupnp client library have less than 15KB code size. For instance, the upnpc sample program is around 20KB.
The project is divided in two main parts : the client library, enabling applications to access the services provided by an UPnP "Internet Gateway Device" present on the network, and the miniupnpd daemon, providing these services to your network from a linux or bsd box being the gateway. At the moment the miniupnpd is developped on OpenBSD 3.0+ with pf. You can see some of the work I have done to integrate with pf on this page.
As pf is also available under FreeBSD, guys at the pfSense project have ported miniupnpd to this system.
For some reasons, it may be not the good solution for you to use the code from the MiniUPnP project directly.
As the code is small and simple to understand, it is a good base to take inspiration for your own UPnP implementation. The KTorrent team UPnP plugin in C++ is a good example.
If you are wondering which home router is working with the miniupnp client, you can find the answer here. In fact, you are more likely to help me fill the list by sending me an email.
Usefulness of the miniUPnP client library
The usage of the miniUPnP client library is useful whenever an application needs to listen for incoming connections.
Examples : P2P applications, FTP clients for active mode, IRC (for DCC) or IM applications, network games, any server.
The typical usage of UPnP capabilities of a router is a file tranfert using MSN messenger. The MSN Messenger software uses the UPnP API of Windows XP to open port for incoming connection. To mimic the MS software, it is a good idea to use UPnP as well.
Enhancements:
- This release adds changes to accommodate the Linux 2.6.22 kernel.

phpSocketDaemon is a PHP socket daemon framework that can handle thousands of client and server connections, asynchronously, with built-in buffering, state handling, etc.

The implementation of a new TCP client or server service (or a mix thereof) with this library is very easy, and allows maximum flexibility.

Motivation for writing this library:

This project came into existence while i was writing a new, ground breaking IRC chat web application.

To deal with 1000s of concurrent, always on (comet aka hanging iframe) http (server) connections, and an equal amount of IRC client connections, plus being able to interpret and parse and delegate all the messages and events, i needed a very fast, stable, flexible and easy to use daemon library for PHP.

However no such thing existed yet, hence this library was created.
The tarbal includes a demo HTTP server implimentation, which will give you a good impression of what its capable off, and how to use this library.

HCSWs Ident Daemon provides a well-written daemon for faking ident replies to IRC servers.

This identd is essentially just a quick and small daemon to fake ident replies. It is primarily intended to provide random ident fields on IRC.


As of 1.1, hsidentd now natively supports IPv6. It will try listening on the same port as it does on IPv4, or 113 by default. To disable IPv6 support, edit the file hsidentd.h and comment out the line that looks like this:

#define HAVE_IPV6

Building:

Just type make

You may have to uncomment the appropriate line at the top of the Makefile.

Installing:

Just copy the executable to somewhere in the filesystem. Or dont. See if I
care.

Running:

As root, just run the hsidentd executable like so:

hsidentd

or

hsidentd

wifistatd is a script which generates a PNG graphing signal/noise/link levels on a selected wireless interface.

To install wifistatd on a UNIX machine untar the archive with program.
Then you must type:

./wifistatd.pl install

If everything went OK (it should), youll get the db.rrd database file in your current working directory.

To configure daemon edit the head part of wifistatd.pl.

getting_started
To start, just type:
./wifistatd.pl start

To stop, just type:
./wifistatd.pl stop

The wmpptpd is a Linux PPTP (Point to Point Tunnelling Protocol) server. Comparing to the existing PPTP client and server, it handles multiple connections and clients, implements window protocol, etc. After few minor changes you can use it as a client, too.

The PPTP, point-to-point tunelling protocol, is used to tunell a PPP connection over the local network. It is often used to build the virtual private networks using Windows 9x machines and NT server. There exists a PPTP server and PPTP client for Linux, both of them used to communicate with a windows machine:

server (PoPToP): http://poptop.lineo.com
client (PPTP-Linux): http://cag.lcs.mit.edu/~cananian/Projects/PPTP

However, there are more implementations than the one in Windows around, and weve got a Compaq Microcom 4000 modem rack, which answers digital incomming calls and forwards the requests to a server (using PPTP of course). At first, we tried to adapt a PoPToP server or client to do the job for us, but unfortunately found many problems, so we started from scratch. Our goals were:
- working PPTP implementation
- extensible and flexible design
- multiple connections at one time
- support for as many pptp-talking clients as possible

After few nights, the first versions were ready, few bugs were caught (for example, we had to throw our implementation of windows, as microcom 4000 does not use them; we found few serious design flaws of PPTP protocol itself, spent some time catching the bugs with multiple connections, ...). Then we installed this all on our production server and forgot about it. After some time, weve got some bug reports, which needed to be ironed out. So we re-visited the sources, fixed the bugs and made this release.

iNet Admin Daemon interacts with services such as an Apache2 load balanced environment, a MySQL 5 clustered environment, PureFTPD, PowerDNS, Cacti, Nagios.
iNet Admin Daemon has various other services to create central ease of management and integration with these services for hosting companies.
Enhancements:
- Functional modules were added for existing services connecting to DBmail, PowerDNS, Apache2, and MySQL 5.

py-libmpdclient2 replaces py-libmpdclient and is completely redesigned and written from the ground up. The result is a much smaller, simpler, more reliable, and more dynamic library.
Using py-libmpdclient2:
test.py should do a decent job of showing how the module works -- theres not a lot to it -- but if you have more questions, your best bet is to get a hold of me (mackstann) in #mpd on irc.freenode.net (not there so much anymore).
Since the library isnt widely packaged, it is probably easiest for you to just include mpdclient2.py in your own clients codebase. And since it is public domain, you have no licensing issues to worry about whatsoever. The code belongs to you no less than it belongs to me.
Enhancements:
- This version has been in use by a few clients for nearly a year, but not officially released.

Audio Daemon is a perl module to daemonize various players and support a single UDP interace for different players. Currently you can set up a server for MPG123, Xmms and an icecast stream (using libshout).

Audio::Daemon is made of two parts, the client and server.

The Client (Audio::Daemon::Client) remains the same across the board no matter what server you are communicating with, with a few exceptions noted in the pods.

The Server currently can be configured to be MPG123, Xmms or an Icecast (libshout) stream. Neither the Client nor the Servers need to be run as root and I strongly advise against it.

Audio::Daemon::MPG132:
Requires Audio::Play::MPG123 an optionally Audio::Mixer for volume control. It automatically spawns mpg123 in the background so there is no need to prestart it.

Audio::Daemon::Xmms:
Requires the Xmms and MP3::Info perl module and xmms installed. Id suggest getting the latest version of the Xmms perl module. It uses the volume and random feature built into xmms and if it doesnt find an xmms running it will try to spawn its own copy. Bear in mind that
xmms MUST HAVE an X display to export to, and that xmms must be running as the same user Audio::Daemon::Xmms is.

Audio::Daemon::Shout:
This wasnt easy to do. It requires MP3::Info and libshout to be installed (http://developer.icecast.org/libshout/) as well as a functioning icecast server. The timing here is pretty critical so I recomend being careful not to be polling the server too much. Be sure to read the icecast docs as Im still confused on how I got this part to work.