Free outer software for linux

IGE - Outer Space is an on-line strategy game with SciFi theme.

IGE - Outer Space is an on-line strategy game which takes place in the dangerous universe. You must become the commander of many stars, planets, and great fleets and you will struggle for survival with other commanders.

Outer Space communicates with the server in the same way as your browser, but you will need a special client to play it. Using this client you can create an account on the server and you can start to explore the world of the Outer Space.

SQL::Routine is a Perl module to specify all database tasks with SQL routines.

SYNOPSIS

This executable code example shows how to define some simple database tasks with SQL::Routine; it only shows a tiny fraction of what the module is capable of, since more advanced features are not shown for brevity.

use SQL::Routine;

eval {
# Create a model/container in which all SQL details are to be stored.
# The two boolean options being set true here permit all the subsequent code to be as concise,
# easy to read, and most SQL-string-like as possible, at the cost of being slower to execute.
my $model = SQL::Routine->new_container();
$model->auto_set_node_ids( 1 );
$model->may_match_surrogate_node_ids( 1 );

# This defines 4 scalar/column/field data types (1 number, 2 char strings, 1 enumerated value type)
# and 2 row/table data types; the former are atomic and the latter are composite.
# The former can describe individual columns of a base table (table) or viewed table (view),
# while the latter can describe an entire table or view.
# Any of these can describe a domain schema object or a stored procedures variables data type.
# See also the person and person_with_parents table+view defs further below; these data types help describe them.
$model->build_child_node_trees( [
[ scalar_data_type, { si_name => entity_id , base_type => NUM_INT , num_precision => 9, }, ],
[ scalar_data_type, { si_name => alt_id , base_type => STR_CHAR, max_chars => 20, char_enc => UTF8, }, ],
[ scalar_data_type, { si_name => person_name, base_type => STR_CHAR, max_chars => 100, char_enc => UTF8, }, ],
[ scalar_data_type, { si_name => person_sex , base_type => STR_CHAR, max_chars => 1, char_enc => UTF8, }, [
[ scalar_data_type_opt, M, ],
[ scalar_data_type_opt, F, ],
], ],
[ row_data_type, person, [
[ row_data_type_field, { si_name => person_id , scalar_data_type => entity_id , }, ],
[ row_data_type_field, { si_name => alternate_id, scalar_data_type => alt_id , }, ],
[ row_data_type_field, { si_name => name , scalar_data_type => person_name, }, ],
[ row_data_type_field, { si_name => sex , scalar_data_type => person_sex , }, ],
[ row_data_type_field, { si_name => father_id , scalar_data_type => entity_id , }, ],
[ row_data_type_field, { si_name => mother_id , scalar_data_type => entity_id , }, ],
], ],
[ row_data_type, person_with_parents, [
[ row_data_type_field, { si_name => self_id , scalar_data_type => entity_id , }, ],
[ row_data_type_field, { si_name => self_name , scalar_data_type => person_name, }, ],
[ row_data_type_field, { si_name => father_id , scalar_data_type => entity_id , }, ],
[ row_data_type_field, { si_name => father_name, scalar_data_type => person_name, }, ],
[ row_data_type_field, { si_name => mother_id , scalar_data_type => entity_id , }, ],
[ row_data_type_field, { si_name => mother_name, scalar_data_type => person_name, }, ],
], ],
] );

# This defines the blueprint of a database catalog that contains a single schema and a single virtual user which owns the schema.
my $catalog_bp = $model->build_child_node_tree( catalog, Gene Database, [
[ owner, Lord of the Root, ],
[ schema, { si_name => Gene Schema, owner => Lord of the Root, }, ],
] );
my $schema = $catalog_bp->find_child_node_by_surrogate_id( Gene Schema );

# This defines a base table (table) schema object that lives in the aforementioned database catalog.
# It contains 6 columns, including a not-null primary key (having a trivial sequence generator to give it
# default values), another not-null field, a surrogate key, and 2 self-referencing foreign keys.
# Each row represents a single person, for each storing up to 2 unique identifiers, name, sex, and the parents unique ids.
my $tb_person = $schema->build_child_node_tree( table, { si_name => person, row_data_type => person, }, [
[ table_field, { si_row_field => person_id, mandatory => 1, default_val => 1, auto_inc => 1, }, ],
[ table_field, { si_row_field => name , mandatory => 1, }, ],
[ table_index, { si_name => primary , index_type => UNIQUE, }, [
[ table_index_field, person_id, ],
], ],
[ table_index, { si_name => ak_alternate_id, index_type => UNIQUE, }, [
[ table_index_field, alternate_id, ],
], ],
[ table_index, { si_name => fk_father, index_type => FOREIGN, f_table => person, }, [
[ table_index_field, { si_field => father_id, f_field => person_id } ],
], ],
[ table_index, { si_name => fk_mother, index_type => FOREIGN, f_table => person, }, [
[ table_index_field, { si_field => mother_id, f_field => person_id } ],
], ],
] );

# This defines a viewed table (view) schema object that lives in the aforementioned database catalog.
# It left-outer-joins the person table to itself twice and returns 2 columns from each constituent, for 6 total.
# Each row gives the unique id and name each for 3 people, a given person and that persons 2 parents.
my $vw_pwp = $schema->build_child_node_tree( view, { si_name => person_with_parents,
view_type => JOINED, row_data_type => person_with_parents, }, [
( map { [ view_src, { si_name => $_, match => person, }, [
map { [ view_src_field, $_, ], } ( person_id, name, father_id, mother_id, ),
], ], } (self) ),
( map { [ view_src, { si_name => $_, match => person, }, [
map { [ view_src_field, $_, ], } ( person_id, name, ),
], ], } ( father, mother, ) ),
[ view_field, { si_row_field => self_id , src_field => [person_id,self ], }, ],
[ view_field, { si_row_field => self_name , src_field => [name ,self ], }, ],
[ view_field, { si_row_field => father_id , src_field => [person_id,father], }, ],
[ view_field, { si_row_field => father_name, src_field => [name ,father], }, ],
[ view_field, { si_row_field => mother_id , src_field => [person_id,mother], }, ],
[ view_field, { si_row_field => mother_name, src_field => [name ,mother], }, ],
[ view_join, { lhs_src => self, rhs_src => father, join_op => LEFT, }, [
[ view_join_field, { lhs_src_field => father_id, rhs_src_field => person_id } ],
], ],
[ view_join, { lhs_src => self, rhs_src => mother, join_op => LEFT, }, [
[ view_join_field, { lhs_src_field => mother_id, rhs_src_field => person_id } ],
], ],
] );

# This defines the blueprint of an application that has a single virtual connection descriptor to the above database.
my $application_bp = $model->build_child_node_tree( application, Gene App, [
[ catalog_link, { si_name => editor_link, target => $catalog_bp, }, ],
] );

# This defines another scalar data type, which is used by some routines that follow below.
my $sdt_login_auth = $model->build_child_node( scalar_data_type, { si_name => login_auth,
base_type => STR_CHAR, max_chars => 20, char_enc => UTF8, } );

# This defines an application-side routine/function that connects to the Gene Database, fetches all
# the records from the person_with_parents view, disconnects the database, and returns the fetched records.
# It takes run-time arguments for a user login name and password that are used when connecting.
my $rt_fetch_pwp = $application_bp->build_child_node_tree( routine, { si_name => fetch_pwp,
routine_type => FUNCTION, return_cont_type => RW_ARY, return_row_data_type => person_with_parents, }, [
[ routine_arg, { si_name => login_name, cont_type => SCALAR, scalar_data_type => $sdt_login_auth }, ],
[ routine_arg, { si_name => login_pass, cont_type => SCALAR, scalar_data_type => $sdt_login_auth }, ],
[ routine_var, { si_name => conn_cx, cont_type => CONN, conn_link => editor_link, }, ],
[ routine_stmt, { call_sroutine => CATALOG_OPEN, }, [
[ routine_expr, { call_sroutine_cxt => CONN_CX, cont_type => CONN, valf_p_routine_item => conn_cx, }, ],
[ routine_expr, { call_sroutine_arg => LOGIN_NAME, cont_type => SCALAR, valf_p_routine_item => login_name, }, ],
[ routine_expr, { call_sroutine_arg => LOGIN_PASS, cont_type => SCALAR, valf_p_routine_item => login_pass, }, ],
], ],
[ routine_var, { si_name => pwp_ary, cont_type => RW_ARY, row_data_type => person_with_parents, }, ],
[ routine_stmt, { call_sroutine => SELECT, }, [
[ view, { si_name => query_pwp, view_type => ALIAS, row_data_type => person_with_parents, }, [
[ view_src, { si_name => s, match => $vw_pwp, }, ],
], ],
[ routine_expr, { call_sroutine_cxt => CONN_CX, cont_type => CONN, valf_p_routine_item => conn_cx, }, ],
[ routine_expr, { call_sroutine_arg => SELECT_DEFN, cont_type => SRT_NODE, act_on => query_pwp, }, ],
[ routine_expr, { call_sroutine_arg => INTO, query_dest => pwp_ary, cont_type => RW_ARY, }, ],
], ],
[ routine_stmt, { call_sroutine => CATALOG_CLOSE, }, [
[ routine_expr, { call_sroutine_cxt => CONN_CX, cont_type => CONN, valf_p_routine_item, conn_cx, }, ],
], ],
[ routine_stmt, { call_sroutine => RETURN, }, [
[ routine_expr, { call_sroutine_arg => RETURN_VALUE, cont_type => RW_ARY, valf_p_routine_item => pwp_ary, }, ],
], ],
] );

# This defines an application-side routine/procedure that inserts a set of records, given in an argument,
# into the person table. It takes an already opened db connection handle to operate through as a
# context argument (which would represent the invocant if this routine was wrapped in an object-oriented interface).
my $rt_add_people = $application_bp->build_child_node_tree( routine, { si_name => add_people, routine_type => PROCEDURE, }, [
[ routine_context, { si_name => conn_cx, cont_type => CONN, conn_link => editor_link, }, ],
[ routine_arg, { si_name => person_ary, cont_type => RW_ARY, row_data_type => person, }, ],
[ routine_stmt, { call_sroutine => INSERT, }, [
[ view, { si_name => insert_people, view_type => INSERT, row_data_type => person, ins_p_routine_item => person_ary, }, [
[ view_src, { si_name => s, match => $tb_person, }, ],
], ],
[ routine_expr, { call_sroutine_cxt => CONN_CX, cont_type => CONN, valf_p_routine_item => conn_cx, }, ],
[ routine_expr, { call_sroutine_arg => INSERT_DEFN, cont_type => SRT_NODE, act_on => insert_people, }, ],
], ],
] );

# This defines an application-side routine/function that fetches one record
# from the person table which matches its argument.
my $rt_get_person = $application_bp->build_child_node_tree( routine, { si_name => get_person,
routine_type => FUNCTION, return_cont_type => ROW, return_row_data_type => person, }, [
[ routine_context, { si_name => conn_cx, cont_type => CONN, conn_link => editor_link, }, ],
[ routine_arg, { si_name => arg_person_id, cont_type => SCALAR, scalar_data_type => entity_id, }, ],
[ routine_var, { si_name => person_row, cont_type => ROW, row_data_type => person, }, ],
[ routine_stmt, { call_sroutine => SELECT, }, [
[ view, { si_name => query_person, view_type => JOINED, row_data_type => person, }, [
[ view_src, { si_name => s, match => $tb_person, }, [
[ view_src_field, person_id, ],
], ],
[ view_expr, { view_part => WHERE, cont_type => SCALAR, valf_call_sroutine => EQ, }, [
[ view_expr, { call_sroutine_arg => LHS, cont_type => SCALAR, valf_src_field => person_id, }, ],
[ view_expr, { call_sroutine_arg => RHS, cont_type => SCALAR, valf_p_routine_item => arg_person_id, }, ],
], ],
], ],
[ routine_expr, { call_sroutine_cxt => CONN_CX, cont_type => CONN, valf_p_routine_item => conn_cx, }, ],
[ routine_expr, { call_sroutine_arg => SELECT_DEFN, cont_type => SRT_NODE, act_on => query_person, }, ],
[ routine_expr, { call_sroutine_arg => INTO, query_dest => person_row, cont_type => RW_ARY, }, ],
], ],
[ routine_stmt, { call_sroutine => RETURN, }, [
[ routine_expr, { call_sroutine_arg => RETURN_VALUE, cont_type => ROW, valf_p_routine_item => person_row, }, ],
], ],
] );

# This defines 6 database engine descriptors and 2 database bridge descriptors that we may be using.
# These details can help external code determine such things as what string-SQL flavors should be
# generated from the model, as well as which database features can be used natively or have to be emulated.
# The si_name has no meaning to code and is for users; the other attribute values should have meaning to said external code.
$model->build_child_node_trees( [
[ data_storage_product, { si_name => SQLite v3.2 , product_code => SQLite_3_2 , is_file_based => 1, }, ],
[ data_storage_product, { si_name => MySQL v5.0 , product_code => MySQL_5_0 , is_network_svc => 1, }, ],
[ data_storage_product, { si_name => PostgreSQL v8, product_code => PostgreSQL_8, is_network_svc => 1, }, ],
[ data_storage_product, { si_name => Oracle v10g , product_code => Oracle_10_g , is_network_svc => 1, }, ],
[ data_storage_product, { si_name => Sybase , product_code => Sybase , is_network_svc => 1, }, ],
[ data_storage_product, { si_name => CSV , product_code => CSV , is_file_based => 1, }, ],
[ data_link_product, { si_name => Microsoft ODBC v3, product_code => ODBC_3, }, ],
[ data_link_product, { si_name => Oracle OCI*8, product_code => OCI_8, }, ],
[ data_link_product, { si_name => Generic Rosetta Engine, product_code => Rosetta::Engine::Generic, }, ],
] );

# This defines one concrete instance each of the database catalog and an application using it.
# This concrete database instance includes two concrete user definitions, one that can owns
# the schema and one that can only edit data. The concrete application instance includes
# a concrete connection descriptor going to this concrete database instance.
# Note that user descriptions are only stored in a SQL::Routine model when that model is being used to create
# database catalogs and/or create or modify database users; otherwise user should not be kept for security sake.
$model->build_child_node_trees( [
[ catalog_instance, { si_name => test, blueprint => $catalog_bp, product => PostgreSQL v8, }, [
[ user, { si_name => ronsealy, user_type => SCHEMA_OWNER, match_owner => Lord of the Root, password => K34dsD, }, ],
[ user, { si_name => joesmith, user_type => DATA_EDITOR, password => fdsKJ4, }, ],
], ],
[ application_instance, { si_name => test app, blueprint => $application_bp, }, [
[ catalog_link_instance, { blueprint => editor_link, product => Microsoft ODBC v3, target => test, local_dsn => keep_it, }, ],
], ],
] );

# This defines another concrete instance each of the database catalog and an application using it.
$model->build_child_node_trees( [
[ catalog_instance, { si_name => production, blueprint => $catalog_bp, product => Oracle v10g, }, [
[ user, { si_name => florence, user_type => SCHEMA_OWNER, match_owner => Lord of the Root, password => 0sfs8G, }, ],
[ user, { si_name => thainuff, user_type => DATA_EDITOR, password => 9340sd, }, ],
], ],
[ application_instance, { si_name => production app, blueprint => $application_bp, }, [
[ catalog_link_instance, { blueprint => editor_link, product => Oracle OCI*8, target => production, local_dsn => ship_it, }, ],
], ],
] );

# This defines a third concrete instance each of the database catalog and an application using it.
$model->build_child_node_trees( [
[ catalog_instance, { si_name => laptop demo, blueprint => $catalog_bp, product => SQLite v3.2, file_path => Move It, }, ],
[ application_instance, { si_name => laptop demo app, blueprint => $application_bp, }, [
[ catalog_link_instance, { blueprint => editor_link, product => Generic Rosetta Engine, target => laptop demo, }, ],
], ],
] );

# This line will run some correctness tests on the model that were not done
# when the model was being populated for execution speed efficiency.
$model->assert_deferrable_constraints();

# This line will dump the contents of the model in pretty-printed XML format.
# It can be helpful when debugging your programs that use SQL::Routine.
print $model->get_all_properties_as_xml_str( 1 );
};
$@ and print error_to_string($@);

