A loopback connection is used to connect two processes whose interface relies on network communications. For instance, this could be two application processes, or a device simulator and a device handler. Loopback connections are generally used in development and test environments, but can also be found in production environments.

Until now, this generally meant that you would connect these two processes by using two physical communications ports, cables and a hardware modem eliminator.

The problems with a conventional hardware loopback connection are:

- Throughput limitations of communications ports or modem eliminators;
- Physical communications ports may not be available;
- A modem eliminator may not be available;
- A Change Request may be required to schedule the installation and configuration of such a connection; adding to delays and pressure on resources.

ComNet now offers the capability to do this entirely in its own software.

In fact, ComNet goes further than simple loopback connections. ComNet can also perform protocol conversion between each end of the loopback. ComNet provides a loopback capability which eliminates all of these difficulties because:

- Physical throughput limitations of a hardware loopback are eliminated;
- No physical communications ports are required;
- No hardware modem eliminator is required;
- Configuration can be easily performed by the end user in a matter of minutes.

A useful application of the loopback capability is in stress testing. Typically, stress tests have been restricted to the number of available physical communications ports, modem eliminators and the available bandwidth. ComNet removes all of these restrictions.

Note: ComNet provides loopback connections without using any other software; i.e. it does not even require communications Access Method software.

Click here for more information on how ComNet can enhance your test environment.