Free castleberry recall software for linux

Check Your Network Address Translator for Compatibility with Peer-to-Peer Protocols.
If you are accessing the Internet from behind a Network Address Translator (NAT) of some kind, I would appreciate your help in surveying the behavior of different NATs, in terms of how and whether they support a certain technique for enabling peer-to-peer communication between NATted hosts (particularly when both endpoints are behind NATs). Down, you can understand what NAT is.
Suppose there are three communicating hosts: A, B, and C. Host A is a "well-known" Internet server with a permanent IP address, which acts as an "introducer" for the other two nodes. (For example, Host A might be a well-known ultrapeer or a game catalog server of some kind.) Host B, using Host As "introduction" services, would like to establish a direct peer-to-peer connection with host C. Both B and C, however, are behind (probably different) network address/port translators, and neither of them has exclusive use of any public IP address.
To initiate a peer-to-peer connection with host C, host B first sends A a message requesting an "introduction" to host C. A sends B a reply message containing Cs IP address and UDP port number as reported by host C, in addition to Cs IP address and UDP port number as observed by A. (If C is behind a NAT, then these two address/port combinations will be different.) At the same time, host A sends host C a message containing Bs IP address and UDP port numbers - again, both the ones reported by B and the ones observed by A, which will be different if B is behind a NAT.
Now B and C each know that they want to initiate a connection with each other, and they know each others public (NATted) as well as original IP addresses and UDP port numbers. Both B and C now start attempting to send UDP messages directly to each other, at each of the available addresses. If B and C happen to be behind the same NAT, then they will be able to communicate with each other directly using their "originally reported" IP addresses and UDP port numbers.
In the more common case where B and C are behind different NATs, the "originally reported" addresses will be useless because they will both be private IP addresses in different addressing domains. Instead, the IP address/UDP port combinations observed by A can be used in this case to establish direct communication. Although Bs NAT will initially filter out any UDP packets arriving from Cs public (NATted) UDP port directed at Bs public port, the first UDP message B sends to C will cause Bs NAT to open up a new UDP session keyed on Cs public port, allowing future incoming traffic from C to pass through the NAT to B. Similarly, the first few messages from B to C may be filtered out by Cs NAT, but will be able to start passing through the firewall as soon as Cs first message to B causes Cs NAT to open up a new session. In this way, each NAT is tricked into thinking that its respective internal host is the "initiator" of this new session, when in fact the session is fully symmetrical and was initiated (with As help) simultaneously in each direction.
Required NAT Behavior
There is one important requirement that the NATs must satisfy in order for this technique to work: the NATs must be designed so that they assign only one (public IP address, public UDP port) pair to each (internal IP address, internal UDP port) combination, rather than allocating and assigning a new public UDP port for each new UDP session. Recall that a "session" in Internet terminology is defined by the IP addresses and port numbers of both communicating endpoints, so host Bs communication with host A is considered to be one session while host Bs communication with host C is a different session. If Bs NAT, for example, assigns one public UDP port for Bs communication with A, and then assigns B a different public UDP port for the new session B tries to open up with C, then the above technique for peer-to-peer communication will not work because Cs messages to B will be directed to the wrong UDP port.
RFC 3022 explicitly allows and suggests that NATs behave in the former, "desirable" fashion, by maintaining a single (public IP, public port) mapping for a given (internal IP, internal port) combination independent of the number of active sessions involving this mapping. This behavior is not only good for compatibility with UDP applications, but it also helps to conserve the NATs scarce pool of public port numbers. Maintaining a consistent public port mapping does not adversely affect security in any way, either, because incoming traffic can still be filtered on a per-session basis regardless of how addresses are translated. There in fact appears to be no good reason not to implement the desirable behavior in a NAT, except perhaps for the implementation simplicity of naively allocating a new public port for every new session. Unfortunately, RFC 3022 does not require NATs to implement the desirable behavior, which has led me to wonder just how many real NATs actually do, and hence this page.
What NAT Check Does
The program natcheck.c is basically just a program that "pings" a well-known UDP port at two different servers that are publically accessible on the Internet. Both of these servers run the program natserver.c, with the command-line arguments "1" and "2" respectively. In addition, there a third "conspiring" server runs natserver with the command-line argument "3". Whenever each of the first two servers receives a UDP request, it not only sends a reply directly to the sender of that request, but also sends a message to the third server, which in turn "bounces" the reply back to the original client. The effect is that the client will receive not only solicited "ping" replies from the server the request was directed to, but also "unsolicited" replies from the third server.
To determine if the network address translator in use is implementing the desirable behavior of maintaining a single (public IP address, public port) mapping for a given (client IP address, client port), the client program natcheck.c basically just initiates a sequence of simultaneous pings to the first two servers (in case some of the requests or replies are lost in transit) and checks that the clients address and UDP port as reported by both servers is the same. If the NAT naively allocates a new public port for each new session, then the source port as reported by the two servers will be different, and its time to upgrade your NAT.
The replies echoed from the third server are used only to check whether the NAT properly filters out unsolicited incoming traffic on a per-session basis. Since the client never sends any messages to the third server, if the NAT is properly implementing firewall functionality, the client should never see the third servers echoed replies even after opening up active communication sessions with the first two servers.
Enhancements:
- The NAT Check client no longer attempts to guess whether you have Basic NAT or Network Address/Port Translation (NAPT). It turns to be quite difficult to test for this property reliably, because many NAPTs attempt to bind a private UDP port to a public port with the same port number if that port number is available, causing NAT Check to falsely report Basic NAT. The only way to test for this property reliably would be to run NAT Check on at least two client machines simultaneously, and since this property isnt terribly important to P2P apps its just not worth the trouble.
- The NAT Check client now tests for one additional NAT feature, which I call loopback translation. If a NAT supports loopback translation, it means that a host on the private network behind the NAT can communicate with other hosts on the same private network using public (translated) port bindings assigned by the NAT. Most NATs probably do not support this feature yet, but it may become increasingly important in the future where P2P clients may be located behind a common ISP-deployed NAT as well as individual home NATs. More details on loopback translation will appear in the next version of my Internet-Draft, to be released soon.
- The NAT Check client program now has a command-line option, "-v", which turns on verbose messages during the test.

