Free predictive dialing software for linux

Pocket Linux is an almost minimal, one floppy linux system designed to quickly convert PC workstation into secure linux-based workstation using ssh to connect to remote host (other networking clients are also supported).
It supports bootp for determining host IP and other network parameters (theres also manual configuration possible, but bootp is recommended).
In addition to workstations equipped with a network card (ethernet or arcnet), you can also use Pocket Linux on a PC equipped with a modem. Modem is automatically detected and then PPP connection is made.
The idea came up some time in 1996 or so. The distribution then was not perfect, but still it shown it was a great idea. It wasnt maintained for about year or so, until I took it up again in the early January 1998. After a complete rebuild Pocket Linux 2.00 was released. It soon gained a huge number of happy users, whose ideas helped its development.
The aim is to provide a small and efficient workstation that autoconfigures as much as possible and lets securely use the network from almost everywhere.
Current version is a nice attempt and future ones will enhance the automation and support for various network equipment and protocols, becoming a total solution. Future plans also include side projects like one floppy router.
In order to understand some of the config options its useful to know something about operations that are done during bootup (in order to automatically configure the network). These are, in order (the later attempts are made if the earlier ones dont set-up the network):
- attempt to setup the network using BOOTP
- attempt to reuse previous manual configuration
- modem detection
- attempt to setup modem conection
Most of the config options switches these operations on and off.
Main menu
You can choose the following network configuration commands from the main menu (only the ones that make sense in the present context are displayed):
- Options - allows setting few binary parameters controlling automatic network configuration and modem handling.
- BOOTP query - attempts to configure network (ethernet or arcnet) using BOOTP. Normally its automatically done during bootup, but this can be switched off.
- Manual configuration - allows manual setting of network configuration parameters (ethernet or arcnet).
- Detect modem - detects serial port the modem is on and its parameters (transfer rate, initialization commands).
- Dial PPP using predefined configuration - creates modem connection (PPP) using one of (up to ten) remembered configurations. By default only TPSA (0202122) configuration is remembered.
- Dial PPP using new configuration - creates new PPP configuration and sets up a modem connection using the newly created config.
- Disconnect PPP - disconnects modem connection.
- Mount /usr via NFS - mounts remote /usr filesystem via NFS. It will be automatically mounted during each Pocket Linux bootup if its turned on in configuration options.
- Exit - Do not config the network - exits the program without configuring the network.
Configuration options
There are following options available:
- Probe network with BOOTP - switches automatic BOOTP probing during bootup on and off. On by default.
- Reuse manual network configs - if on, an attempt is made to restore network configuration during bootup. Netconf remembers 10 most recent manual configurations along with network cards MAC addresses. If cards MAC address matches one of the remembered ones, assigned configuration is used. On by default.
- Automatically setup PPP - switches automatic attempt to create modem connection during bootup on and off. Its made with the first config on PPP configs list. On by default.
- Reuse modem configuration - if on, modem detection is not performed during bootup - instead most recently used modem configuration is used. Off by default.
- Pulse dialing - switches dialing mode used for modem connections between tone dialing (DTMF) and pulse dialing. Default is off (that is tone dialing).
- Automount disk partitions - switches on and off automatical disk partitions mounting (ext2 and vfat filesystems) and swap partition activation during bootup. On by default.
- Add swap file if low memory - switches on and off automatical swap file creation during bootup. Swap file is created if, and only if, theres less than 16 MB memory available (including potentially activated swap partitions) and theres a disk partition on which it could be created available. On by default.
- Automount NFS /usr - switches on and off /usr filestem mounting via NFS during bootup. NFS path to the filestem must be set using "Mount /usr filesystem via NFS" command in main menu. Off by default.
Manual network card configuration
You can enter network configuration parameters in this window:
- This machines IP - enter IP number for this computer here
- Network mask - enter netmask here. If omitted, mask will be calculated based on IP (which will not necessarily be right).
- Broadcast address - enter network broadcast address here. If omitted broadcast address will be calculated based on IP (not mask! - which will not necessarily be right).
- Default gateway - enter IP address of default network gateway (router) here.
- Nameserver IP(s) - enter one or more (separated by spaces) name servers IP addresses here. Can be omitted, but then domain names couldnt be used.
- Default domain(s) - you can enter one or more (separated by spaces) domain names to search host if incomplete domain names will be used. Its optional.
PPP configuration
You can enter modem connection configuration parameters in this window:
- Config name - config name (used in existing configuration selection menu).
- Phone number - phone number to dial (eg. 0w202122 for TPSA access modems).
- Username - username to send to remote server
- Password - password to send to remote server
- Nameserver IP(s) - enter one or more (separated by spaces) name servers IP addresses here. Can be omitted, but then domain names couldnt be used.
- Default domain(s) - you can enter one or more (separated by spaces) domain names to search host if incomplete domain names will be used. Its optional.
Because of permanent configuration that is kept on the floppy you should remember to:
- dont write protect the floppy
- dont remove the floppy from the drive (at least during network configuration)
Enhancements:
- bugfixes in netconf reuse code
- disk partitions automounting, swap partitions autoactivating
- automatic swap file creation
- extended support for NFS mountable /usr
- PS/2 mouse support
- new startup logo

