Free terminal server connections software for linux

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.

Net::FreeDB2::Connection is a FreeDB/CDDB abstract connection class.

Net::FreeDB2::Connection is an abstract class to represent connections to FreeDB/CDDB servers. After a successfull connection, FreeDB/CDDB queries, reads etc can be made to obtain/provide information from/to FreeDB/CDDB databases.

CONSTRUCTOR

new (OPT_HASH_REF)

Creates a new Net::FreeDB2::Connection object. By default connect () is called to initiate the connection but see option no_connect. See the implementation for complements/restrictions.

Options for OPT_HASH_REF may include:

client_name

Mandatory option to name the connecting client software.

client_version

Mandatory option with the client software version string.

client_host

The hostname of the client. Defaults to &Sys::Hostname::hostname ().

client_user

The user of the client. Defaults to scalar (getpwuid ($>));

freedb_host

The FreeDB/CDDB host. Defaults to freedb.freedb.org.

freedb_port

The port on the FreeDB/CDDB host.

proxy_host

Proxy host.

proxy_port

Port on the proxy host. Defaults to 8080.

proxy_user

Proxy user name to use.

proxy_passwd

Proxy password to use.

no_connect

Do not call connect () during instanciation.

S-terminal lets you create a secure X terminal over an ecrypted tunnel.

Regular X terminals pass unencrypted data between you the remote machine.

S-terminal creates an encrypted tunnel through which all X traffic passes.

It replaces the remote xdm login screen with a local application that collects username and password, then sets up an ssh tunnel to the remote host and starts a session.

It is highly configurable both in appearance and behavior, and deployed S-terminals can be remotely administered.

S-terminal was developed to run under Knoppix, but it should be portable to most Linux systems. With minor changes, it should work on any Unix-like system that has X, perl, tcl/tk and expect installed.

Best of all, it can be added to a KNOPPIX CD to create an instant, bootable, secure X terminal CD.

Gnome Terminal Launcher applet reads the profiles from GConf and creates the corresponding menu entry to invoke the gnome-terminal command and its arguments.

If you are a system administrator, perhaps a command line junkie, and you deal with a large number of servers on a daily basis, you may have already created profiles to define the connection characteristics of each server.

Ive also experienced an improvement in usability assigning a different color and icon to a server or group of servers. After a while, you can quicly identify which server are you connected to with just a glimpse of the screen.

But this has a drawback, the only way to open a terminal is from another terminal unless youve already created launchers for the specific profiles.

To provide a cleaner solution. Ive create the gnome-terminal-launcher applet that reads the profiles from GConf and creates the corresponding menu entry to invoke the gnome-terminal command and its arguments.

The NoMachine NX Web Companion is a small Java applet and a plugin interface that links the availability of the Web to the unmatched power of NX.

NoMachine NX is a fast terminal server system based on the X11 protocol. In addition, NX also translates and embeds the MS Windows Terminal Server and VNC protocols into X/NX. NX is an order of magnitude faster than VNC or X11 and can run on bandwidth as narrow as 10 kBit/sec.

By embedding RDP and RFB, it enables users to compress and accelerate remote Windows and VNC sessions. NX lets you work fluently even across slow links like modems.

The NX project provides a suite of libraries and X11 proxying agents implementing efficient compression and optimized transport of X11, SMB, IPP, HTTP, and arbitrary protocols like audio over the Internet.