# SQL::Routine throws object exceptions when it encounters bad input; this function
# will convert those into human readable text for display by the try/catch block.
sub error_to_string {
my ($message) = @_;
if (ref $message and UNIVERSAL::isa( $message, Locale::KeyedText::Message )) {
my $translator = Locale::KeyedText->new_translator( [SQL::Routine::L::], [en] );
my $user_text = $translator->translate_message( $message );
return q{internal error: cant find user text for a message: }
. $message->as_string() . . $translator->as_string();
if !$user_text;
return $user_text;
}
return $message; # if this isnt the right kind of object
}

Note that one key feature of SQL::Routine is that all of a models pieces are linked by references rather than by name as in SQL itself. For example, the name of the person table is only stored once internally; if, after executing all of the above code, you were to run "$tb_person->set_attribute( si_name, The Huddled Masses );", then all of the other parts of the model that referred to the table would not break, and an XML dump would show that all the references now say The Huddled Masses.

For some more (older) examples of SQL::Routine in use, see its test suite code.

Scum of the Universe is a space trading game that combines two genres: arcade and strategy. On one side, its a classic vertical-scrolling space shooter game. On the other side, it is an adventure and strategy. You should choose whether youll be an independent space trader, firearms smuggler, fierce freedom-fighter or something in between.