Intelligent Wardialer is a "war dialer" used for auditing your PSTN (phone) network. Its features include random/sequential dialing, Voice over IP using the IAX2 (Intra-Asterisk eXchange) protocol, ASCII flat file and MySQL logging, a curses-based front end, key stroke marking, multiple modem support, several methods of "tone detection", save/load state, banner detections (to determine remote system types) and blacklist support.
Main features:
- Full and Normal logging: Full logging records all possible events during dialing (busy signals, no answers, carriers, etc). By default it only records things that we might find interesting (carriers, possible telco equipment).
- ASCII flat file and MySQL logging: You can log to a traditional ASCII flat file, and record information into a MySQL database.
- Dials randomly or sequentially.
- Remote system identification: When finding a remote modem and connecting, iWar will remain connected and attempt to identify the remote system type.
- Key stroke marking: When actively "listening" to iWar work, if you hear something interesting, you can manually "mark" it by hitting a key. You can also enter a "note" about something you find interesting.
- Multiple modem support, because... well, hey - this is "Unix". iWar will support as many modems you can hook up
- Nice "curses" based display. This means that if youre using iWar from a Linux console or a VT100 based terminal, it should work fine. Its not a escape sequence kludge, but true "curses".
- Full control over the modem: Unlike other kludges, iWar doesnt just open the modem as a typical "file". It controls the baud rate, parity, and CTS/RTS (Hardware flow control) DTR (Data terminal ready). This is important for controlling the modem and making it preform the way you want it to during scanning. For example, DTR hang ups.
- Blacklisted phone number support: For numbers the system should never dial.
- Save state: If within the middle of a "wardialing" session you want to quit, you can save the current state to a file. This allows you to come back later and restart iWar where you left off. (via the -l option)
- Load pre-generated numbers: You can load a file (via the -L option) of numbers that you want to dial. This is useful if you want to load numbers generated by another routine (perl/shell script/etc).
- Tone location, if your modem supports it. iWar uses two different methods. The traditional "ATDT5551212w;" (Toneloc) and "silence" detection.
- Records remote system banners on connection for later review
- iWar can be used to attack PBXs and Voice mail systems
- Terminal window so you can watch modem interactions and carrier results in real time
- Support the IAX2 (Intra-Asterisk eXchange) "Voice over IP" (VoIP) protocol. This allows you to scan without the need of additional hardware! To my knowledge, iWar is the first war dialer with VoIP functionality
- In IAX2 mode, iWar acts as a "full blown" VoIP client. In this mode, key 0-9, * and # play there DTMF equivalents. In this mode, you can also directly "talk" (using a microphone) with the remote target if so desired.
- In IAX2 mode, if your VoIP provider supports it, you can "set" your caller ID number (caller ID spoofing).
- Comes with complete source code and is released under the GNU General Public License.
Enhancements:
- Major bugfixes were made for BSD type systems.
- Some other minor bugs were also fixed. VoIP IAX2 (Intra-Asterisk eXchange) support was added.
- With this, you can scan with no additional hardware (such as an analog modem).
- Instead, calls are placed over the Internet.
- DTMF support for when under IAX2 mode was added.

tkdial is a small tool for starting dialup connections on various network devices such as ISDN.
Each network device (ippp0, ippp1, ...) is configured for a different ISP (internet service provider). With tkdial the user can choose a ISP an the computer dial with this configuration to the internet.
Enhancements:
- new option "-c" for configuration file in tkdial
- new option "-h" for usage help in tkdial

