client server connections
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 6344
LineControl Server 2.1.21
LineControl allows you to remotely control the Internet connection of a Linux masquerading server using multiple clients. more>>
LineControl allows you to remotely control the Internet connection of a Linux masquerading server using multiple clients. It takes care with the number of clients using the connection and decides upon this number whether the connection should be up or down.
The clients show the time the connection is up and throughput statistics. Different connection types are supported, such as analog modems, ISDN, or even cable modems and ADSL devices.
Main features:
- user accounting using Linux-PAM or passwd/shadow file
- controlling multiple lines
- throughput measuring
- logging & analizing (view example)
- logging to a MySQL database (view example)
- html formatted status report via webserver (view example)
- different line types (analog, isdn, adsl, ... it should be possible to run LC with any line!)
- pinger (to avoid line-drops)
- reporting data (time, nr, ...) about incoming isdn calls to the clients (inclusive addressbook lookup)
- client dependant modifications of the NAT servers firewall (using an external script whenever a client goes on- or offline)
<<lessThe clients show the time the connection is up and throughput statistics. Different connection types are supported, such as analog modems, ISDN, or even cable modems and ADSL devices.
Main features:
- user accounting using Linux-PAM or passwd/shadow file
- controlling multiple lines
- throughput measuring
- logging & analizing (view example)
- logging to a MySQL database (view example)
- html formatted status report via webserver (view example)
- different line types (analog, isdn, adsl, ... it should be possible to run LC with any line!)
- pinger (to avoid line-drops)
- reporting data (time, nr, ...) about incoming isdn calls to the clients (inclusive addressbook lookup)
- client dependant modifications of the NAT servers firewall (using an external script whenever a client goes on- or offline)
Download (0.20MB)
Added: 2005-09-19 License: GPL (GNU General Public License) Price:
1496 downloads
DTLS Client/Server Example 0.2
DTLS Client/Server Example contains a simple DTLS client and DTLS server. more>>
DTLS Client/Server Example contains a simple DTLS client and DTLS server to show how to send UDP data over an encrypted channel using OpenSSL DTLSv1 support.
LIST OF FILES:
Directory: common - Contains callback functions and error reporting functions common to client and server
sslmgr.h
sslmgr.c
Directory: dtls_server
dtls_server.c - DTLS server part
Directory: dtls_client
dtls_client.c - DTLS client part
<<lessLIST OF FILES:
Directory: common - Contains callback functions and error reporting functions common to client and server
sslmgr.h
sslmgr.c
Directory: dtls_server
dtls_server.c - DTLS server part
Directory: dtls_client
dtls_client.c - DTLS client part
Download (0.010MB)
Added: 2006-11-03 License: Free For Educational Use Price:
1092 downloads
Jabber::Connection 0.03
Jabber::Connection is a simple Perl module with connectivity functions for Jabber. more>>
SYNOPSIS
# client connection:
my $c = new Jabber::Connection(
server => jabber.org,
log => 1,
);
# component connection:
# my $c = new Jabber::Connection(
# server => localhost:5700,
# localname => comp.localhost,
# ns => jabber:component:accept,
# log => 1,
# debug => 1,
# );
die "oops: ".$c->lastError unless $c->connect();
$c->register_beat(10, &every_10_seconds);
$c->register_handler(presence,&presence);
$c->register_handler(iq,&handle_iq_conference);
$c->register_handler(iq,&handle_iq_browse);
$c->auth(qmacro,password,myresource); # client auth
# $c->auth(secret); # component auth
$c->send( );
$c->start;
DESCRIPTION ^
The Jabber::Connection package provides basic functions for connecting clients and components to a Jabber server.
Download (0.012MB)
Added: 2007-03-21 License: Perl Artistic License Price:
952 downloads
XML-RPC Client/Server C Library 0.9.10
XML-RPC Client/Server C Library supports persistent HTTP/1.1 conenctions over SSL. more>>
XML-RPC Client/Server C Library is a cross-platform software written in C that supports persistent HTTP/1.1 conenctions over SSL and comes with XML-RPC interface description language and client/server code compiler. Libxr depends on glib2 and libxml2.
Main features:
- Persistent connections over HTTP/1.1
- SSLv3/TLSv1 using OpenSSL.
- XML-RPC interface description language (XDL).
- XML-RPC client stubs/servlet skels compiler.
- Multiple servlets per server.
- Servlet lifetime (init -- call -- call -- fini).
- Multiplatform (linux, mingw32 on windows).
- IPV6 as soon as OpenSSL 0.9.9 is released.
<<lessMain features:
- Persistent connections over HTTP/1.1
- SSLv3/TLSv1 using OpenSSL.
- XML-RPC interface description language (XDL).
- XML-RPC client stubs/servlet skels compiler.
- Multiple servlets per server.
- Servlet lifetime (init -- call -- call -- fini).
- Multiplatform (linux, mingw32 on windows).
- IPV6 as soon as OpenSSL 0.9.9 is released.
Download (0.40MB)
Added: 2007-05-19 License: LGPL (GNU Lesser General Public License) Price:
894 downloads
LoginServer 0.0.2
LoginServer provides a multi-client TCP server class with username/password access control. more>>
LoginServer provides a multi-client TCP server class with username/password access control.
A multi-client TCP server with username/password access control. This server binds to a port and waits for connections. It then spawns LoginServerThreads. In order to create your own server you have to extend the LoginServerThread class to your needs.
Field Details
ALLOW
public static final int ALLOW
This doubleLoginPolicy allows a user to be connected to this LoginServer several times at once.
Field Value:
0
DENY
public static final int DENY
This doubleLoginPolicy denies any additional connections to a particular user when he is already logged on at this LoginServer.
Field Value:
2
KICK
public static final int KICK
This doubleLoginPolicy will close the first (=old) connection when a user logs on twice at this LoginServer.
Field Value:
1
<<lessA multi-client TCP server with username/password access control. This server binds to a port and waits for connections. It then spawns LoginServerThreads. In order to create your own server you have to extend the LoginServerThread class to your needs.
Field Details
ALLOW
public static final int ALLOW
This doubleLoginPolicy allows a user to be connected to this LoginServer several times at once.
Field Value:
0
DENY
public static final int DENY
This doubleLoginPolicy denies any additional connections to a particular user when he is already logged on at this LoginServer.
Field Value:
2
KICK
public static final int KICK
This doubleLoginPolicy will close the first (=old) connection when a user logs on twice at this LoginServer.
Field Value:
1
Download (0.013MB)
Added: 2007-04-19 License: GPL (GNU General Public License) Price:
918 downloads
Terminal Server Client 0.150
Terminal Server Client (tsclient) is a frontend for rdesktop and other remote desktop tools. more>>
Terminal Server Client (tsclient) is a frontend for rdesktop and other remote desktop tools.
Main features:
- GTK+-2 frontend for rdesktop and other remote desktop tools
- GNOME panel applet to quickly launch saved profiles
- reads and writes profiles in the Microsoft format (.rdp), maintaining compatability with the Microsoft client
- similar look and functionality to the Microsoft client
- written in C using GTK and GNOME
- features a profile launcher which launches saved profiles
- Translated to 20+ languages.
- support for rdesktop 1.3
- support for VNC clients (*vncviewer)
- supported vnc options are -fullscreen, -geometry, -depth and -viewonly (set by checking "no motion events"). for a vncpasswd file, put the full path to the file in the username field.
- support for X via Xnest
<<lessMain features:
- GTK+-2 frontend for rdesktop and other remote desktop tools
- GNOME panel applet to quickly launch saved profiles
- reads and writes profiles in the Microsoft format (.rdp), maintaining compatability with the Microsoft client
- similar look and functionality to the Microsoft client
- written in C using GTK and GNOME
- features a profile launcher which launches saved profiles
- Translated to 20+ languages.
- support for rdesktop 1.3
- support for VNC clients (*vncviewer)
- supported vnc options are -fullscreen, -geometry, -depth and -viewonly (set by checking "no motion events"). for a vncpasswd file, put the full path to the file in the username field.
- support for X via Xnest
Download (0.49MB)
Added: 2007-04-26 License: GPL (GNU General Public License) Price:
933 downloads
Net::Server 0.93
Net::Server is an extensible, general Perl server engine. more>>
Net::Server is an extensible, general Perl server engine.
SYNOPSIS
#!/usr/bin/perl -w -T
package MyPackage;
use Net::Server;
@ISA = qw(Net::Server);
sub process_request {
#...code...
}
MyPackage->run(port => 160);
exit;
Main features:
- Single Server Mode
- Inetd Server Mode
- Preforking Simple Mode (PreForkSimple)
- Preforking Managed Mode (PreFork)
- Forking Mode
- Multiplexing Mode using a single process
- Multi port accepts on Single, Preforking, and Forking modes
- Simultaneous accept/recv on tcp, udp, and unix sockets
- Safe signal handling in Fork/PreFork avoids perl signal trouble
- User customizable hooks
- Chroot ability after bind
- Change of user and group after bind
- Basic allow/deny access control
- Customized logging (choose Syslog, log_file, or STDERR)
- HUP able server (clean restarts via sig HUP)
- Dequeue ability in all Fork and PreFork modes.
- Taint clean
- Written in Perl
- Protection against buffer overflow
- Clean process flow
- Extensibility
Net::Server is an extensible, generic Perl server engine. Net::Server combines the good properties from Net::Daemon (0.34), NetServer::Generic (1.03), and Net::FTPServer (1.0), and also from various concepts in the Apache Webserver.
Net::Server attempts to be a generic server as in Net::Daemon and NetServer::Generic. It includes with it the ability to run as an inetd process (Net::Server::INET), a single connection server (Net::Server or Net::Server::Single), a forking server (Net::Server::Fork), a preforking server which maintains a constant number of preforked children (Net::Server::PreForkSimple), or as a managed preforking server which maintains the number of children based on server load (Net::Server::PreFork). In all but the inetd type, the server provides the ability to connect to one or to multiple server ports.
Net::Server uses ideologies of Net::FTPServer in order to provide extensibility. The additional server types are made possible via "personalities" or sub classes of the Net::Server. By moving the multiple types of servers out of the main Net::Server class, the Net::Server concept is easily extended to other types (in the near future, we would like to add a "Thread" personality).
Net::Server borrows several concepts from the Apache Webserver. Net::Server uses "hooks" to allow custom servers such as SMTP, HTTP, POP3, etc. to be layered over the base Net::Server class. In addition the Net::Server::PreFork class borrows concepts of min_start_servers, max_servers, and min_waiting servers.
Net::Server::PreFork also uses the concept of an flock serialized accept when accepting on multiple ports (PreFork can choose between flock, IPC::Semaphore, and pipe to control serialization).
<<lessSYNOPSIS
#!/usr/bin/perl -w -T
package MyPackage;
use Net::Server;
@ISA = qw(Net::Server);
sub process_request {
#...code...
}
MyPackage->run(port => 160);
exit;
Main features:
- Single Server Mode
- Inetd Server Mode
- Preforking Simple Mode (PreForkSimple)
- Preforking Managed Mode (PreFork)
- Forking Mode
- Multiplexing Mode using a single process
- Multi port accepts on Single, Preforking, and Forking modes
- Simultaneous accept/recv on tcp, udp, and unix sockets
- Safe signal handling in Fork/PreFork avoids perl signal trouble
- User customizable hooks
- Chroot ability after bind
- Change of user and group after bind
- Basic allow/deny access control
- Customized logging (choose Syslog, log_file, or STDERR)
- HUP able server (clean restarts via sig HUP)
- Dequeue ability in all Fork and PreFork modes.
- Taint clean
- Written in Perl
- Protection against buffer overflow
- Clean process flow
- Extensibility
Net::Server is an extensible, generic Perl server engine. Net::Server combines the good properties from Net::Daemon (0.34), NetServer::Generic (1.03), and Net::FTPServer (1.0), and also from various concepts in the Apache Webserver.
Net::Server attempts to be a generic server as in Net::Daemon and NetServer::Generic. It includes with it the ability to run as an inetd process (Net::Server::INET), a single connection server (Net::Server or Net::Server::Single), a forking server (Net::Server::Fork), a preforking server which maintains a constant number of preforked children (Net::Server::PreForkSimple), or as a managed preforking server which maintains the number of children based on server load (Net::Server::PreFork). In all but the inetd type, the server provides the ability to connect to one or to multiple server ports.
Net::Server uses ideologies of Net::FTPServer in order to provide extensibility. The additional server types are made possible via "personalities" or sub classes of the Net::Server. By moving the multiple types of servers out of the main Net::Server class, the Net::Server concept is easily extended to other types (in the near future, we would like to add a "Thread" personality).
Net::Server borrows several concepts from the Apache Webserver. Net::Server uses "hooks" to allow custom servers such as SMTP, HTTP, POP3, etc. to be layered over the base Net::Server class. In addition the Net::Server::PreFork class borrows concepts of min_start_servers, max_servers, and min_waiting servers.
Net::Server::PreFork also uses the concept of an flock serialized accept when accepting on multiple ports (PreFork can choose between flock, IPC::Semaphore, and pipe to control serialization).
Download (0.080MB)
Added: 2006-06-27 License: Perl Artistic License Price:
1219 downloads
BitWise Routing Server for Linux 1.7
allows you to accept BitWise connections to multiple computers behind a router. more>> 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).<<less
Download (1011KB)
Added: 2009-04-20 License: Freeware Price: Free
187 downloads
Darwin Calendar Server
Darwin Calendar Server provides a CalDAV server. more>>
Darwin Calendar Server provides a CalDAV server.
The Darwin Calendar Server is a standards-compliant server that allows multiple users to collaboratively share calendaring information. It provides a shared location on the network to store schedules, and allows users to send each other and manage invitations.
In order to provide interoperability with multiple calendaring clients, the server implements the CalDAV protocol, which is an extension of WebDAV, which is in turn an extension of HTTP.
<<lessThe Darwin Calendar Server is a standards-compliant server that allows multiple users to collaboratively share calendaring information. It provides a shared location on the network to store schedules, and allows users to send each other and manage invitations.
In order to provide interoperability with multiple calendaring clients, the server implements the CalDAV protocol, which is an extension of WebDAV, which is in turn an extension of HTTP.
Download (MB)
Added: 2007-02-07 License: The Apache License Price:
1003 downloads
pDonkey Server 0.01
pDonkeyS is Perl implementation of an eDonkey server. more>>
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.
<<lessThis 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.
Download (0.011MB)
Added: 2006-06-20 License: GPL (GNU General Public License) Price:
1228 downloads
VTQLserver 0.91
The VTQLserver package contains a server and clients for videotext access for Linux. more>>
The VTQLserver package contains a server and clients for videotext access for Linux. The server stores the pages of several TV-stations for parallel reading and searching.
You can run many clients in parallel i.e. search all videotext pages, and view them. The only limit is, that the server does not scale well and is not as stable as you may expect it for running it on a server machine. It is intended to be used on workstations, since I do not think, servers have TV cards nor do I have a server machine.
<<lessYou can run many clients in parallel i.e. search all videotext pages, and view them. The only limit is, that the server does not scale well and is not as stable as you may expect it for running it on a server machine. It is intended to be used on workstations, since I do not think, servers have TV cards nor do I have a server machine.
Download (0.30MB)
Added: 2006-07-19 License: GPL (GNU General Public License) Price:
1193 downloads
BitWise Routing Server 1.7
BitWise Routing Server allows multiple PCs behind a router to make direct connections. more>>
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.
<<lessThe 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.
Download (1.0MB)
Added: 2006-03-02 License: Freeware Price:
1331 downloads
Socks Server 5 3.6.4-3
SS5 is a socks server that implements the SOCKS v4 and v5 protocol. more>>
SS5 is a socks server that implements the SOCKS v4 and v5 protocol. As a proxy server, SS5 authenticates, profiles and processes network requests for clients.
Socks Server 5 establishes connections to application hosts for client applications. When the client attempts to access the network, the client connects to the SS5 daemon instead of the application host.
Following authentication, clients request that SS5 perform network activities for the client.
The activities might include:
CONNECT
BIND
UDP ASSOCIATE
The SS5 protocol is independent of application protocols, and can assist with different networking services, including telnet, ftp, finger, whois, gopher, and WWW access.
Enhancements:
- Fix code
<<lessSocks Server 5 establishes connections to application hosts for client applications. When the client attempts to access the network, the client connects to the SS5 daemon instead of the application host.
Following authentication, clients request that SS5 perform network activities for the client.
The activities might include:
CONNECT
BIND
UDP ASSOCIATE
The SS5 protocol is independent of application protocols, and can assist with different networking services, including telnet, ftp, finger, whois, gopher, and WWW access.
Enhancements:
- Fix code
Download (0.16MB)
Added: 2007-06-16 License: GPL (GNU General Public License) Price:
866 downloads
Poptop-PPTP Server 1.3.0
PPTP stands for Point to Point Tunneling Protocol. more>>
PPTP stands for Point to Point Tunneling Protocol. It was developed by a consortium including Microsoft and is used for establishing VPN (Virtual Private Network) tunnels across the Internet. This allows remote users to securely and inexpensively access their corporate network from anywhere on the Internet.
PPTP is built on a client-server model for establishing VPN connections. Most Microsoft operating systems ship with a PPTP client, so there is no need to purchase third-party client software. PPTP has the additional advantage over other VPN technologies of being easy to setup.
Before Poptop, no solution existed if you wish to connect PPTP clients to Linux servers. Using Poptop, Linux servers can now function seamlessly in a PPTP VPN environment. This enables administrators to leverage the considerable benefits of both Microsoft and Linux operating systems.
The current release version supports Windows 95/98/Me/NT/2000/XP PPTP clients and Linux PPTP clients.
Poptop is free software, licensed under the terms of the GNU GPL.
Main features:
- Microsoft compatible authentication and encryption (MSCHAPv2, MPPE 40 - 128 bit RC4 encryption)
- Support for multiple client connections
- Seamless integration into a Microsoft network environment (LDAP, SAMBA) using RADIUS plugin
- Works with Windows 95/98/Me/NT/2000/XP PPTP clients
- Works with Linux PPTP client
- Poptop is, and will remain, totally free under the GNU General Public License
<<lessPPTP is built on a client-server model for establishing VPN connections. Most Microsoft operating systems ship with a PPTP client, so there is no need to purchase third-party client software. PPTP has the additional advantage over other VPN technologies of being easy to setup.
Before Poptop, no solution existed if you wish to connect PPTP clients to Linux servers. Using Poptop, Linux servers can now function seamlessly in a PPTP VPN environment. This enables administrators to leverage the considerable benefits of both Microsoft and Linux operating systems.
The current release version supports Windows 95/98/Me/NT/2000/XP PPTP clients and Linux PPTP clients.
Poptop is free software, licensed under the terms of the GNU GPL.
Main features:
- Microsoft compatible authentication and encryption (MSCHAPv2, MPPE 40 - 128 bit RC4 encryption)
- Support for multiple client connections
- Seamless integration into a Microsoft network environment (LDAP, SAMBA) using RADIUS plugin
- Works with Windows 95/98/Me/NT/2000/XP PPTP clients
- Works with Linux PPTP client
- Poptop is, and will remain, totally free under the GNU General Public License
Download (0.091MB)
Added: 2006-06-27 License: GPL (GNU General Public License) Price:
1227 downloads
Messa 1.01a (Server)
Messa is an instant messager client and server. more>>
Messa is an instant messager client and server. The client has a curses interface and works on the console.
Messa project supports multilingual messages and private messages. The server supports monoprocess operation (without threads), the ability to choose the listening port, and the ability to run under the console.
<<lessMessa project supports multilingual messages and private messages. The server supports monoprocess operation (without threads), the ability to choose the listening port, and the ability to run under the console.
Download (0.011MB)
Added: 2006-07-21 License: LGPL (GNU Lesser General Public License) Price:
1190 downloads
Other version of Messa
Messa is an instant messager client and server. The client has a curses interface and works on ... Messa is an instant messager client and server. The client has a curses interface and works onLicense:LGPL (GNU Lesser General Public License)
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above client server connections search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