Following the main storyline, you go through the galaxy from one planet to another. Space travel requires fuel, so you need to keep earning money to buy it. You can also buy various upgrades for your spaceship and weapons that affect the arcade part of the game. The storyline itself is not linear. There are also some points where youll need to make decisions that will determine your destiny.

For thousands of years, people of planet Xen have colonized the planets in their galaxy. As time went by, many colonies grew unhappy about their status, as everything was controlled by Xen. Some of them organized military units and declared independence. You can see the status of each planet by "Rebel Sentiment" indicator. Planets with RS higher than 50% are ruled by the Rebel government, and Rebel laws apply.

Trading firearms is legal on planets ruled by Rebels, as they need as much firepower as they can get. On the other hand, Empire forbid all the trading with firearms and other ground weaponry as they wish to maintain their military advantage. One of the ways to make a lot of money is to buy cheap guns at Empire planets and sell them for a lot of money on Rebel planets where demand is extremely high. But be careful as youll need to fight Empire fleet once they find out youre a smuggler.

Beside the raging war between Xen Empire and the rebels there is increased activity of alien species, who destroy human ships. The stronger alien activity, the more waves of alien ships youll need to defeat in each planets outer orbit. Some of the aliens you destroy may drop artifacts (big blue ones) which you can sell at any space station for 20credits a piece.