ISDN.py aims to be a simple, no-frills ISDN dialer. Its written in Python using PyGTK bindings. Currently it dials and hangups the line, if you grant to a normal user the rights to do it (normally it cant). The interface is pretty straightforward. Improvements and beautification for gui are planned.
Now there are two executables: isdnpy is the "normal" ISDN.py and isdnpy.qtisdnlinux is a version tailored to run with qtisdnlinux.
Enhancements:
- I dont own an ISDN anymore, so I prefer to release the code as 1.0

Telephony::CountryDialingCodes is a Perl module that can convert international dialing codes to country codes and vice versa.

SYNOPSIS

# Usage method 1 (using object methods):
use Telephony::CountryDialingCodes;
my $o = new Telephony::CountryDialingCodes();
my $country_code = NL;
print "The dialing access code for country $country_code is " . $o->dialing_code($country_code) . "n";
my $dialing_code = 1;
my @country_codes = $o->country_codes($dialing_code);
print "The country code(s) for dialing access code $dialing_code is/are: " . join(,,@country_codes) . "n";


# Usage method 2 (using class methods):
use Telephony::CountryDialingCodes;
my $country_code = NL;
print "The dialing access code for country $country_code is " . Telephony::CountryDialingCodes->dialing_code($country_code) . "n";
my $dialing_code = 1;
my @country_codes = Telephony::CountryDialingCodes->country_codes($dialing_code);
print "The country code(s) for dialing access code $dialing_code is/are: " . join(,,@country_codes) . "n";

# Extracting an intl dialing code from an intl phone number:
use Telephony::CountryDialingCodes;
my $o = new Telephony::CountryDialingCodes();
my $dialing_code = $o->extract_dialing_code(+521234567890);
# $dialing_code will contain 52.

This class exports a method for determining a countrys international dialing code, and another method for doing the reverse: i.e. determining the country code(s) that belong(s) to a given international dialing code.

You can call these methods as class methods or you can create an object and call these methods as object methods. The difference is that if you call them in object context that the internal lookup tables are freed when the object is destroyed, otherwise if you call the methods in class context, then the internal lookup tables are global and will persist for the lifespan of the current process. Its not really a big deal which approach you choose, so for the sake of style, use the object method approach if you have no clue which is better.

THC-Dialup Login Hacker is a tool for penetrating dialup modems.

All you need is UNIX and minicom. Have fun with this little release!

The internet is not the only door into a network. In this new days, wavelans are becoming popular, in old days, there were dial-in modems. But today, dial-in modems are still present in any company.

While tools for wardialing (scanning phone numbers for modems by dialing every number and checking if theres a carrier) are available for all operating systems for years, there were only a very few tools for trying to guess login/passwords against modem carriers, and they were all for MS-DOS only. Years ago, I wrote such a tool called LOGIN-HACKER, which is still in use by many people, just because theres no real choice.

About 5 years ago I completely moved from MS-DOS to UNIX (Linux and OpenBSD) so executing penetration tests became a pain in the ass for modem login hacking. Finally I wrote some scripts to hack into modem carriers for Unix as well.

To make it flexible and portable, I chose not to write my own terminal program and scripting language, like I did with LOGIN-HACKER. I just use simple Minicom scripts. And they are very effective! Also they could include more commands to interact with the operating system while the script is running, I made it possible, to autodetect almost any prompt, and detect if a login/password, or password only prompt was successfully passed or not.

Gnome-Dial is an user-friendly PPP dialer for GNOME 2. The idea which has given this project to light is quite simple: giving GNOME 2 users a usable, fullly-featured, GNOME-integrated, clean and fast interface to the ppp package in order to make dialup connections easily.

There already are tons of such tools and some are particullarly valid (Gnome-PPP for example), but they often need other programs like WvDial to make connections, or are not so clean, fast or well-integrated with the GNOME interface.

You can consider Gnome-Dial (expecially in this moment of hard development), a frontend for PPP, but this is not what it is intented to be: it will sooner or later begin to include new features and its own configuration files to represent modems, connections etc.

However it will not try to replace the ppp package. The package will soon include also a configuration generator.

GNU Archimedes is the GNU package for the design and simulation of submicron semiconductor devices. Archimedes is a 2D Fast Monte Carlo simulator which can take into account all the relevant quantum effects, thank to the implementation of the Bohm effective potential method.

