This Speed Touch User Guide provides you with both basic configuration information and more advanced networking concepts.

• Read and understand all instructions

  Follow all warnings and instructions marked on the product.

• Cleaning

  Unplug this product from the wall outlet before cleaning. Do not use liquid cleaners or aerosol cleaners. Use a damp cloth for cleaning.

• Water and moisture

  Do not use this product near water, for example, near a bathtub, wash bowl, kitchen sink, laundry tub, in a wet basement or near a swimming pool.

• Power sources

  This product should be operated only from the type of power source indicated on the marking labels. If you are not sure of the type of power supply to your home, consult your product dealer or local power company.

• Power cord protection

  Do not allow anything to rest on the power cord. Do not locate this product where the cord will be subject to persons walking on it.

• Overloading

  Do not overload wall (mains) outlets and extension cords as this can result in the risk of fire or electric shock.

• Servicing

  To reduce the risk of electric shock, do not disassemble this product, but take it to a qualified serviceman when service or repair work is required. Opening or removing covers may expose you to dangerous voltages or other risks. Incorrect reassembly can cause electric shock when the appliance is subsequently used.

• Damage requiring service

  Unplug this product from the wall outlet and refer servicing to qualified service personnel under the following conditions:

  • When the power supply cord or plug is damaged or frayed;
  • If liquid has been spilled into the product;
  • If the product has been exposed to rain or water;
  • If the product does not operate normally by following the operating instructions;
  • If the product has been dropped or damaged in any way;
  • If the product exhibits a distinct change in performance.
• Modem/Telephone use

  Avoid using a modem/telephone (other than a cordless type) during an electrical storm. There may be a remote risk of electric shock from lightning.

  Do not use the telephone to report a gas leak in the vicinity of the leak.

SAVE THESE INSTRUCTIONS!

Only qualified service personnel may access the interior of the unit. None of its parts are user-replaceable; therefore, no reason exists for user access.

The Speed Touch equipment is not intended to be connected to an IT-type power system.

The Speed Touch equipment is intended for in-house stationary use, desktop or wall-mounted.

The Speed Touch equipment must not be mounted in a location exposed to solar and/or heat radiation.

The Speed Touch equipment must not be exposed to heat trap conditions and must not be subjected to water or condensation.

If normal phone service is required on the same line, a splitter must be installed.

Installation of the cable between the Speed Touch modem and the splitter must be carried out by qualified service personnel.

The mains socket outlet must be near the equipment and easily accessible.

The Speed Touch equipment must be installed in a Pollution Degree 2 environment.

Before installing the Speed Touch, you need to visually inspect it for damage that might have occurred during shipment. Make sure the box package contains all of the components listed below:

• The Speed Touch (*);
• Power supply adapter with 2m (6.56ft) connecting cable;
• 2m Ethernet/ATMF straight-through cable (RJ45/RJ45);
• 2m RJ14/RJ14 cable;
• User guide.

In case your Speed Touch or any other item listed above is damaged or missing, contact the organization you obtained the Speed Touch from and ask for further instructions.

The Speed Touch requires the following hardware and system configuration :

Generic

• A telephone line that supports the ADSL service;
• Information on which protocols are supported at the remote end of the connections;
• For Internet Access via an ISP or Corporate location access, a user account i.e. User ID and Password;

  Additional User IDs and Passwords might be required for access to specific servers.

Ethernet

• A PC/Workstation with an Ethernet 10Base-T PC-NIC installed;
• for local networking, a 10BaseT HUB and the necessary connection cables.

ATMF-25

• A PC/Workstation with an ATMF-25 PC-NIC installed;
• for advanced networks a workgroup ATM switch supporting ATMF-25 interfaces.

Operating System

• When the Speed Touch is used in Bridging mode, it does not put any requirements on the OS, all you need is an Ethernet PC-NIC
• When the Speed Touch is used in PPP-to-PPTP Relay mode, the OS must support local tunneling based on the PPP/PPTP protocol.
• When the Speed Touch is in IP Routing mode it requires the TCP/IP protocol stack.
• If the ATMF-25 interface on the Speed Touch is used, see the manual of the ATMF-25 PC-NIC for additional requirements.

Local Speed Touch Configuration

• Command line interface (Speed Touch Pro only):
  • A serial cable;
  • An ASCII terminal (VT100) or a PC with terminal emulation.
• Telnet:
  • A TCP/IP protocol stack;
  • A telnet application.
• HTTP/HTML:
  • A TCP/IP protocol stack;
  • A Web browser (Netscape, Internet Explorer).

Following table explains the functions of the LEDs on the Front Panel:

Congratulations for purchasing this Speed Touch family product! It contains the Alcatel state-of-the-art Asymmetric Digital Subscriber Line (ADSL) technology and a whole range of advanced features.

In the topics below we will highlight some key features of the Speed Touch in order to help you find the best solution for your networking needs.

There are two versions of the Speed Touch: the Speed Touch Home and the Speed Touch Pro. On the outside, both products look alike. The difference can be found in the protocols supported on the Ethernet interface:

• The Home version supports Bridging and PPP/PPTP;
• The Pro version implements IP Routing in addition to the protocols supported on the Home version.

You might want to surf the internet at high speeds or suppose you want to create your own private WAN/LAN, the Speed Touch has a solution for you.

Indeed, the Speed Touch supports multiple networking options allowing you to achieve communication in various environments. However, due to specific properties one solution might better fit a specific application than another.

Independent of your application, the protocols supported at both ends of the connection must be a mirror image of each other for successful communication.

For Internet or Corporate access these are the solutions that are most appropriate:

All given examples use the Transmission Control Protocol (TCP) /Internet Protocol (IP) protocol suite because it is widely available. However the Speed Touch can cope with other protocols too, as it is a true multiprotocol device.

If you read this manual you will discover the Speed Touch is actually a toolbox containing various building blocks. These are designed to be combined in a flexible manner allowing you to create solutions to specific networking needs.

The Speed Touch Pro provides high-speed connections to the Internet and Corporate Intranets using Asynchronous Transfer Mode (ATM) and ADSL on a standard telephone line.

ADSL

ADSL is state-of-the-art modem technology that unlocks the potential bandwidth of the widely available public telephone network. The Alcatel ADSL service has been designed to coexist with the standard telephone service. More importantly your telephone lifeline service will not be affected by any failure of the Speed Touch.

ATM

Whether you are using Voiceband modems, ISDN modems or the ADSL modem, all rely upon a Wide Area communication infrastructure. In the Alcatel ADSL solution, ATM was selected for this purpose. ATM is a connection-oriented packet switching technology using fixed-size packets, called cells. These cells can carry information to and from your LAN over large distances.

Speed Touch

The Speed Touch Pro connects your computer and/or network to the Internet and/or Corporate Network. You can connect your computer and/or network to the Speed Touch by means of the industry standard ATM-Forum 25.6 Mbps (ATMF) and 10Base-T Ethernet interfaces. Both ATMF-25 and Ethernet can exploit the high bit-rates available through the ADSL line.

Cables

Following cables are provided with your Speed Touch:

• RJ11/RJ11 (RJ14/RJ14), referred to as the ADSL cable further in this document;
• RJ45/RJ45 (Ethernet/ATMF), referred to as the LAN cable further in this document;
• Serial Cable (Speed Touch Pro only).

As soon as your ADSL provider enables the ADSL service on your telephone line, two "channels" exists on the single twisted-pair:

• the standard voice channel reserved for your regular telephone service;
• the ADSL channel that will transport data to and from your PC(s).

In order for the ADSL channel not to disturb the phone channel and vice versa, splitters or filters must be installed first. A few configurations are possible:

• a centralized splitter might be installed in a enclosure outside your home labeled "TELEPHONE NETWORK INTERFACE";
• this centralized splitter might also be installed inside your home;
• an alternative approach is to place distributed filters in front of every telephone set.

Irrespective of splitter location or type, the installation must be performed by qualified service personnel of your ADSL provider.

Depending on your local ADSL configuration and the wiring inside your house, the connection between the Speed Touch and the ADSL line will differ.

