Free miniupnp client and daemon 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.

iFTPd, Independent FTP Daemon, is an open source FTP server written in Java. Independent FTP Daemon features platform independence, system independence, ruggedness and a virtual file system.
The target audience of the FTP server is for those admins that need to be able to share files without having to install several other programs and databases and without having to configure the rest of the system.
Main features:
- Platform independence (Where do you want your JVM to go today?)
- System independence
- Does not require any users / groups on the host system.
- Does not require an SQL database.
- Does not does have weird and wonderful dependencies that must be downloaded from 500 different places.
- Ruggedness
- Once started, only the admin can stop iFTPd
- Virtual file system
- Create virtual file links, virtual directory links
- Merge several directories into one virtual directory
- Completely transparent to the user
- Users and groups
- Firewall friendly
- Multithreading
- Text file-based configuration
- Telnet-based status monitor
- HTML status monitor
Installation:
Unpack iftpd.zip.
Check that conf/iftpd.conf is to your liking.
Make at least one group in conf/groups/.
Make sure that at least one of the groups has a root directory.
"/stash/ftp/" r+ "/"
Make at least one user file in conf/users/.
Start iFTPd.
Linux users run: iftpd.sh
Enhancements:
- SSL (AUTH TLS) support has been added.
- Old scripts have been replaced with iftpd.sh.
- ALLO has been added for binary mode, but untested because no clients support it.
- Groups can contain other groups.
- SITE UTIME support has been added.
- Group files can have empty lines.
- CLNT support has been added.
- StatusToHtml (#CLIENTNAME#) has been added.
- The rename bug has been fixed (only worked with full paths before).
- Aborted transfer notification should finally be fixed.
- FEAT support has been added.
- IdleStrictChecking has been added in iftpd and iftpd.conf.

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

Music Player Daemon (MPD) is a server that allows remote access for playing music (MP3, Ogg Vorbis, FLAC, AAC, Mod, and wave) and managing playlists.
Music Player Daemon makes a great desktop player with frontend options (Qt, GTK, ncurses, Windows, and Web clients are available). It is also appropriate as a console player that is scriptable, and is especially useful if X is restarted frequently.
A set of rapid development tools for clients are being developed and include a C library, Python module, PHP class, Perl module, and Java Class.
The goals are to be easy to install and use, to have minimal resource requirements, to be stable and flexible, and easy to interface.
MPD is designed around a client/server architecture, where the clients interact with MPD over a network. Thus, running MPD is only half of the equation; to use MPD, you need to install a MPD client:
Web Clients
- phpMp - Web interface written in PHP
- phpMp2 - Another web interface written in PHP
Graphical Clients
- gmpc - Gnome Music Player Client
- kmp - Graphical interface written in Qt
- MPDCon - A GNUstep Graphical interface
- glurp - Graphical interface written in GTK+
- WMmp - Window Maker dockapp
- gtk2mp - Try gmpc first! Graphical interface written in Gtk+
Command Line Clients
- ncmpc - ncurses (command line) client
- mpc - (Scriptable) command line client
- bashmp - client written as bash aliases and functions
Miscellaneous Clients
- mpcstick - Linux joystick client
- arthist - Perl client to generate a web blog of MPD activity

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

Internet Registry Routing Daemon (IRRd) is a freely available, stand-alone Internet Routing Registry database server. IRRd supports the RPSL and RPSLng Routing Policy Specification Language standards.

The IRRd package includes all required IRR support services, including: automated near real-time mirroring of other IRR databases, update syntax checking, authentication/security, and notification.

LDAP Mailing Lists Access Policy Daemon (MLAPD) is a mailing list manager that uses LDAP (instead of BDB or GDBM) to control list access. Its designed to work in conjunction with Postfix as an access policy delegation daemon. It manages electronic mail discussion and e-newsletter lists. Its goal is to store/read list data on/from LDAP.
It works as a Postfix access policy delegation agent, so it can be installed one time and used by multiple Postfix instances, or installed multiple times and not suffer database access concurrency issues (because it uses LDAP).
Enhancements:
- This can be considered the first stable and usable release.

The PXE daemon allows network managers to boot PXE-enabled machines over the network. Basically it envolves BOOTP, TFTP (so far so good) and a PXE daemon. This is where all the trouble starts. There is only one implementation arround, and if doesnt work on anything other than little endian machines.
I originally tried to correct some of the major problems in this code. However firstly, I could not find anyone with at Red Hat or Intel to deal with and secondly, Intel seem very unintrested in porting the code the big endian machines. The source is also very messy and it would have taken longer to correct the original code, than to re-write the whole daemon. If you dont believe me on this point, just have a look at it, IMHO any daemon that responds to keyboard input is a bad thing (it thinks it had packets coming from the keyboard even when in daemon mode)
You are lucky then, but a lot of places have already got a bootserver, and most likely it will be a UNIX based machine that is not x86. So, why put in another machine when there is already one there?
If you know enough about PC, you will know there are several operating modes. The mode the PC boots in is only able to access the low 640KB of memory. By using the PXELINUX bootstrap code it is possible to boot using the full amount to memory in the system. The means you can do some nice things including boot a Linux kernel + Ramdisk over the network, as you would for a Sun. Please note that the Intel bootstraping code is very limited in this sense.
I dont recommend it anymore, I just havent had time to do a lot of updates, PXELINUX is far far better (see link below). However Intels PXE daemon is naff (IMHO)
Enhancements:
- Increase the interface buffer to hold more than three interfaces
- Fixed a segfault in when multicast was disabled
- Fixed null pointer dereference when looking at interfaces with no IP address