Free dsl 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.

DSLR Notifier is a Firefox extension which enables members of Dsl/Broadbandreports.com to keep tabs on their instant messages.

Enables members of Dsl/Broadbandreports.com to keep tabs on their instant messages and updated topics.

Drools is a Rules Engine implementation based on Charles Forgys Rete algorithm tailored for the Java language. Adapting Rete to an object-oriented interface allows for more natural expression of business rules with regards to business objects. Drools is written in Java, but able to run on Java and .Net.
Drools is designed to allow pluggeable language implementations. Currently rules can be written in Java, Python and Groovy. More importantly, Drools provides for Declarative Programming and is flexible enough to match the semantics of your problem domain with Domain Specific Languages (DSL) via XML using a Schema defined for your problem domain.
DSLs consist of XML elements and attributes that represent the problem domain.
Enhancements:
Bug
- DROOLS-294 - WorkingMemory synchronization is not complete (Barry Kaplan)
- DROOLS-314 - MethodMetadataSources need a stopping Class (Barry Kaplan)
- DROOLS-318 - WorkingMemoryEventListenerProcessor implements wrong interface (Barry Kaplan)
- DROOLS-347 - Maven build of drools-spring-jdk5 fails on Mac OS X (Andy Barnett)
- DROOLS-367 - Wrong rule executed when modifying object in workingmemory (Michael Neale)
- DROOLS-374 - Caching of classloaders in causes problems with hot deployment in some J2EE containers (Michael Neale)
- DROOLS-376 - Make source file (c) headers consistent with codehaus (Michael Neale)
- DROOLS-386 - Bug with the Escalation example? (Robert Laflamme)
- DROOLS-401 - Missing semaphore types in schema file (rules.xsd) (Edson Tirelli)
- DROOLS-403 - no-loop incorrectly removes all instances of a rule from the agenda (Michael Neale)
- DROOLS-409 - rename getNoLoop to isNoLoop to obey JavaBean naming convention (Mark Proctor)
- New Feature
- DROOLS-303 - Default rule-method parameter annotation (Barry Kaplan)
- DROOLS-360 - Maven goal for drools-all-src-XXX.zip (Mark Proctor)
- DROOLS-361 - Auto add RuleSet to RuleBase (Barry Kaplan)
- DROOLS-363 - Decision tables in spreadsheets (Michael Neale)
- DROOLS-383 - Integrate java:functions feature in decision tables. (Michael Neale)
- DROOLS-388 - Support for application data (variables), per rule duration, salience and names (Ricardo Rojas)
- DROOLS-408 - Xor Group so only one rule can fire for a specific group (Mark Proctor)
Improvement
- DROOLS-296 - Allow for default id value in parameter annotations (Barry Kaplan)
- DROOLS-297 - Allow multiple consequence annotations per rule (Barry Kaplan)
- DROOLS-301 - Remove Drools prefix from annotations (Barry Kaplan)
- DROOLS-309 - MethodMetadataSource to ignore certain classes (Barry Kaplan)
- DROOLS-310 - Condition sharing for POJO rules (Peter Royal)
- DROOLS-348 - JDK 1.3 no longer supported (Barry Kaplan)
- DROOLS-350 - Utilize 1.4 nested exceptions (Barry Kaplan)
- DROOLS-357 - Packaging between factory and meta needs some attention (Barry Kaplan)
- DROOLS-364 - Update spring libs and config files for 1.2 (Barry Kaplan)
- DROOLS-372 - Update Groovy to JSR-03 (Mark Proctor)
- DROOLS-381 - Add object-condition tests to RuleBuilderTest (Barry Kaplan)
- DROOLS-387 - add ability for a DSL to acces the XML namespace information in a Configuration (James Strachan)
- DROOLS-402 - Refactor maven.xml and drools:dist to make it faster and more intelligent (Mark Proctor)
- DROOLS-410 - Update Janino to 2.3.8 (Mark Proctor)
Test
- DROOLS-346 - Ant build.xml doesnt run drools-jsr94 unit tests (Andy Barnett)
- Task
- DROOLS-351 - Remove drools-annotation and derivitives from 2.1 (Barry Kaplan)
- DROOLS-370 - Add in drools-decisiontables subproject (Michael Neale)

