Free upnp 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

Portable SDK for UPnP Devices in short libupnp provides developers with an API and code for building control points, devices, and bridges that are compliant with Version 1.0 of the Universal Plug and Play Device Architecture Specification.
This allows discovery, event notification, and control of devices on a network, independent of operating system, programming language, or physical network connection.
UPnP is an architecture that enables discovery, event notification, and control of devices on a network, independent of operating system, programming language, or physical network connection. UPnP is based on common Internet standards and specifications such as TCP/IP, HTTP, and XML.
Enhancements:
- Full support for the Windows and FreeBSD operating systems was added.
- Fixes were made for x86_64 architectures.
- Several memory leaks and possible reasons for crashes were fixed.

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

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.

Arudius is a live CD Linux distribution based on Minislack (Zenwalk) and Slaxs Linux Live scripts.
It contains an extensive set of software tools used by IT security professionals for penetration testing and vulnerability analysis.
Its goal is to include the most comlete set of useful tools and still maintain a small footprint.
Enhancements:
- This release features the addition of some novel security tools: tools for passive network discovery by analyzing broadcast traffic, very fast SMB password cracking tool, a UPnP device discovery tool analyzing M-SEARCH packets, and a few others.

BitWise Routing Server allows multiple PCs behind a router to make direct connections.

The BitWise Routing Server allows you to accept BitWise connections to multiple computers behind a router. Typically, using a router, you would set up port forwarding on BitWises client port (4137), and specify a single destination IP. This is fine until multiple users behind a router all need to accept incoming connections.

As shown by the picture at right, the Routing Server allows individual users to register themselves with the Routing Server, and then the Routing Server accepts all incoming connections and directs those connections to the appropriate user.

The Routing Server requires that your physical router support port forwarding with a way to specify different external and internal ports (this is sometimes labeled "UPnP" by many common home routers).

The Routing Server has several options allowing you to customize the Routing Server for your environment. Many of the options are self-explanatory. The two that are not are Listen on Port and IP filtering. IP filtering is explained in the next section.

The BitWise Routing Server listens on a different port than the BitWise IM client. This allows the Routing Server and the IM client to be run on the same computer without causing conflicts. You will want to set up your router (more detail in a later step) to shift the port of the incoming connections from 4137 to another port. It doesnt particularly matter which port you want to use, as long as it is not a port used by another program. The default port is 4200.

Depending on the complexity of the network, it may be desirable to filter the IP addresses that are allowed to register with the Routing Server. This can be done in the preferences. One very likely scenario would be limiting registrations to the 192.168.1.x IP addresses (192.168 is reserved for local networks). When specifying an IP as the comparison address, you can use any valid IP numbers for wildcards.

In the case shown here, the Routing Server will limit connections to computers having IP addresses of 192.168.1.x. Any number, 0 through 255, could be placed for x in the Routing Server preferences.

If you are not familiar with IP address classes and IP filtering, it will usually be safe to leave Any selected.

Setting up the physical router

The picture at right was taken from a Linksys router, other routers will have a similar capability, although it may be layed out differently. On some routers, the advanced port forwarding options are mistakingly labeled UPnP.

The router setup shows that we are accepting connections on port 4137 and then sending them inside the network on port 4200 (the default port). Enter the IP address of the machine on the network running the Routing Server, and make sure that the rule is enabled. You will want to enter a rule for both TCP and UDP (UDP is used only for voice).

Please consult your router manual for more detailed instructions about how to set up port forwarding on your specific model.

Configuring BitWise to use the Routing Server

In order for you to enjoy the connectivity benefits of the Routing Server, you will need to register with the Routing Server when you log in to BitWise. Prior to logging in to BitWise, click the Setup button next to the Connect button to open the BitWise Setup. There is an area to enter an address for the Routing Server, and to specify what port to use. The port must be the same as the port used above (4200 is the default).

Upon connecting to BitWise, you will be registered with the Routing Server. If you could not be registered, an error message will be displayed. Double-check that the correct address was entered in the Setup.

Registration with the Routing Server

Upon successfully registering with the Routing Server, the Routing Server will display the user name and the IP address of the registration. If you want to unregister a user, click on the username, and then click Unregister. Incoming connections will no longer be forwarded to the specified computer.

It is worth pointing out two things here. First, if you later log in from a different computer, and that computer is also set to use the Routing Server, you will be re-registered with your new IP address. Second, if you are unregistered, or move to another computer but are not set up to use the Routing Server, you will not be able to benefit from the services of the Routing Server.
By default, the Routing Server saves the registered user list when it is closed down.

Using the Routing Server

Assuming that everything is set up correctly, everyone that registers with the Routing Server when they log in to BitWise will be able to enjoy significantly increased connectivity with other BitWise users. As incoming connections are established, you will see the connections listed in the right pane of the Routing Server window. The IP address and the time of the connection is also displayed, and the connection is later marked when it is disconnected.

The disconnected/closed connections may be cleaned from the list at any time using the Clean List button. Only active connections will be left displayed.

FoxTorrent is a Firefox extension that lets you stream torrents as they download, from your web browser, with zero configuration needed.
Main features:
Streaming Fast Delivery
- Watch video and listen to audio as it downloads.
Complete Firefox Integration
- Manage your torrent downloads from your browser window.
Windows, Mac, and Ubuntu Linux
- Consistent downloading experience across all three platforms.
Background Downloading
- Continues to work even after your browser window has been closed.
Low Resource Footprint
- Foxtorrent uses less than 8 MB of RAM, and doesnt hog bandwidth.
Configuration-Free
- Automatic support for NATs, uPNP, and firewalls, with no tinkering necessary.