Free isp software for linux

Kdsl is a tool to help setup, and manage Internet accounts quickly and easily. Despite its name, Kdsl is designed to be a tool to handle many different types of Internet connections, including dial-up.
Main features:
- Kdsl offers dock icon themes - you can download and choose which modem lights you want.
- Accounts can have their unique icons.
- Accounts are available instantly for all users
- An inline browser is available to check your Usage statistics if your ISP supports this feature.
Currently, with version 0.5 , Kdsl supports The following protocols:
DSL accounts - PPPoE is well supported.
PPPoA is supported but untested, and may not work at this time.
Dial-Up Account with Pap/Chap support
Unsupported Protocols
ISDN is unsupported at this time, however, development for ISDN is occuring at present.
Cable support is scratchy at present
Static IP support is untested.

FileBunker is a file backup application which uses one or more GMail accounts as its backup repository.

Because each GMail account supplies 1000 megabytes of storage, it serves as an excellent facility for this purpose. Files are compressed and encrypted for security and efficiency, and can be restored on demand.

Configuring Filebunker:

Before FileBunker can be used to backup your files, you need to configure the application. This is done by choosing Configuration from the File menu. The following describes the information that must be provided to complete this configuration.

FileBunker Password:

First and foremost, FileBunker requires you to establish a password. This password is used to encrypt the data that you backup so that it is secure.

Longer passwords are better, and you should not use a password which coincides with the password to any of the GMail accounts that you are using for backups. Note in order to make sure your password is correctly recorded, you must type it again in the Confirm Password field.

SMTP Server:

FileBunker transfers files to GMail by sending them using the standard email transfer protocol SMTP. You must identify an SMTP server that will send your email. This is usually an address like smtp.mycompany.com, or mail.myisp.com.

If you are not sure what to specify, check the account configuration in your email application (such as Outlook or Eudora), or contact your ISP. Some SMTP servers require authentication in order to transfer messages.

This involves specifying a user name and password which is used to authenticate you to the SMTP server. If your server requires this authentication, check the Requires Authentication checkbox, and click the Configure button to specify the user name and password.

As with establishing your FileBunker password, you will need to confirm your password to make sure it is correctly recorded. Again, check the configuration of your email application, or contact your ISP, if you are not sure whether your SMTP server requires authentication.

Email Repositories:

Finally, and perhaps most importantly, in order to perform any backups you need to specify one or more GMail accounts which your files will be sent to.

Clicking the New button will prompt you to specify the email address and password for an existing GMail account. Note the @gmail.com is already specified, so you will only need to specify the user name (e.g. jsmith).

As with other password fields in this configuration, you will need to confirm the password to ensure it is recorded correctly. After pressing OK you will be returned to the main configuration dialog, and you will see the new account in the Email Repositories list.

You can select it, and click Edit to change the details of that account, or Delete to remove it. Each GMail account gives you 1000 megabytes of storage. You can register multiple accounts at any time as your storage requirements grow.

FileBunker will automatically use a new account as old ones are filled up.
NOTE If you delete an account that already has files backed up to it, those files will not be accessible from FileBunker.

pmacct is a small set of passive network monitoring tools to measure, account and aggregate IPv4 and IPv6 traffic; aggregation revolves around the key concept of primitives (VLAN id, source and destination MAC addresses, hosts, networks, AS numbers, ports, IP protocol and ToS/DSCP field are supported) which may be arbitrarily combined to build custom aggregation methods; support for historical data breakdown, triggers and packet tagging, filtering and sampling.

Aggregates can be stored into memory tables, SQL databases (MySQL or PostgreSQL) or simply printed to stdout. Data is collected from the network either using libpcap (and optionally promiscuous mode) or reading NetFlow v1/v5/v7/v8/v9 and sFlow v2/v4/v5 datagrams, both unicast and multicast.

IP accounting is the key in ISP/IXP network operations like billing, graphing network resources usage, live or historical traffic analysis, handling of network thresholds, provisioning and SLA monitoring. SNMP counters sometime are not this useful because of their coarse granularity.

Finer granularities become valuable if data are historical and match logical entities of interest such as Autonomous System Numbers, departmental or customer network chunks, specific traffic flows, etc. Further, actual large-scale networks are able to produce, in very short times, high amounts of data that become quickly difficult to be processed in a meaningful way

In this context, traffic aggregation and advanced filtering and sampling capabilities are requirements that cannot be missed anymore.

Either using memory or SQL tables as backend storage, pmacct can easily feed data to tools like MRTG, RRDtool, Cacti and Gnuplot among the others. A little scripting abilities are required to glue pmacct with external tools and a number of sample scripts and some tutorials are already available.

LinuxMagic magic-smtpd is a drop in replacement for Dan Bernsteins qmail-smtpd, and was originally designed to be part of the LinuxMagic Magic Mail Server.
This opensource version has been released to allow others to benifit from its anti-spam components, and valid user checking to reduce server loads, and spam volumes.
It is designed to support stock qmail installations, qmail/vpopmail installations, as well as having database support.
Designed for ISP service, this will work for all mail servers large and small. Comments are welcome. Support for other mailers expected in the future.
Enhancements:
- A compilation bug for Red Hat/Mandrake, an SMTP AUTH problem with ext_prog, and a problem loading directories with a newline have been fixed.

SMTarPit is a chrooted SMTP honeypot and tarpit.

