Free serial ws v1.0 software for linux

LibSerial provides a collection of C++ classes that allow one to access serial ports on POSIX systems like standard C++ iostream objects.

Member functions are provided for setting various parameters of the serial ports such as the baud rate, character size, flow control and others. LibSerials idea is to simplify serial port programming on POSIX systems.

When you have installed the above tools, run the following commands:

Installation:

./configure
make
make install

Note: The html documentation will not be installed by "make install". I will fix this in the future release.

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)

Surblhost project is a small program to see if hostnames are listed in the Spam URI Realtime Blocklists (SURBL).

Hosts that are blacklisted means that global spam email have been reported to contain links to these hosts.

Many popular spam email filters use these lists to identify spam email, but this program makes it possible to use the lists for any conceivable purpose, such as filtering out bad hosts from URL redirection, and so on.

Examples:

Verbose output

$ surblhost -v bigredskhoediet.com clowndiket.com
checking against multi.surbl.org
bigredskhoediet.com.multi.surbl.org is blacklisted by [jp][ab][ob][sc][ws]
clowndiket.com.multi.surbl.org is blacklisted by [jp][ob][sc][ws]

see http://www.surbl.org/lists.html for more information on the blacklists

More verbose output

$ surblhost -vv --test
test.sc.surbl.org.sc.surbl.org 127.0.0.2 is blacklisted by spamcop
test.sc.surbl.org.sc.surbl.org txt record: sc.surbl.org permanent test point

Whitelisting and stripping of subdomains

$ surblhost -vv -s www.google.com
checking against multi.surbl.org
google.com is in whitelist

Recognition of two-level TLDs

$ surblhost -vv -s www.somewhere.co.uk
checking against multi.surbl.org
somewhere.co.uk.multi.surbl.org is not blacklisted

Blocked site discovered using recursive checking

# NO HIT
$ surblhost -v 156.tissuqeweightloss.com
checking against multi.surbl.org
warning: hostname contains subdomains: 156.tissuqeweightloss.com (try option -r)
156.tissuqeweightloss.com.multi.surbl.org is not blacklisted

# OPTION -r GIVES HIT
$ surblhost -v -r 156.tissuqeweightloss.com
checking against multi.surbl.org recursively
156.tissuqeweightloss.com.multi.surbl.org is not blacklisted
tissuqeweightloss.com.multi.surbl.org is blacklisted by [jp][ob][sc][ws]

see http://www.surbl.org/lists.html for more information on the blacklists

slsnif is a serial line sniffer. It listens to the specified serial port and logs all data coming through it. slsnif works transparently for both the device connected to the serial port and the controlling software for this device. It operates by opening a pseudo tty (pty) and linking it to the actual serial port.
slsnif operates by opening a pty and linking it to the serial port. These are following parameters / options:
1. Serial port to open (required).
2. Name of the file to direct output to (optional, defaults to stdout).
3. Desired baudrate (optional, defaults to 9600 baud).
4. Timestamp On/Off (optional, defaults to Off).
5. Print ascii values in hex On/Off (optional, defaults to Off)
6. Print number of bytes transmitted On/Off (optional, defaults to Off).
7. Optional colors for timestamp, number of bytes transmitted and normal output.
8. Lock port On/Off (optional, defaults to On).
9. Use Unix98 ptys instead of BSD ptys (optional, defaults to BSD style).
10. Second serial port to open. If specified, this port will be used instead of a pty, thus providing an ability to log data between two serial ports.
Enhancements:
- Added ability to resynchronize ports at any time by sending a SIGUSR1 signal to slsnif. Useful for debugging applications that change port parameters mid-way, after starting the transmission. One example is pppd daemon, which sets initial parameters in the chat script, and changes them later, after chat script terminates.
- Added ability to use SYSV (Unix98) ptys instead of BSD ones (see -u and --unix98 parameters). This option can also be turned on/off from rc-file.

AlchemySOAP is a fork of the EasySoap++ SOAP 1.1 library. Adding enhanced protocol support (SOAP 1.2), a large number of automated unit tests and interoperability tests, and several other notable features (Multithreaded SOAP request handling, optional SSL/DOM, serialization improvements to work with WS-* protocols, etc.). This library is open source, licensed under the LGPL.
AlchemySOAP can interoperate with a large number of 3rd party SOAP stacks, including: Apache, MS SOAP Toolkit, gSoap, SOAP::Lite, SQL Data, and White Mesa.
Enhancements:
- Support for SOAP 1.2 was added.
- The SOAPServer and SOAPServerDispatch classes were refactored to allow multithreaded handling of requests.
- Serialization and deserialization of Xerces-C elements are supported.
- Saving whitespace between SOAP elements during deserialization and including it during serialization is supported.
- This allows a SOAP message to remain the same after the deserialization or serialization cycle (which is needed for WS-Security).

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.

KSMS-Tool is a tool for sending SMS via your mobile phone. In principle, every modern mobile phone should be supported; these have been explicitely tested so far:
- Siemens S55
- Sony-Ericsson K700i
The connection to the mobile phone is established via the serial interface. In principle, every serial emulation (e.g. via USB, IrDA, Bluetooth) should also work if an error-free connection is guaranteed (especially in the wireless cases IrDA resp. Bluetooth).
Details on choosing a non-default connection to the mobile phone or on how to populate the user-defined addressbook can be found on the KSMS-Tool homepage.