Darkstat is a network traffic analyzer. Its basically a packet sniffer which runs as a background process on a cable/DSL router and gathers all sorts of useless but interesting statistics.
Darkstat is no longer under active development or maintainership.
I no longer have the time to do it. And I no longer have a need for it. darkstat was originally written because I had very specific requirements for a network link monitor. I now use traf.
I started work on darkstat 3 a long time ago, got a fair bit of work done on it, then stalled for ages as other things took priority. If someone else wants to take over, mail me about it. I considered putting up a "work in progress" tarball on this page.
Compatibility:
Darkstat works fine for me under Gentoo Linux and FreeBSD STABLE. It sort-of works on OpenBSD and NetBSD.
Enhancements:
- The Web interface has been improved.
- Reports can now be paged through and sorted by different criteria.
- Promiscuous sniffing and DNS resolution can now be disabled on the command line.
- Minor bug fixes and performance improvements were made.

Damn Small Linux is a business card size (50MB) bootable Live CD Linux distribution. Despite its minuscule size, Damn Small Linux strives to have a functional and easy to use desktop.
Having a working Linux desktop distro on a 50 mb bootable business card CD is just too cool not to do.
Damn Small Linux has a nearly complete desktop, including XMMS (MP3, and MPEG), FTP client, Dillo web browser, links web browser, FireFox, spreadsheet, Sylpheed email, spellcheck (US English), a word-processor (FLwriter), four editors (Beaver, nVi, Zile [emacs clone], and Nano [Pico clone]), graphics editing and viewing (Xpaint, and xzgv), Xpdf, emelFM (file manager), Naim (AIM, ICQ, IRC), VNCviwer, Rdesktop, SSH/SCP server and client, DHCP client, PPP, PPPoE (ADSL), a web server, calculator, generic and GhostScript printer support, NFS, Fluxbox window manager, games, system monitoring apps, a host of command line tools, USB support, and pcmcia support, some wireless support.
If you like DSL you can install it on your hard drive. Because all the applications are small and light it makes a very good choice for older hardware.
Originally DSL was based on model_k, which did an excellent distillation of Knoppix down to 33 megabytes. But more recent versions are a reduction from Knoppix proper.
As many know Knoppix is based on Debian which really made my task a lot easier, but the applications on the CD are not pure Debian. I am using a few apps that are not available via apt-get.
Whats New in 4.0 RC1 Development Release:
- New pendrive usbhdd installation script now uses grub with DSL on 2nd small partition.
- Removed pendrive usbzip install script, syslinux and mtools.
- Changed default root menu from dfm to chosen WM menu.
- Updated "Getting Started" to reflect changed defaults.
- Changed kernel from 2.4.34.1 to 2.4.31 to gain user contributed modules, e.g., ipw2and nvidia.
- Created new support modules: cloop, unionfs, ndiswrapper, fuse, and madwifi in support of kernel change.
- Updated nano-tiny to v2.0.6.
- Fixed non-critical bug in dsl-config concerning hard drive installations.
- Added dsl 3 runlevel for multiple user dsl consoles.
- Fixed bug in iwconfig-setup
- Updated functions5.lua
- Updated fluxbox menus to use system default (helvetica).
- Added vim link
- Patched knoppix-autoconfig to correct language issues.

The Wonder Shaper is a very special network shaper script with a lot of features. Works on Linux 2.4 & higher.

Goals

I attempted to create the holy grail:

* Maintain low latency for interfactive traffic at all times.

This means that downloading or uploading files should not disturb SSH or even telnet. These are the most important things, even 200ms latency is sluggish to work over.

* Allow surfing at reasonable speeds while up or downloading

Even though http is bulk traffic, other traffic should not drown it out too much.

* Make sure uploads dont harm downloads, and the other way around