For an external splitter it can be as simple as using the ADSL cable to connect the ADSL line interface to the wall socket in which the ADSL line is terminated.

However, ask your ADSL provider for advice on:

• optimum ADSL line performance;
• seamless integration of the phone service and the ADSL service.

The Ethernet port available on the Speed Touch is a 10Base-T interface of type MDI-X on which you can connect either a single PC or a small network.

Use the LAN cable that is included in your Speed Touch box to connect the Ethernet interface of your Speed Touch to the Ethernet port on your PC.

The most convenient way to connect a LAN with multiple users to your Speed Touch is by using an Ethernet HUB.

Use a crossover LAN cable to connect the Ethernet interface of your Speed Touch to one of the ports of your HUB.

Use straight-through LAN cables to make the connections between the HUB ports and the PCs/workstations.

The ATMF port available on the Speed Touch is an ATMF-25 interface. The interconnection between the ATM Forum equipment and the Speed Touch must most likely be made with a straight-through LAN cable. This is because the ATMF-25 interface of the Speed Touch is of type ATM Network Equipment and most ATMF-25 PC-NIC cards are of type ATM End Equipment.

Connect the PC with an ATM Forum PC-NIC directly to the ATMF interface of the Speed Touch using the LAN cable that is included in the box package.

To connect multiple PCs to the ATMF interface, an ATM switch is needed. Note that for the connection between the Speed Touch and the ATM switch a crossover cable will have to be used since both ATMF-25 interfaces are of the type Network Equipment.

The Speed Touch variant equipped with an Ethernet and ATMF-25 interface is designed for concurrent use of both interfaces.

The Speed Touch is delivered with a modular external power supply adapter of 120 V_AC/60Hz (US standard) or 230 V_AC/50Hz (European standard) converting to:

• 9V_DC/1A unregulated output voltage for passive splitter versions ;
• 12V_DC/1A unregulated output voltage for active splitter versions.

Proceed as follows to connect the power supply adapter :

The Speed Touch offers you different packet services from which you can choose:

• IEEE 802.1D Transparent Bridging
• PPP-to-PPTP Relay
• IP Routing (Speed Touch Pro only)
  • PPP & IP Routing
  • CIP & IP Routing

The criteria below can be of help to select the most appropriate packet service for your application:

• the configuration required by your ISP or Corporate LAN administrator;
• the application protocol you want to use (within the boundaries of the remote end);
• the session aspect: an "Always-on" connection or a connection that is established when needed i.e. "Dial-up";
• connectivity to a single or remote networks simultaneously;
• security features such as identification, authentication and encryption.

  Table 2. Speed Touch Functionality Decision Table

  Interface	Packet Service	Application Protocol	See Section	Model
  10Base-T Ethernet	IEEE 802.1D Bridging	Multiprotocol	5.2	Pro & Home
  	PPP-to-PPTP Relay	TCP/IP, IPX/SPX, NETBEUI	5.3	Pro & Home
  	PPP & IP Routing	TCP/IP Protocol suite	5.4	Pro only
  	RFC1577 CIP & IP Routing	TCP/IP Protocol suite	5.4.2	Pro only
  ATMF-25	The supported data services depend on the functionality is offered by the drivers included with the ATMF-25 PC-NIC you purchased.			Pro & Home

You might select the Speed Touch Bridging packet service because of its protocol transparency and its inherent simplicity for configuration.

• Platform and Operating System (OS) independent;
• True multiprotocol support;
• No constraints on the number of attached users (practical limit w.r.t. performance: 16 PCs);
• Plug & play;
• Concurrent access to multiple remote destinations.

Remote Organization

The remote Access Server must support RFC1483 Bridged PDU Encapsulation on ATM.

Additionally the Remote Organization must provide you with:

From this point on, using bridging is rather straight-forward. Just power on both your Speed Touch and your PC, start your browser and you are on the Internet.

This form of remote network access is what is sometimes called "Always-on": no connection must be established prior to connectivity.

However, the remote organization might present you with a welcome screen on which you can supply an user ID and password before you are granted access to certain servers or the Internet.

You might select the PPP/PPTP packet service for your applications because it provides complete TCP/IP protocol transparency. Even so the remote organizations might require you to identify and authenticate yourself prior to providing access to the Internet and/or allowing you to use their internal resources.

PPP-to-PPTP Relay has the following features:

• Standard "Dial-up" behavior;
• Security through identification, authentication and encryption;
• Multiprotocol support depending on PPTP implementation e.g. MS Windows: TCP/IP, IPX/SPX and NETBEUI;
• Complete TCP/IP protocol transparency, hence no Network Address Translation is required.
• Concurrent access to multiple remote destinations (depending on provisioning);
• Simultaneous access is limited to the number of virtual connections provisioned by the network operator. Regardless of the provisioning, the Speed Touch supports 14 virtual channels.

Remote Organization

The remote Access Server must support RFC2364 PPP Encapsulation on ATM, at the remote end of the virtual channel.

Additionally the Remote Organization must provide you with:

TCP/IP

PPP is carried in ATM cells over the ADSL line. However, on the Ethernet segments between the Speed Touch and your PC(s), IP tunnels are used instead. Prior to establishing IP tunnels, IP addresses must properly be configured in both machines initiating and terminating the tunnel.

Again, this procedure describes the Windows98 platform only.

5.3.3.1. Setting Up a PPP/PPTP Connection

After having configured the connection, proceed as follows to establish the PPP/PPTP connection:

5.3.3.2. Disconnecting a PPTP Connection

To disconnect a PPTP connection, proceed as follows :

1. Click on the appropriate button.


2. Press the button.

The network connection to your ISP no longer exists.

Next to Bridging and PPP-to-PPTP relaying the Speed Touch Pro offers a third packet forwarding mode: IP Routing. This mode provides Wide Area connectivity, yet prevents local traffic from being forwarded off premisses.

IP Routing can be used in combination with both the PPP protocol suite and Classical IP.

5.4.1.1. Features

