Free application level gateway software for linux

Alamin GSM SMS Gateway provides a SMS-to-SMSQP/SMTP gateway and client to send SMS from an IP client.
Alamin GSM SMS Gateway is a gateway for exchanging messages between GSM and IP networks.
The main objective of the gateway is to provide a reliable delivery service and conversion in both directions in order to extend to the GSM network the functions of IP-based applications.
To make an analogy, its like a web server for HTML pages. They need the web server and provide it with content. The Alamin Gateway paves the way for all types of mobile applications on GSM using SMS messages. One very common use for the gateway is to send an alarm from a computer network to its system administrators. Another is the currently common apps showing tv viewers comments on tv programs.
Currently, the connection to the gateway from the IP network can be achieved using SMSQP (11201), the native protocol of the gateway for sending messages and managing the queue. The SMSQP protocol can be used directly or through the "gsgc" client. Implementing a SMTP interface is easy configuring your MTA for calling a script that prepares the message and calls "gsgc".
The connection between the gateway and the GSM network can be realized through a GSM modem or through a telephone supported by the project Gnokii. A SMPP connector is being developed these days.
At present, only GSM modems can be used in "text" mode. In the future, "pdu" mode will also be supported. Not all devices support both modes, so that you will have to read the manual of your mobile telephone or GSM modem and consult the GSM devices page.
Alamin is developed on Debian GNU/Linux but runs almost in all perl enabled systems.
Enhancements:
- smtp interface has been removed, it was buggy and not fully implemented.
- SMPP interface for sending and receiving messages, both connectors are in own daemons, outside the core module and the message dispatcher.
- SMPP interface uses the Net::SMPP perl module.
- It has been tested onlywith mblox servers.
- MySQL interface for inserting records from received messages and send messages in a table.
- New config files are in perl script format.

WAG Applications provides a collection of WAG-hosted Web applications.
WAG Applications is a collection of Web applications that are capable of being hosted by the Web Application Gateway.
WAG provides core functionality such as user definition, authentication, and administration, for all hosted Web applications.
Enhancements:
- Added application specific handlers to the wagErrorHandler function.
- Added is_email() function to functions.php which checks if a a given e-mail address is valid. It checks for all top level domains including the new ones (.biz, .info, .museum etc.) and the special ones (.arpa, .int etc.) as well as with e-mail addresses based on IPs (e.g. webmaster@123.45.123.45). (Function derived from PHP user contributed notes.)
- Enhanced the error reporting for both WAG and application database errors to include the server name and user name/id. This will help admins target problems if they are responsible for multiple WAG installations.
- Added "Date Added" and "Date Last Login" information to Administration > Users screen.
- Made style sheet changes related to form field fonts.
- Bug Fixes
- Validation of user e-mail addresses was not performed correctly and causing any valid e-mail address to be flagged as invalid.
- When admin changes a users password, the e-mail password, if configured, is also changed. This allows the admin to "lockout" a user from both WAG and e-mail if needed.

Coherent Mail Gateway is intended to be a very easy to set up MTA using SMTP and POP3. Greylisting is used on the SMTP daemon to reduce spam.

In addition, quite a lot of checks on the validity of information from the SMTP client (such as claimed server name and sender) are carried out, and anyone caught telling lies is disconnected.

Grey-, black-, and white-listing are supported, as well as (optionally) ClamAV and Spamhaus. The target market is users with static IP addresses. Others can use the system, but its value will be limited to outgoing email.

Wap-IRC gateway allows you to chat on IRC with any WAP-enabled mobile phone. It works by running the server program on a Unix-like system that is accessible over the Internet. It doesnt require phones which have programs written in Java.
I am Tomas Vilda, student studying at University of Vilnius, Lithuania. I started interested in wap when I bought my first wap enabled mobile phone. I searched for the running irc-wap gateway. But with no success. Actually, I found some, but no such, that I make to connect to specified IRC server. Then I found wapirc gateway written by Alan Cox . I tried it on my FreeBSD server. During compilation I got error, because of bad Makefile. So I compiled it by correcting Makefile and ran successful. My mobile is Siemens C55. To start using this wapirc gateway I have to make some modifications. They are listed below.
Enhancements:
- cgi/main():refresh included into main-cgi, saves us .htaccess and external wmlscript
- cgi/write_wml(): fixed bug in linked nicks with ACTIONs and * in there.
- server/parseinput(): Added /me Command for * ACTION in channels
- cgi/write_card(): get refresh timer from config.h
- server/removeallitems(): doing a list cleanup when disconnecting, so we can rejoin after quit without part
- server/print_out(): screenbuffer with latest messages, scrolling top down
- cgi/write_card(): reload on a regular basis, when not typing something in. New formular works on more phones, informative header
- cgi/wml_link()/wml_header(): wml1.2 compatible links/input field for accesskey element
- cgi/write_wml(): new linewise printout, italic makeup, nicks are linked setting defaultvalues for talking on channels and privat.
- cgi/main(): Expire header
- Makefile: make install

This is the IRC gateway for Microsoft(tm) Messenger.

You probably wonder what this is and why I wrote this. Some more information can be found in the DESIGN document that is included in this package.

