ack
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 36
ETrace 1.1
ETrace is a configurable static port network tracing tool, similar to traceroute, but supporting ICMP, TCP, UDP, etc. more>>
ETrace is a configurable static port network tracing tool, similar to traceroute, but supporting ICMP, TCP, UDP and other IP protocols.
Usage:
etrace [ -BbCcnv ] [ -p profile ] [ -F config ] [ -i interface ] [ -I icmp-type ] [ -T port ] [ -U port ] [ -P protocol ] [ -r probe-count ] [ -t timeout ] [ -1 hop ] [ -h hop ] [ -m hop ] [ -A address ] [ -s port ] [ -f flags ] [ -d data ] [ -D data-file ] [ -R count ] [ -q seq] [ -w window ] target [...]
Options:
etrace has a wealth of options ranging in function from controlling output to the detailed construction of trace packets.
Profile Options:
A profile is a pre-configured list of options stored in a shared, or user specific configuration file. By defining profiles, complex etrace option sets can be easily accessed with a single command line option.
-p, --profile
Specify a profile.
-C, --clear
Clear the current list of probes. This option can be used to allow a profile to inherit options from another profile, but specify its own list of probes.
-F, --config
Specify an alternative profiles file.
Interface options
-i, --interface
Specify interface. If unspecified, etrace will examine the routing table and select the most appropriate interface for each target address.
-c, --promisc
Put in interface into promiscuous mode. As this option increases the load on the system in general, it should only be used if spoofing of source packets address is enabled with the "-A" option.
Trace Type Options
-I, --icmp
Specify an ICMP trace and the packet type to use. ICMP traces may use Echo (E or P), Timestamp (T or S), Netmask (N or M) or Info (I). The default trace probe is an ICMP Echo.
-h, --hop
Specify a specific hop to investigate.
-m, --maximum
Specify the maximum number of hops.
-r, --probes
Set the maximum number of probes to send per hop. The default is 3.
-t, --timeout
Set the maximum amount of time, in milli-seconds, to wait for a response to a probe. The default is 3000 (three seconds).
Packet Construction Options
-A, --address
Specify the source IP address of generated packets.
-s, --source
Set the source port of the generated probe packets. If unspecified, etrace uses a random high port.
-f, --flags
Specify TCP and/or IP flags. Takes a comma delimitered list of any of the following flags: RF, DF, MF, FIN, SYN, RST, PSH, ACK, URG, ECE, CWR (Default: SYN)
-d, --data
Specify the data content of generated probe packets. Standard meta-characters are recognised (e.g. "nt") as are binary values given in octal (e.g. " 00x00");
-D, --data-file
Load the data content of the generated probe packets from the specified file. Filenames beginning with @ a loaded from the etrace shared data directory (usually /usr/local/share/etrace). etrace currently ships with the following predfined packet data files: dns, ike.
-R, --random
Fill the data content of the generated probe packets with the specified number of random bytes.
-b, --badcksum
Generate and send probe packets with bad checksums.
-q, --seq
Specify the TCP sequence number.
-w, --window
Specify the TCP window size.
Output Options
-v, --verbose
Increase output verbosity.
-B, --debug
Enable debugging output.
-n, --numeric
Disable name resolution.
Examples:
etrace www.sample.com
Launches a trace ICMP Echo, the default, trace to www.sample.com. Specifiying the options "-I E" whould accomplish the same results.
etrace -T 80 www.sample.com
Similar to the previous example, except the trace is performed on TCP port 80.
etrace --udp 53 --data-file @dns ns.sample.com
Starts are trace to ns.sample.com on UDP port 53 with the trace packets containing data loaded from the file /usr/local/share/etrace/dns (a file supplied with etrace that contains a simple dns request to resolve 127.0.0.1).
etrace -p dns -p fast ns.sample.com
The default profiles shipped with etrace include "dns" (which equates to the options shown in the previous example) and "fast" (which decreases both timeouts and the number of probes sent for each hop, as well as disabling name resolution). Profiles are stackable, with latter options overriding those specified in earlier profiles.
<<lessUsage:
etrace [ -BbCcnv ] [ -p profile ] [ -F config ] [ -i interface ] [ -I icmp-type ] [ -T port ] [ -U port ] [ -P protocol ] [ -r probe-count ] [ -t timeout ] [ -1 hop ] [ -h hop ] [ -m hop ] [ -A address ] [ -s port ] [ -f flags ] [ -d data ] [ -D data-file ] [ -R count ] [ -q seq] [ -w window ] target [...]
Options:
etrace has a wealth of options ranging in function from controlling output to the detailed construction of trace packets.
Profile Options:
A profile is a pre-configured list of options stored in a shared, or user specific configuration file. By defining profiles, complex etrace option sets can be easily accessed with a single command line option.
-p, --profile
Specify a profile.
-C, --clear
Clear the current list of probes. This option can be used to allow a profile to inherit options from another profile, but specify its own list of probes.
-F, --config
Specify an alternative profiles file.
Interface options
-i, --interface
Specify interface. If unspecified, etrace will examine the routing table and select the most appropriate interface for each target address.
-c, --promisc
Put in interface into promiscuous mode. As this option increases the load on the system in general, it should only be used if spoofing of source packets address is enabled with the "-A" option.
Trace Type Options
-I, --icmp
Specify an ICMP trace and the packet type to use. ICMP traces may use Echo (E or P), Timestamp (T or S), Netmask (N or M) or Info (I). The default trace probe is an ICMP Echo.
-h, --hop
Specify a specific hop to investigate.
-m, --maximum
Specify the maximum number of hops.
-r, --probes
Set the maximum number of probes to send per hop. The default is 3.
-t, --timeout
Set the maximum amount of time, in milli-seconds, to wait for a response to a probe. The default is 3000 (three seconds).
Packet Construction Options
-A, --address
Specify the source IP address of generated packets.
-s, --source
Set the source port of the generated probe packets. If unspecified, etrace uses a random high port.
-f, --flags
Specify TCP and/or IP flags. Takes a comma delimitered list of any of the following flags: RF, DF, MF, FIN, SYN, RST, PSH, ACK, URG, ECE, CWR (Default: SYN)
-d, --data
Specify the data content of generated probe packets. Standard meta-characters are recognised (e.g. "nt") as are binary values given in octal (e.g. " 00x00");
-D, --data-file
Load the data content of the generated probe packets from the specified file. Filenames beginning with @ a loaded from the etrace shared data directory (usually /usr/local/share/etrace). etrace currently ships with the following predfined packet data files: dns, ike.
-R, --random
Fill the data content of the generated probe packets with the specified number of random bytes.
-b, --badcksum
Generate and send probe packets with bad checksums.
-q, --seq
Specify the TCP sequence number.
-w, --window
Specify the TCP window size.
Output Options
-v, --verbose
Increase output verbosity.
-B, --debug
Enable debugging output.
-n, --numeric
Disable name resolution.
Examples:
etrace www.sample.com
Launches a trace ICMP Echo, the default, trace to www.sample.com. Specifiying the options "-I E" whould accomplish the same results.
etrace -T 80 www.sample.com
Similar to the previous example, except the trace is performed on TCP port 80.
etrace --udp 53 --data-file @dns ns.sample.com
Starts are trace to ns.sample.com on UDP port 53 with the trace packets containing data loaded from the file /usr/local/share/etrace/dns (a file supplied with etrace that contains a simple dns request to resolve 127.0.0.1).
etrace -p dns -p fast ns.sample.com
The default profiles shipped with etrace include "dns" (which equates to the options shown in the previous example) and "fast" (which decreases both timeouts and the number of probes sent for each hop, as well as disabling name resolution). Profiles are stackable, with latter options overriding those specified in earlier profiles.
Download (0.046MB)
Added: 2007-08-18 License: GPL (GNU General Public License) Price:
798 downloads
Device::SerialPort::Xmodem 1.03
Device::SerialPort::Xmodem contains an Xmodem file transfer protocol for Device::SerialPort. more>>
Device::SerialPort::Xmodem contains an Xmodem file transfer protocol for Device::SerialPort.
SYNOPSIS
use Device::SerialPort::Xmodem;
This is an Xmodem implementation designed to receive a file using 128 byte blocks. This module is intended to be passed an open and prepared port with active connection.
At this time it can only receive 128 byte blocks, however 1k blocks are in the works. I do plan to write a send functionality soon.
Device::SerialPort::Xmodem::Constants
Synopsis
This is a set of contants that return hex values for the following:
nul ^@ 0x00 null
soh ^A 0x01 start of header 128 byte block
stx ^B 0x02 start of header 1k byte block
eot ^D 0x04 end of trasmission
ack ^E 0x06 acknowlegded
nak ^U 0x15 not acknowledged
can ^X 0x18 cancel
C 0x43 C ASCII char
ctrl_z ^Z 0x1A end of file marker
Xmodem::Block
Class that represents a single Xmodem data block.
Synopsis
my $b = Xmodem::Block->new( 1, My Data...< until-128-chars >... );
if( defined $b ) {
# Ok, block instanced, verify its checksum
if( $b->verify( checksum, < my_chksum > ) ) {
...
} else {
...
}
} else {
# No block
}
# Calculate checksum, crc16, 32, ...
$crc16 = $b->crc16();
$crc32 = $b->crc32();
$chksm = $b->checksum();
$b->to_string(); # outputs a formated message block
<<lessSYNOPSIS
use Device::SerialPort::Xmodem;
This is an Xmodem implementation designed to receive a file using 128 byte blocks. This module is intended to be passed an open and prepared port with active connection.
At this time it can only receive 128 byte blocks, however 1k blocks are in the works. I do plan to write a send functionality soon.
Device::SerialPort::Xmodem::Constants
Synopsis
This is a set of contants that return hex values for the following:
nul ^@ 0x00 null
soh ^A 0x01 start of header 128 byte block
stx ^B 0x02 start of header 1k byte block
eot ^D 0x04 end of trasmission
ack ^E 0x06 acknowlegded
nak ^U 0x15 not acknowledged
can ^X 0x18 cancel
C 0x43 C ASCII char
ctrl_z ^Z 0x1A end of file marker
Xmodem::Block
Class that represents a single Xmodem data block.
Synopsis
my $b = Xmodem::Block->new( 1, My Data...< until-128-chars >... );
if( defined $b ) {
# Ok, block instanced, verify its checksum
if( $b->verify( checksum, < my_chksum > ) ) {
...
} else {
...
}
} else {
# No block
}
# Calculate checksum, crc16, 32, ...
$crc16 = $b->crc16();
$crc32 = $b->crc32();
$chksm = $b->checksum();
$b->to_string(); # outputs a formated message block
Download (0.043MB)
Added: 2007-08-08 License: Perl Artistic License Price:
812 downloads
Chart::Sequence 0.002
Chart::Sequence is a sequence Perl class. more>>
Chart::Sequence is a sequence Perl class.
SYNOPSIS
use Chart::Sequence;
my $s = Chart::Sequence->new(
Nodes => [qw( A B C )],
Messages => [
[ A => B => "Message 1" ],
[ B => A => "Ack 1" ],
[ B => C => "Message 2" ],
],
);
# or #
my $s = Chart::Sequence->new(
SeqMLInput => "foo.seqml",
);
my $r = Chart::Sequence::Imager->new;
my $png => $r->render( $s => "png" );
$r->render_to_file( $s => "foo.png" );
<<lessSYNOPSIS
use Chart::Sequence;
my $s = Chart::Sequence->new(
Nodes => [qw( A B C )],
Messages => [
[ A => B => "Message 1" ],
[ B => A => "Ack 1" ],
[ B => C => "Message 2" ],
],
);
# or #
my $s = Chart::Sequence->new(
SeqMLInput => "foo.seqml",
);
my $r = Chart::Sequence::Imager->new;
my $png => $r->render( $s => "png" );
$r->render_to_file( $s => "foo.png" );
Download (0.015MB)
Added: 2007-07-27 License: Perl Artistic License Price:
819 downloads
Net::Stomp 0.32
Net::Stomp is a Streaming Text Orientated Messaging Protocol Client. more>>
Net::Stomp is a Streaming Text Orientated Messaging Protocol Client.
SYNOPSIS
# send a message to the queue foo
use Net::Stomp;
my $stomp = Net::Stomp->new( { hostname => localhost, port => 61613 } );
$stomp->connect( { login => hello, passcode => there } );
$stomp->send(
{ destination => /queue/foo, body => test message } );
$stomp->disconnect;
# subscribe to messages from the queue foo
use Net::Stomp;
my $stomp = Net::Stomp->new( { hostname => localhost, port => 61613 } );
$stomp->connect( { login => hello, passcode => there } );
$stomp->subscribe(
{ destination => /queue/foo,
ack => client,
activemq.prefetchSize => 1
}
);
while (1) {
my $frame = $stomp->receive_frame;
warn $frame->body; # do something here
$stomp->ack( { frame => $frame } );
}
$stomp->disconnect;
# write your own frame
my $frame = Net::Stomp::Frame->new(
{ command => $command, headers => $conf, body => $body } );
$self->send_frame($frame);
This module allows you to write a Stomp client. Stomp is the Streaming Text Orientated Messaging Protocol (or the Protocol Briefly Known as TTMP and Represented by the symbol :ttmp). Its a simple and easy to implement protocol for working with Message Orientated Middleware from any language.
Net::Stomp is useful for talking to Apache ActiveMQ, an open source (Apache 2.0 licensed) Java Message Service 1.1 (JMS) message broker packed with many enterprise features.
A Stomp frame consists of a command, a series of headers and a body - see Net::Stomp::Frame for more details.
<<lessSYNOPSIS
# send a message to the queue foo
use Net::Stomp;
my $stomp = Net::Stomp->new( { hostname => localhost, port => 61613 } );
$stomp->connect( { login => hello, passcode => there } );
$stomp->send(
{ destination => /queue/foo, body => test message } );
$stomp->disconnect;
# subscribe to messages from the queue foo
use Net::Stomp;
my $stomp = Net::Stomp->new( { hostname => localhost, port => 61613 } );
$stomp->connect( { login => hello, passcode => there } );
$stomp->subscribe(
{ destination => /queue/foo,
ack => client,
activemq.prefetchSize => 1
}
);
while (1) {
my $frame = $stomp->receive_frame;
warn $frame->body; # do something here
$stomp->ack( { frame => $frame } );
}
$stomp->disconnect;
# write your own frame
my $frame = Net::Stomp::Frame->new(
{ command => $command, headers => $conf, body => $body } );
$self->send_frame($frame);
This module allows you to write a Stomp client. Stomp is the Streaming Text Orientated Messaging Protocol (or the Protocol Briefly Known as TTMP and Represented by the symbol :ttmp). Its a simple and easy to implement protocol for working with Message Orientated Middleware from any language.
Net::Stomp is useful for talking to Apache ActiveMQ, an open source (Apache 2.0 licensed) Java Message Service 1.1 (JMS) message broker packed with many enterprise features.
A Stomp frame consists of a command, a series of headers and a body - see Net::Stomp::Frame for more details.
Download (0.006MB)
Added: 2007-06-23 License: Perl Artistic License Price:
854 downloads
MINIX 3.1.3a
MINIX 3 is a new open-source operating system designed to be highly reliable and secure. more>>
MINIX 3 is a new open-source operating system designed to be highly reliable and secure. This project is based somewhat on previous versions of MINIX, but is fundamentally different in many key ways.
MINIX 1 and 2 were intended as teaching tools; MINIX 3 adds the new goal of being usable as a serious system on resource-limited and embedded computers and for applications requiring high reliability.
This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code. The parts that run in user mode are divided into small modules, well insulated from one another.
For example, each device driver runs as a separate user-mode process so a bug in a driver (by far the biggest source of bugs in any operating system), cannot bring down the entire OS.
In fact, most of the time when a driver crashes it is automatically replaced without requiring any user intervention, without requiring rebooting, and without affecting running programs. These features, the tiny amount of kernel code, and other aspects greatly enhance system reliability.
MINIX 3 is initially targeted at the following areas:
- Applications where very high reliability is required
- Single-chip, small-RAM, low-power, $100 laptop for Third-World children
- Embedded systems (e.g., cameras, DVD recorders, cell phones)
- Applications where the GPL is too restrictive (MINIX 3 uses a BSD-type license)
- Education (e.g., operating systems courses at universities)
Main features:
- POSIX compliant
- Networking with TCP/IP
- Two ANSI C compilers (ACK and gcc)
- Over 300 UNIX programs
- Many improvements since V2
- Full multiuser and multiprogramming
- Support for memory up to 4 GB
- Device drivers run as user processes
- Full C source code supplied
- Runs on 386, 486, Pentium, etc.
To run MINIX 3, you need a PC driven by a 386, 486, or Pentium CPU or compatible. The standard configuration requires 16 MB of RAM. An 8-MB version is also available, but it is slower due to a smaller buffer cache. Since the distribution comes on a live CD, you can test it without allocating any hard disk space, but for a hard disk installation, 200 MB is needed as a minimum, 400 MB minimum if you want all the sources.
<<lessMINIX 1 and 2 were intended as teaching tools; MINIX 3 adds the new goal of being usable as a serious system on resource-limited and embedded computers and for applications requiring high reliability.
This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code. The parts that run in user mode are divided into small modules, well insulated from one another.
For example, each device driver runs as a separate user-mode process so a bug in a driver (by far the biggest source of bugs in any operating system), cannot bring down the entire OS.
In fact, most of the time when a driver crashes it is automatically replaced without requiring any user intervention, without requiring rebooting, and without affecting running programs. These features, the tiny amount of kernel code, and other aspects greatly enhance system reliability.
MINIX 3 is initially targeted at the following areas:
- Applications where very high reliability is required
- Single-chip, small-RAM, low-power, $100 laptop for Third-World children
- Embedded systems (e.g., cameras, DVD recorders, cell phones)
- Applications where the GPL is too restrictive (MINIX 3 uses a BSD-type license)
- Education (e.g., operating systems courses at universities)
Main features:
- POSIX compliant
- Networking with TCP/IP
- Two ANSI C compilers (ACK and gcc)
- Over 300 UNIX programs
- Many improvements since V2
- Full multiuser and multiprogramming
- Support for memory up to 4 GB
- Device drivers run as user processes
- Full C source code supplied
- Runs on 386, 486, Pentium, etc.
To run MINIX 3, you need a PC driven by a 386, 486, or Pentium CPU or compatible. The standard configuration requires 16 MB of RAM. An 8-MB version is also available, but it is slower due to a smaller buffer cache. Since the distribution comes on a live CD, you can test it without allocating any hard disk space, but for a hard disk installation, 200 MB is needed as a minimum, 400 MB minimum if you want all the sources.
Download (445.3MB)
Added: 2007-06-10 License: GPL (GNU General Public License) Price:
881 downloads
Business::PayPal::SDK 0.14
Business::PayPal::SDK is an interface to paypals SDKs. more>>
Business::PayPal::SDK is an interface to paypals SDKs.
SYNOPSIS
use Business::PayPal::SDK;
my $pp = new Business::PayPal::SDK(
{
paypal_apiid => "sdk-seller_api1.sdk.com",
paypal_apipw => "12345678",
paypal_cert => "paypal_java_sdk/samples/Cert/sdk-seller.p12",
paypal_certpw => "password",
paypal_env => "sandbox",
java_sdk_dir => "/path/to/paypals/java/sdk",
}
);
my $res = $pp->SetExpressCheckout(
{
OrderTotal => 10.00,
ReturnURL => http:://mydomain.com/myreturn,
CancelURL => http:://mydomain.com/mycancel,
}
);
print $res->{token};
Business::PayPal::SDK is a perl interface to the SDK provided by paypal (http://www.paypal.com/sdk). You can use this module to implement paypal pro and paypal express transactions in perl. On the back end this modules uses Inline::Java to interface directly with the paypals java sdk. Consequently you will need to get a J2SDK and Inline::Java installed. This was done for 2 reasons. 1) Speed of development, didnt have to deal with all the SOAP stuff. 2) Easier maintanance regarding future changes. That is to say, I only have to make sure I keep this compatiable with paypals SDK, not thier underlying protocol changes.
This document assumes you have an understanding of the java SDK and API provided by PayPal.
All methods take a single hashref as an argument. All methods return a hashref, or undef if there is an internal failure of some sort. Check $ret->{ack} to see if the call to PayPal was successful. If $ret->{ack} is not Success than you can check the $res->{ErrorCodes}, this will be an hashref with the key being the error code from paypal and the value is the getLongMessage from the error. Check $obj->error for description of failure.
<<lessSYNOPSIS
use Business::PayPal::SDK;
my $pp = new Business::PayPal::SDK(
{
paypal_apiid => "sdk-seller_api1.sdk.com",
paypal_apipw => "12345678",
paypal_cert => "paypal_java_sdk/samples/Cert/sdk-seller.p12",
paypal_certpw => "password",
paypal_env => "sandbox",
java_sdk_dir => "/path/to/paypals/java/sdk",
}
);
my $res = $pp->SetExpressCheckout(
{
OrderTotal => 10.00,
ReturnURL => http:://mydomain.com/myreturn,
CancelURL => http:://mydomain.com/mycancel,
}
);
print $res->{token};
Business::PayPal::SDK is a perl interface to the SDK provided by paypal (http://www.paypal.com/sdk). You can use this module to implement paypal pro and paypal express transactions in perl. On the back end this modules uses Inline::Java to interface directly with the paypals java sdk. Consequently you will need to get a J2SDK and Inline::Java installed. This was done for 2 reasons. 1) Speed of development, didnt have to deal with all the SOAP stuff. 2) Easier maintanance regarding future changes. That is to say, I only have to make sure I keep this compatiable with paypals SDK, not thier underlying protocol changes.
This document assumes you have an understanding of the java SDK and API provided by PayPal.
All methods take a single hashref as an argument. All methods return a hashref, or undef if there is an internal failure of some sort. Check $ret->{ack} to see if the call to PayPal was successful. If $ret->{ack} is not Success than you can check the $res->{ErrorCodes}, this will be an hashref with the key being the error code from paypal and the value is the getLongMessage from the error. Check $obj->error for description of failure.
Download (0.009MB)
Added: 2007-06-07 License: Perl Artistic License Price:
871 downloads
IPFIRE-wall 0.98.4
IPFIRE-wall is an IPv4 Packet Filter with Network Address Translation capabilities. more>>
IPFIRE-wall is an IPv4 Packet Filter with Network Address Translation capabilities. It can be used in desktop systems and in simple network configurations, providing a friendly interface and a simple installation. Also unprivileged users can personalize.
Enhancements:
Kernel: Added support for version 2.6.20.
- Corrected a little bug that used to send in userspace also the packets pre/post routed although the silent modality had been chosen.
User Interface:
- Added a new submenu, accessed by the combination CTRL-B, which allows the user to easily add an address to block by its name. This menu can show the list of blocked web addresses, and provides an interface to add and remove new entries.
- The TCP flags representation has been changed: instead of the full name SYN, ACK, RST, PSH, URG, FIN, the user interface, for the sake of brevity, will now just print the corresponding initial letters, i.e. S, A, R, P, U, F, respectively. The Urgent flag will be printed in dark red color, from this version on.
- The length of the rule name has been extended to support 24 characters instead of the 19 of the previous versions.
Documentation:
- the web documentation is being updated and corrected. This process will continue after this release. Until now, practically the firts 14 topics of the documentation text (see ipfirewall documentation index) has been updated. The remaining pages, together with the new screenshots, are still being revised. Keep an eye on them to stay up to date and be able to use the software at its maximum capabilities.
<<lessEnhancements:
Kernel: Added support for version 2.6.20.
- Corrected a little bug that used to send in userspace also the packets pre/post routed although the silent modality had been chosen.
User Interface:
- Added a new submenu, accessed by the combination CTRL-B, which allows the user to easily add an address to block by its name. This menu can show the list of blocked web addresses, and provides an interface to add and remove new entries.
- The TCP flags representation has been changed: instead of the full name SYN, ACK, RST, PSH, URG, FIN, the user interface, for the sake of brevity, will now just print the corresponding initial letters, i.e. S, A, R, P, U, F, respectively. The Urgent flag will be printed in dark red color, from this version on.
- The length of the rule name has been extended to support 24 characters instead of the 19 of the previous versions.
Documentation:
- the web documentation is being updated and corrected. This process will continue after this release. Until now, practically the firts 14 topics of the documentation text (see ipfirewall documentation index) has been updated. The remaining pages, together with the new screenshots, are still being revised. Keep an eye on them to stay up to date and be able to use the software at its maximum capabilities.
Download (0.30MB)
Added: 2007-06-06 License: GPL (GNU General Public License) Price:
871 downloads
LLnextgen 0.5.0
LLnextgen is an Extended LL(1) parser generator. more>>
LLnextgen is an Extended-LL(1) parser generator. LLnextgen project is a rewrite of the LLgen parser generator by D. Grune and C.J.H. Jacobs which is part of the Amsterdam Compiler Kit (ACK).
Like all parser generators, LLnextgen takes the description of the grammar with associated actions as input, and generates a parser routine for use in compilers and other text processing programs.
LLgen, and therefore LLnextgen, extends on the LL(1) class of parser generators by allowing FIRST/FIRST conflicts and FIRST/FOLLOW conflicts to be resolved with both static and dynamic conditions.
Enhancements:
- This release adds a new operator for specifying an optional-final repetition.
- This is useful for implementing grammar rules like C99/C++ enums where a comma after the last constant is allowed, but not required.
- An option was added to change the extensions of the generated files.
<<lessLike all parser generators, LLnextgen takes the description of the grammar with associated actions as input, and generates a parser routine for use in compilers and other text processing programs.
LLgen, and therefore LLnextgen, extends on the LL(1) class of parser generators by allowing FIRST/FIRST conflicts and FIRST/FOLLOW conflicts to be resolved with both static and dynamic conditions.
Enhancements:
- This release adds a new operator for specifying an optional-final repetition.
- This is useful for implementing grammar rules like C99/C++ enums where a comma after the last constant is allowed, but not required.
- An option was added to change the extensions of the generated files.
Download (MB)
Added: 2007-05-27 License: Open Software License Price:
880 downloads
Fwctl 0.28
Fwctl is a Perl module to configure the Linux kernel packet filtering firewall. more>>
Fwctl is a Perl module to configure the Linux kernel packet filtering firewall.
SYNOPSIS
use Fwctl;
my $fwctl = new Fwctl( %opts );
$fwctl->dump_acct;
$fwctl->reset_fw;
$fwctl->configure;
Fwctl is a module to configure the Linux kernel packet filtering firewall using higher level abstraction than rules on input, output and forward chains. It supports masquerading and accounting as well.
Why Fwctl ? Well, say you are the kind of paranoid firewall administrator which likes his firewalls rules tight. Very tight. Say the kind, that likes to distinguish between a SYN and ACK packet when accepting a TCP connection (anybody configuring packet filters should care about that last point), or like to specify the interface name on each rules. (Whether this is really need, or such a stance is relevant, is not the point.) How would such an administrator proceed ? First of all you deny everything on all interfaces and on all chains (input, forward and output) and turn on logging. Now starting from this configuration (in which Fwctl puts the firewall on initialization), say you want to enable ping from the internal network to the internal ip. What rules do you need ? You need a rule on the input chain to accept the echo-request packet and a rule on the output chain to accept the echo-reply request. Right ? Well, what about the loopback. For sure, when we say from local net to local ip, this imply local ip to local ip ? Then you add a rule to the output chain with the loopback interface, and a rule on the input rule to the loopback chain. And we didnt even start forwarding yet ! Add masquerading to the lot and multi connections protocols like FTP and you got something unmanageable. So you start accepting things you shouldnt to get your job done and in the end your filters look like emmenthal.
Fwctl handles all the complexity of this, so that when you say
accept ftp -src FTP_PROXY -dst INTERNET -noport
you dont accept too much of what you didnt intend. (Well you just opened arbitrary TCP connections to unprivileged ports on the Internet from your proxy server, but thats because of the FTP protocol, not because your cheating on the firewall rules.)
Fwctl works with entity known as service. A service can be ftp, netbios, ping or anything else. The service abstraction handles all the communication necessary for that application. (The UDP and TCP communication in DNS, or the control, data and passive connections for FTP.)
Additionally, to handle all the special case with ANY specification, when the src of dst imply a local IP, or masquerading, in short for Fwctl to be able to deduce the interface implicated by the src and dst portion of a rules you need to provide it with your network topology. Fwctl must guess from your topology the routing decision that will be made in the kernel. In the best of worlds, Fwctl should contains the same routing algorithm as the one in the kernel. Well, it doesnt so if you are using fancy routing feature, Fwctl wont work. In fact, it can only handle something equivalent to simple static routing. You have been warned.
So in short, to configure your packet filters with Fwctl you need to
Define your network topology using the interfaces file.
(Optional) Define meaningful aliases for hosts and networks which are part of your configuration.
Implement your security policy using high level abstract rules in the rules file.
Finally, Fwctl is extensible. You can easily add services modules using the Fwctl::RuleSet module which contains all the primitive you need to handle all the special cases involved in the input, forward and output chain selection.
<<lessSYNOPSIS
use Fwctl;
my $fwctl = new Fwctl( %opts );
$fwctl->dump_acct;
$fwctl->reset_fw;
$fwctl->configure;
Fwctl is a module to configure the Linux kernel packet filtering firewall using higher level abstraction than rules on input, output and forward chains. It supports masquerading and accounting as well.
Why Fwctl ? Well, say you are the kind of paranoid firewall administrator which likes his firewalls rules tight. Very tight. Say the kind, that likes to distinguish between a SYN and ACK packet when accepting a TCP connection (anybody configuring packet filters should care about that last point), or like to specify the interface name on each rules. (Whether this is really need, or such a stance is relevant, is not the point.) How would such an administrator proceed ? First of all you deny everything on all interfaces and on all chains (input, forward and output) and turn on logging. Now starting from this configuration (in which Fwctl puts the firewall on initialization), say you want to enable ping from the internal network to the internal ip. What rules do you need ? You need a rule on the input chain to accept the echo-request packet and a rule on the output chain to accept the echo-reply request. Right ? Well, what about the loopback. For sure, when we say from local net to local ip, this imply local ip to local ip ? Then you add a rule to the output chain with the loopback interface, and a rule on the input rule to the loopback chain. And we didnt even start forwarding yet ! Add masquerading to the lot and multi connections protocols like FTP and you got something unmanageable. So you start accepting things you shouldnt to get your job done and in the end your filters look like emmenthal.
Fwctl handles all the complexity of this, so that when you say
accept ftp -src FTP_PROXY -dst INTERNET -noport
you dont accept too much of what you didnt intend. (Well you just opened arbitrary TCP connections to unprivileged ports on the Internet from your proxy server, but thats because of the FTP protocol, not because your cheating on the firewall rules.)
Fwctl works with entity known as service. A service can be ftp, netbios, ping or anything else. The service abstraction handles all the communication necessary for that application. (The UDP and TCP communication in DNS, or the control, data and passive connections for FTP.)
Additionally, to handle all the special case with ANY specification, when the src of dst imply a local IP, or masquerading, in short for Fwctl to be able to deduce the interface implicated by the src and dst portion of a rules you need to provide it with your network topology. Fwctl must guess from your topology the routing decision that will be made in the kernel. In the best of worlds, Fwctl should contains the same routing algorithm as the one in the kernel. Well, it doesnt so if you are using fancy routing feature, Fwctl wont work. In fact, it can only handle something equivalent to simple static routing. You have been warned.
So in short, to configure your packet filters with Fwctl you need to
Define your network topology using the interfaces file.
(Optional) Define meaningful aliases for hosts and networks which are part of your configuration.
Implement your security policy using high level abstract rules in the rules file.
Finally, Fwctl is extensible. You can easily add services modules using the Fwctl::RuleSet module which contains all the primitive you need to handle all the special cases involved in the input, forward and output chain selection.
Download (0.078MB)
Added: 2007-05-11 License: Perl Artistic License Price:
896 downloads
IPChains 0.5
IPChains is a Perl module to create and manipulate ipchains via Perl. more>>
IPChains is a Perl module to create and manipulate ipchains via Perl.
SYNOPSIS
use IPChains;
$fw = IPChains->new(-option => value, ... ); $fw->append(chain);
This module acts as an interface to the ipchains(8) userspace utility by Paul "Rusty" Russell (http://www.rustcorp.com/linux/ipchains/). It attempts to include all the functionality of the original code with a simplified user interface via Perl. In addition, plans for log parsing facilities, an integrated interface to ipmasqadm, and possibly traffic shaping are slated for up and coming versions.
The new() and attribute() methods support the following options:
Source
Specifies origination address of packet. Appending hostmask to this address using a / is OK, as well as specifying it separately (see SourceMask).
SourceMask
Hostmask for origination address. Can either be in 24 or 255.255.255.0 style.
SourcePort
Specific port or port range (use xxx:xxx to denote range), requires specific protocol specification.
Dest
Specifies destination address of packet. Appending hostmask to this address using a / is OK, as well as specifying it separately (see DestMask)
DestMask
Destination address, (see SourceMask).
DestPort
Destination Port, (see SourcePort).
Prot
Protocol. Can be tcp, udp, icmp, or all. Required for specifying specific port(s).
ICMP
ICMP Name/Code (in place of port when ICMP is specified as protocol).
Here is a small table of some of the most common ICMP packets:
Number Name Required by
0 echo-reply ping
3 destination-unreachable Any TCP/UDP traffic.
5 redirect routing if not running
routing daemon
8 echo-request ping
11 time-exceeded traceroute
Rule
Target. Can be ACCEPT, DENY, REJECT, MASQ, REDIRECT, RETURN, or a user-defined chain. Note: This is case sensitive.
Interface
Specify a specify interface as part of the criteria (ie, eth0, ppp0, etc.).
Fragment
Rule only refers to second and further fragments of fragmented packets (1 or 0).
Bidir
Makes criteria effective in both directions (1 or 0).
Verbose
Set verbose option for setting rules or list() (1 or 0).
Numeric
Show output from list() in numeric format. No DNS lookups, etc.. (1 or 0).
Log
Enable kernel logging (via syslog, kern.info) of matched packets (1 or 0).
Output
Copy matching packets to the userspace device (advanced).
Mark
Mark matching packets with specified number (advanced).
TOS
Used for modifying the TOS field in the IP header. Takes 2 args, AND and XOR masks, (ie, (TOS => ["0x01", "0x10"])). This feature is highly untested.
The first mask is ANDed with the packets current TOS, and the second mask is XORed with it. Use the following table for reference:
TOS Name Value Typical Uses
Minimum Delay 0x01 0x10 ftp, telnet
Maximum Throughput 0x01 0x08 ftp-data
Maximum Reliability 0x01 0x04 snmp
Minimum Cost 0x01 0x02 nntp
Exact
Display exact numbers in byte counters instead of numbers rounded in Ks, Ms, or Gs (1 or 0).
SYN
Only match TCP packets with the SYN bit set and the ACK and FIN bits cleared (1 or 0).
<<lessSYNOPSIS
use IPChains;
$fw = IPChains->new(-option => value, ... ); $fw->append(chain);
This module acts as an interface to the ipchains(8) userspace utility by Paul "Rusty" Russell (http://www.rustcorp.com/linux/ipchains/). It attempts to include all the functionality of the original code with a simplified user interface via Perl. In addition, plans for log parsing facilities, an integrated interface to ipmasqadm, and possibly traffic shaping are slated for up and coming versions.
The new() and attribute() methods support the following options:
Source
Specifies origination address of packet. Appending hostmask to this address using a / is OK, as well as specifying it separately (see SourceMask).
SourceMask
Hostmask for origination address. Can either be in 24 or 255.255.255.0 style.
SourcePort
Specific port or port range (use xxx:xxx to denote range), requires specific protocol specification.
Dest
Specifies destination address of packet. Appending hostmask to this address using a / is OK, as well as specifying it separately (see DestMask)
DestMask
Destination address, (see SourceMask).
DestPort
Destination Port, (see SourcePort).
Prot
Protocol. Can be tcp, udp, icmp, or all. Required for specifying specific port(s).
ICMP
ICMP Name/Code (in place of port when ICMP is specified as protocol).
Here is a small table of some of the most common ICMP packets:
Number Name Required by
0 echo-reply ping
3 destination-unreachable Any TCP/UDP traffic.
5 redirect routing if not running
routing daemon
8 echo-request ping
11 time-exceeded traceroute
Rule
Target. Can be ACCEPT, DENY, REJECT, MASQ, REDIRECT, RETURN, or a user-defined chain. Note: This is case sensitive.
Interface
Specify a specify interface as part of the criteria (ie, eth0, ppp0, etc.).
Fragment
Rule only refers to second and further fragments of fragmented packets (1 or 0).
Bidir
Makes criteria effective in both directions (1 or 0).
Verbose
Set verbose option for setting rules or list() (1 or 0).
Numeric
Show output from list() in numeric format. No DNS lookups, etc.. (1 or 0).
Log
Enable kernel logging (via syslog, kern.info) of matched packets (1 or 0).
Output
Copy matching packets to the userspace device (advanced).
Mark
Mark matching packets with specified number (advanced).
TOS
Used for modifying the TOS field in the IP header. Takes 2 args, AND and XOR masks, (ie, (TOS => ["0x01", "0x10"])). This feature is highly untested.
The first mask is ANDed with the packets current TOS, and the second mask is XORed with it. Use the following table for reference:
TOS Name Value Typical Uses
Minimum Delay 0x01 0x10 ftp, telnet
Maximum Throughput 0x01 0x08 ftp-data
Maximum Reliability 0x01 0x04 snmp
Minimum Cost 0x01 0x02 nntp
Exact
Display exact numbers in byte counters instead of numbers rounded in Ks, Ms, or Gs (1 or 0).
SYN
Only match TCP packets with the SYN bit set and the ACK and FIN bits cleared (1 or 0).
Download (0.050MB)
Added: 2007-05-10 License: Perl Artistic License Price:
897 downloads
The Amsterdam Compiler Kit 6.0 pre3
The Amsterdam Compiler Kit is a fast, lightweight and retargetable compiler suite and toolchain. more>>
The Amsterdam Compiler Kit or in short just ACK, is a fast, lightweight and retargetable compiler suite and toolchain written by Andrew Tanenbaum and Ceriel Jacobs, and was Minix native toolchain. The ACK was originally closed-source software (that allowed binaries to be distributed for Minix as a special case), but in April 2003 it was released under a BSD open source license.
The ACK achieves maximum portability by using an intermediate byte-code language called EM. Each language front-end produces EM object files, which are then processed through a number of generic optimisers before being translated by a back-end into native machine code.
Unlike gccs intermediate language, EM is a real programming language and could be implemented in hardware; a number of the language front-ends have libraries implemented in EM assembly. EM is a relatively high-level stack-based machine, and one of the tools supplied with ACK is an interpreter capable of executing EM binaries directly, with a high degree of safety checking. See the em document referenced below for more information.
ACK comes with a generic linker and librarian capable of manipulating files in the ACKs own a.out-based format; it will work on files containing EM code as well as native machine code. (You can not, however, link EM code to native machine code without translating the EM binary first.)
Installation:
To install the ACK, you need to download the source package and compile it.
Version 5.6 compiles cleanly on Linux, but it has had little testing so far. The installation instructions are complex but straightforward provided you follow the instructions. Please read the README; it provides a detailed walk-through of the compilation process, telling you what to type at each stage.
Enhancements:
- Support has been added for generating CP/M binaries using the 8080 code generator.
- The various optimisers have been beaten into shape, and its now possible to use them on all platforms; a basic peephole optimiser has been set up for the 8080.
- The floating point system has been confirmed working on the pc86 and linux386 platforms.
- ANSI compatibility has been improved, binary sizes have been reduced, and there are many bugfixes everywhere.
<<lessThe ACK achieves maximum portability by using an intermediate byte-code language called EM. Each language front-end produces EM object files, which are then processed through a number of generic optimisers before being translated by a back-end into native machine code.
Unlike gccs intermediate language, EM is a real programming language and could be implemented in hardware; a number of the language front-ends have libraries implemented in EM assembly. EM is a relatively high-level stack-based machine, and one of the tools supplied with ACK is an interpreter capable of executing EM binaries directly, with a high degree of safety checking. See the em document referenced below for more information.
ACK comes with a generic linker and librarian capable of manipulating files in the ACKs own a.out-based format; it will work on files containing EM code as well as native machine code. (You can not, however, link EM code to native machine code without translating the EM binary first.)
Installation:
To install the ACK, you need to download the source package and compile it.
Version 5.6 compiles cleanly on Linux, but it has had little testing so far. The installation instructions are complex but straightforward provided you follow the instructions. Please read the README; it provides a detailed walk-through of the compilation process, telling you what to type at each stage.
Enhancements:
- Support has been added for generating CP/M binaries using the 8080 code generator.
- The various optimisers have been beaten into shape, and its now possible to use them on all platforms; a basic peephole optimiser has been set up for the 8080.
- The floating point system has been confirmed working on the pc86 and linux386 platforms.
- ANSI compatibility has been improved, binary sizes have been reduced, and there are many bugfixes everywhere.
Download (1.1MB)
Added: 2007-05-01 License: BSD License Price:
908 downloads
SIPp 2.0
SIPp is a free Open Source test tool / traffic generator for the SIP protocol. more>>
SIPp is a free Open Source test tool / traffic generator for the SIP protocol. It includes a few basic SipStone user agent scenarios (UAC and UAS) and establishes and releases multiple calls with the INVITE and BYE methods.
SIPp project can also reads custom XML scenario files describing from very simple to complex call flows. It features the dynamic display of statistics about running tests (call rate, round trip delay, and message statistics), periodic CSV statistics dumps, TCP and UDP over multiple sockets or multiplexed with retransmission management and dynamically adjustable call rates.
Other advanced features include support of IPv6, TLS, SIP authentication, conditional scenarios, UDP retransmissions, error robustness (call timeout, protocol defense), call specific variable, Posix regular expression to extract and re-inject any protocol fields, custom actions (log, system command exec, call stop) on message receive, field injection from external CSV file to emulate live users.
While optimized for traffic, stress and performance testing, SIPp can be used to run one single call and exit, providing a passed/failed verdict.
Last, but not least, SIPp has a comprehensive documentation available both in HTML and PDF format.
SIPp can be used to test many real SIP equipements like SIP proxies, B2BUAs, SIP media servers, SIP/x gateways, SIP PBX, ... It is also very useful to emulate thousands of user agents calling your SIP system.
Enhancements:
- New: Statistical (conditional) branching feature. See
- http://sipp.sf.net/doc/reference.html#Randomness+in+conditional+branching.
- New: 3PCC extended mode - see
- http://sipp.sourceforge.net/doc/reference.html#3PCC+Extended
- Tool: monitor remote SIP servers through SNMP - see
- http://sipp.sourceforge.net/wiki/index.php/Getting_feedback_from_the_server
- Enh: extends the -aa option to UPDATE messages
- Enh: changes in the compilation with external libs - useful for the package
- generation system
- Enh: Allow sampling from a Weibull distribution for pause duration
- Enh: use stat_delimiter for the trace_rtt option and include number that is
- being reported.
- Enh: Add repeat_rtd keyword for repeated RTD calculations
- Enh: Handle stripping Control-M characters from multi-valued headers in
- get_header
- Enh: Update the clock_tick more frequently so that we have a higher timer and
- statistics resolution
- Enh: for option that take a time as argument - allow them to be specified using
- seconds or milliseconds
- Enh: fail when parsing a scenario that has pcap if pcap is not enabled
- Enh: print the actual location of the error log file and the error condition
- (if any) on creation
- Enh: fail when parsing a scenario that enables authentication if SSL is not
- enabled
- Enh: Makefile - include EXTRAENDLIBS keyword so that libraries can be appended
- to the list after SSL Enh: Add regexp_match argument to the receive command for
- universal catching
- Enh: remote control: increase the allowed number of control sockets.
- Enh: 3pcc extended: clean the reach of the allowed number of local twin sockets
- Enh: amelioration of statistic computing
- Enh regexp: add case_indep, occurence and start_line options for the hdr
- matching case
- Enh: Stats: Use RTDs that are precise to the microsecond in -trace_rtt, and
- improve the consistency between trace_rtt and the averages
- Enh: Only include RTDs that are actually used in the CSV output
- Enh: Allow loss percentages less than 1 and also a global command line option to
- specify that packets should be lost at a given percentage
- Fix: fix for -t un error for non-IPv6 platform like win32 - Unable to bind UDP
- socket, errno = 106 (Address family not supported by protocol)
- Fix: Do not initialize the screen library in background mode
- Fix: allow having an optional recv before a recvCmd
- Fix: Authentication: allow [fieldn] values for the [authentication] field
- Fix: updated support of short header forms
- Fix: small bug fix to the micrortt.diff which is required for the initial call
- rate to work properly
- Fix:Allow the code to compile with -Wall -Werror on Linux
- Fix: empty line was generated when [routes] keyword was used and proxy did not
- record-route
- Fix: pcap on HPUX; Fix: Simple fixes identified with valgrind
- Fix: 3pcc extended: problem when quitting
- Fix: regexp: add a warning when the specified header is not present in the
- received message
- Fix: pcap: destroy the send packets thread properly even if the sendto failed
- Fix: bug in regexp due to an incomplete commit (rev 172) - remove some debugging
- traces in message log file
- Fix: bugs on retransmission counters and on cookies for optional messages
- Fix: Incorrect branch in automatic ACK answering to unexpected >= 400 responses,
- as well as automatic CANCEL - in such cases, branch must be identical to the
- branch of the initial INVITE request
- Fix: 3pcc extended: clean up when screen exit. Fix: stop logging when the
- maximum allowed file size is reached (avoid core dump)
- Fix: incomplete Via header in automatic responses when aborting calls
- Fix: -h: -key parameter
- Fix: 3pcc/3pcc extended modes: closes twin sockets properly when twin instance
- exits, to break the poll() loop and avoid the print of empty messages
- Fix: in 3pcc/3pcc extended modes: send BYE/CANCEL before exit due to other twin
- instance exit
- Fix: force exit when pressing q twice (Q press can still be used)
- Fix: Aka authentication for synchro case, also added password len as password
- for authentication might contain char Fix: possible core dump in SDP parser
- Fix: accept up to the 5 defined RTDs (previously would only accept one less)
- Fix: Fail if there is an invalid repartition table specification - previous
- behavior was a core dump
- Fix: added -users option to the parameter table
- Fix: change option description to match timed options
- Fix: trace_err did not work in background mode
- Fix: bug when testing the presence of the 3PCC compilation flag
- Fix: bug in -r -rp option
<<lessSIPp project can also reads custom XML scenario files describing from very simple to complex call flows. It features the dynamic display of statistics about running tests (call rate, round trip delay, and message statistics), periodic CSV statistics dumps, TCP and UDP over multiple sockets or multiplexed with retransmission management and dynamically adjustable call rates.
Other advanced features include support of IPv6, TLS, SIP authentication, conditional scenarios, UDP retransmissions, error robustness (call timeout, protocol defense), call specific variable, Posix regular expression to extract and re-inject any protocol fields, custom actions (log, system command exec, call stop) on message receive, field injection from external CSV file to emulate live users.
While optimized for traffic, stress and performance testing, SIPp can be used to run one single call and exit, providing a passed/failed verdict.
Last, but not least, SIPp has a comprehensive documentation available both in HTML and PDF format.
SIPp can be used to test many real SIP equipements like SIP proxies, B2BUAs, SIP media servers, SIP/x gateways, SIP PBX, ... It is also very useful to emulate thousands of user agents calling your SIP system.
Enhancements:
- New: Statistical (conditional) branching feature. See
- http://sipp.sf.net/doc/reference.html#Randomness+in+conditional+branching.
- New: 3PCC extended mode - see
- http://sipp.sourceforge.net/doc/reference.html#3PCC+Extended
- Tool: monitor remote SIP servers through SNMP - see
- http://sipp.sourceforge.net/wiki/index.php/Getting_feedback_from_the_server
- Enh: extends the -aa option to UPDATE messages
- Enh: changes in the compilation with external libs - useful for the package
- generation system
- Enh: Allow sampling from a Weibull distribution for pause duration
- Enh: use stat_delimiter for the trace_rtt option and include number that is
- being reported.
- Enh: Add repeat_rtd keyword for repeated RTD calculations
- Enh: Handle stripping Control-M characters from multi-valued headers in
- get_header
- Enh: Update the clock_tick more frequently so that we have a higher timer and
- statistics resolution
- Enh: for option that take a time as argument - allow them to be specified using
- seconds or milliseconds
- Enh: fail when parsing a scenario that has pcap if pcap is not enabled
- Enh: print the actual location of the error log file and the error condition
- (if any) on creation
- Enh: fail when parsing a scenario that enables authentication if SSL is not
- enabled
- Enh: Makefile - include EXTRAENDLIBS keyword so that libraries can be appended
- to the list after SSL Enh: Add regexp_match argument to the receive command for
- universal catching
- Enh: remote control: increase the allowed number of control sockets.
- Enh: 3pcc extended: clean the reach of the allowed number of local twin sockets
- Enh: amelioration of statistic computing
- Enh regexp: add case_indep, occurence and start_line options for the hdr
- matching case
- Enh: Stats: Use RTDs that are precise to the microsecond in -trace_rtt, and
- improve the consistency between trace_rtt and the averages
- Enh: Only include RTDs that are actually used in the CSV output
- Enh: Allow loss percentages less than 1 and also a global command line option to
- specify that packets should be lost at a given percentage
- Fix: fix for -t un error for non-IPv6 platform like win32 - Unable to bind UDP
- socket, errno = 106 (Address family not supported by protocol)
- Fix: Do not initialize the screen library in background mode
- Fix: allow having an optional recv before a recvCmd
- Fix: Authentication: allow [fieldn] values for the [authentication] field
- Fix: updated support of short header forms
- Fix: small bug fix to the micrortt.diff which is required for the initial call
- rate to work properly
- Fix:Allow the code to compile with -Wall -Werror on Linux
- Fix: empty line was generated when [routes] keyword was used and proxy did not
- record-route
- Fix: pcap on HPUX; Fix: Simple fixes identified with valgrind
- Fix: 3pcc extended: problem when quitting
- Fix: regexp: add a warning when the specified header is not present in the
- received message
- Fix: pcap: destroy the send packets thread properly even if the sendto failed
- Fix: bug in regexp due to an incomplete commit (rev 172) - remove some debugging
- traces in message log file
- Fix: bugs on retransmission counters and on cookies for optional messages
- Fix: Incorrect branch in automatic ACK answering to unexpected >= 400 responses,
- as well as automatic CANCEL - in such cases, branch must be identical to the
- branch of the initial INVITE request
- Fix: 3pcc extended: clean up when screen exit. Fix: stop logging when the
- maximum allowed file size is reached (avoid core dump)
- Fix: incomplete Via header in automatic responses when aborting calls
- Fix: -h: -key parameter
- Fix: 3pcc/3pcc extended modes: closes twin sockets properly when twin instance
- exits, to break the poll() loop and avoid the print of empty messages
- Fix: in 3pcc/3pcc extended modes: send BYE/CANCEL before exit due to other twin
- instance exit
- Fix: force exit when pressing q twice (Q press can still be used)
- Fix: Aka authentication for synchro case, also added password len as password
- for authentication might contain char Fix: possible core dump in SDP parser
- Fix: accept up to the 5 defined RTDs (previously would only accept one less)
- Fix: Fail if there is an invalid repartition table specification - previous
- behavior was a core dump
- Fix: added -users option to the parameter table
- Fix: change option description to match timed options
- Fix: trace_err did not work in background mode
- Fix: bug when testing the presence of the 3PCC compilation flag
- Fix: bug in -r -rp option
Download (0.18MB)
Added: 2007-04-27 License: GPL (GNU General Public License) Price:
926 downloads
Synscan 3.1
Synscan is a tool to determine the TCP ports that are in an OPEN state. more>>
Another aspect of enumeration of hosts is the determining of TCP ports in an OPEN state, that is to say TCP ports which respond to SYN packets with a Syn and the ACK flag set, Syn-Ack.
Synscan is impressively fast at determinining this via the use of two processes, one to send the Syn packets and one to listen for the responses. NB: At first start with low settings as it can impact systems if it is run too fast. The portparse utility is also a useful little tool!
Should compile cleanly on IRIX, Solaris and Linux if you have
libpcap installed.
Licensed under the GPL version 2. If you modify this app for your own needs, i would appreciate a copy of the changes being emailed to me.
Edit synscan.h to configure a few parameters before compiling.
Synscan works using 2 programs..
The "synscan" tool will send SYN packets.
And a second program, either synscand or sslog will listen for the resulting SYN/ACK packets to determine if ports are open.
Compiling this tool will create 3 binaries:
synscan - for sending SYN packets
synscand - logs replies and performs protocol specific checks
sslog - logs replies and shows ip:port results
<<lessSynscan is impressively fast at determinining this via the use of two processes, one to send the Syn packets and one to listen for the responses. NB: At first start with low settings as it can impact systems if it is run too fast. The portparse utility is also a useful little tool!
Should compile cleanly on IRIX, Solaris and Linux if you have
libpcap installed.
Licensed under the GPL version 2. If you modify this app for your own needs, i would appreciate a copy of the changes being emailed to me.
Edit synscan.h to configure a few parameters before compiling.
Synscan works using 2 programs..
The "synscan" tool will send SYN packets.
And a second program, either synscand or sslog will listen for the resulting SYN/ACK packets to determine if ports are open.
Compiling this tool will create 3 binaries:
synscan - for sending SYN packets
synscand - logs replies and performs protocol specific checks
sslog - logs replies and shows ip:port results
Download (0.033MB)
Added: 2007-04-21 License: GPL (GNU General Public License) Price:
920 downloads
uEagle-ATM 1.3
uEagle-ATM provides a rewritten driver for ADSL USB modems with ADIs Eagle-USB chipset. more>>
uEagle-ATM provides a rewritten driver for ADSL USB modems with ADIs Eagle-USB chipset.
uEagle-ATM is a driver for ADSL USB modems with ADIs Eagle-USB chipset like Sagem Fast 800 or Comtrend CT-350.
This driver has been rewritten to adapt to the usbatm library, which is also used by the driver for Speedtouch 330 and Connexant AccessRunner.
It is based on Damien Bergaminis ueagle driver for *BSD. It works with Linux kernel 2.6.10 and above.
All encapsulations, such as PPPoA, PPPoE, or Routed IP, are taken into account.
Enhancements:
- improve debug trace in order to make easy to solve user problems.
- indent some code
- increase version number
- increase ack timeout for slow system (geode 233MHz where HZ=100)
- reset the cmv ack flag when rebooting
- fix potential null pointer dereference. Found by the Coverity checker.
- fix leak of memory allocated to intr if allocation of sc->urb_int fails. Found by the Coverity checker.
<<lessuEagle-ATM is a driver for ADSL USB modems with ADIs Eagle-USB chipset like Sagem Fast 800 or Comtrend CT-350.
This driver has been rewritten to adapt to the usbatm library, which is also used by the driver for Speedtouch 330 and Connexant AccessRunner.
It is based on Damien Bergaminis ueagle driver for *BSD. It works with Linux kernel 2.6.10 and above.
All encapsulations, such as PPPoA, PPPoE, or Routed IP, are taken into account.
Enhancements:
- improve debug trace in order to make easy to solve user problems.
- indent some code
- increase version number
- increase ack timeout for slow system (geode 233MHz where HZ=100)
- reset the cmv ack flag when rebooting
- fix potential null pointer dereference. Found by the Coverity checker.
- fix leak of memory allocated to intr if allocation of sc->urb_int fails. Found by the Coverity checker.
Download (0.037MB)
Added: 2007-04-16 License: GPL (GNU General Public License) Price:
933 downloads
DHCPsql 0.2-pre6
DHCPsql projects implements the RFC2132 and at least RFC3046 as a dynamic configurable SQL-based DHCP server. more>>
DHCPsql projects implements the RFC2132 and at least RFC3046 as a dynamic configurable SQL-based DHCP server, based on the udhcpd code, extended to mask-and-select by client DHCP packets.
Targets:
- Discover, start with a working pre prototype, always send first ip in subnet
- Leases, SQL implementation should be done for storing and recieving leases. To send next free ip in subnet.
- Static leases, fixed leasetime
- Request, basics send ACK/NAK
- Webfrontend, initial frontend for viewing the database
Enhancements:
- This version of DHCPsql supports OPTION_LIST with OPTION_IP.
- This allows administrators to add multiple IP addresses to their DHCP options.
- This feature was lacking in the previous releases where only one IP address was allowed, and this limited the use of the nameserver field.
<<lessTargets:
- Discover, start with a working pre prototype, always send first ip in subnet
- Leases, SQL implementation should be done for storing and recieving leases. To send next free ip in subnet.
- Static leases, fixed leasetime
- Request, basics send ACK/NAK
- Webfrontend, initial frontend for viewing the database
Enhancements:
- This version of DHCPsql supports OPTION_LIST with OPTION_IP.
- This allows administrators to add multiple IP addresses to their DHCP options.
- This feature was lacking in the previous releases where only one IP address was allowed, and this limited the use of the nameserver field.
Download (0.043MB)
Added: 2007-03-07 License: GPL (GNU General Public License) Price:
962 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above ack search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
