|
|
The IPeXchange Internet Gateway connects Novell NetWare or other IPX-based users to the Internet or other TCP/IP-based network services. IPeXchange allows workstations to use TCP/IP-based applications such as Telnet, FTP, and Netscape Navigator without requiring a TCP/IP protocol stack on each workstation. Instead, the IPeXchange Internet Gateway provides a TCP/IP gateway with a single IP address for the entire IPX network.
The IPeXchange Internet Gateway is a client/server product.
The server is a Cisco router that runs the Cisco IOS software as the IPeXchange server software. The server, which is sometimes referred to as a gateway, is connected to both an IPX network and a TCP/IP-based network, such as the Internet.
An IPeXchange client is a Windows 3.x-based or Windows 95-based PC that runs the IPeXchange client software. The PC is connected to an IPX network.
Figure 12 illustrates the relationship between the IPeXchange components.
The IPeXchange Internet Gateway offers the following benefits:
This feature is supported on the Cisco 2500 series platform.
To use the IPeXchange Internet Gateway, you must set up your router to route the IPX protocol. You must also configure one or more IPeXchange Internet Gateway clients.
To learn more about configuring your router for IPX routing, see the Cisco IOS Release 11.2 Network Protocols Configuration Guide, Part 2.
To learn more about configuring the IPeXchange client software, see the Cisco IPeXchange Internet Gateway User Guide.
This section describes configuration tasks associated with configuring and monitoring the IPeXchange Internet Gateway.
To enable the IPeXchange Internet Gateway server software on the router, perform the following tasks beginning in global configuration mode:
To monitor the IPeXchange Internet Gateway, perform one or more of the following tasks in EXEC mode:
The following configuration commands enable the IPeXchange Internet Gateway on Ethernet interface 0. The configuration assigns the router an IPX internal network number of 2abc. It also assigns both an IP address and an IPX network number to the interface. Finally, it sets up the private service, myownservice, on TCP port number 2311.
ipx routing ipx internal-network 2abc interface ethernet 0 ip address 131.22.1.1 ipx network AB45EC20 ipx ip-gateway ethernet 0 ip service tcp myownservice 2311
This section documents the following new commands:
All other commands used with this feature are documented in the Cisco IOS Release 11.2 command references, or in the Cisco IPeXchange Internet Gateway User Guide.
To add new TCP or UDP private services to the router services file, use the ip service interface configuration command. To remove TCP or UDP services, use the no form of this command.
ip service [tcp | udp] service-name port-number| tcp | (Optional) Specifies services to be added using the TCP transport function. |
| udp | (Optional) Specifies services to be added using the UDP transport function. |
| service-name | Name of the private service to be added. |
| port-number | The TCP/IP port number of the service. The range is 0 to 65535. |
Interface configuration
This command first appeared in Cisco IOS Release 11.2 F.
The ip service command adds new private services to the router services file. The router services file defines the TCP or UDP services that the IPeXchange gateway provides to IPeXchange clients. It also defines the port on which each service is provided. Well-known TCP and UDP services (such as Telnet and FTP) are automatically available, and need not be added.
The services file is similar to the /etc/services file commonly found on a UNIX workstation. This file is required so that the IPeXchange gateway can respond to requests for services from clients on the TCP/IP network to which the gateway is connected. The services file on the IPeXchange gateway contains default mappings of well-known services to their port numbers.
The port number assigned to a new private service must be unique. If the port number assigned to the new private service has been previously assigned, the new assignment will override the initial assignment. Because well-known service port numbers are defined in the range of 0 to 1024, it is recommend that all private services use port numbers above 1024.
Use the show ip services command to see a list of assigned port numbers.
The following example adds the private TCP service myownservice and assigns it to TCP port number 2311:
ip service tcp myownservice 2311
ipx ip-gateway
show ip services
show ipx ip-gateway status
show ipx servers
To activate the IP-IPX gateway function, use the ipx ip-gateway global configuration command. To disable the function, use the no form of this command.
ipx ip-gateway interface| interface | The name and number of the interface that is connected to the Internet or other TCP/IP-based network. |
The IP-IPX gateway is disabled.
Global configuration
This command first appeared in Cisco IOS Release 11.2 F.
The ipx ip-gateway command is used to activate the IPeXchange Internet Gateway software on the router. The IPeXchange Internet Gateway connects Novell NetWare or other IPX-based users to the Internet or other TCP/IP-based network services. IPeXchange allows workstations to use TCP/IP-based applications such as Netscape Navigator, Telnet, and FTP without requiring a TCP/IP protocol stack on each workstation.
The IPeXchange Internet Gateway is a client/server product. The server is a Cisco router that runs the Cisco IOS software as the IPeXchange server software. The server, which is sometimes referred to as a gateway, is connected to both an IPX network and a TCP/IP-based network.
An IPeXchange client is a Windows 3.x-based or Windows 95-based PC that runs the IPeXchange client software. The PC is connected to an IPX network.
The following example activates the IP-IPX gateway function on Ethernet interface 0:
ipx ip-gateway ethernet 0
ip service
show ip services
show ipx ip-gateway status
show ipx servers
To display the entries in the router services file, use the show ip services user EXEC command.
show ip servicesThis command has no arguments or keywords.
User EXEC
This command first appeared in Cisco IOS Release 11.2 F.
The router services file is similar to the /etc/services file commonly found on a UNIX workstation. This file defines the TCP or UDP services that the IPeXchange gateway provides and the port on which that service is provided. This file is required so that the IPeXchange gateway can respond to requests for services from clients on the TCP/IP network to which the gateway is connected. The services file on the IPeXchange gateway contains default mappings of well-known services to their port numbers. It also contains private services that have been added using the ip service command.
The following is sample output from the show ip services command:
Router> show ip services
Default configured services:
Services Type Port
bgp tcp 179
chargen tcp 19
cmd tcp 514
daytime tcp 13
discard tcp 9
domain tcp 53
echo tcp 7
Table 8 describes the fields shown in the display.
| Field | Description |
|---|---|
| Services | Name of the TCP or UDP service. |
| Type | Protocol type of the service. |
| Port | Port number that has been assigned to the service. |
Table 9 provides a complete list of all default configured services.
| Service | Type | Port |
|---|---|---|
| bgp | TCP | 179 |
| chargen | TCP | 19 |
| cmd | TCP | 514 |
| daytime | TCP | 13 |
| discard | TCP | 9 |
| domain | TCP | 53 |
| echo | TCP | 7 |
| exec | TCP | 512 |
| finger | TCP | 79 |
| ftp | TCP | 21 |
| ftp-data | TCP | 20 |
| gopher | TCP | 70 |
| irc | TCP | 194 |
| hostname | TCP | 101 |
| klogin | TCP | 543 |
| kshell | TCP | 544 |
| login | TCP | 513 |
| whois | TCP | 43 |
| nntp | TCP | 119 |
| pop2 | TCP | 109 |
| pop3 | TCP | 110 |
| lpd | TCP | 515 |
| smtp | TCP | 25 |
| sunrpc | TCP | 111 |
| syslog | TCP | 514 |
| tacacs | TCP | 49 |
| talk | TCP | 117 |
| telnet | TCP | 23 |
| uucp | TCP | 540 |
| www | TCP | 80 |
| bgp | UDP | 179 |
| chargen | UDP | 19 |
| cmd | UDP | 514 |
| daytime | UDP | 13 |
| discard | UDP | 9 |
| domain | UDP | 53 |
| echo | UDP | 7 |
| exec | UDP | 512 |
| finger | UDP | 79 |
| ftp | UDP | 21 |
| ftp-data | UDP | 20 |
| gopher | UDP | 70 |
| irc | UDP | 194 |
| hostname | UDP | 101 |
| klogin | UDP | 543 |
| kshell | UDP | 544 |
| login | UDP | 513 |
| whois | UDP | 43 |
| nntp | UDP | 119 |
| pop2 | UDP | 109 |
| pop3 | UDP | 110 |
| lpd | UDP | 515 |
| smtp | UDP | 25 |
| sunrpc | UDP | 111 |
| syslog | UDP | 514 |
| tacacs | UDP | 49 |
| talk | UDP | 117 |
| telnet | UDP | 23 |
| uucp | UDP | 540 |
| www | UDP | 80 |
ip service
ipx ip-gateway
show ipx ip-gateway status
show ipx servers
To display information about the status of the IPeXchange Internet Gateway router, use the show ipx ip-gateway status user EXEC command.
show ipx ip-gateway statusThis command has no arguments or keywords.
User EXEC
This command first appeared in Cisco IOS Release 11.2 F.
The following is sample output from the show ipx ip-gateway status command:
Router> show ipx ip-gateway status
====================================================
Cisco IPeXchange Gateway - Connection Relay Stats.
1 Client(s) Connected.
3 Socket(s) Opened.
4 Client Session(s) Opened.
****** Connected Clients **(START)***
Client Addr:IPX Net#:AB.45.EC.0:Node#:0.A0.24.92.1.54: CtlConv 871
****** Connected Clients **(END)***
====================================================
Cisco IPeXchange Gateway - Connection Manager Stats.
7 Connections Opened.
Gateway Name :IJ-FR
Gateway Address :882F @IPX Net#:C.33.A.DE:Node#:0.0.0.0.0.1:
Hops : 0
Age : 8281 sec
Selected Packet size : 1500 bytes
IPX ucast packet counts: in:42951, out:41747
IPX bcast packet counts: in:8, out:8
====================================================
Cisco IPeXchange Gateway.
Gateway Type : Cisco IOS
Gateway Version : 1.2.1
Gateway Hostname : IJ-FR
Gateway IP address : 171.69.236.46
Gateway IPX address : C330ADE.0000.0000.0001
Number of users support : 50
Table 10 describes the fields that are shown in the display.
| Field | Description |
|---|---|
| Client(s) Connected | Number of clients connected to the gateway. |
| Socket(s) Opened | Number of open TCP and UDP sockets. |
| Client Session(s) Opened | Number of open TCP and UDP sessions. |
| Client Addr:IPX Net#: | Network number of the client. |
| Node#: | MAC address of the client. |
| Gateway Name | Host name of the router. |
| Gateway Address | Internal IPX network number assigned to the router. |
| Hops | Distance to the IPX internal network (always 0 on the router). |
| Age | Age of the router entry. |
| Selected Packet size | Size of packets being sent between the client and the gateway. |
| IPX ucast packet counts | Number of unicast packets that have been sent or received by the gateway. |
| IPX bcast packet counts | Number of broadcast packets that have been sent or received by the gateway. |
| Gateway Type | Always set to Cisco IOS. |
| Gateway Version | Version of the IPeXchange Internet Gateway software. |
| Gateway Hostname | Host name of the router. |
| Gateway IP address | IP address assigned to the gateway interface. |
| Gateway IPX address | IPX network number assigned to the gateway interface. |
| Number of users support | Maximum number of concurrent clients that can connect via this gateway. |
ip service
ipx ip-gateway
show ip services
show ipx servers
This section documents the new debug command associated with the IPeXchange Internet Gateway.
Use the debug ipx ip-gateway EXEC command to display information about Internetwork Packet Exchange (IPX)-to-IP conversions. The no form of this command disables debugging output.
[no] debug ipx ip-gateway {dns | netif | socket}
| dns | Displays information about calls to the Domain Name System (DNS) server. |
| netif | Displays information on network interface calls between clients and the router. |
| socket | Displays information about the socket level interface between clients and the router. |
Figure 13 shows sample debug ipx ip-gateway dns command output when a client requests the IP address of a device during a Telnet session.
router# debug ipx ip-gateway dns
DNS: DNS process was woken up!..
DNS: Queue has a element
DNS: The Msg is 22F3AA8
crPrcMsgInThread : Msg is 23CAF30
crIosHostInfo : pMsg : 23422E4, *pMsg is 23CAF30
Get_host_by_name :Name engr40.scudc.scu.edu
fPrcDns: processing in crIosHostInfo
DNS: DNS process was woken up!..
DNS: Queue has a element
Recvd a response 53-9769
Got a Name response..
DOM: hostname is engr40.scudc.scu.edu, RR type=1, class=1, ttl=79468, n=4
DOM: address is 129.210.120.40
The first three lines indicate that the DNS server has a request in its queue. The packet containing the request is located at the memory address 22F3AA8.
DNS: DNS process was woken up!.. DNS: Queue has a element DNS: The Msg is 22F3AA8
The next four lines indicate that a DNS module is processing the name request.
crPrcMsgInThread : Msg is 23CAF30 crIosHostInfo : pMsg : 23422E4, *pMsg is 23CAF30 Get_host_by_name :Name engr40.scudc.scu.edu fPrcDns: processing in crIosHostInfo
The next four lines indicate that the module has replied to DNS with the IP address. The client's port is 9769, and the standard port number for a DNS server is 53.
DNS: DNS process was woken up!.. DNS: Queue has a element Recvd a response 53-9769 Got a Name response..
The final two lines describe the DNS reply packet.
DOM: hostname is engr40.scudc.scu.edu, RR type=1, class=1, ttl=79468, n=4 DOM: address is 129.210.120.40
Figure 14 shows sample debug ipx ip-gateway netif command output during a normal exchange of packets between the router and a client.
router# debug ipx ip-gateway netif
Netif: Sendto: C330ADE.0000.0000.0001->AB45EC20.00a0.2491.f57e len=178
Netif: Recvfrom: Et0:AB45EC20.00a0.2491.f57e->C330ADE.0000.0000.0001 len= 58
Netif: Sendto: C330ADE.0000.0000.0001->AB45EC20.00a0.2491.f57e len=146
Netif: Recvfrom: Et0:AB45EC20.00a0.2491.f57e->C330ADE.0000.0000.0001 len= 58
The first line indicates that the router, which has a gateway address of C330ADE.0000.0000.0001, is sending a packet to its client at AB45EC20.00a0.2491.f57e. The packet is 178 bytes long.
Netif: Sendto: C330ADE.0000.0000.0001->AB45EC20.00a0.2491.f57e len=178
The second line shows the client sending a packet to the router on the Ethernet interface.
Netif: Recvfrom: Et0:AB45EC20.00a0.2491.f57e->C330ADE.0000.0000.0001 len= 58
Figure 15 shows sample debug ipx ip-gateway socket command output.
router# debug ipx ip-gateway socket
send (in) (s=37219380,buf=41490256,len=900,flags=NULL)
send (out) (rc=900)
connect (in) (s=37277476, addr fam: 2 Port 80 Ipaddr 171.69.73.92, adrlen=16)
connect-(out) (rc=-1)
socket (in) (af=2,type=1,proto=6)
socket (out) (rc=37233816)
setsockopt (in) (s=37233816,level=65535,optname=4097,optval,optlen=4)
setsockopt (out) (s=37233816,level=65535,optname=4097,optval,optlen=4,rc=0)
close (in) (s=37219380)
close (out) (rc=0)
Table 11 describes possible debug ipx ip-gateway socket command output fields.
| Field | Description |
|---|---|
| send | Indicates that the router is sending a packet out to the IP network. |
| recv | Indicates that the router has received a packet from the IP network. |
| connect | Indicates that the router is opening a TCP/IP connection for a client. |
| socket | Indicates that the router is creating a socket. |
| setsockopt | Indicates that the router is setting the socket options |
| close | Indicates that the router is closing a TCP/IP connection for a client. |
| bind | Indicates that the router is binding a socket to a port. |
| listen | Indicates that the router has more packets than it can process. The output lists the number of packets waiting. |
| accept | Indicates that the router is accepting a connection from a client. |
| gethostname | Indicates that the router is getting the name of a host. |
| gethostbyname | Indicates that the router is getting the address information of a host by its name. |
| getservicebyname | Indicates that the router is getting the socket information about a service by its name. |
| getsockname | Indicates that the router is getting the name associated with a socket. |
| getprotobyname | Indicates that the router is getting the protocol number of a protocol, given the name of the protocol. |
| getpeername | Indicates that the router is getting the name of a peer. |
| send(in) | Indicates the information sent to the send routine. |
| send(out) | Indicates that information returned from the send routine. |
| s= | Memory location of the socket structure. |
| buf= | Memory location of the buffer containing the information. |
| len= | Length of the packet. |
| flags= | Special flags. |
| rc= | Return code. |
| af= | Address family. |
| type= | Type of connection. |
| proto= | Protocol. |
| level= | Protocol level affected by the option. |
For more information on configuring the IPeXchange client software, see the Cisco IPeXchange Internet Gateway User Guide.
|
|