This software is written by Johannes Verelst and is licensed through the GPL license (http://www.gnu.org/licenses/gpl.html).

Note that this is pre-alpha code, it probably does a bit that you want, but dont email me bugreports or feature requests. It is under heavy development.

If this program doesnt run try to install corectly all required perl modules yourself.

The idea for this program came when I was getting annoyed by the fact that I had to use different programs for both IRC and MSN. Since I dont know of any good MSN clients that can do IRC too (on unix, ofcourse), I started thinking about the other way around: an IRC client that can do MSN.

When I saw a piece of software written by Adam Swann that allows easy connectivity to MSN with perl, I decided to write an IRC server in perl that would connect to MSN for you. This is the result.

PAPI aims to provide the tool designer and application engineer with a consistent interface and methodology for use of the performance counter hardware found in most major microprocessors.
PAPI enables software engineers to see, in near real time, the relation between software performance and processor events.
The Performance API (PAPI) project specifies a standard application programming interface (API) for accessing hardware performance counters available on most modern microprocessors.
These counters exist as a small set of registers that count Events, occurrences of specific signals related to the processors function. Monitoring these events facilitates correlation between the structure of source/object code and the efficiency of the mapping of that code to the underlying architecture.
This correlation has a variety of uses in performance analysis including hand tuning, compiler optimization, debugging, benchmarking, monitoring and performance modeling. In addition, it is hoped that this information will prove useful in the development of new compilation technology as well as in steering architectural development towards alleviating commonly occurring bottlenecks in high performance computing.
PAPI provides two interfaces to the underlying counter hardware; a simple, high level interface for the acquisition of simple measurements and a fully programmable, low level interface directed towards users with more sophisticated needs.
The low level PAPI interface deals with hardware events in groups called EventSets. EventSets reflect how the counters are most frequently used, such as taking simultaneous measurements of different hardware events and relating them to one another.
For example, relating cycles to memory references or flops to level 1 cache misses can indicate poor locality and memory management. In addition, EventSets allow a highly efficient implementation which translates to more detailed and accurate measurements.
EventSets are fully programmable and have features such as guaranteed thread safety, writing of counter values, multiplexing and notification on threshold crossing, as well as processor specific features. The high level interface simply provides the ability to start, stop and read specific events, one at a time.
PAPI provides portability across different platforms. It uses the same routines with similar argument lists to control and access the counters for every architecture. As part of PAPI, we have predefined a set of events that we feel represents the lowest common denominator of every good counter implementation.
Our intent is that the same source code will count similar and possibly comparable events when run on different platforms. If the programmer chooses to use this set of standardized events, then the source code need not be changed and only a fresh compilation and link is necessary. However, should the developer wish to access machine specific events, the low level API provides access to all available events and counting modes.
If an event or feature does not exist on the current platform, PAPI returns an appropriate error code. This significantly reduces the porting effort of code using PAPI because the semantics of each call to PAPI remains the same, just the argument lists need updating. In addition to the standard set, each PAPI implementation supports all native events through the ability to directly accept platform specific counter numbers. Definitions for most, if not all of these, are included as conditional macros in the header file. In this way, PAPI avoids having inefficient code to translate all events for all platforms into a uniform representation and back again.
This translation is only done for the relatively few events defined in the standardized set. Some processors like those in the POWER series have counter groups. They enable access to specific groups of counters, instead of individual events. This presents a serious portability problem, thus PAPI abstracts hardware counters from their groups with a packed naming scheme. Each counter control value or event is made up of the counter group number and the number of the specific counter in that group.
PAPI can be divided into two layers of software. The upper layer consists of the API and machine independent support functions. The lower layer defines and exports a machine independent interface to machine dependent functions and data structures. These functions access the substrate, which may consist of the operating system, a kernel extension or assembly functions to directly access the processors registers.
PAPI tries to use the most efficient and flexible of the three, depending on what is available. Naturally, the functionality of the upper layers heavily depends on that provided by the substrate. In cases where the substrates do not provide highly desirable features, PAPI attempts to emulate them as described below.
PAPI makes sure the underlying operating system or library guards against overflow of counter values.
Each counter can potentially be incremented multiple times in a single clock cycle. This combined with increasing clock speeds and the small precision of some of the physical counters means that overflow is likely to occur.
One of the more advanced features of PAPI is to provide a portable implementation of asynchronous notification when counters exceed a user specified value.
This functionality provides the basis for PAPIs SVR4 compatible profiling calls, that generate an accurate histogram of performance interrupts based on hardware metrics, not on time. Such functionality provides the basis for all line level performance analysis software, from the antiquated days of AT&Ts prof to SGIs SpeedShop. Thus for any architecture with even the most rudimentary access to hardware performance counters, PAPI provides the foundation for a truly portable, source level, performance analysis tool based on real processor statistics.
Enhancements:
- The API was extended to decouple abstraction layers from hardware support and to provide initial support for different types of performance counters.

The KTA is a complete telnet and SSH application designed for use by both end-users and developers. For end-users it provides a cross-platform vt320-compatible terminal written in Java.

For developers it provides an extensible plugin API that can be used to implement automated telnet and SSH solutions in a client/server environment.

The RSS-IM Gateway allows any site with an RSS feed to make their feed available via the IM network of their choice. It is very easy to set up.
Just create a new IM nick on your favorite network (links here) - something like "MySiteIM" always works - fill out the blanks in the config.im file, and your headlines are viewable on that network automatically, including from most cell phones if you use AIM or MSN. It works with AIM, ICQ, YIM and Jabber.
This project is a derivative of the SDBA Revolution IM Application Server version 1.85 and includes all files you will need. You will need to have an uptodate version of Perl with XML::RSS, in addition to the other libraries required.
Using:
- Make sure Perl is set up correctly, with all libraries (including XML::RSS!).
- Open config.im and put in your chosen nick and password for the bot, edit the network (default is AIM), and put in the URL to your feed.
- Start sdba.pl from the command line.
- Message the nick you chose from any IM client.