I wrote this program because I looked around the Internet for an SMTP Tarpit/Honeypot that was: written in Perl; and, was only an SMTP tarpit/honeypot - I couldnt find one.

SMTarPit is a combined SMTP honey 7187 7187pot and tarpit released under the GPL. It is writen in Perl so it should work on virtually any platform that supports Perl (except Windows). It uses xinetd which looks at port 25 (instructions in the tarball) and when someone calls it, smtarpit is launched and then it chroots itself. It then decides whether there is a man or a machine on the other end and sets about wasting their time.

There are plenty of instructions as to how to configure the program - if Perl is not your first language, you should still be able to see what to do. You will certainly need to put a valid domain name in there but it is all well laid out so that you can install it and run it as a part of xinetd.

If you are an ISP with a tarpitted connection, you can tell which one it is from the fact that the tarpitted connection has a paritcular profile of inactivity and persistancy that no normal SMTP connection has. With this in mind, you can look at your RADIUS logs and take action on the spammer - the one thing that you know from monitoring the connection is that there will be many mails to the same domain from the same source address and that none of them will be solicited as there is in reality nobody to solicit them.

Unsolicited bulk email equals spam and with the RADIUS logs, you can notify the authorities and have the spammer arrested and procecuted - or do nothing more than throw them off and let them spam another day. All spam connections are logged by the tarpit.

How does it work?

Every time an incoming call to port 25 happens, xinetd starts a copy of this server. It only has a small memory footprint and doesnt really consume much processor time.
When the server is started, it responds with the usual welcome message and then waits for the client to respond. When the client does respond, it looks at how long it took and tries to work out whether it is a man or machine at the other end (you can adjust this time in the program if you want).

If the server thinks that it is a machine at the other end, it goes into tarpit mode where everything takes a long time. In SMTP, the server response codes have a three figure number and if that is followed by a dash (-), the client has to wait until it receives one with a space after it. This can take an hour or so.

There are time-outs but you can make the response times all different to avoid profiling/finger-printing of the server - SMTarPit can do this automatically. While all of this is going on, the server is just sitting there, asleep. It doesnt take any significant processor time (arguably any at all) and only a few kB in memory. You can limit the number of concurrent servers with xinetd (explanation and example in the program file at the beginning) and impose any other limitations you want.

In other words, this server allows you to tarpit (stall) several spamming processes (up to the limit you define in the program and your xinetd configuration files) for hours at a time with only minor resource consumption on your part. You certainly wont see any bandwidth eaten away by it (50 Bytes per minute on average is typical).

mysqlApache is a MySQL database backend and browser based frontend for managing large numbers of Apache web servers (each of more than a 1000 virtual and IP-based web sites).

It is part of the OpenISP project and works if you like with mysqlBind, mysqlISP, mysqlIPM, and mysqlSendmail.

Our mysqlISP component systems focus is on a very stable telco quality ISP services via static configuration of servers from mySQL, but with mySQL not required to be live.

Igloo is the perfect solution for mutual interest (MIG) and special interest (SIG) groups and membership based organisations wishing to create a knowledge network around their interests.
Members can create and publishing blogs, wiki pages, polls, discussions, channels, tasks and activities to either their network, the group or to the public.
These tools are integrated tightly into a simple to use platform enabling you to empower your membership around your shared interests.
Main features:
- Membership Wiki, Blog, Events, Tasks, Polls.
- Customisable social networking.
- Really simple publishing tools.
- Membership access control system.
- RSS
- Newsletters
- Configurable file upload
- Channels
- Tagging
Igloo is a web standard product. Igloo will work with standard web server configurations such as a GNU/Linux distribution running Apache and PHP services or a Microsoft server running IIS or PHP. These are available from most internet service providers (ISP) should you wish to host externally.
Igloo has a small hard disk footprint (appox 3mb). The amount of space given to each user for file storage is configurable at installation. Awarding large disk quotas to users will increase your disk space usage which if with an ISP will increase your costs.
Igloo is easy to install and configure for personel trained in server administration.
Enhancements:
- User interface cleanups, a navigation overhaul, support for public publishing, and email notification on comment receipt.

Alternate Password Library (libaltpw) adds alternate password support dynamically with LD_PRELOAD or by linking the shared library with the executable.
Useful, for example, to make sendmail, procmail, and pop3d use an alternate password if you are an ISP.
Works with any program that uses the getpw* family of functions and the password file is configurable through the environment.
Basically this is just another library, you can link against it and it overrides getpw* to point at an alternate password file specified by the environment variable ALTPASSWD.
So the normal way to use it, in non SUID form, would be:
# export ALTPASSWD=/some/other/passwd.file
# export LD_PRELOAD=/usr/local/lib/libaltpw.so.X
# < some command >
And some command will see the alternate password file. This does not work in an SUID contect because LD_PRELOAD is ignored for SUID binaries. To help determine when things will and will not work like expected, there is the runaltpw command. So the above becomes this:
# runaltpw /some/other/passwd.file < some command > < arg > < arg >
And if it thinks things look OK, i.e. not SUID, passwd exists and everything else, it will exec the command after setting up the environment. If things look strange, if will exit instead.
There are also some README.* files that deal with specific programs I had trouble with, either because they had a strange build process, were SUID by default, or both.
Enhancements:
- Added support for the getgr* group handling functions, and a /etc/group.switch and ALTGROUP in the environment, all similar to how the altpw functions work but for groups, as suggested by Bruce Richardson.