The tecla library provides UNIX and LINUX programs with interactive command line editing facilities, similar to those of the unix tcsh shell. In addition to simple command-line editing, it supports recall of previously entered command lines, TAB completion of file names, and
in-line wild-card expansion of filenames.

The internal functions which perform file-name completion and wild-card expansion are also available externally for optional use by programs, along with a module for tab-completion and lookup of filenames in a list of directories.

Note that special care has been taken to allow the use of this library in threaded programs. The option to enable this is discussed in the Makefile, and specific discussions of thread safety are presented in the included man pages.

Installation:

To compile and optionally install the library, it is first necessary to create a makefile for your system, by typing:

./configure

The Makefile that this generates is designed to install the files of the library in subdirectories of /usr/local/. If you would prefer to install them under a different directory, you can type:

./configure --prefix /wherever

Where you would replace /wherever with your chosen directory. Other command-line options are available, and can be listed by typing:

./configure --help

Having run the configure script, you are then ready to make the library. To do this, just type:

make

What make does depends on whether the configure script knows about your system. If the configure script doesnt know anything specific about your system, it will arrange for make to produce the static tecla library, called libtecla.a, and if possible, the reentrant
version of this called libtecla_r.a. If it does know about your system, it will also create shared libraries if possible.

If you are on a system that isnt known, and you would like shared libraries to be compiled, please read the file called PORTING to see how this can
be achieved.

To install the library, its include file and it manual pages, type:

make install

Note that this will also compile the library if you havent already done so.

Having compiled the library, if you wish, you can test it by running the demo programs. After building the library, you should find two programs, called demo and demo2, in the current directory.

The first of the demos programs reads input lines from the user, and writes what was typed back to the screen. While typing a line of input, you can experiment with line editing, tab completion, history recall etc.

For details about these line editing features, see the man page gl_get_line(3). If you havent installed this yet, you can see it anyway by typing:

nroff -man man3/gl_get_line.3 | more

The second demo program, called demo2, demonstrates command-completion
with the UNIX PATH. If you type in a partial command name, and press TAB, the command name will be completed if possible, and possible completions will be listed if it is ambiguous.

When you then enter the line, the demo program then prints out the full pathname of the command that you typed. If you type anything after the command name, filename completion with the tab key reverts to its default behavior of completing filenames in the current directory.

Web Diary is a Web-based multi-user CGI diary applet. It includes scripts for allowing users to make entries publicly viewable, easy administration, and user preference editing.

There are two changes to the database structure in this release and is very simple:

1. There is a new table (see diary.tbls), categories, and two pieces of information that needs to go in there. Nothing too complicated.
2. There needs to be one column added to, and one column removed from entries. You can accomplish this via something like:

alter table entries add entFCat int not null default 1
update entries set entFCat=2 where entFIsPublic=1
alter table entries drop entFIsPublic

Though, as usual, you might be wise to make a backup, though this is what I did, and didnt have a problem with it. What this does, in order, is 1) creates the new column, 2) preserves the public entries.
3) gets rid of the old column.

Other than that, I dont recall any signigicant changes that were made in
thi version that will affect the database.

Object Builder is a tool I wrote to make building and maintaining CeaMuS easier. I stole the idea (but not the code, which is in another language) wholesale from a tool that I wrote to manage the task of making data objects for an enterprise management system.

Object Builder project is a generic, language-neutral implementation of the Active Record software design pattern. Given a database, Object Builder tools will extract the schema to a generic form, then transform that schema into application code to manipulate database records.