tvmet is a Vector and Matrix template library that uses Meta Templates and Expression Templates (ET) to evaluate results at compile time, thus making it fast for low-end systems.
Temporaries are avoided because of this. The produced code is similar to hand-coded code, but the quality of the code still depends on the compiler and its version. The dimensions for vectors and matrices are static and bounded at compile time using template arguments.
Main features:
- Matrices and Vectors with fixed sizes (of course), the data is stored in a static array.
- compile time dimension check for Vectors and Matrices to preserve the mathematical meaning.
- vector, matrix, matrix-matrix and matrix-vector fast operations:
- complete set of standard arithmetic operations for Vectors and Matrices (blitz++ supports this only for TinyVector).
- complete set of standard compare operations for Vectors and Matrices as well as ternary functions like a ? b : c (see eval for use).
- binary and unary operations.
- meta template use for Matrix-Matrix-Product $M,M$, Matrix-Transpose $M^T$ and Matrix-Vector-Product $M,x$ functions and operators.
- meta template for special functions like $M^T, x$, $M^T,M$, $M,M^T$ and $(M,M)^T$ functions, see ... special Meta-Template Functions.
- simple Matrix rows and column access as a Vector.
- chaining of matrix and vector expressions is possible and working.
- Vector inner and outer product (dot and cross product).
- special handling for the aliasing problem - see ... about aliasing.
- STL iterator interface. This opens the door to all sorts of great STL applications.
- type promotion (for handling Matrices and Vectors of differing types).
- works on self defined types such as the std::complex type.
- makes no use of exceptions. Therefore you can use it for embedded systems or in Linux kernel space.
- nice expression level printing for debugging purposes (print the expanded expression tree).
- good documentation with examples.
- regression tests for nearly all operations and functions.
- support for several compilers (see Compiler Support).
- written as a pure class and template library, no binary libraries and versioning are needed - designed to avoid code blot due to the use of templates.
- ISO/IEC 14882:1998 compliant.