• because of its use in the Internet, IP routing is standard and well known technology;
• IP is supported on most if not all platforms (PC's, Workstations) and by all operating systems (Windows, Unix, MAC OS, ...);
• IP has broad application support;
• PPP is the protocol of choice for ISP and large Corporate access due to features like session concept, authentication, autoconfiguration and its historical use in the narrowband world.

5.4.1.2. Configuring IP Routing & PPP

Remote Organization

The remote Access Server must support RFC2364 PPP Encapsulation on ATM.

Additionally Remote Organization must you provide you with:

You have now successfully made a PPP connection.

5.4.1.4. Disconnecting a PPP Connection

After having established a PPP connection, proceed as follows to disconnect that connection:

The network connection no longer exists.

5.4.2.1. Features

• The IP features listed for IP Routing & PPP also apply to Classical IP (CIP) ;
• Besides PPP over ATM, CIP is a second standardized method for creating IP networks on top of ATM technology;
• CIP has traditionally been well supported at the remote end of the connection by ATM access routers.

5.4.2.2. Configuring IP Routing & CIP

Remote Organization

The remote organization must support RFC 1577 CIP Encapsulation on ATM.

Additionally the Remote Organization must provide you with:

If your terminal equipment is connected to the ATMF interface, ATM service is delivered to the PC. This means ATM cells sourced by the applications on the PC are captured by the ATMF-25 interface and cross-connected or switched to the ADSL line.

Since the Speed Touch only relays ATM cells, the available services (bridging, tunneling, routing,...) depend on your PC-NICs capabilities. Consult the documetation of your PC-NIC for more information on how to configure these sevices.

In the previous chapters, it has become clear that the TCP/IP protocol suite plays a crucial role. Not only for the various networking capabilities of the Speed Touch, but also for its internal configuration.

Because of the flexibility and features of TCP/IP, a wealth of configurations exists. The purpose of this chapter is to highlight a few of the possibilities.

These are the possible IP applications:

• accessing the Internet via your ISP or Corporate Network;
• private LAN-to-LAN interconnections over the ADSL/ATM network;
• local IP connectivity towards the other PCs on your LAN.

Independent of your application, IP addresses must always be configured at both ends of the connection.

Prior to configuring an IP address, you must choose a suitable one first. Below the criteria are listed that may influence your choice.

Basically, Bridging does not require any IP address at all: neither in your PC(s), nor in your Speed Touch. However, in case of Internet Access or private IP networking, your PC(s) must be configured for TCP/IP.

If your ISP or Corporate Administrator:

For PPTP to operate at least local IP addresses must be configured. The use of the IP addresses for local IP connectivity is limited to the local network. Hence you are free to choose any IP address as long as it is compatible with your local network and is unique in that same network.

As the Speed Touch has a preconfigured Net10 address (10.0.0.138) you should configure IP addresses like 10.0.0.1, 10.0.0.2, ... in your PCs.

For PPP to operate at least local IP addresses must be configured either manually or automatically. The scope of the IP addresses for local IP connectivity is limited to the local network. Hence you are free to choose any IP address as long it is compatible with your local network and is unique in that same network.

As the Speed Touch has a preconfigured Net10 address (10.0.0.138) you should configure IP addresses like 10.0.0.1, 10.0.0.2, ... in your PCs.

As already mentioned, for local IP connectivity between PC(s) and your Speed Touch to exist:

• IP addresses of both Speed Touch and your PC(s) must fall within the same IP network (e.g. Net10).
• If subnetting is applied to the local network, the subnetwork of your PC(s) must match with that of the Speed Touch.
• The assigned IP addresses must be unique within the same network/subnetwork e.g. 10.0.0.1, 10.0.0.2 and 10.0.0.138.

The Speed Touch comes with a preconfigured Net10 address i.e. 10.0.0.138 .

7.5.2.1. Bridging and PPP-to-PPTP Relay Mode

In these modes the subnet mask has almost no significance for the Speed Touch, so leave them unchanged. The default subnet mask is 255.0.0.0 .

7.5.2.2. IP Routing Mode

When the Speed Touch operates as a router, your PC(s) must configure the IP address of the Speed Touch as their default gateway.

7.5.3.1. Single PC

In the drawing below, a simple configuration is given: one PC attached to the Speed Touch. It is most applicable to Bridging and PPP-to-PPTP relay. For IP Routing, the default gateway in the PC must contain the Speed Touch IP address.

7.5.3.2. Small Workgroup

You can setup a local workgroup around the Speed Touch. The drawing below shows a small workgroup centered around the Speed Touch. Notice that the default gateways in the PCs point to the Speed Touch.

DHCP is short for Dynamic Host Configuration Protocol and is part of the TCP/IP protocol suite. It is intended to allow individual hosts to extract their IP parameters from a central server, instead of configuring them all manually.

A computer supporting DHCP, requests amongst others, following IP parameters:

• its own IP address and subnet mask;
• the IP address of the default gateway;
• the IP addresses of the Primary and Secondary DNS servers.

DHCP operates in client/server mode: a computer in its booting stage acts as a DHCP client and emits DHCP requests. These are intercepted by a DHCP server on the same network which responds with DHCP replies.

Depending on the size and complexity of your network a few DHCP configurations can be envisaged:

• simple IP network: no DHCP at all i.e. see manual configuration earlier in this chapter;
• medium sized network: Speed Touch acting as DHCP Server;
• advanced local network: Speed Touch acting a DHCP Client.

One of the Speed Touch features is that it can automatically revert from DHCP client to DHCP server. At boot time the Speed Touch probes for 20 seconds to see if a DHCP server is available on the network. If so, it will act as a DHCP client. If no response received within the specified time limit, the Speed Touch becomes a DHCP server.

To setup the Speed Touch for Auto DHCP, proceed as follows:

For advanced networks, the role of DHCP Server might be performed by another IP node on the local LAN than the Speed Touch. Typically such functions are attributed to Home Gateways: computers having more networking capabilities than other hosts on the home LAN.

All local PCs remain configured as DHCP clients but including the Speed Touch.

To setup the Speed Touch as DHCP Client, proceed as follows:

For small home LANs it might be interesting to configure all your PCs as DHCP clients and the Speed Touch as DHCP server. In this configuration each time a computer boots, it will obtain its IP configuration from the Speed Touch.

To setup the Speed Touch as DHCP Server, proceed as follows:

To setup the Speed Touch without DHCP, proceed as follows:

The default DHCP configuration of the Speed Touch is Auto DHCP. In this configuration the Speed Touch initially issues DHCP requests for a period of 20 seconds in intervals. If no valid responses are returned form a DHCP server on the local network, the Speed Touch switches to DHCP server mode.

IP addresses are fundamental to the operation of the Internet. They not only uniquely identify an Internet node but also allow IP routers to forward datagrams to their destination. IP addresses are 32-bit numbers. They are ideally suited for computers but are far from usable to humans.

Therefore the Internet engineering community designed a system called DNS. Basically DNS is a hierarchical system of DNS servers that resolves DNS names to IP addresses.

Most likely you are confronted with DNS without knowing e.g. when you type www.alcatel.com, into the URL field of the browser. Your browser must resolve www.alcatel.com into an IP address in order for the HTTP request to end up in the Alcatel World Wide Web server.

Most of the time your ISP or Corporate Network performs this DNS resolving. However the Speed Touch can play a role too: local DNS resolving and DNS proxying.

The same mechanism for resolving computer names to IP addresses when surfing the Net, applies to your local network. Instead of using the IP addresses for a local IP nodes e.g. 10.0.0.138 for the Speed Touch, give your nodes names and let a local DNS server do the resolving.

DNS is active by default, so nothing has to be configured.

In the DNS scenario, it is assumed DHCP is used for IP parameter distribution.

When your PC is powered on, TCP/IP launches a DHCP request on the local network. One of the fields in the DHCP request contains the computer name e.g. YourPC.

The Speed Touch reacts by intercepting this request and returns a DHCP reply containing:

• the IP address for his computer e.g. 10.0.0.1;
• the DNS name i.e. YourPC;
• the local Domain Name i.e. ADSL.net;
• the IP address of the local DNS server i.e. 10.0.0.138 being the Speed Touch.

A second PC is powered on and is configured via a DHCP as below:

• the IP address for his computer e.g. 10.0.0.2;
• the DNS name i.e. MyPC;
• the local Domain Name i.e. ADSL.net;
• the IP address of the local DNS server i.e. 10.0.0.138.

As an example, it is now possible to ping both PCs by referring to their computer name instead of their IP addresses.

The mechanism is as follows:

1. Issue a "ping YourPC" on MyPC;


2. MyPC will launch a DNS request: basically this request says: What is the IP address of YourPC?


3. As the Speed Touch is a DNS server it will respond with the appropriate IP address being 10.0.0.1


4. The ping utility in MyPC will now submit the ping to 10.0.0.1 which may eventually reply.

The Speed Touch only resolves names in the local domain i.e. local.net. All other domain names it cannot resolve are forwarded over the appropriate link on the ADSL line.

It could happen that you are no longer able to reach the Speed Touch via IP, for example due to a configuration error or you simply forgot the IP address you once configured.

Additionally, because the Speed Touch has many features and quite some configuration flexibility, you might end up in a situation where restoring all manufacturing defaults might be necessary.

The Speed Touch has a few tools to cope with these situations:

• Speed Touch Home:
  • Push button;
  • Ping-of-Life, Ping-to-Defaults.
• Speed Touch Pro:
  • DIP switches;
  • Serial Interface;
  • Ping-of-Life, Ping-to-Defaults.

If you only want to reset the IP address of the Speed Touch Home you must use the Ping-of-Life feature. For the Speed Touch Pro you can also do this via the serial interface.

The principle is simple, a special ping packet will deliver an IP address to your Speed Touch.

The steps to be performed are:

• Pre-configure the intended IP address in the ARP cache of one of your systems;
• Reset your Speed Touch and allow the selftest to end (takes about 30 seconds). Now ping this IP address within 60 seconds;
• If everything goes well, your Speed Touch has assimilated this IP address.

The procedure for Windows 95 is described below. There might be small differences for other platforms.

Another method to reset all settings to factory defaults is the Ping-to-defaults method.

The technique is identical to that used for the Ping-of-life, except that another MAC address is used, i.e. 01-90-D0-00-01-FF.

The following steps will cause the Speed Touch to revert to the default values:

1. Add the following to the arp cache:

           arp -a <any IPaddress> 01-90-D0-00-01-FF



2. Reset the Speed Touch and wait for the selftest to end.


3. Ping the IPaddress :

           ping <any IPaddress>

	Be careful when using the Ping-to-defaults command as it destroys all changes previously made to the Speed Touch internal settings.

The Speed Touch can be configured in different ways:

• using a Web Browser (Home and Pro version);
• using a Command Line Interface:
  • via telnet (Ethernet port) (Home and Pro version);
  • via the serial interface (Pro version only).

The Speed Touch comes with an Integrated Local Configuration capabilities. The Interface is based on the "HTTP Server/Web Browser Concept" which allows you to configure the Speed Touch via your web browser.

To configure your Speed Touch, make sure your browser is not using a proxy server. The procedure to disable proxy settings depends on the browser you are using:

Netscape Navigator

1. Select 'Edit' pull-down, then select Preferences. Advanced, Proxies.


2. In the 'Category' box select Advanced, Proxies.


3. Activate the radio button 'Direct Connection to the Internet'.

Microsoft Explorer

1. Select Internet icon, click with the right mouse button.


2. From the pop-up menu select 'Properties'.


3. Remove the tick mark from 'Use Proxy Server' check box.

After configuring your Speed Touch, do not forget to set your browser to its original settings !

To access the Speed Touch Local Management proceed as follows:

Below you will find the function of all generic buttons. These buttons appear on most of the web pages and help you to manage the Speed Touch internal settings.

Apply

Once this button is pressed, all changes you made, will take effect. However, as they are only stored in volatile memory, these settings will be lost when the Speed Touch is reset or powered off.

Save

Via this button you can save changes in permanent storage. Unlike with the 'Apply' button, the active configuration parameters will remain in effect when the Speed Touch is reset or powered on/off.

Defaults

If you make a mistake during configuration, 'Defaults' allows you to recall the default settings for a particular topic. You must still press 'Save' to make the default settings persistent again.

Advanced

Most configurable items are presented in a two-level hierarchy:

• Standard;
• Advanced.

Pressing the latter will present you with the more advanced items for a particular topic.

Home

Independent of the page you are on, this button brings you back to the Speed Touch "Welcome Page".

Back

Independent of the page you are on, this button allows you to go "one step back".

This is the opening (home) page of the Speed Touch Local Management browser.

The following buttons apply to this page only:

Initial Setup

This button brings you to the 'Speed Touch Configuration' page, allowing you to adapt the Speed Touch internal settings to your local networking needs.

System Setup

This button brings you to the 'System Setup' page, allowing you to restrict the access to the local configuration by specifying a password. This password will have to be entered each time you access the local configuration via a web browser, telnet or the serial interface.

Phonebook

This button brings you to the 'Phonebook' page, allowing you to adapt the Speed Touch VPI/VCI values.

Dial-in

This button brings you to the 'PPP Connection table' page, allowing you to setup a connection.

Routing

This button brings you to the 'Routing' page, allowing you to configure settings for very specific IP configurations.

Bridge, PPTP, PPP, CIP

These buttons open the configuration page for the networking model involved.

The Speed Touch Pro supports four networking models, one based on LAN bridging, one based on PPP relaying and local tunneling by means of PPTP, one based on IP Routing over PPP and one based on Classical IP.

The Speed Touch Home offers LAN Bridging and PPP/PPTP only. Indeed, pressing the PPP or CIP button with the Home version will popup an error message.

DHCP, DNS

These pages allow you to configure advanced internal settings for your local networking needs.

System Overview

Pressing this button gives you an instant view of all Speed Touch connections and their parameters.

Upgrade

Allows to perform a software update of the Speed Touch.

A number of functions in the Speed Touch rely on an Internet Protocol (IP) for their operation. IP requires a minimum set of parameters for its internal functioning:

• IP address
• Netmask

These parameters can be configured manually, entering the values in the fields of the 'User defined configuration' box or automatically via the 'DHCP Configuration' page.

As the Speed Touch-IP layer supports multi-homing (one interface supporting multiple IP addresses), the manually configured IP address and the automatically required IP address are both active at the same time.

	These IP parameters are for local communication only. This means between the machines on your own local network and the Speed Touch. Via PPP/PPTP a second IP parameter set will be negotiated between the PC(s) and the remote site. This second IP set will be invisible to you and will not interfere with the local IP configuration.

Parameters used on this page:

Speed Touch MAC Address

The MAC address of the Speed Touch Ethernet interface is displayed just under the header of the configuration page

• User Defined Configuration Box

IP Address

In this field you can change the user defined IP address of the Speed Touch to a value more suitable to your local IP address policy.

Netmask / Subnet Mask

This field represents the default netmask associated with the particular IP address class you assigned to the Speed Touch. Leave this field unchanged if no subnetting is applied in your local network.

The Speed Touch will automatically fill out the default netmask for the particular IP address class e.g., 255.0.0.0 for the preconfigured IP address. If you want to apply subnetting in your local network, extend the subnet mask with additional bits.

This page allows you to configure settings for very specific IP configurations.

• IP Address Table

This table summarizes all IP addresses configured in the Speed Touch, e.g. User Defined and BOOTP acquired. In addition the Loopback IP address is shown.

The following fields are shown in the IP Address table:

Intf

Indicates the Interface to which the IP parameter set was assigned to. It can take two values, i.e. Ethernet and Loopback

Address

Shows the IP address of the Interface

Netmask

If available, shows the Subnet mask of the Interface

Type

Indicates the origin of the IP parameters and can take three values:

• User Defined

  Filled out manually through the Initial Configuration Page

• Automatic

  The parameters were acquired automatically through BOOTP/DHCP, for more information see Initial Configuration Page

• Extra

  Implies that an additional IP parameter set was added through this page.

Action

Allows you to Delete a parameter set if you are in the first part of the table or allows you to add additional IP parameter sets if you are at the bottom of the table.

• IP Route Table

  Because the Speed Touch is a router, it has the ability to access machines in other networks than its own. This can be achieved by adding specific routes in this Routing Table.

  Note that most IP hosts display routing entries for every configured IP address. This principle is not followed in the Speed Touch; only specific routes are displayed in this table.

  In order to add a route to the routing table, use the bottom row of the table. The specific fields that can be filled out are:

  • Destination
  • Source
  • Gateway
  • Intf
  • Action

    This field is in fact a button that can perform two actions:

    • Add
    • Delete

10.1.7.1. Definition

The Speed Touch Phonebook is like any ordinary phonebook, a repository for names and numbers. In contrast with a standard phonebook though, it is extended with additional information.

The Speed Touch Phonebook contains 5 columns:

• Name

  This column shows names or aliases referring to organizations connected at the remote end of the virtual channels. In fact you may give any name to an entry.

• VPI/VCI

  The VPI/VCI column lists the VPI/VCI values of the virtual channels that may be cross-connected to these remote organizations.

• Type

  Represents the packet service that is possibly supported at the remote end of the virtual channel. The supported packet services are: Bridging, PPTP, PPP and CIP.

• Usage

  This column indicates the state of the virtual channel (e.g. configured, in use etc.).

• Action

  The Action column allows you to either add or delete entries in the ST Phonebook.

10.1.7.2. Using the Phonebook

The main function of the Speed Touch Phonebook is to present an immediate overview of all possible entries and their status. Another important function is that it helps you to navigate through the various Speed Touch connectivity possibilities.

Entries in the Speed Touch Phonebook can be added or changed at will. However connections that are in use or configured in other pages cannot be deleted from the Speed Touch Phonebook. This to prevent unintentionally deleting a connection.

As Phonebook entries do not consume Speed Touch communications resources, you are free to store all you favoured connections for reference at a later date.

10.1.7.3. Configuration

The first time the Speed Touch Phonebook is consulted, it will show manufacturing defaults. You can change these defaults or or add new entries.

The Speed Touch contains an IEEE 802.1D compliant databridge that can be reconfigured using this page.

Normally for bridging nothing needs to be configured for proper operation as it is a plug & play device.

Should interoperability problems occur, you can easily change the default settings according to the information supplied by the remote organization (ISP or Corporate network).

• Bridge Configuration Table

Bridge Port

One of the characteristics of a databridge is the number of ports it supports. A bridge port is in fact the logical equivalent of an interface. By default the Speed Touch supports one local port (Ethernet interface) and four remote ports. The remote ports are mapped to the virtual ATM connections on the ADSL Line. Only the remote ports are shown in the table and are indicated by ADSL Port 0, 1, 2 and 3.

Encap

Encapsulation/Decapsulation refers to the encapsulation/decapsulation of Ethernet or IEEE 802.3 frames in/from AAL5/ATM. Encapsulation/decapsulation will be referred to as 'encapsulation' for readability.

The Speed Touch is compliant with RFC 1483 "Multiprotocol Encapsulation over ATM Adaptation Layer 5" and supports both the LLC/SNAP method and the VC MUX method for Bridged Ethernet V2.0/IEEE 802.3 PDU's. By default the Encapsulation method is set to LLC/SNAP and the Access Server of your remote organization (ISP or Corporation) must use the same method. If this is not the case, please contact your ISP or Corporate network administrator.

FCS

Part of the RFC 1483 encapsulation method indicating whether the last four bytes of the MAC frames (MAC Medium Access Control frames, mostly referred to as Ethernet or IEEE 802.3 frames) will be preserved or not.

By default the FCS of a MAC frame will not be preserved and is set to NO in the particular column.

If the remote site requires the FCS to be preserved over the ADSL connection, fill out YES.

State

This field allows you to change the state of the individual LAN ports. By default only two ports (local port and one virtual one) are in forwarding state, meaning that traffic can pass via these ports. The other ports can be enabled putting them in the Enabled state.

Action

This column contains Action Buttons allowing to add or delete bridge ports.

The maximum number of remote bridge ports supported is 4.

Deleting bridge ports might be useful if you want to use more than the 8 PPP/PPTP ATM connections currently available (default value).

• Ageing

  This box contains the ageing timer of the bridge internal database. Only in exceptional cases may the default value of 300s (5 minutes) be modified. The range allowed is from 10 seconds to 12 days which is compliant with the IEEE 802.1D bridging standard.

The PPTP Destination table displayed on this page presents you with relevant PPP/PPTP connection information.

The following three fields are part of the PPTP Destination table:

Channel ID

The numbers found in this column refer to the ATM Virtual Channels on the ADSL line. Using one of these numbers in the PPTP Connection Icon on your PCs desktop allows you to select a particular remote destination.

Name

Has the same functionality as 'Channel ID' parameter, but refers to the ATM Virtual Channels. However, with 'Channel ID' you can customize this entry to reflect the remote organization connected to this virtual channel. Suppose the Local Operator established 4 permanent virtual channels from your Speed Touch to your corporate headquarters; You "name" these virtual channels after your company or favorite IS, e.g.,:

In this example, from now on you can supply "Alcatel" in the PPTP Connection Icon on your PCs desktop. The Speed Touch will then connect you to one of the free Alcatel virtual channels. An additional advantage of the 'Name' field is that you are automatically transferred to a free channel (provided the channel pool is not exhausted) which is not the case when using Channel ID.

Encaps

Encapsulation/Decapsulation refers to the encapsulation/decapsulation of PPP packets in/from AAL5/ATM. Encapsulation/decapsulation will be referred to as 'encapsulation' for readability.

The Speed Touch is compliant with RFC 2364 "PPP Over AAL5" and supports both the LLC/NLPID method and the VC MUX method. By default the Encapsulation method is set for LLC/NLPID and the Access Server of your remote organization (ISP or Corporation) must use the same method. If this is not the case contact your ISP or Corporate.

HDLC Framing

In order to cope with these PPP packet differences the Speed Touch adapts to the different formats on a per connection base . Although RFC2364 is quite clear with regards to PPP format on AAL5, the Speed Touch offers a configuration possibility if interoperability problems should arise.

The PPP/AAL5 format configuration options are:

1. never:

   The Speed Touch will make sure that FF-03 will never be found in front of a PPP packet encapsulated on an AAL5/ATM connection, independent of the actual format of the PPP packets in the tunnel. This is the default setting and follows RFC 2364.



2. always

   The Speed Touch will make sure that FF-03 is always in front of a PPP packet encapsulated on an AAL5/ATM connection. Although not supported by RFC 2364, some equipment may rely on this format.



3. keep

   The Speed Touch will not change the PPP packet arriving via a tunnel, that is, it will keep the two bytes in front of packet when it does the encapsulation.

State

The Speed Touch allows multiple users to connect to different remote organizations simultaneously. However this has a price, as every time somebody surfs through the Speed Touch a connection is no longer available for other users. From the moment a connection is taken, the field "In Use" changes from "IDLE" to "In Use (xxx.xxx.xxx.xxx)". The number in brackets is the IP address of the PC currently using the connection.

This page gives you an overview of all ADSL channels on the Speed Touch. It is in fact a summary of the Bridge page , the PPTP page, the PPP page an the CIP page.

As mentioned in the introductorary part, the Speed Touch exhibits a Command Line Interface (CLI) . The CLI can be accessed via either the serial port (Pro version only) or via the Ethernet interface (Home & Pro version).

Via a PC connected to the Ethernet interface of the Speed Touch you can execute CLI commands. You must gain access to the Speed Touch first, by opening a TCP/IP Telnet session.

To execute CLI commands via Telnet proceed as follows:

1. From your local PC connected to the Ethernet port of the Speed Touch, open a Telnet session and supply the IP address of the Speed Touch.


2. The Speed Touch will prompt you with "User:". It is not required to specify a username, just type a carriage return:
   • if no System Password is configured, the Speed Touch CLI banner will appear on your PC's screen;
   • if a System Password is configured, you must supply this password prior to gaining CLI access.


3. At this point you reached the CLI prompt, => you can start executing commands. Description of these commands is beyond the scope of this manual. However typing "help" will show you the command groups that are currently available.


4. CLI access is closed either via timeout or by closing the Telnet application.

For the Speed Touch Pro you can execute CLI commands from the serial port.

Setup the serial interface of your ASCII terminal for:

• 9600 BAUD;
• 8 databits;
• no parity, 1 stopbit.

Connect the ASCII terminal or a PC with terminal emulation to the port marked "Console" at the back of the Speed Touch. Similar to Telnet Access, the Speed Touch CLI banner will appear on your ASCII Terminal.

The serial interface of the Speed Touch is a 9 pins D-type connector and has the following pin numbering and assignment.

The Speed Touch supports two software upgrade possibilities:

• a new version of the software can be downloaded from the ADSL network to your Speed Touch;
• or you can upload new Speed Touch software packages from a PC on your local LAN.

Both features are simultaneously supported. However the final result depends on the ADSL Provider's policy.

This feature is controlled by the ADSL operator. At some point in time your ADSL provider might decide to upgrade the software in your Speed Touch. This download will happen almost unnoticed. Though you will see a change in the software version if you surf to the Upgrade page.

The procedure to upload software from a PC is as follows:

1. A correct Speed Touch software package must reside either on your harddisk or on a floppy disk, to be inserted in your PC.


2. Start your Web Browser and surf to the Speed Touch web pages.


3. From the Speed Touch Welcome page, click the "Upgrade" button and the Software Upgrade page appears. This page should show at least the Speed Touch package that is actually running. It is labeled "Active software version".


4. Click the "Browse" button next to "Passive software version" and locate the new Speed Touch software package on either your harddisk or floppy.


5. If the correct package is selected click the "Upload" button. From this point, the software package will be transferred from your PC to the Speed Touch.


6. After a successful transfer, two software versions are stored on the Speed Touch. Press the "Switchover" button to activate the uploaded version.

   Your Speed Touch will reboot and come online again with the new version. Surfing to the Upgrade page shows that active and passive versions (prior to the upgrade) have trade places.

ATM is a connection-oriented packet switching technology using fixed-size packets, called cells. ATM cells consist of a header and a payload and are switched through a public or private ATM network depending on the contents of the header. End-to-end connections are formed by cross-connecting individual ATM segments in ATM switches.

Virtual Channels

ATM uses Virtual Channels (VC) to create individual communication links between network nodes. ATM uses two types of VCs:

• Permanent Virtual Channels (PVC) are static connections between network nodes that are configured manually. The nodes of the connection operate as if they are connected with a dedicated physical line.
• Switched Virtual Channels (SVC) are similar to voice telephone network connections. These are temporary connections between any two end points on the network which are configured via signaling. SVCs are created dynamically for each session and deleted when the information exchange is complete.

Currently ATM connections are static i.e. of type PVC.

Channel Identifiers

Each ATM cell contains a VPI and a VCI as part of its header. Each ATM channel, commonly referred to as virtual channel, is fully identified by these two values. Therefore, multiple ATM channels can reside on your ADSL line.

Practically speaking, a number of virtual channels to one or multiple remote destination(s) can start from/are terminated at the Speed Touch. By default, a number of channels are terminated in the Speed Touch for Ethernet; others are cross-connected to the ATMF-25.6 interface.

ATM traffic arriving at the Speed Touch is switched to either the Ethernet interface or the ATMF-25 interface depending on the VPI/VCI values in the individual cells.

Inside ATM virtual channels any protocol can be transported. However, at both endpoints that is where the ATM channels terminate, the same protocol must be supported. If not there will be no end-to-end connectivity.

ATMF-25

This interface does not terminate ATM connections, it just switches ATM cells between the ADSL and ATMF-25 port. It is the ATMF-25 PC-NIC that actually initiates or terminates ATM channels. It is important to check in advance which protocols are supported by the PC-NIC driver. At least RFC 1483 and RFC 2364 should be fully implemented.

Ethernet

This interface terminates a number of ATM connections and extracts frames from arriving cells and encapsulates frames in departing cells.

Only frames recognized/supported by the Speed Touch on a particular ATM connection are extracted or encapsulated.

Currently the supported encapsulations are:

• For Bridged connections:

  RFC 1483, Ethernet V2.0/IEEE 802.3 bridged PDUs for both the LLC/SNAP method and VCMUX method;

• For PPP/PPTP connections:

  RFC 2364, PPP PDUs for both the LLC/NLPID method and VCMUX method;

• For Routed connections:

  RFC 2364, PPP PDUs for both the LLC/NLPID method and VCMUX method;

• For Classical IP connections:

  RFC 1483, Routed PDUs for both the LLC/SNAP method and VCMUX method.

Your ISP or Corporate LAN administrator will provide you with the following:

• the VPI/VCI values of the virtual channels to which it is cross-connected;
• the protocols that are supported on these virtual connections.

Example

VPI=8

VCI=35

Protocol = transport of bridged frames, LLC/SNAP encapsulated.

Basically the Speed Touch offers two solutions to access remote information infrastructures: "Direct Networking" and "Dial-Up Networking".

Direct Networking refers to how the network connection is experienced by the user. The connection is always-active. No actions need be performed to connect. Direct Networking is what is typically experienced when using computers on a LAN. Initial configuration of all networking nodes in the end-to-end network is still required but this must be performed only once when the service is enabled. As soon this is accomplished, all that is necessary is powering up the local PCs, including the Speed Touch, and the user is able to interact with the network.

With Dial-Up Networking there is initially no connectivity; you must explicitly request a connection in the form of dialing up the network. The remote organization will require you to identify and authenticate yourself. Before you are allowed to access its resources it will request you to supply your personal user account and password.

The Speed Touch supports both solutions independently of whether you are using the Ethernet or the ATMF-25 interface.

Though the transparent character of the ATMF-25 interface supports both networking modes, the PC applications will determine whether you use the Direct or Dial-Up mode.

For the Ethernet interface the scenario is more complicated as you will see below:

Bridging is a Layer 2 technology allowing Ethernet frames to be transparently relayed. Depending on the destination MAC address of an Ethernet frame, the bridge takes a decision whether it will forward the frame or not. This decision is based on information contained in the filtering database.

The filtering database is the core of the bridge. All functions performed by the bridge are based on information contained in this filtering database.

When the bridge is powered on, the filtering database is empty. It is gradually filled with entries via the learning mechanism because all Ethernet frames arriving on any port are inspected for their source MAC address and put into the filtering database together with the port ID the frames arrived on.

When an Ethernet frame arrives the destination MAC address is searched in the filtering database. When the destination MAC address is not found (which means it that has not been learned yet), it is forwarded to all ports in the forwarding state except the one the frame arrived on. This process is called flooding.

When an Ethernet frame arrives with a destination MAC address that is found in the filtering database (which means it that has been learned before), it is forwarded to the port that is associated with that entry. This process is called forwarding.

As the bridging functionality operates below the network layer, it is transparent to any layer 3 protocol. Indeed, to the Bridge of the Speed Touch it makes no difference whether your PCs or workstations use TCP/IP, Sequenced Packet Exchange (SPX) /Internetwork Packet Exchange (IPX) , Appletalk or any other protocol suite. This implies that any protocol you are currently using for your applications can be transported to your remote destinations and vice-versa.

Stated otherwise, you can connect any type of machine via Ethernet to the Speed Touch whether it is a PC, a MAC or a SUN workstation; to the Speed Touch it makes no difference.

Through the dynamic learning and ageing mechanism of the bridge, the number of PCs that can be connected to either the local or virtual ports is theoretically unlimited. Practically the bridge database can hold as many as 256 entries simultaneously.

Assume a sample configuration with 4 remote ports and one local port (Ethernet interface). If all systems are evenly distributed over all ports, you could connect around 50 systems per port to completely fill up the database. This is of course a theoretical example as the upstream bandwidth is limited to 1 Mbit/s maximum. Should only one virtual port be in use, the 256 entries can be divided over two ports (virtual, Ethernet port).

The Speed Touch Bridge is a 'plug & play' device, through the bridge learning and ageing mechanism it discovers at which side of the bridge machines are located. Through this knowledge it is able to keep traffic submitted to your local printer from crossing the bridge. Yet it allows frames belonging to "conversations" with remote machines to pass over the ADSL line.

As already mentioned, the Speed Touch is plug and play, but both your local PCs and remote machines must be configured properly in order to have end-to-end connectivity.

Parameters below are of importance for the Speed Touch bridge:

Within the context of networking with the Speed Touch, a PPTP tunnel is established between two peers on the local IP network. The Speed Touch terminates one end of the tunnel, the node that initiated the tunnel terminates the other end. Within this tunnel, PPP packets are transported between these two PPTP peers.

The net result of PPTP tunneling is that PPP packets can cross the local Ethernet segment: between the Speed Touch and the client computer and vice versa. This would otherwise not be possible as PPP is designed to run on point to point connections, e.g. Dial-Up connections, whereas Ethernet is a shared medium.

The figure below provides an overview of the end-to-end architecture.

A double-click on a previously created connection icon is all that is required for a specific remote connection to your ISP or your corporate headquarters.

By default, the Speed Touch is configured for 4 PPP/ATM connections. However, check with your ISP/corporate headquarters to ensure that these are cross-connected in the wide area network and hence that end-to-end connectivity is assured.

Using PPP/PPTP it is now possible to explicitly indicate which remote destination you want to connect to. You will therefore need to modify the 'VPN Server' field in the 'Connect To' window according to the possibilities described in the following paragraphs.

Any Connection

Specific Connection

It is possible that multiple remote organizations are connected to your Speed Touch, e.g., your private ISP and your corporate headquarters. In this case, the Speed Touch ATM channels will be split over both locations. For example, 2 ATM channels could be provisioned to your ISP and 2 channels to your corporate headquarters. Although it is still possible to establish a connection to one of both locations using the procedure explained under 'Any Connection', it is safer to explicitly indicate which one you want to connect to. If you do not, the Speed Touch will select the first available connection which could be either your corporate site or your ISP.

By inserting C:n in the VPN Server field of the 'Connect To' window, you are able to specify which ATM connection to use. C refers to Connection and n indicates a virtual ATM channel in the range 0 to 3.

You need to check with your ISP and your corporate LAN administrator to verify which ATM virtual channels are cross-connected to which location. In the example given below, channels 0 & 1 are cross-connected to an ISP and 2 & 3 to a corporate location.

Custom Connection

Tunneling does not influence your local communication; you may add as many machines as your local network supports. However there is an upper limit to the number of simultaneous outbound connections.

Unlike bridging, an ATM/PPP channel cannot be shared by multiple users. Every local user establishing a tunnel requires an ATM channel on the network. Therefore, any user on your local network can initiate a tunnel as long as free/unused ATM channels are still available.

By default, the Speed Touch supports 4 PPP/ATM channels. If all PPP/ATM channels are in use and a user tries to set-up a new tunnel, the Speed Touch will refuse the request and an error message will appear on the screen.

TCP/IP is used to establish PPTP tunnels between local machines and the Speed Touch. The data that can be transported end-to-end may be TCP/IP, IPX/SPX or NETBEUI. The limitations are not a part of the tunneling protocol or the ATM connection but are a function of the PPTP client.

The tunneling applications supported on your PC might have limitations. Listed below are those of the most popular platforms currently in use:

The figure below provides an overview of the general end to end architecture.

The main function of the IP router in the Speed Touch, is to route IP packets from the local network to the remote networks over the ATM/ADSL connections and vice versa.

Routing to ATM/ADSL Connections actually means:

• Routing between the local LAN and Classical Logical IP Subnet (LIS) s and vice/versa;
• Routing between the local LAN and PPP connections and vice/versa.

Basically the IP router only cares about IP addresses i.e. the 'Destination IP address' of any packet received on any of its interfaces (PPP, CIP or Ethernet) is looked up in the routing table. The lookup process will determine the best route that may lead to the final destination of the packet. Consequently it will forward the packet to the interface that may reach this destination.

An IP address is a 32-bit number that uniquely identifies a computer on your network or the Internet. This number is commonly represented in "dotted quad" format. Each octet (8 bits) is represented as a decimal number. Dots are used as octet separators (e.g. 10.0.0.138).

Historically, an IP address consists of two parts: a network part and a host part. The network part identifies the network on which a host resides. The host part identifies a particular host on a given network. The dividing line between the network part and the host part can be derived from the netmask or subnet mask.

The 1 bits in the subnet mask represent the contiguous leading bits of the IP address that has network significance.

For example, an IP address is 172.16.0.2 and the subnet mask is 255.255.255.0. The binary notation of the IP address equals: 10101100.00010000.00000000.00000010. The dotted quad notation of the subnet mask equals: 11111111.11111111.11111111.0000000. Since all the 1-bits of the subnet mask have network significance, the network part of the IP address would be: 10101100.00010000.00000000 or 172.16.0 and the subnet part 00000010 or 2.

A more up to date representation of subnet masks do not refer to a subnet mask, but to a prefix length. The length of the prefix equals the number of ones in the subnet mask. For example the subnet mask 255.255.255.0 could also be written as the prefix /24. In the routing table of the Speed Touch this notation will be used.

The routes in an ordinary routing table or Forwarding Information Base (FIB) include among others destination IP addresses, subnet masks and gateways.

When an IP packet arrives at the router, the router examines the destination IP address. The router looks up the most specific match in the routing table for that destination IP address. Finding the most specific match equals finding the longest subnet mask for that IP address.

For example the subnet mask 255.255.255.0 is more specific than 255.255.0.0 because the network part in the first case is longer (and thus more specific) than the network part in the second case. Once the most specific match is found, the router forwards the IP packet to the gateway associated with that match.

Depending on the configuration made, the Speed Touch may use an extended routing table. In addition to the data contained in an ordinary routing table, it contains information about the source IP address and the source subnet mask. The lookup principle may also be extended: not only the combination of destination IP address and subnet mask is looked up, but also the combination of source IP address and subnet mask. The 'Extended routing table' gives extra functionality to the Speed Touch and is explained in the next topic.

When the Speed Touch is powered on, routes are automatically configured in the routing table e.g. :

• As soon as the Ethernet interface is up and running, a route (being the IP address of the Ethernet interface) is added;
• If a Classical IP client is created and configured with an IP address, this IP address will show up in the table;
• The IP address negotiated between the remote Peer and a PPP connection (configured for Always-On) will also be automatically added to the routing table.

When you start PPP outbound connections, additional routes will be added. For the advanced user, the Speed Touch allows you to manually configure routes to dedicated destinations.

Depending on the configurations you make in the PPP Configuration page the settings in the routing table will change when the connection is established.

12.5.3.1. Connection Sharing

The "Connection Sharing" list box can take three values:

Only Me

Only the PC that initiated the connection will be routed over this connection.

Suppose you opened a connection to your Corporate Headquarters (HQ) and other LAN members are surfing the Internet. Via this setting you can prevent them from using the connection to your HQ as their gateway to the Internet.

Everybody

All PCs on the local LAN can be routed over this connection.

This setting is exactly the opposite from "Only me". If you setup a connection to the Internet, other LAN members can share this connection. In this way they are not required to open a connection themselves.

My Subnet Only

All members configured in the same subnet can use this outbound routed connection.

This setting is intended for members that belong to the same workgroup/subnet to have access to an outbound connection:

• Configure the PCs that are part of the workgroup in a particular subnet (don't forget to make the Speed Touch also a member of the workgroup);
• Configure "Connection Sharing" for a PPP connection in the Speed Touch for "My Subnet only";
• It is sufficient now to start this PPP connection from one PC. Only the members of that subnet can now share this PPP connection.

12.5.3.2. Destination networks

The "Destination networks" list box influences the destination mask in the routing table and can take any of the four values below:

All Networks

The result is that the Speed Touch can potentially route all destination IP addresses over this connection. This connection acts if it was a default gateway.

Remote Subnet Only

A connection configured for "Remote subnet only", only forwards traffic that is destined to this specific network. All other traffic is blocked.

Remote Machine Only

Only those IP packets from which the destination IP address matches exactly this entry in the routing table are forwarded over this connection. In fact communication with the single remote host only is possible.

Specific Network

If all previous cases do not fulfill your requirements, "Specific network" might help you out. Via the "Specific network" field you can add a destination/mask entry to the routing table. Destination IP addresses that matches this entry in the routing table, will be forwarded over this connection.

The Speed Touch Pro supports Port & Network Address Translation (PAT) and Network Address Translation (NAT) for at least the protocols below:

• All generic TCP/UDP protocols e.g., HTTP (Hyper Text Transfer Protocol);
• Internet Control Message Protocol (ICMP) ;
• File Transfer Protocol (FTP) ;
• Internet Relay Chat (IRC) ;
• Real Audio;
• Real Time Stream Protocol (RTSP) .

You can enable/disable NAT/PAT via the PPP connections configuration page.

NAT & PAT are techniques that allow you to shield or decouple your internal (private) IP addresses from the external (public) IP addresses. In addition via Port Address Translation a single public IP address can be shared by multiple users on the local LAN.

However this feature comes at the expense of the Speed Touch transparency. This because a number of protocols that are layered on top of either TCP/IP or UDP/IP do not adhere to the ISO OSI reference model.

An important consequence is that changing IP addresses or TCP/UDP ports via NAT/PAT affect the other layers. Due to these changes, applications that are the ultimate consumers of the protocols cannot decode the information correctly anymore.

The speed touch offers a few solutions to cope with this situation. Basically these solutions boil down in transporting public IP addresses transparently through the Speed Touch towards a machine where a more advanced NAT/PAT can be performed.

12.5.5.1. ATMF-25

The ATMF-25 interface offers maximum TCP/IP transparency because it switches ATM cells and does not touch TCP/IP information.

You might consider the setup below:

• Install both an ATMF-25 PC-NIC and Ethernet PC-NIC in a PC or workstation;
• Install an Operating System on this machine that has routing capabilities e.g. Windows NT, LINUX, SUN Solaris;
• Install an NAT/PAT package on this machines that supports all TCP/IP protocols;
• Connect the ATMF-25 interface to the ATMF-25 PC-NIC;
• Connect your local LAN to the Ethernet PC-NIC.

In this way the public IP address end up in this advanced "Home Gateway" where more complex NAT/PAT operations can be performed.

12.5.5.2. PPTP

A similar configuration as above can be used in combination with the Speed Touch PPP-to-PPTP relay. But instead of installing an ATMF-25 PC-NIC you must install a second Ethernet PC-NIC that connects to the Speed Touch.

By setting up a PPTP tunnel from the home gateway, again the public IP address is transported transparently through the Speed Touch.

12.5.5.3. PPP-to-DHCP Spoofing

A third technique is to use the PPP-to-DHCP Spoofing feature of the Speed Touch.

The network configuration is identical to the one described above:

• The Speed Touch is connected to a first Ethernet PC-NIC of the home gateway;
• Your local network to the second PC-NIC of the home gateway;
• The home gateway is configured as DHCP client for the Ethernet interface connected to the Speed Touch;
• The Speed Touch is configured as DHCP Server;
• DHCP in the Speed Touch must be configured for DHCP Spoofing (Advanced DHCP page);
• At least one Speed Touch PPP connection must begin with the mnemonic "DHCP" in its Phonebook name e.g. DHCP_Spoof.

As soon as a DHCP request from the home gateway hits the Speed Touch, a PPP/DHCP Spoofing connection is triggered. The IP parameters that are negotiated with the remote peer are carried up to the home gateway via a DHCP reply message.

If you want to configure the ATM network to operate in the same way as legacy LANs, Classical IP (CIP) is the best solution.

The figure below provides an overview of the general end-to-end architecture.

An important concept in CIP networks is that of a Logical IP Subnet (LIS) . A LIS is a group of hosts configured as members of the same IP subnet. In other words: they have the same IP network and subnetwork numbers.

Within a LIS, host-to-host communication is accomplished by address resolution protocols, broadcast capabilities and the shared nature of the medium. Routers do not intervene at this stage but come into action when IP connectivity is required between LISs.

In the CIP model, ATM handles the communication between IP hosts on the same LIS. The router comes only into action when connectivity between IP subnets is required, regardless of whether direct ATM connectivity is possible.

If the troubleshooting tips listed above have not resolved the problem, contact the company from which you purchased this product for assistance.

The exact functionality of the Speed Touch modem depends on the model you have purchased. Each model has a unique eight part product code. The product code is printed on one of the labels that can be found on the bottom of the Speed Touch housing.

The product code reflects the functionality of your Speed Touch as explained below.

X field

Y field

Z field

S field

H field

The supplied power supply adapter has the following output specifications:

• 9V_DC unregulated or 12 V_DC unregulated output voltage
• Maximum 1A output voltage
• Maximum 860 V_eff ripple voltage
• Limited power source (according to IEC/EN 60950, sub-clause 2.11).

This chapter explains how to download and install the Windows Dial-Up Networking 1.3 Performance and Security Upgrade for Windows 95.

Furthermore it describes how to configure and setup a dial-up connection over standard telephone lines and virtual private network connections over IP networks such as the Internet on a Windows95 platform.

The PPTP dial-up feature is not included in the standard Windows 95 installation. It can be downloaded without cost from the Microsoft website (http://www.microsoft.com).

System Requirements

The Windows 95 workstation must meet the following minimum requirements :

• Intel Pentium processor (or compatible);
• 90 MHz+;
• 16MB RAM;
• Windows compatible modem.

Download Procedure

To download the Windows Dial-Up Networking 1.3 Performance and Security Upgrade for Windows 95 :

The Dial-Up Networking 1.3 Performance & Security Upgrade (MSDUN13.exe) must be installed to be able to setup a dial-up connection to your corporate headquarters and/or your ISP.

Installation Procedure

To install the MSDUN13.exe file proceed as follows:

1. At your desktop, click on 'Start', and select 'Run' from the menu with your left mouse button.


2. The 'Run' window appears.

   Specify the path for the 'MSDUN13.exe' file in the 'Open' box (the one you specified during the download procedure).

   Press the button.



3. The system will ask if you want to start the MSDUN13 installation:

   <--  This will install Microsoft Dial-Up Networking 1.3 for Windows 95. Do you wish to continue?

   Press the button.



4. The 'End-User License Agreement' window appears.

   This license agreement must be accepted to start the installation. To do so press the button.

The installation starts. During the installation, setup will ask you to restart the machine twice. After restart, the installer will rebuild your driver twice: once for Dial-Up-Networking and once to enable virtual private networking. This is normal.

When the installation is complete, the 'Microsoft VPN Adapter' will have been added to the list of devices in the 'Make New Connection Application'.

To configure a new PPTP connection (tunnel) to your corporate network or ISP, do the following:

After having configured the connection, proceed as follows to establish the PPTP connection:

To disconnect a PPTP connection, proceed as follows :

1. Click on the appropriate button.


2. Press the button.

The network connection to your ISP no longer exists.

This chapter describes how to create and setup a PPTP dial-up connection over standard telephone lines and virtual private network connections over IP networks such as the Internet On a Windows NT platform.

	Make sure that 'Microsoft Service Pack 3' has been installed on your PC before you start creating tunnel sessions.

Before you can start creating tunnels, the PPTP Network Protocol must be added to your Windows NT platform.

To install the PPTP networking protocol, proceed as follows:

The server will inform you it needs to be restarted in order for the changes to take effect. Click on to restart.

The following procedure tells how you can create a tunnel session for use with the Corporate LAN or dial-up transport. A tunnel session contains the IP address of a PPTP server and your user account information on that server. You can create as many tunnel definitions as you need for different accounts or different PPTP servers.

To create a tunnel session to your headquarters or a PPTP server:

When the tunnel session to your VPN server has been created, proceed as follows to log on:

To uninstall a tunnel, proceed as follows :

1. Click on the appropriate button.


2. Press the button.

The network connection to your ISP no longer exists.

Corporate LANs mostly use fixed IP addresses, so consult your LAN administrator to obtain an IP address and a subnet mask.

This section describes how you can configure the IP address of your PC. The following instructions assume a Windows 95 environment:

If your ISP or Corporate Network supports DHCP, this allows your PC to acquire initialization parameters (IP addresses, masks, etc.) automatically. These initialization parameters are valid for a limited period (usually a few hours). When they expire, new parameters are obtained automatically. Therefore your PC must be properly configured to use BOOTP/DHCP.

The following instructions to enable DHCP assume a Microsoft Windows 95 environment :

In the examples throughout this document private IP addresses are used for local IP configurations. Private IP addresses are defined in RFC1918 Address Allocation for Private Internets. This RFC is categorized as "Best Current Practice".

In order to cope with IPv4 address depletion the Internet Assigned Numbers Athority (IANA) reserved blocks of IP address space for use in private internets only.

Private hosts are hosts that do not require access to hosts in other enterprises or to the Internet. Therefore it is sufficient for the host to have an IP address that is unique within the enterprise but may be ambiguous between enterprises and on the Internet.

• Private IP address:

  In principle if an IP address is assigned to a host and the connectivity is limited to intra enterprise communication only, the IP address can be assumed to be privately held. The limitation however is that communication between enterprises and connection to the Internet itself is not possible and even not allowed.

• Public IP address:

  Is an officially assigned IP address by an Internet Registry which is guaranteed to be worldwide unique. As a consequence the host to which the address is assigned has worldwide Internet connectivity.

IANA defined blocks of IP addresses for private addressing purposes only, which are:

Interference Information: Part 15 of FCC Rules

Your Alcatel product has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. However, there is no guarantee that interference will not occur in a particular installation.

If your Alcatel product causes interference to radio or television reception when it's in use, you might correct the interference with any one or all of these measures:

1. Reorient or relocate the receiving antenna.


2. Increase the separation between the equipment and receiver.


3. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

Modifications to this product not expressly approved by Alcatel could void the user's authority to operate the equipment.