Free pdu software for linux

check_apc_pdu application can check load and outlet status of a APC PDU by snmp.

Usage:

usage:
-H (--hostname) Hostname to query - (required)
-C (--community) SNMP read community (defaults to public,
used with SNMP v1 and v2c
-v (--snmp_version) 1 for SNMP v1 (default)
2 for SNMP v2c
SNMP v2c will use get_bulk for less overhead
3 for SNMPv3 (requires -U option)
-p (--port) SNMP port (default 161)
-o (--on) Outlets (name or number) must be on
-O (--off) Outlets (name or number) must be off
-L (--seclevel) choice of "noAuthNoPriv", "authNoPriv", or "authPriv"
-U (--secname) username for SNMPv3 context
-c (--context) SNMPv3 context name (default is empty string)
-A (--authpass) authentication password (cleartext ascii or localized key
in hex with 0x prefix generated by using "snmpkey" utility
auth password and authEngineID
-a (--authproto) Authentication protocol ( MD5 or SHA1)
-X (--privpass) privacy password (cleartext ascii or localized key
in hex with 0x prefix generated by using "snmpkey" utility
privacy password and authEngineID
-M (--maxmsgsize) Max message size - usefull only for v1 or v2c
-t (--timeout) seconds before the plugin times out (default=15)
-V (--version) Plugin version
-h (--help) usage help

Device::Gsm is a Perl extension to interface GSM phones / modems.

SYNOPSIS

use Device::Gsm;

my $gsm = new Device::Gsm( port => /dev/ttyS1, pin => xxxx );

if( $gsm->connect() ) {
print "connected!n";
} else {
print "sorry, no connection with gsm phone on serial port!n";
}

# Register to GSM network (you must supply PIN number in above new() call)
$gsm->register();

# Send quickly a short text message
$gsm->send_sms(
recipient => +3934910203040,
content => Hello world! from Device::Gsm
);

# Get list of Device::Gsm::Sms message objects
# see `examples/read_messages.pl for all the details
my @messages = $gsm->messages();

Device::Gsm class implements basic GSM functions, network registration and SMS sending.

This class supports also PDU mode to send SMS messages, and should be fairly usable. In the past, I have developed and tested it under Linux RedHat 7.1 with a 16550 serial port and Siemens C35i/C45 GSM phones attached with a Siemens-compatible serial cable. Currently, Im developing and testing this stuff with Linux Slackware 10.2 and a Cambridge Silicon Radio (CSR) USB bluetooth dongle, connecting to a Nokia 6600 phone.

Please be kind to the universe and contact me if you have troubles or you are interested in this.

Please be monstruosly kind to the universe and (if you dont mind spending an SMS) use the examples/send_to_cosimo.pl script to make me know that Device::Gsm works with your device (thanks!).

Recent versions of Device::Gsm have also an utility called autoscan in the bin/ folder, that creates a little profile of the devices it runs against, that contains information about supported commands and exact output of commands to help recognize similar devices.

Be sure to send me your profile by email (if you want to), so I can add better support for your device in the future!

Convert::ASN1 is an ASN.1 Encode/Decode library.

SYNOPSYS

use Convert::ASN1;

$asn = Convert::ASN1->new;
$asn->prepare(q<

[APPLICATION 7] SEQUENCE {
int INTEGER,
str OCTET STRING
}

>);

$pdu = $asn->encode( int => 7, str => "string");

$out = $asn->decode($pdu);
print $out->{int}," ",$out->{str},"n";

use Convert::ASN1 qw(:io);

$peer = asn_recv($sock,$buffer,0);
$nbytes = asn_read($fh, $buffer);
$nbytes = asn_send($sock, $buffer, $peer);
$nbytes = asn_send($sock, $buffer);
$nbytes = asn_write($fh, $buffer);
$buffer = asn_get($fh);
$yes = asn_ready($fh)

Convert::ASN1 encodes and decodes ASN.1 data structures using BER/DER rules.

SMSLink project implements a client/server gateway to the SMS protocol (short messages on the mobile phones).
It requires the use of dedicated hardware (a serial GSM module).
Both SMS emission and reception are supported, either in text-mode or in PDU-mode.
It also includes an SMS to eMail gateway module.
The server runs under Linux and FreeBSD and supports interactive mode via telnet.
The command-line client already exists for Linux, FreeBSD, Solaris, HP-UX, and Win32.
A basic Web interface is also provided.
Main features:
- The use of TCP/IP sockets for communication between client and server means that the application is network-aware from the start and that deploying it over a WAN (or across the internet) is a piece of cake. Expanding it as well, since writing additional clients for it is possible on any platform supporting sockets. Various ports of the client to Win32 are now available.
- The server process has a command-line interface connected to the socket, making it possible to use it interactively from a telnet session (only line mode telnet supported at the present time - see server/BUGS and server/TODO in the sources directory). This feature is of enormous help when troubleshooting or debugging.
- The command-line interface is backed by a parser written in lex and yacc (flex/bison, actually), which makes the language relatively easy to extend.
- The server was built from the start with the idea of multiple GSM modules in mind. Adding a line to two configuration files (and connecting the hardware, of course) is all there is to using two modules instead of one. The number of modules supported by the server is limited by the hardware only.
- The choice to use specific hardware (the serial GSM module), although limiting the general-purpose use of this application, allows for some very usefull features, the most prominant one being the ability to receive SMS messages as well as send them. This feature is now implemented (as of version 0.41b). Once downloaded from the GSM module, those messages can either be stored in an inbox file or fed through an external program or script, or both.
- By sitting straight on the GSM network, the use of the GSM module offers an advantage that far outweighs its cost : provider independance. The ability to send and receive SMS might be limited in some way or another by the level of your subscription, but all providers should offer a standard way of doing it. No "provider-specific driver" is required in this case. Whats more, all SMS routing aspects are being taken care of by the GSM network itself. Caution is advisable when choosing the provider though, as some of them might place some restrictions on routing to and/or from outside networks (e.g. Mobistar and Itineris*) or lack the implementation of some advanced features of the SMS protocol such as "point-to-point SMS" or "SMS-back" (e.g. Proximus through the UCP interface*).
- As of version 0.48b, initial support for PDU mode and the creation of a "driver-like" capability table for the GSM modules means that most module brands on the market could be supported with little effort. This "driver" approach also garanties that youll be able to mix and match different brands and models of modules on the same server with no problem. Support for PDU mode also opens up a new batch of options, like setting the validity period for a message, potential support for non-standard alphabet, binary content delivery to the mobile phone (logos, tunes, etc. ?) and more.
- A full-fledged access control mechanism allows you to specify precisely which client machine or subnet should be allowed to connect and which shouldnt. The access control is IP-based (as opposed to user-based) and defaults to "deny" for increased security. When the situation doesnt require any access control, the whole thing can be easily disabled by the administrator.