Free upnp igd software for linux

GUPnP application is an object-oriented open source framework for creating UPnP devices and control points, written in C using GObject and libsoup. The GUPnP API is intended to be easy to use, efficient and flexible.

The GUPnP framework consists of the following two libraries:

GSSDP implements resource discovery and announcement over SSDP.
GUPnP implements the UPnP specification: resource announcement and discovery, description, control, event notification, and presentation (GUPnP includes basic web server functionality through libsoup). GUPnP does not include helpers for construction or control of specific standardized resources (e.g. MediaServer); this is left for higher level libraries utilizing the GUPnP framework.
The GUPnP framework was born out of frustration with libupnp and its mess of threads. GUPnP is entirely single-threaded (though asynchronous), integrates with the GLib main loop, and provides the same set of features as libupnp while hiding most of the UPnP internals through an elegant object-oriented design.

This project is free software released under the GNU LGPL.

upnp2mrtg is a add-on for the mrtg (Multi Router Traffic Grapher). upnp2mrtg is a command line tool written in shell which can gather statistics from an upnp enabled FritzBox DSL router.
Main features:
- shell script
- if your bash is compiled with --enable-net-redirections no netcat is required
- only 1700 bytes or 70 lines of code
- very well tested! ;-))
- very little requirements
- fast
- works

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.

The Linux UPnP Internet Gateway Device Project is an attempt to begin work on a UPnP Forum-compliant Internet Gateway Device. It allows Windows Messenger or other this kind of programs to use voice/video through a Linux firewall running Iptables.
This program only creates DNAT (portmap) entries in you firewall on the external interface (public ip). Any other firewall code must be set to allow basically all tcp and udp through the FORWARD chain to your client machines, and the client machines must be able to contact the firewall using tcp and udp through the firewalls INPUT chain on it internal interface.
We will be adding some checks to see if FORWARD has a default policy of DROP or REJECT, however placing rules once we determine this is a bit tricky. Theres at the moment no real way to check to see if a packet matchin this rule will pass through any additional rules that may be located above it. Also, we will probably need to check for any rules below as well. Hopefully we can get this implemented soon.
In the meantime, please be aware of this fact, and if you are seeing Advertisements sent in the /var/log/debug file (or whatever you have syslog set to log DEBUG level messages to), but you are not seeing AddPortMaps, the most likely this is the problem, or it could be the following problem.
UPnP works with the 239.0.0.0/255.0.0.0 multicast addresses. Windows Messenger may also send request to a Unicast address, and thus the reason for the patch to the UPnP source code for this to work. Nevertheless, to add a route in your box for the multicast address, just use the following command, replaceing with the interface name of your inside interface name (i.e., eth0).
Enhancements:
- Fixed issues with Direct Play games not deleting broadcast port mappings So most if not all Direct Play games will now work correctly.
- Added Byte and Packet counter code contributed by giussani
- Changed all the xml and skl files to include our UUID and some other updatet information that needed to be changed.
- Added a CREDITS file to make sure I give thanks to the person who inspired me to write this program, along with everyone else whos contributing.
- Fixed the startup message in messages to report the correct version now.
- Once again, other small changes i cant remember

GeeXboX uShare is a UPnP A/V Media Server. It implements the server component that provides UPnP media devices with information on available multimedia files. uShare uses the built-in http server of libupnp to stream the files to clients.

GeeXboX uShare is a fork from the GMediaServer (UPnP Audio Media Server) from Oskar Liljeblad. It has been stripped down for GeeXboX purpose in order to be a lighweight multimedia media server.

By opposition to GMediaServer, it does _NOT_ grab any information from audio files (like ID3 tags) but is _NOT_ limited to audio files. GeeXboX uShare is able to provide access to both images, videos, music or playlists files (see below for a complete file format support list). It does not act as an UPnP Media Adaptor and thus, cant transcode streams to fit the client requirements.

uShare is written in C by Benjamin Zores for the GeeXboX project. It is designed to provide access to multimedia contents to GeeXboX but can of course be used by any other UPnP client device. It should compile and run on any modern POSIX compatible system such as Linux.