This is a much observed phenomenon where upstream traffic simply destroys download speed. It turns out that all this is possible, at the cost of a tiny bit of bandwidth. The reason that uploads, downloads and ssh hurt eachother is the presence of large queues in many domestic access devices like cable or DSL modems.

Why it doesnt work well by default

ISPs know that they are benchmarked solely on how fast people can download. Besides available bandwidth, download speed is influenced heavily by packet loss, which seriously hampers TCP/IP performance. Large queues can help prevent packetloss, and speed up downloads. So ISPs configure large queues.

These large queues however damage interactivity. A keystroke must first travel the upstream queue, which may be seconds (!) long and go to your remote host. It is then displayed, which leads to a packet coming back, which must then traverse the downstream queue, located at your ISP, before it appears on your screen.

This HOWTO teaches you how to mangle and process the queue in many ways, but sadly, not all queues are accessible to us. The queue over at the ISP is completely off-limits, whereas the upstream queue probably lives inside your cable modem or DSL device. You may or may not be able to configure it. Most probably not.

So, what next? As we cant control either of those queues, they must be eliminated, and moved to your Linux router. Luckily this is possible.

Limit upload speed somewhat

By limiting our upload speed to slightly less than the truly available rate, no queues are built up in our modem. The queue is now moved to Linux.

Limit download speed

This is slightly trickier as we cant really influence how fast the internet ships us data. We can however drop packets that are coming in too fast, which causes TCP/IP to slow down to just the rate we want. Because we dont want to drop traffic unnecessarily, we configure a burst size we allow at higher speed.

Now, once we have done this, we have eliminated the downstream queue totally (except for short bursts), and gain the ability to manage the upstream queue with all the power Linux offers.

Let interactive traffic skip the queue

What remains to be done is to make sure interactive traffic jumps to the front of the upstream queue. To make sure that uploads dont hurt downloads, we also move ACK packets to the front of the queue. This is what normally causes the huge slowdown observed when generating bulk traffic both ways. The ACKnowledgements for downstream traffic must compete with upstream traffic, and get delayed in the process.

We also move other small packets to the front of the queue - this helps operating systems which do not set TOS bits, like everything from Microsoft.

Allow the user to specify low priority traffic (new in 1.1!)

Sometimes you may notice low priority OUTGOING traffic slowing down important traffic. In that case, the following options may help you:

NOPRIOHOSTSRC
Set this to hosts or netmasks in your network that should have low priority

NOPRIOHOSTDST
Set this to hosts or netmasks on the internet that should have low priority

NOPRIOPORTSRC
Set this to source ports that should have low priority. If you have an unimportant webserver on your traffic, set this to 80

NOPRIOPORTDST
Set this to destination ports that should have low priority.

See the start of wshaper and wshaper.htb

Results

If we do all this we get the following measurements using an excellent ADSL connection from xs4all in the Netherlands:

Baseline latency:
round-trip min/avg/max = 14.4/17.1/21.7 ms

Without traffic conditioner, while downloading:
round-trip min/avg/max = 560.9/573.6/586.4 ms

Without traffic conditioner, while uploading:
round-trip min/avg/max = 2041.4/2332.1/2427.6 ms

With conditioner, during 220kbit/s upload:
round-trip min/avg/max = 15.7/51.8/79.9 ms

With conditioner, during 850kbit/s download:
round-trip min/avg/max = 20.4/46.9/74.0 ms

When uploading, downloads proceed at ~80% of the available speed. Uploads at around 90%. Latency then jumps to 850 ms, still figuring out why.

What you can expect from this script depends a lot on your actual uplink speed. When uploading at full speed, there will always be a single packet ahead of your keystroke. That is the lower limit to the latency you can achieve - divide your MTU by your upstream speed to calculate. Typical values will be somewhat higher than that. Lower your MTU for better effects!

A small table:

Uplink speed | Expected latency due to upload
--------------------------------------------------
32 | 234ms
64 | 117ms
128 | 58ms
256 | 29ms

