Free isp software for linux

• Small - The complete content management system is less than 100 KB.
• Simple - simple to install and easy to modify. The entire site is stored in a single HTML-file - no database is needed. You edit your entire site with your favorite HTML-editor, upload the content file and get a dynamic website!
• Smart - There is an integrated online WYSIWYG (What-You-See-Is-What-You-Get) editor with link validation, image handling, online editing of system files and an automatic backup on logout. These features that makes CMSimple simply smart!

Major Features:

1. Easy installation
2. The CMS script is less than 100 KB
3. Template driven layout using a css script
4. The contents of the site is stored in a single HTML-file
5. Many languages available (both for the user and for site maintenance)
6. Written in PHP - it runs on Linux/Apache servers, or on Win32 with Apache or IIS
7. Inbuilt WYSIWYG editor (both on IE and Mozilla) - or other alternative editors
8. Uploading of images and files
9. Link validation
10. Search function
11. Print version option
12. User downloads from their HTML content file
13. Simple mailform included
14. Easy setup of multi language sites
15. PHP-scripting may be included within the content (named CMSimple Scripting)
16. Integration with 3rd party scripts possible (using CMSimple scripting)
17. Online editing of system configuration
18. wwwaut login available
19. Automatic backup on logout

Requirements:

• Requirements:
• • CMSimple is recommended for sites with text contents less than 2 MB - This is about 1000 pages of text (about 2,000 characters per page). There is no maximum size to the site but speed will become an issue. Photographs are stored separately, there is no limit to the number of photographs you can use. You are only restricted by the capacity you have bought from your ISP, and by limitations imposed by your PHP settings.
  • Editing of the files is normaly done on your local machine, using a normal browser (see below). You will also need an FTP program (like WS_FTP or WinSCP) to upload the files to your webserver.
• Server requirements
• • CMSimple is written in PHP. Thus, PHP >= 4.0.4 is required on your server. To install PHP on a webserver, you must have administrator rights. Many webhotels offer PHP as part of their standard service.
  • CMSimple runs on a Linux server under Apache, or on Win32 under Apache or IIS. It also runs on Abyss. No database is needed as the entire site contents are stored in a single HTML-file.
• WWW-Authenticate
• • For better password protection it is advised to use wwwaut.
  • On Linux where PHP is installed as an Apache module (not a CGI), this feature will work just by setting wwwaut to 'true' under the configuration settings of CMSimple.
• The WYSIWYG online editor
• • The editor works with new versions of IE, Firefox and Opera.
  • The WYSIWYG online editor does NOT work with Safari, old versions of Opera, Firefox < 1.0 or IE5.
  • The inbuilt WYSIWYG online editor is written in JavaScript. It was formerly known as OEdit.
  • Though the final result of an edit can be viewed by all browsers, the editing can only be done with the following browsers. Linux: Mozilla 1.3 and above.

Enhancements:

• Several language codes have been changed for language/flag files to comply to ISO 639-1 language codes.
• All languages are available from the new download form, and all languages have a flag.
• The licence text in files was changed.
• The Hungarian translation was updated.
• A "readme.txt" file was added in the downloads directory.

daloRADIUS is an advanced RADIUS web management application aimed at managing hotspots and general-purpose ISP deployments. The project features user management, graphical reporting, accounting, a billing engine and integrates with GoogleMaps for geo-locating.

daloRADIUS is written in PHP and JavaScript and utilizes a MySQL database. It is based on a FreeRADIUS deployment with MySQL serving as the backend. Among other features it implements ACLs, GoogleMaps integration for locating hotspots/access points visually and many more features.

CGI::Wiki::Kwiki is an instant wiki built on CGI::Wiki.

A simple-to-use front-end to CGI::Wiki. It can be used for several purposes: to migrate from a CGI::Kwiki wiki (its original purpose), to provide a quickly set up wiki that can later be extended to use more of CGI::Wikis capabilities, and so on. It uses the Template Toolkit to allow quick and easy customisation of your wikis look without you needing to dive into the code.

