Free upnp server software for linux

pDonkeyS is Perl implementation of an eDonkey server. The main goal of the server is to provide framework for further eDonkey protocol exploration, but it could be useful in testing of client software, since the server can be configured to output very detailed debugging info about eDonkey traffic.

This server was made to provide framework for further eDonkey protocol exploration, but it could be usefull in testing of client software, since the server can be configured to output very detailed debug info about eDonkey traffic.

GN gopher server provides a fast gopher and HTTP server.

GN is a fast, light and (for 1995 standards) secure gopher server. An effort is underway to fix the known buffer overflows and bring GN up to par with todays standards.

To use these scripts with the sample sample setup as descibed in the installation guide you need to run mkcache in this (/docs/examples) directory or run mkcache -r in the /docs directory.

To use the image clicking capabilities involving "imagemap" you must get this program from NCSA and compile it. Instructions for setting it up are at

The compiled C program must be renamed imagemap.cgi (or at least something with a suffix .cgi)

Anemon Dhcp Servers goal is to create an implementation of the DHCP protocol under GPL and a lot of stuff around to facilitate network management.
The python sqlobject modules gives anemon the ability to use many database as backend (mysql, postgresql, mssql, sqllite, sybase, etc..)
The project is subdivised (at the moment) in 4 components :
- The Anemon Dhcp Server is a Python/SQL implementation of the DHCP server protocol
- The Anemon Web Center is a web management interface to Anemon Dhcp Server and MyDNS
- The Anemon Dhcp Client will be a Python implementation of the DHCP client protocol
- The Anemon Dhcp relay will be a Python implementation of the DHCP relay protocol

Video server is a streaming video server which feeds a Java applet/application for display. The updates are rather slow, somewhere in the 10 frames/second range on a PIII. The server is written in Bigloo scheme and C. The client is written in Java.

To bring up the video server you have to do the following.

./vs --channel 25 --sd 12 --input 0

./vs --help
for more options. (This seems broken with the newest version of bigloo .... )

How to bring up a java client to connect to a server:
Insure that video/java is in your classpath, and invoke

java vpanel servername

CrossFTP Server is a professional FTP Server for multiple platforms. It is a high-performance, extremely configurable, and most of all a secure FTP server. CrossFTP Server has an easy-to-use GUI for user to configure the servers behavior.
Main features:
- 100% pure Java, free, open source FTP server.
- Multi platform support and multithreaded design.
- User virtual directory, write permission, idle time-out and upload/download bandwidth limitation support.
- You can monitor all the user activities.
- Anonymous login support.
- Both upload and download files are resumable.
- Handles both ASCII and binary data transfers.
- IP restriction support to allow/ban IPs.
- Database and LDAP can be used to store user data.
- All the FTP messages are customizable.
- Implicit/explicit SSL/TLS support.
- MDTM support - your users can change the date-time stamp of files.
- "MODE Z" support for faster data upload/download.
- Easy installation/update by Java Web Start technology.

X personal web server is a personal Web server that sits in your desktop notification area (as a tray icon).

X personal web server is a (much) simpler cousin of KPF, but doesnt require kicker and uses the GTK 2 library for its minimal user interface.

NNML::Server is a minimal NNTP server.

SYNOPSIS

perl -MNNML::Server -e server
perl -MNNML::Server -e unspool

NNML::Server server implements a minimal NNTP server. It is (hope-) fully conformant to rfc977. In addition the commands XOVER and AUTHINFO are implemented.

Supported commands:

ARTICLE, AUTHINFO, BODY, GROUP, HEAD, HELP, IHAVE, LAST, LIST,
MODE, NEWGROUPS, NEWNEWS, NEXT, POST, QUIT, SLAVE, STAT

XOVER, XHDR, LIST NEWSGROUPS ng-spec

The main reason for writing this was to synchronize my mail directories across different hosts. The Mail directories are MH-Style with a .overview file in each folder and an active file in the base directory. These are maintained by the Emacs Gnus backend NNML. To get started, you can generate/update this files using the overview program. Upon POST and IHAVE commands this files will also be updated.

To start from scratch use:

touch /tmp/active;
perl -MNNML::Server -e server(base => "/tmp", port => 3000)

To export your mh-Mail use:

perl overview -base ~/Mail
perl -MNNML::Server -e server(base => "$ENV{HOME}/Mail", port => 3000)

The command POST and IHAVE honour the Newsgroups header if not overwritten by the X-Nnml-Groups header. Articles will contain an appropriate X-Nnml-Groups header when retrieved by message-id.

When the client submits the SLAVE command, all forther post requests are spooled in $Config-spool> (usually ~/Mail/NNML.spool) for performance reasons. You can process the spooled articles by submitting the XUNSPOOL command or by calling

perl -MNNML::Server -e unspool

Rejected articles will be saven in $Config-bad> (usually ~/Mail/NNML.bad)

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.