Free what is upnp software for linux

Play What I Mean project allows a user to, from a single commandline or terminal, enter a string, or list of strings, that represent what he/she wishes to have played by whatsoever media player he chooses, the default being MPlayer, and then having that particular item be found and played.
What this essentially means is that if I were to have a sudden hankering to listen to a particular song or video, lets say Ice Pick by The Pillows, which happens to be the song to a particular music video that I enjoy watching. Under the traditional methods of video viewing I would be stuck with two potential courses of action for playing this particular file:
- Change directories several times to that one folder somewhere that I "know" its in, or
- Point and Click my mouse until I find that same directory and then search through what could be countless files to find it.
Each of these prospective choices have their own inherent difficulties and ire. Using the commandline often requires alot of typing to arrive at the desired directory, often times nestled deep within the tree.
Once there your problems only multiply by the number of files you actually store in your "media" folder, try ls | moreing through a heavily populated folder looking for the name of that file you wanted to play sometime, it isnt too fun and further is a waste of my valuable time.
You may be thinking at this point that the second option, the graphical one, must be easier since its exciting, full of pictures, and frankly novel, I disagree. I may not be the best judge on this matter, seeing as how I cant see out of my right eye however, I feel that scanning through a large folder, or folders, full of files is quite a strain on the vision, and more importantly an unnescesary burden on what should be a simple matter.
Main features:
- Nestable Playlist support
- Multi-string arguments
- Transparent command option passing
- Cache for faster access of frequently played files
- Graphical configure

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.

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

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.

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.

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