INSTALLATION

The distribution ships with and installs a script called cgi-wiki-kwiki-install. Create an empty directory somewhere that your web server can see, and run the script. It will set up a SQLite database, install the default templates into the current directory, and create a cgi script to run the wiki. You now have a wiki - edit wiki.cgi to change any of the default options, and youre done.

MORE DETAILS

wiki.cgi will look something like this:

#!/usr/bin/perl -w
use strict;
use warnings;
use CGI;
use CGI::Wiki::Kwiki;

my %config = (
db_type => SQLite,
db_name => /home/wiki/data/node.db,
formatters => {
default => CGI::Wiki::Formatter::Default,
},
);

my %vars = CGI::Vars();
eval {
CGI::Wiki::Kwiki->new(%config)->run(%vars);
};

if ($@) {
print "Content-type: text/plainnn";
print "There was a problem with CGI::Wiki::Kwiki:nn--n";
print "$@";
print "n--n";
print STDERR $@;
}

In the following directions, we use "webserver" to mean the user that your webserver executes CGI scripts as. Often this is actually you yourself; sometimes it is "www-data" or "apache". If you dont know, ask your ISP.
In the script above and in the following, replace /home/wiki/data/node.db with a filename in a directory that you will be able to make readable and writeable by the webserver. SQLite requires access to both the file (for writing data) and the directory it resides in (for creating a lockfile).