Ticket-IT is a tool for the creation, management, and accompaniment of tickets.
Ticket-IT is a tool directed towards companies that need a better integration and distribution of informantion about service to customers, support, development of products, callcenter, etc, among its several departments.
Ticket-IT has resource of easy utilization, concentration display and distribution of information, making possible its total adaptation to most distintc institutes and applications, being a perfect tool to HelpDesk, CallCenter and online support.
Main features:
Control and management of access
- User registration;
- Group registration;
- Access permission and actions based in group;
- Schedule of events;
- Users profile, top-configured;
Integration among sectors/departments
- Control of context categories, making possible the organization and cataloging of calls (tickets) being made or already made;
- Assign of users group per categories;
- Forwarding ticket to outer users that will be able to display calls and post comments;
- Partial or total ticket forwarding, making possible to manage information and function of the contributors of your company;
Information distribution
- Alerts via e-mail about create, opening, proceeding, close and re-opening or comments of tickets to those involved in categories;
- Main display of personal tickets, or collaborating, getting fast access to tickets, making service easier;
- Exchanging information based in a simple fulfilling of information, which due to Ticket-IT utomation, distribute it to those involved in the process;
- Protocol forwarding to outer agent access (customers, reps, etc) without the necessity of user and password;;
Enhancements:
- This release implements a Web installer and an option for personalization of the feedback message.
- The item "User of Companies" has already been implemented, along with its existing resources.
- A mask was applied (ticket comments and feedback) for guest users, so they will see the groups name instead of the users name in comments.
- Some minor bugs have been fixed.
- The gettext internationalization schema has been finished.
- The English (US) translation is done.
- There are some visual improvements.

