Free upnp av software for linux

libupnp is a Linux SDK and UPnP devices library.

The Linux SDK for UPnP Devices is an SDK for development of UPnP device
and control point applications for Linux.

It consists of the core UPnP protocols along with a UPnP-specific eXtensible Markup Language (XML) parser supporting the Document Object Model (DOM) Level 2 API and an optional, integrated mini web server for serving UPnP related documents.

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.

NeEM is a library that provides an implementation of epidemic multicast (also called probabilistic or gossip-based) in wide-area networks by using multiple TCP/IP connections in a non-blocking fashion.
Epidemic multicast protocols achieve stable high throughput regardless of node and network faults and scale to very large numbers of participants. Implementation is based on Java 5 and takes advantage of NIO. The goal of this implementation is to be small, self-contained, and practical.
Enhancements:
- Introduces logging and the ability to bind to and advertise specific addresses.
- Some dead code removed in the network layer.
- UPnP based NAT traversal sample application added.

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).

Kino is a non-linear DV editor for GNU/Linux. It features excellent integration with IEEE-1394 for capture, VTR control, and recording back to the camera. Kino captures video to disk in Raw DV and AVI format, in both type-1 DV and type-2 DV (separate audio stream) encodings.
You can load multiple video clips, cut and paste portions of video/audio, and save it to an edit decision list (SMIL XML format). Most edit and navigation commands are mapped to equivalent vi key commands.
Also, Kino can export the composite movie in a number of formats: DV over IEEE 1394, Raw DV, DV AVI, still frames, WAV, MP3, Ogg Vorbis, MPEG-1, MPEG-2, and MPEG-4. Still frame import and export uses gdk-pixbuf, which has support for BMG, GIF, JPEG, PNG, PPM, SVG, Targa, TIFF, and XPM. MP3 requires lame. Ogg Vorbis requires oggenc. MPEG-1 and MPEG-2 require mjpegtools or ffmpeg. MPEG-4 requires ffmpeg.
The current release introduces an experimental fx module, which is accessed from the FX tab in the main window. It provides some basic audio and video fx such as importing, filters and transitions for audio and video. It also provides some basic plug-in functionality to allow third party extension.
Currently, Kino does not support other video file formats or encodings. It does not support multiple layers or tracks of video and audio. We plan to implement most of these features, but first we chose to focus on the basics of IEEE-1394, video, audio, and file input and output. We place a lot of emphasis on quality, stability, performance, and workflow.
Main features:
General
- Free Software (GNU GPL)
- GTK+ 2.0 (GNOME) UI
- XML (SMIL like) project file format
- OSS audio
- GDK or XVideo
- online help
- Peer and developer support forums
- User interface translated to Danish, Swedish, French, Czech, and Spanish.
- Extensible project metadata system.
- Ability to "publish" project file and still frames using an extensible scripting interface.
Media Support
- DV-based (libdv codec)
- PAL or NTSC
- AVI (type1 or type2) or Raw DV files. with large AVI (OpenDML) and LFS (>2GB) support
Capture
- IEEE 1394 (Linux 1394) capture and export
- IEEE 1394 transport control (AV/C)
- USB Jog/Shuttle transport control
Editing
- Fast and frame-accurate navigation/scrubbing
- vi keybindings
- GUI transport controls, scrub bar, and shuttle control
- Storyboard view with drag-n-drop
- Trimmer with 3 point insert editing
- Fine-grain thumbnail viewer (Timeline, but not a typical NLE timeline)
- Drag-n-drop from file manager
- USB Jog/Shuttle input
- Undo/Redo up to 99X
Export
- IEEE 1394 DV Export
- Export audio as WAV, Ogg Vorbis (oggenc), MP3 (lame), or MP2 (mp2enc)
- Export (and import) multiple still frames as JPEG, PNG, TIFF, PPM, and others
- Export audio/video as MPEG-1, MPEG-2, and MPEG-4 (with mjpegtools or ffmpeg)
- Export raw DV via pipe, which is extensible with shell scripts.
Effects General
- Background generator: solid colour, gradient, colour range, noise, and image import
- Effects preview
- Effects plugin API (API not yet stable)
Video Filters
- Black/White
- Sepia tone
- Reverse (i.e. inverse or negative)
- Mirror
- Kaleidescope
- Swap (flip)
Video Transitions
- Fade to/from colour
- Dissolve
- Push Wipe
- Barn Door Wipe
- Colour Differences (and Similarities)
Audio Filters
- Silence
- Fade In/Out
Audio Transitions
- Cross-fade
- Dub (from external file)
- Mix (from external file)

oRTP is a library implementing the Real-time Transport Protocol (RFC3550), written in C.
oRTP project is easy to use and provides a packet scheduler for sending and receiving packets on time, adaptive jitter compensation, and automatic sending of RTCP compound packets. It works with IPv6.
Main features:
- Written in C
- Implement the RFC3550 (RTP) with a easy to use API with high and low level access.
- Includes support for multiples profiles, AV profile (RFC1890) being the one by default.
- Includes a packet scheduler for synchronizing rtp recv and send. Scheduling is optionnal, rtp sessions can remain not scheduled.
- Implements blocking and non blocking IO for RTP sessions.
- Supports mutiplexing IO, so that hundreds of RTP sessions can be managed by a single thread.
- Supports part of RFC2833 for telephone events over RTP.
- The API is well documented using gtk-doc.
- Licensed under the Lesser Gnu Public License.
- RTCP messages sent periodically since 0.7.0 (compound packet including sender report or receiver report + SDES)
Enhancements:
- This version includes new API documentation built with Doxygen and integrates minor patches and optimizations.