If the phrase Active Record sounds familiar, but you dont seem to recall it from any of your computer science courses and it doesnt show up anywhere in Erich Gamma et. al.s Design Patterns, its because youve heard it from the Ruby On Rails crowd. According to its proponents Active Record is what makes Ruby on Rails the best thing since buttered toast (to be fair, there are other advantages; a lot of people seem to like to work in Ruby).

Funny thing is, Ive been using this design pattern for several years now, long before I ever heard of Active Record or Ruby on Rails. Not that it makes me special. Thats what design patterns are: a lot of people come up with a similar way of solving the same problem, so somebody sticks a label on it and weve got a new design pattern. The Ruby On Rails people just had the good sense to get their name behind it.

Object Builder is a great way to make sure that your application code is always in synch with your database schema. Because its made of command line tools, its easy to incorporate it into your build process.

If your application only has a couple of tables, Object Builder might be overkill. If you have half a dozen tables or more though, and you make changes from time to time, Object Builder can make your life a lot easier by incorporating those changes into code automatically.

QuickMark is an Amarok script that allows you to set and recall Amaroks current file and position from the context menu.

In the playlist context menu, use the Set Mark entry in the QuickMark menu to create a mark in the players current position. Once set, a mark will appear in the bottom of the QuickMark menu.

Selecting that mark will cause your player to return to the position it was in when the mark was set. If the file you saved the mark in is no longer loaded, it will be added to your current playlist. Use the Clear All Marks entry to clear all marks.

Hyper Estraier is a full-text search system. You can search lots of documents for some documents including specified words.
If you run a web site, it is useful as your own search engine for pages in your site. Also, it is useful as search utilities of mail boxes and file servers.
Main features:
- High performance of search
- High scalability of target documents
- Perfect recall ratio by N-gram method
- Phrase search, attribute search, and similarity search
- Multilingualism with Unicode
- Independent of file format and repository
- Simple and powerful API
- Supporting P2P architecture
Hyper Estraier is an open-source software released under the terms of the GNU Lesser General Public License. It works on Linux, Windows, Mac OS X, and other UNIX-like systems.
Enhancements:
- estraier.c (est_set_ecode): new function.
- estraier.c (est_search_union): scoring of ASIS mode was modified.
- estraier.c (est_resmap_add, est_resmap_dump_keys): new functions.
- estraier.c (est_narrow_scores): efficiency of narrowing index was improved.
- estraier.c (est_utime): new function.
- estraier.c (est_cond_scores, est_cond_set_narrowing_scores): new functions.
- estraier.c (est_rescc_put): a bug of memory leak was fixed.
- estnode.c: the function "est_datum_printf" was replaced by "cbdatumprintf".
- estmaster.c (sendnodecmdsearch): accuracy of hints was improved.
- estfraud.c (sendnodecmdputdoc): accuracy of hints was improved.
- estfraud.c (sendnodecmdputdoc): morphological analyzer support was added.
- estfraud.c (sendnodecmdputdoc): accuracy of hints was improved.
- estwaver.c (runinit, procinit): "-apn", "-acc", "-sv", "-si", "-sa" options was added.
- estscout.c: new file.
- estsupt.c: new file.

coNCePTuaL software is a tool designed to facilitate rapidly generating programs that measure the performance and/or test the correctness of networks and network protocol layers.
coNCePTuaL centers around a simple, domain-specific progamming-language; a few lines of coNCePTuaL code can produce programs that would take significantly more effort to write in a conventional programming language.
One of coNCePTuaLs goals is to raise network benchmarking from an art to a science. To that end, coNCePTuaL programs log not only measurement data but also a wealth of information about the experimental setup, making it easy for someone else to reproduce your performance tests.
Exemple
numreps is "Number of repetitions" and comes from "--reps" or "-r" with default 100.
For numreps repetitions plus 2 warmup repetitions {
task 0 resets its counters then
task 0 sends a 1 megabyte message to task 1 then
task 1 sends a 1 megabyte message to task 0 then
task 0 logs elapsed_usecs/2 as "One-way latency (us)" and
the median of (total_bytes/elapsed_usecs)*1E6/1M as "Bandwidth (MB/s)"
}
The data is stored in an easy-to-parse comma-separated value (CSV) format with the first row of column headers taken right from the program. The second row of headers indicates how the data in each column were aggregated.
Whats important, however, is all of the other information in the log file. coNCePTuaL log files are intended to function as a laboratory notebook, including not only the results of an experiment but also a precise description of the setup that led to those results. How many processors are in my system? How fast are they? What compiler and compiler options were used to compile simple? What command-line parameters were passed to the program? Its all in the log file.
The log files also lists the complete program source code so theres no ambiguity about what was measured. You can look at a coNCePTuaL log file a year in the future and still know exactly what the measurements represent?a lot more useful than a performance test which spits out only 397.2 and requires you to recall what that refers to.
Enhancements:
- pciutils is used (if available) to automatically log the make and model of every network interface that resides on the PCI bus.
- Debian users can now run "make dpkg" from the coNCePTuaL build directory to generate a custom Debian package for their system.