The physics and geometry of a general device is introduced by typing a simple script, which makes, in this sense, GNU Archimedes a powerfull tool for the simulation of quite general semiconductor devices.

In the present release, GNU Archimedes is able to simulate electrons and heavy holes in Silicon and GaAs (Gamma and L-valleys) devices (holes are simulated by means of a simplified MEP model), and in the next release, which is in preparation, it will be able to make simulations in 1D, 2D and 3D (this release will be delivered as soon as possible).

The Scientifical and Industrial Motivations
In today semiconductor technology, the miniaturization of devices is more and more progressing. In this context, it is easy to see that numerical simulations play an important role at every level of device manufacture. In fact, the cost of designing and physically constructing prototypes for VLSI semiconductor devices is very high and without the availability of advanced simulators the efforts for devices miniaturization would, likely, be brought to a halt. From assessing the performance of individual transistors, to circuits and systems, and, consequently, with the promise of improved device performance, industries are encouraged to keep on miniaturizing with lower manufacture costs.

But, unfortunately, such simulations are not whithout their challenges... A first consequence of device miniaturization is that simulations of submicron semicondutor devices requires advanced transport models. Because of the presence of very high and rapidly varying electric field, phenomena occur which cannot be described by means of the well-known drift-diffusion models, which do not incorporate energy as a dynamical variable.

That is why some generalization has been sought in order to obtain more physically accurate models, like energy-transport and hydrodynamical models. The energy-transport models which are implemented in commercial simulators are based on phenomenological constitutive equations for the particle flux and energy flux depending on a set of parameters which are fitted to homogeneous bulk material Monte Carlo simulations. So, this is not, certainly, a satisfactory physical description of the internal electronic dynamics in a semiconductor device.

As current device technologies quickly approach the scales whereby quantum effects due to strong confinement of carriers and direct source-drain tunneling will begin to dominate, new simulation techniques are required in order to fully understand and acurately simulate the physics behind the technology operation.

Of all the simulation methods currently employed, ensemble Monte Carlo has always been, both in the accademic and industrial community, the most vigorous and trusted method for device simulation, as it is proven to be reliable and predictive, as one can easily see from the vast bibliography on this subject.

However, as Monte Carlo relies on the particle nature of the electron (in fact we consider an electron like a biliard ball), quantum effects associated with the wave-like nature of electrons cannot fully incorporated into the actual simulators, i.e. the ensemble Monte Carlo have to be lightly (or strongly, it depends on the point of view and on the methods implemented...) modified to take into account the quantum effects, at least at a first order of approximation, which is certainly enough to take into account correctly all the relevant quantum effects present in the present-day semiconductor devices (till 2015 probably...). In order to take into account the wave-like nature of electrons we use a recently introduced quantum theory, the so-called Bohm effective potential theory.

So it is challenging and very interesting to develop such a code for 2D quantum submicron semiconductor devices. This is why I have decided to implement this code, but these are not the only motivations...

The Ethical Motivations
The very sad situation you quickly observe working in a semiconductor industry, but also in all places in which researches about semiconductor devices are made, the only codes for simulation you can find are not free and are proprietary codes.

That is a very bad situation because, at the present time, if you need to develop your own code for the purpose of simulating a device it is IMPOSSIBLE to obtain an advanced one in a short time, and, trust me, this is EXTREMELY BAD for scientific research... (Immagine if you had to re-discover the Newtonian laws every time you need them...) So, you can find a huge amount of papers describing a lot of numerical methods for simulating, in a very advanced way, semiconductor devices (even in the quantum case), but nobody will give you a code on which you can construct your own method (with the unlikely exception that at least one of the programmers is a friend of yours :) ).

Even worst, if you are a semiconductor device designer and you want to simulate "realistically" a new device, you have to pay (trust me, at very high costs!) a BINARY (just a binary and not the code!) from some well-known software industry. This binary will certainly have some bugs (because it is coded by humans which are not perfect...) and you will never have the possibility of fix them on your own. Of course, you can write to the software house and tell them that there is a bug, but, how many time do you will wait for a new release without those bugs? I dont think it will be a short time...

My impression is that, after a long research on the Web for a Free Software dealing with advanced 2D semiconductor device simulation, there was not a free code for the purpose of semiconductor devices simulation (i mean under GPL license). To be sure about it, I asked to the great Richard Stallman (by mail) if it will be worth to do a code like this and he encouraged me to code it, because there wasnt a code like this as free. So I decided to write this code..