So to calculate your effective latency, take a baseline measurement (ping on an unloaded link), and look up the number in the table, and add it. That is about the best you can expect. This number comes from a calculation that assumes that your upstream keystroke will have at most half a full sized packet ahead of it.

This boils down to:

mtu * 0.5 * 10
-------------- + baseline_latency
kbit

The factor 10 is not quite correct but works well in practice.

Your kernel

If you run a recent distribution, everything should be ok. You need 2.4 with QoS options turned on.

If you compile your own kernel, it must have some options enabled. Most notably, in the Networking Options menu, QoS and/or Fair Queueing, turn at least CBQ, PRIO, SFQ, Ingress, Traffic Policing, QoS support, Rate Estimator, QoS classifier, U32 classifier, fwmark classifier.

In practice, I (and most distributions) just turn on everything.

The scripts

The script comes in two versions, one which works on standard kernels and is implemented using CBQ. The other one uses the excellent HTB qdisc which is not in the default kernel. The CBQ version is more tested than the HTB one!

See wshaper and wshaper.htb.

Tuning

These scripts need to know the real rate of your ISP connection. This is hard to determine upfront as different ISPs use different kinds of bits it appears. People report success using the following technique:

Estimate both your upstream and downstream at half the rate your ISP specifies. Now verify if the script is functioning - check interactivity while uploading and while downloading. This should deliver the latency as calculated above. If not, check if the script executed without errors.

Now slowly increase the upstream & downstream numbers in the script until the latency comes back. This way you can find optimum values for your connection. If you are happy, please report to me so I can make a list of numbers that work well. Please let me know which ISP you use and the name of your subscription, and its reputed specifications, so I can list you here and save others the trouble.

Installation

If you dial in, you can copy the script to /etc/ppp/ip-up.d and it will be run at each connect.

If you want to remove the shaper from an interface, run wshaper stop. To see status information, run wshaper status.

KNOWN PROBLEMS

If you get errors, add an -x to the first line, as follows:

#!/bin/bash -x

And retry. This will show you which line gives an error. Before contacting me, make sure that you are running a recent version of iproute!

Recent versions can be found at your Linux distributor, or if you prefer compiling, here:
ftp://ftp.inr.ac.ru/ip-routing/iproute2-current.tar.gz

tzoperl is a Perl Client-Daemon for TZO DDNS Services. The service works with dial-up, DSL, Cable Modems, ISDN, and most types of connections that get you connected to the Internet.
The TZO Perl v2 is the preferred TZO client as it requires no compilation of code.. just run the text-based wizard installer to configure. You may install TZO Perl v2 as a system daemon/service for automatically start during system boot-up.
This client is tested and has full installer support for Redhat Linux, Apple Mac OS X, Sun Solaris and FreeBSD. Other versions of Linux and UNIX are also supported (including versions of Cobolt that TZO does not have a special package for).
This code is released under the GPL license and may be modified for additional software platforms. Experimental (limited) support exists for other UNIX, Microsoft Windows (ActiveState Perl), MacPerl and Novell.
TZO offers Domain Registration Services and Dynamic Domain Registration Service (Official Registrar), SMTP Mail Store and Forward, and Web Hosting options for users with
Static or Dynamic IP Addresses(you can host multiple virtual domains with your one IP Address). TZO also allows for DNS Hosting/Parking Services for Cable and DSL users as well as standard ethernet and PPP. Host Private Domains on your Linux Server with a Dynamic IP Address. Private Domains are less that $60 per year if your domain is already registered!
Enhancements:
- Fixed file collision bug (TZO v. tzo) occuring on Apple OSX and Microsoft Windows.
- WIN32: Moved some file-path targets into a hash array to make future Windows/other OS support easier. Lots more needs to be done.
- Some cleanup of the code flagged future code updates with comments. Created TODO file.
- OSX: Created README.osx in osx folder
- OSX: Fixed StartupItems TZO file to work more in line with other OSX startup scripts. The script does not handle Shutdown and restart commands properly (yet), but the actual tzo daemon can be shut down using tzo -q.
- OSX: Moved INIT script from /System/Library/StartupItems to /Library/StartupItems
-