Arnos IPTABLES firewall script was initially written because I needed to protect my single-homed Linux machine at work. I wrote it at the time I couldnt find any script that really satisfied my needs except for one that was written by a guy called Seven.
I helped him for several months with the work on his script by suppling patches, reporting bugs etc. In this period I was fortunately also able to master scripting for iptables myself because soon Seven discontinued his work, I never got to even talk to the guy ever again. At that point I decided to continue his work, or actually I started my own branch based on his script.
In the summer of 2002 I finally got an ADSL connection at home. Initially I used the iptables firewall that came with the great ADSL4LINUX-package (http://www.adsl4linux.nl). But it didnt take me long to come to the conclusion that their iptables firewall lacked important features like port-forwarding and flexbility with "trusted hosts" etc.
I also didnt like the fact that I had to use a different firewall for my home machine and the machine at work. This made me decide to use some of the ADSL4LINUX knowledge to implement ADSL support.
By now (about 1 year later as of writing) there are only few remnants left of Sevens original script and many, many, many improvements were applied. One major improvement is the ADSL and NAT support (Check the features page with the specifiations of my firewall). For version 2 (alpha) I plan to completely rewrite to script to make it more flexible and to increase the usability for others.
Main features:
- Very secure stateful filtering firewall
- Both kernel 2.4 & 2.6 support
- It can be used for both single- and multi(eg. dual)-homed boxes
- Masquerading (NAT) and SNAT support
- Multiple external (internet) interfaces
- Support multiroute NAT & SNAT (load balancing over multiple (internet) interfaces)
- Port forwarding (NAT)
- Support MAC address filtering
- Support for DSL/ADSL modems
- Support for PPPoE, PPPoA and bridging modem setups
- Support for static and ISP assigned (DHCP) IPs
- Support for (transparent) proxies
- Full support for DMZs and DMZ-2-LAN forwarding. You can also use it to isolate your eg. wireless LAN.
- (Nmap)(stealth) portscan detection
- Protection against SYN-flooding (DoS attacks)
- Protection against ICMP-flooding (DoS attacks)
- Extensive user-definable logging with rate limiting to prevent log flooding
- Includes options to optimize your throughput
- User definable open ports, closed ports, trusted hosts, blocked hosts etc.
- Log & protection options are both highly customizable
- Support for custom iptables rules in a seperate file
- It can be used with chkconfig runlevel system (eg. RedHat/Fedora)
- Main focus on TCP/UDP/ICMP but additional support for *ALL* IP protocols
- It works with Freeswan IPSEC (VPN) & SSH Sentinel (http://www.freeswan.org) (+virtual IPs)
- It works with PoPTop PPTP (http://www.poptop.org)
- It works with UPnP
- DRDOS protection/detection (experimental)
- Its easy to configure
- And much more.
Enhancements:
- This release fixes a nasty bug in the NAT forwarding rules that caused using subnet-source-restrictions not to work.
- It adds an extra rule to the DHCP server section to allow packets from DHCP servers in the same segment.
- There are several plugin updates.
- A Racoon IPSEC VPN plugin and a transparent DNAT plugin have been added.

Project Observer is an autodiscovering network management system focused primarily on Cisco and Linux networks.
Introduction & History
Autodiscovering PHP/MySQL/SNMP/CDP based network management system focused primarily on Cisco and Linux networks. Capable of automatically generating network diagrams. Networks are automatically discovered based on CDP data collected via SNMP. IP subnet SNMP scanning is not yet implemented but is planned.
The main strenghts of Project Observer lie in being able to easily navigate a large ISP style network, but it has also been designed to be competant at monitoring Unix servers and services such as Apache.
This is the third incarnation of this design that I know of, the original, Brockrigg, was written by Simon Woodward for Onyx Internet and the second, Kikker, was written by myself for Entanet International.
I used the Brockrigg system quite heavily whilst I was at Onyx, so its seemed only sensible for me to write something similar as Kikker when I moved to Enta. Project Observer has been written with learnt during the Kikker development, and will hopefully be a far more flexible and useful piece of software. With the exception of the unfinished diagram drawing code, Project Observer is far superior to the Kikker implementation.
Im currently using Project Observer as my primary network management/graphing system, but I wouldnt classify it as production software, far from it!
If youd like to test the software, please download it below and email me to tell me that youre using it! Its at the stage where a lot of user input, and development help!, is needed, so please contact me if youre using it.
Developed to work with
- Cisco Catalyst 2950, 3548XL, 3550
- Cisco 7200
- Linux Debian / Ubuntu
- FreeBSD (m0n0wall / pfSense)
- Most other Linux and Cisco hardware
Main features:
- Connected-device discovery via CDP.
- Aware of subnets to show machines on the same broadcast domain.
- Graph interface traffic, packets and errors
- Understands a simple interface naming scheme
- Graph cpu usage, load, memory usage, uptime, users, processes for Net-SNMP servers
- Aware of m0n0wall and pfSense SNMP limitations
- Graph mail statistics collected on remote hosts using mail-graph and courier-graph
- Collect data from Apache hosts using /server-status/
- Can detect Linux, FreeBSD, Windows and Cisco OS types
- Parses Cisco version strings and other OIDs to get hardware type, os version and os featureset
- Heavy use of overlib rollover images to ease use
- Generates primative network diagrams using graphviz

mod_vhost_alias is an Apache module that creates dynamically configured virtual hosts, by allowing the IP address and/or the Host: header of the HTTP request to be used as part of the pathname to determine what files to serve. This allows for easy use of a huge number of virtual hosts with similar configurations.

Directory Name Interpolation

All the directives in this module interpolate a string into a pathname. The interpolated string (henceforth called the "name") may be either the server name (see the UseCanonicalName directive for details on how this is determined) or the IP address of the virtual host on the server in dotted-quad format. The interpolation is controlled by specifiers inspired by printf which have a number of formats:

%%

insert a %

%p

insert the port number of the virtual host

%N.M

insert (part of) the name

N and M are used to specify substrings of the name. N selects from the dot-separated components of the name, and M selects characters within whatever N has selected. M is optional and defaults to zero if it isnt present; the dot must be present if and only if M is present. The interpretation is as follows:

0

the whole name

1

the first part

2

the second part

-1

the last part

-2

the penultimate part

2+

the second and all subsequent parts

-2+

the penultimate and all preceding parts

1+ and -1+

the same as 0

If N or M is greater than the number of parts available a single underscore is interpolated.

Examples

For simple name-based virtual hosts you might use the following directives in your server configuration file:

UseCanonicalName Off
VirtualDocumentRoot /usr/local/apache/vhosts/%0

A request for http://www.example.com/directory/file.html will be satisfied by the file /usr/local/apache/vhosts/www.example.com/directory/file.html.
For a very large number of virtual hosts it is a good idea to arrange the files to reduce the size of the vhosts directory. To do this you might use the following in your configuration file:

UseCanonicalName Off
VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.1/%2.2/%2.3/%2

A request for http://www.example.isp.com/directory/file.html will be satisfied by the file /usr/local/apache/vhosts/isp.com/e/x/a/example/directory/file.html. A more even spread of files can be achieved by hashing from the end of the name, for example:

VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.-1/%2.-2/%2.-3/%2

The example request would come from /usr/local/apache/vhosts/isp.com/e/l/p/example/directory/file.html. Alternatively you might use:

VirtualDocumentRoot /usr/local/apache/vhosts/%3+/%2.1/%2.2/%2.3/%2.4+

The example request would come from /usr/local/apache/vhosts/isp.com/e/x/a/mple/directory/file.html.
For IP-based virtual hosting you might use the following in your configuration file:

UseCanonicalName DNS
VirtualDocumentRootIP /usr/local/apache/vhosts/%1/%2/%3/%4/docs
VirtualScriptAliasIP /usr/local/apache/vhosts/%1/%2/%3/%4/cgi-bin

A request for http://www.example.isp.com/directory/file.html would be satisfied by the file /usr/local/apache/vhosts/10/20/30/40/docs/directory/file.html if the IP address of www.example.com were 10.20.30.40. A request for http://www.example.isp.com/cgi-bin/script.pl would be satisfied by executing the program /usr/local/apache/vhosts/10/20/30/40/cgi-bin/script.pl.
If you want to include the . character in a VirtualDocumentRoot directive, but it clashes with a % directive, you can work around the problem in the following way:

VirtualDocumentRoot /usr/local/apache/vhosts/%2.0.%3.0

A request for http://www.example.isp.com/directory/file.html will be satisfied by the file /usr/local/apache/vhosts/example.isp/directory/file.html.

gnome-ppp_logger is a project that logs the amount of time spent on the net when connected with gnome-ppp.

This program lets you establish a PPP connection to your ISP using gnome-ppp. It saves your online time in a log for later analysis. This will prevent you from getting into that state of shock when the phone bill comes.

Hotclient provides an authentication client for users of Hotwire Internet connections.

Currently hotclient is available as
. linux shell application
. Windows command line application
. Perl Command line - Platform Independent under the GNU - General Public License

Hotwire - Internet Private Limited is an ISP which provides 24-7 always on Internet connections. You can visit them at http://www.hotwireindia.net. I do not claim any affiliation with Hotwire or Primus Telecommunications India Limited (the parent company) or anybody else thereof. I am just a user of Hotwire services and promise to abide by their terms of usage/service.

Why Hotclient?
People would ask wasnt the authentication software provided by Primus good enough. Well their software can be got from their website at http://hotwireindia.net/Hotwire.exe. Other clients are available as well at the below links

But I have a actual 24-7 connection. Whenever the network fails or the server goes down for a reboot all these clients just exit out of the program.
Well .....Hello! Im not at my desk at all times. What I needed was a client which picks up the connection as and when it becomes available again so that my downloads would continue. Hence the first version for Linux was born (Im better at gcc than VC, besides i dont actually have a valid copy of VC). The Perl version started and was finished on the same day.

Once I did that well I just went ahead and did the same for Windows. Both the GCC and Win-GCC versions are shell based programs.