Free your internet connection is not configured properly. please verify your settings in connections software for linux

QoS Connection Tuning HOWTO is a document which explains how to tune network connection performance.

This enables you to get the maximum benefit out of your connection without lag and loss.

Connection Manager allows you to pre-configure all this, and use a single consistant interface to get connected to all of these various systems.
Do you have to log in to a lot of different systems? If you do, odds are that you have to use a variety of methods. You probably have some systems that require ssh and others that only support rdesktop. For some you may have to use vnc. Some may only support telnet. Connection Manager allows you to pre-configure all this, and use a single consistant interface to get connected to all of these various systems.
To install from the source distibution type (you probably will have to be root):
make install
To make rpms for rpm-based ditros type:
make rpm
Main features:
- Command Line Interface - Connection Manager will have a command line interface that allows for easy initiation of any connection. Some users, especially system administrators, will prefer this method of interaction
- Qt/KDE interface - Connection Manager will have a full featured graphical interface based on the Qt and KDE widgets. This interface will allow a user to manage their own connections, as well as maintain all of the various configuration files. You shouldnt have to use a text editor to edit configuration files unless you really want to
- Documentation - Connection Manager will be completely documented, including man pages, a user reference guide, and an administrator reference guide.
- Packaging - every effort will be made to make Connection Manager easy to install. Packages will be provided for a variety of platforms.
- Internationalization - Connection Manager will be designed and built so that it will be easy to add support for different languages.

Internet Chess ToolKit project is a Java library for chess with PGN, FEN, SAN, and ICS (FICS, ICC) support.
Internet Chess ToolKit is a Java-based set of libraries and widgets useful for performing common tasks such as reading SAN (internationalized), FEN, PGN, generating legal moves, and connection to Internet Chess Servers (FICS).
The purpose of the Internet Chess ToolKit is to provide an extensible library to facilitate the development of internet server clients, bots, training programs, peer-to-peer players, and and various other programs useful for the game player. The library was designed with a high level of abstraction and utilization of object oriented design patterns to make it extensible; The model set up should allow for implementations of many games besides Chess, which is the main focus of this library.
Such other games might include chess variants like BugHouse, or completely different games like scrabble and the Chinese game of Go. Another goal of the library is ease of use. A lot of effort has gone into comprehensive documentation and providing sensible names for methods, as well as providing many convenience methods.
Main features:
- FICS support (limited)
- legal move generation.
- game history with variation support (alternative move suggestions).
- move comment support in text and Numeric Annotation Glyphs (NAG).
- Standard Algebraic Notation (SAN) read/write support (internationalized for presentation in 16 languages).
- Portable Game Notation (PGN) read/write support (including move variations, and FEN).
- Forsyth-Edwards Notation (FEN) read/write support.
- True MVC structure with board displays driven by game model events.
- Command-line Board display (GUI to come).
- Well documented. Sample code also provided.
Enhancements:
- Limited FICS support style12, match request, kibitz, whisper, say, tell, channel tell, shout, c/t/-shout, emote, move list, pin, gin, seek ads, seek remove, seek clear, game results
- Timeseal support
- XSLT java code generation for ICS events
- Sample ICS Client
- PGN bugs fixed

BitWise Routing Server allows multiple PCs behind a router to make direct connections.

The BitWise Routing Server allows you to accept BitWise connections to multiple computers behind a router. Typically, using a router, you would set up port forwarding on BitWises client port (4137), and specify a single destination IP. This is fine until multiple users behind a router all need to accept incoming connections.

As shown by the picture at right, the Routing Server allows individual users to register themselves with the Routing Server, and then the Routing Server accepts all incoming connections and directs those connections to the appropriate user.

The Routing Server requires that your physical router support port forwarding with a way to specify different external and internal ports (this is sometimes labeled "UPnP" by many common home routers).

The Routing Server has several options allowing you to customize the Routing Server for your environment. Many of the options are self-explanatory. The two that are not are Listen on Port and IP filtering. IP filtering is explained in the next section.

The BitWise Routing Server listens on a different port than the BitWise IM client. This allows the Routing Server and the IM client to be run on the same computer without causing conflicts. You will want to set up your router (more detail in a later step) to shift the port of the incoming connections from 4137 to another port. It doesnt particularly matter which port you want to use, as long as it is not a port used by another program. The default port is 4200.

