Free kerio mailserver serial software for linux

COMSERV is a program that allows you to talk to a network terminal server such as a Xyplex MAXserver 1600.
The handy thing about this program is that the client side of the connection does not need to know anything about how to talk to the terminal server. COMSERV handles the connection details. Thus, you can use existing programs like tip to talk to devices attached to your network terminal server without any modification.
Also, you can use COMSERV to turn your Unix computer itself into a terminal server and serve up its own local serial ports over the network for remote systems to access. This is handy if you have several systems lying around and you want to utilize devices attached to their serial ports.
My primary motivation for writing this program was to expand the I/O capabilities of my FreeBSD home computer. I have many serial devices that I want to connect to my PC which include my modem, Palm Pilot, GPS, various micro-controllers, my EEPROM programmer, and other computers and printers. But with only two serial ports on my PC, I became annoyed at having to reach around the back of my computer and swap cables every time I wanted to plug in a different device. [I think all inventions are the product of the laziness of the inventor :-)] So I searched eBay and found a couple of these Xyplex terminal servers that looked promising, I bid on them, got them, and began hacking.
The only problem with using this type of device for serial expansion, is that if you use a program like tip on Unix (tip is a very basic but functional program to connect directly to a serial port), it expects to be able to open the serial port by opening a /dev/xyz device file that corresponds to a real serial device. The Xyplex, on the other hand, communicates to the Unix system via an ethernet network. In order to talk to one of the serial ports on the Xyplex, you need to establish a TCP/IP connection between your Unix computer and the Xyplex device at a particular TCP port. The TCP port you connect to determines which Xyplex serial port you connect to. For the Xyplex 1600, serial port 1 is TCP port 2100, serial port 2, is TCP port 2200 and so on.
Unfortuneately, tip, and programs like it, have no idea how to establish a TCP/IP connection to the Xyplex in order to transfer data to and from a serial device connected to the Xyplex.
This is what COMSERV does. COMSERV creates a set of pseudo-tty device files that are palatable to tip and other programs. COMSERV opens the master side of the pseudo terminal and the client program (tip in this case) opens the slave side. Data written on the slave endpoint comes out on the master endpoint and vice-versa. This mechanism establishes a connection between the client program and COMSERV. COMSERV then uses TCP/IP to establish a connection to the network terminal server.
Thus, data originating from the client program is written to the slave tty where is read by COMSERV. COMSERV then writes the data to the network socket to the Xyplex, which then passes it on to the designated serial port. Data originating from the serial device attached to the Xyplex takes the reverse path.
Only one instance of COMSERV is required to be running on your system to handle all of your network terminal servers (it can handle as many terminal servers and ports as the speed and resources of your system allows). COMSERV is designed to handle many connections in this fashion, and does so by multiplexing between them using asynchronous device and socket I/O.
While I wrote COMSERV to talk to a Xyplex MAXserver 1600, it should work with other manufacturers products as long as they follow a similar API. The Xyplex devices that I have are 16 port devices that connect serial devices to an ethernet network.
If COMSERV sounds useful to you, feel free to download and use it. The program is provided in source form, so you will need to extract it and compile it. If you use FreeBSD, simply do the following:
% cd /usr/ports/comms/comserv
% make install
I use it on FreeBSD 4-STABLE. I dont currently know of any outstanding bugs, but if you find and fix any bugs, please send me your fixes so that others can benefit from them as well.
If you do decide to use COMSERV, please note the accompanying license. In a nutshell, you can use it without restriction as long as you credit me and keep the copyright notice intact. If you happen to like it, feel free to send your thanks, letting me know. If you dont like it, let me know why, perhaps I can improve it. If you improve it, please send me your changes and Ill see about integrating them so that others can benefit from your improvements.
Enhancements:
- Implement a power of 2 backoff and retry for failing connections with a maximum 10 minute wait. This keeps from filling up the logs with failed repeated attempts.

Tiny serial terminal is a simple and dumb tool to access serial ports. Mainly intended for use to access serial consoles of various hardware.

Usage:

Download: com.c
Version : 1.1
Size : 4607 bytes
MD5 : 73a394b6d5ad333c2bf542315e1a0b73
SHA1 : 53c8ea8a1d5450ac4237a20c843e1462acaaa96e

Building: cc -o com com.c
Usage : ./com /dev/device [speed]
Example : ./com /dev/ttyS0 [115200]
Keys : Ctrl-A - exit, Ctrl-X - display control lines status
Darcs : darcs get http://tinyserial.sf.net/
Scr.shot: screenshot.png (8862 bytes)

Doc::Perlish::Writer is a base class for stream output functions.

SYNOPSIS

# using - generally use a subclass
my $writer = Doc::Perlish::Writer::XML->new();

$doc->receiver($writer);
$doc->send_all();

my $output = $writer->output; # an IO::All object

# or, you can pass an object or specify an IO::All source
$writer->output("filename");
$writer->output($scalar);

# to get the document body
$writer->doc;

A writer is something that takes Doc::Perlish Serial API events, and converts them into a stream.

Incollector is an application to collect various kind of informations (like notes, conversation logs, source code, quotes, serial numbers, webaddresses, words). All entries can be tagged.

Application can also search and browse entries easly. Incollector is very young project. There can be some bugs. If you will find any bugs, send an e-mail. All the 0.x versions can be unstable. 1.0 version will be the first stable and ready to use version.

Serial Over IP is a tool for the transport of serial interfaces over UDP/IP. It is very usefull for connecting distant equipment that run via a serial interfaces to a local computer.


One linux will be server and one will be client. On the server you can start the program typing the following command:

bash# serialoverip -d /dev/ttyS0 9600-8n1 -s 127.0.0.1 3000

... and on the client:

bash# serialoverip -c 127.0.0.1 3000 -d /dev/ttyS1 9600-8n1

In both commands the IP address is the server IP. Note that you have to start the server first, and it will be efectively be running only after the first packet received from the client.

JKhepera is a Java class library for Khepera mini robots. It includes a class which allows you to open connections from a host computer to the Khepera robot via a serial interface easily.
Communication between Khepera and a computer is also simple, using methods like "setSpeed" or "readProximitySensors".
In addition, there are GUI classes to display the whole communication for debugging purposes and to control the robot manually.
Main features:
- Open Source - JKhepera is published under the terms of GPL.
- Easy to handle communication between Khepera robots and a host computer via serial interface.
- The gui component KheperaPanel, to control Khepera manually
- The gui component KheperaMonitor, to display the complete communication between Khepera and a host computer for debugging purposes
- An Interface KheperaMotionalAlgorithm, that allows the implementation of individual control algorithms (additionally to the existing BraitenbergAlgorithm) to control Khepera automatically.
- The KheperaAgent, to control Khepera by an individual algorithm in an independent thread.

GtkTerm is a "clone" of the famous Hyperterminal. But it is much more simple, that is to say, that it can only communicate with a serial link and that it does not support all the modem protocols.
If you are searching for a more complete application of that kind that is more dedicated to be used with a modem, have a look at minicom. I wrote this gtkterm because I am electronician, and there was no simple program that could be used to dialog on a serial port easily.
Main features:
- Serial port terminal window
- Serial port setup (speed, parity, bits, stopbits, flow control)
- Using the termios API
- Possible to send a file (only RAW data, no protocol)
- Possible to save data (RAW also)
- End of line delay while sending a file
- Special character wait before next line while sending a file
- Possible to toggle control lines manually (DTR, CTS) and send breaks
- Also reads the state of control lines (RTS, CD, DSR, RI)
- Hexadecimal view
- Possible to send raw hexadecimal chars
- Possible to define macros (keyboard shortcuts)