Intellidiscs is a Remake of Tron: Deadly Discs for the classic Intellivision console. Its also one of the few, if not the first, Tron freeware games that has nothing to do with light-cycles.

Basically, you run around in an arena fighting off bad guys with your disc. There are four different varieties of bad guy, and one of them has three different varieties of disc. More difficult enemies appear as your score increases, with the most difficult showing up if you can reach 1,000,000 points.

Bad guys enter through doors on the sides of the arena. You can jam these doors open by either hitting them with your disc, or by running into them. If you jam open doors that are opposite each other, you can run in one side and come out the other. This is very important to your survival.

If you jam enough doors, eventually a recognizer will be dispatched to fix them. If you can hit the recognizer when its eye is open, it will stop fixing the doors and leave the arena. Plus, you get lots of points for this.

You can take three hits before you die, and every hit makes you slower! You will eventually recover from damage, regaining your speed as well. Touching the recognizer kills you instantly, so dont do it.

Default controls are the familiar WASD to move, and the outer keys of numpad (1, 2, 3, 4, 6, 7, 8, 9, non-Mac users turn Num Lock on!) throw your disc in any of eight directions. If you press one of the throw keys while your disc is in flight, it will return to you. Discs are harmless when returning. If you move away from your disc as it is flying back, it will never catch up to you, you must stop and catch it. All of the controls can be changed from the main menu.

tcpproxy project is a proxy (or tunnel or redirector) for TCP/IP protocols. In standalone mode it waits for incoming connections forwarding them to another machine or starting a local server program.
Several programs with this function or something similiar are around. However, tcpproxys design goal was to let it operate on some kind of firewall.
Main features:
- Extensive logging to syslog,
- Interface based configuration,
- can bind to a particular interface on a multi-homed host,
- sets environment variables before calling a local server program,
- support for external access control programs,
- can be started from inetd or run in standalone mode.
tcpproxy was created with a transparent TCP proxy in mind. When its used to start local server programs (e.g. an FTP server) it can however also work as "port multiplexer" since it requires different configurations for different interfaces (there are no defaults).
Interface based configuration
tcpproxys services are always bound to a certain interface. Suppose you have a multi-homed host (e.g. a firewall) with the IP numbers 192.168.0.1 (part of your LAN) and 10.11.12.13 (connected to the Internet). The configuration
port 119
interface 192.168.0.1
server news.provider.com
forwards then any connection made to your local interface on the NNTP port to the machine news.provider.com. The providers news server appears now to run on your firewall. Furthermore, if you for each port only a single interface where you want to have tcpproxys service, tcpproxy will not even bind to the others. For the example above this means that someone trying to connect to your external interface would only see a closed port.
Now suppose you want to use a second NNTP server from your LAN. You would first configure a second IP number on your internal interface, e.g. 192.168.0.2 and then reconfigure tcpproxy:
port 119
interface 192.168.0.1
server news.provider.com
interface 192.168.0.2
server news.freshmeat.com
Depending on the incoming interface of a client request the connection is forwarded to one of the servers.
In this case the firewalls external interface is opened on port 119 and a port scan would show that theres some kind of service. If however someone connects to the outer interface the connection is immediatly dropped, simply because tcpproxy isnt configured to handle request on the interface 10.11.12.13 and tcpproxy doesnt accept service defaults.
If you like you can extend this configuration to
port 119
interface 192.168.0.1
server news.provider.com
interface 192.168.0.2
server news.freshmeat.com
interface 10.11.12.13
exec /bin/date
for the scanners amusement. But you might also want to write a message to your systems syslog.
Access control
tcpproxy implements access control by calling external, user provided, script, the so called "access control programs" (or in short: acps). I implemented them because I wanted to be able to deny service usage based on anything I like, not just on the clients IP number or its name.