Free proxy server connections software for linux

Anon Proxy Server is a fast http, https, socks caching proxy server. Easy web based configuration, optional p2p anonymous mode.
Main features:
- Easy Configuration - Web based, no editing text configuration files.
- Memory - No big databases are kept in memory, no matter how large the cache is, memory usage will only increase when more users access it at the same time.
- Speed - To see how much cpu the proxy uses, run top or task manager. Then open multiple windows and hit reload continously, on my computer I usually run out of bandwidth before it goes near 3-5% cpu usage.
- Shared Cache - Can be used as a general cache for all users of a computer/network instead of one cache per profile.
- Automatic config - Auto generates the .pac file for automatic proxy settings, no more updating in the do not use proxy section of individual users browsers.
- Anonymous P2P proxy - Joining the anonymous proxy network will allow you to use other peoples proxys for browsing and allow them to use yours.
- SOCKS - Supports enough of SOCKS to run ftp, most Instant messengers, irc, limewire, etc.
- User authentication - Supports external user authentication.
Enhancements:
- The program now checks for errors in access configuration.
- Variable timeout values were added.
- Log rotation was fixed.
- Occasional crashes on a bad URL were fixed.
- The auto configuration .pac file was fixed, so it should work even if the proxys URL was not set properly.
- Anon proxy defaults to 3 keys now for more reliability.

Proxy Detector is a PHP class that can detect HTTP requests via proxy. This class can detect if a visitor uses a proxy server by scanning the headers returned by the user client.
When the user uses a proxy server, most of the proxy servers alter the header. The header is returned to PHP in the array $_SERVER.
Enhancements:
- This is the first release of the class and implementation example.

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.

Viralator is a Perl script that virus scans HTTP/FTP downloads request on a UNIX server after passing through the Squid proxy server.
Even when I implemented virus protection for my network email server we still continued to get the odd virus. Most of the viruses came from people using free webmail accounts like Hotmail or Yahoo and downloading the infected attachments to their machines or through downloading junk.
Rather than block access to the users I decided to look at how we could better protect the network. I looked at a couple of different products both comercial and free but they were either too expensive or did not meet my needs.
That is how Viralator was born. Viralator Proxy Virus Scanner is licenced under the GPL.
Viralator should work in any UNIX system that uses Apache and Squid servers. We have reports about successful instalations on:
- RedHat Linux
- Mandrake Linux
- SuSe Linux
- e-Smith Linux
- Slackware Linux
- Conectiva Linux
- Debian Gnu Linux
Supported Redirectors:
- Squirm
- SquidGuard
- Jesred
Supported Virus Scanners
- AntiVir
- AVP
- RAV
- Inoculate
- Sophos Sweep
- McAfee
- Trend
- Clamav
- Bit Defender (free edition)
The original concept for Viralator came from the Viromat project. Without Viromat the Viralator project would not have had a starting point. We can also thank Ralph Meyer for badgering me into releasing the script under the GPL.
Enhancements:
- Parenthesis are included on the regular expression used to validate URLs.
- The character set checking step, which was not working before last patch released, has been fixed.

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)

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.