GeeXboX uShare is free software - it is licensed under the terms of the GNU General Public License (GPL).

buzztard project aims to provide a free replacement (or clone) of the currently windows only and closed source software Buzz. The buzz software is not really further developed, as the main developer has lost his source code.
We want to provide a music production environment, that is based on a very modular approach (following some of the ideas behind buzz), to allow many people to get involved. We hope that our software will have a better usabillity than buzz has although. We dont want to make this a 1:1 copy though.
The buzztard project itself has no direct link to buzz (apart from concepts). To allow migration for buzz users, we will provide song-file import and buzz-machine reuse.
The projects objective is a music application. If youve used programs like FastTracker or the original AMIGA SoundTracker, that will give you an idea. The buzztard editor uses a similiar concept, where a song consists of a sequence with tracks and in each track one uses patterns with events (musical notes and control changes). In contrast to the Tracker programs, tracks are not simply sample players. A song has a setup where one can arrange virtual audio plugins and link them together. Each of these machines can be controlled realtime or via patterns in the sequencer.
The buzztard editor will be just one possible application of the framework we will implement. Tools like a dj mixing application or a live session composer are other things that could be built using this framework.
The main goal is to get as far as buzz now is. Beyond that, we have thousands of ideas to make to improve the usability and production potential of such software. Buzztard should not be just a clone of buzz. It shall live beyond! Yay!
Enhancements:
- This version has lots of UI usability improvements, bug fixes, more instant apply settings and introduces some interactivity features (interaction controller and upnp playback controller).
- The gstreamer extension modules got two new interfaces for presets and help.
- A Fluidsynth generator plugin has been started.

GMediaRender is a UPnP media renderer for POSIX-compliant systems, such as GNU/Linux or UNIX. It implements the server component that provides UPnP controllers a means to render media content (audio, video and images) from a UPnP media server.

MediaServer / AV

UPnP A/V is a three-tier system, consisting of Servers, Renderers and Controllers. With an A/V UPnP controller you can instruct a UPnP A/V Renderer (such as GMediaRender) to play multimedia content (pictures, music tracks, radio broadcasts, movies, ..) available from a UPnP A/V Server.

UPnP A/V components are available both as stand-alone consumer electronics devices, as well as are software-only implementations. Listed below are some software implementations which run on GNU/Linux.

PyMediaServer is a barebones UPnP-based Media Server for use with a Netgear MP101 Digital Music Player.
PyMediaServer currently:
- supports the Netgear MP101 and has not been tested with any other UPnP client devices
- Supports browsing MP3s (only MP3s at this point) via the UPnP ContentDirectory service, but only provides organization by directories (that is, it does not support an Artist category, Genre category, etc.)
- Supports ordering MP3s found in a given folder via track number if those track numbers are available via ID3v2
- Supports playing MP3s via RTSP and RTP/UDP to the MP101
Development is currently in progress to add support for organization by Artist, Genre, and Alblum. Additional features Id like to include are:
- Playlist support
- Internet Radio support
- PyGTK Interface
- Improved Installer
- WMA support
- Additional Media Player support
Installing and Running
The installation process at the moment is straightforward, though there are some noted issues with it.
In a nutshell I recommend downloading the source to /usr/src or /usr/local/src and then running install.sh in the pymediaserver directory. This merely creates a link from /usr/bin/pymediaserver to the MediaServer.py file. You will have to edit install.sh if you want the link created in a different bin directory.
Running should be straightforward:
pymediaserver /path/to/mp3s/ to load a new set of content
Note that /path/to/mp3s/ is an absolute path and should be readable by the user from which pymediaserver is launched (robustness isnt supported yet).
If no arguments are presented to pymediaserver it will try to load a stored dictionary in $HOME/.pymediaserver/. If one doesnt exist it will fail (probably with a nasty traceback).
Enhancements:
- The non-graphical version no longer requires GTK+ or X in any fashion, allowing it to be started as a daemon.
- The Media Directory is now read directly from the Amarok database if available using a SQLite interface.
- Error handling when encountering malformed ID3 tags was improved along with the handling of character encoding of MP3 titles.