Depending on the complexity of the network, it may be desirable to filter the IP addresses that are allowed to register with the Routing Server. This can be done in the preferences. One very likely scenario would be limiting registrations to the 192.168.1.x IP addresses (192.168 is reserved for local networks). When specifying an IP as the comparison address, you can use any valid IP numbers for wildcards.

In the case shown here, the Routing Server will limit connections to computers having IP addresses of 192.168.1.x. Any number, 0 through 255, could be placed for x in the Routing Server preferences.

If you are not familiar with IP address classes and IP filtering, it will usually be safe to leave Any selected.

Setting up the physical router

The picture at right was taken from a Linksys router, other routers will have a similar capability, although it may be layed out differently. On some routers, the advanced port forwarding options are mistakingly labeled UPnP.

The router setup shows that we are accepting connections on port 4137 and then sending them inside the network on port 4200 (the default port). Enter the IP address of the machine on the network running the Routing Server, and make sure that the rule is enabled. You will want to enter a rule for both TCP and UDP (UDP is used only for voice).

Please consult your router manual for more detailed instructions about how to set up port forwarding on your specific model.

Configuring BitWise to use the Routing Server

In order for you to enjoy the connectivity benefits of the Routing Server, you will need to register with the Routing Server when you log in to BitWise. Prior to logging in to BitWise, click the Setup button next to the Connect button to open the BitWise Setup. There is an area to enter an address for the Routing Server, and to specify what port to use. The port must be the same as the port used above (4200 is the default).

Upon connecting to BitWise, you will be registered with the Routing Server. If you could not be registered, an error message will be displayed. Double-check that the correct address was entered in the Setup.

Registration with the Routing Server

Upon successfully registering with the Routing Server, the Routing Server will display the user name and the IP address of the registration. If you want to unregister a user, click on the username, and then click Unregister. Incoming connections will no longer be forwarded to the specified computer.

It is worth pointing out two things here. First, if you later log in from a different computer, and that computer is also set to use the Routing Server, you will be re-registered with your new IP address. Second, if you are unregistered, or move to another computer but are not set up to use the Routing Server, you will not be able to benefit from the services of the Routing Server.
By default, the Routing Server saves the registered user list when it is closed down.

Using the Routing Server

Assuming that everything is set up correctly, everyone that registers with the Routing Server when they log in to BitWise will be able to enjoy significantly increased connectivity with other BitWise users. As incoming connections are established, you will see the connections listed in the right pane of the Routing Server window. The IP address and the time of the connection is also displayed, and the connection is later marked when it is disconnected.

The disconnected/closed connections may be cleaned from the list at any time using the Clean List button. Only active connections will be left displayed.

SYNOPSIS

# client connection:
my $c = new Jabber::Connection(
server => jabber.org,
log => 1,
);

# component connection:
# my $c = new Jabber::Connection(
# server => localhost:5700,
# localname => comp.localhost,
# ns => jabber:component:accept,
# log => 1,
# debug => 1,
# );

die "oops: ".$c->lastError unless $c->connect();

$c->register_beat(10, &every_10_seconds);

$c->register_handler(presence,&presence);
$c->register_handler(iq,&handle_iq_conference);
$c->register_handler(iq,&handle_iq_browse);

$c->auth(qmacro,password,myresource); # client auth
# $c->auth(secret); # component auth

$c->send( );

$c->start;
DESCRIPTION ^
The Jabber::Connection package provides basic functions for connecting clients and components to a Jabber server.

Linux on the WRT54G is a mini-distribution for the router and access point Linksys wrt54g 802.11b/g

It includes basic tools such as sh, syslog, telnetd, httpd (with cgi-bin support), vi, snort, mount, insmod, rmmod, top, grep, find, nfs modules, etc.

The installation script runs in about 20 seconds and installs strictly to the RAM disk. If you mess anything up, simply reset the box.

After installing the distribution youll be able to telnet in, add Web pages, change iptable rules, change routing, configure snort, etc.

Quick Install:

Modify the IP and password in wrt54g.sh and run it. For more
information, See README, and the details in wrt54g.sh.

Make sure that the WAN port on the box is configured. To verify that your box
is set up properly, test the stanard Linksys ping diagostic. If you can "ping"
something on the Internet using this screen, you should be good to go.