TITLE: IPX Over Point to Point Connection Using Point to Point Protocol (PPP) 
DATE: August 20, 1999 

PURPOSE: 

This  procedure is for connecting Lucent PortMaster (TM) products over a Point to Point connection. 

FOR THE FOLLOWING MODELS: 

Each of the following models are equipped with synchronous ports that can be used as Wide Area Network (WAN) interfaces. The synchronous ports for each unit are listed. 

PM2R,   W1
PM2ER,  W1
IRX211, S1
IRX111, S1
IRX112, S1,S2
IRX114, S1,S2,S3,S4
OR-LS,  W1
OR-HS,  W1

SUMMARY: 

To set up Internet Packet eXchange (IPX) over a WAN,  assign the WAN ports a common IPX network number. 

Command> set w1 ipxnet feedfefe

Additional Information:  If you only want IPX over your WAN set up Internet Protocol (IP). IP allows easier administrative access to debug, telnet, ping and other tools. 

  IP NET: 192.168.1.0/24
  IPX NET: FEEDFEFE
  ====ETHERNET======================
                 |
                 | E0 IP: 192.168.1.100
           +-----+-----+
           |     E0    |
           | ROUTER A  |
           |     W1    |
           +-----+-----+
                 |
                 |
                 |
                 |   WAN-IPX NET: C0A86400
                 |                        
                 |                
                 |
           +-----+-----+           
           |     W1    |           
           | ROUTER B  |           
           |     E0    |           
           +-----+-----+           
                 |E0 IP: 192.168.2.200
                 |                  
          ===========ETHERNET==          
          IP NET:192.168.2.0/24   
          IPX NET: C0A80200       
                        

BEFORE YOU START: 
1) Pick your IPX network numbers and framing types. 
IPX network numbers are 8 digit hex numbers. You generally pick whatever number you like as long as it does not overlap with another IPX network number on your system. If you are running a Novell server  you will want to use the external network number found in the Novell server auotexec.ncf file. 
2) Be sure to have two separate ip subnets and IP addresses for each router. Each side of the point to point connection must have its own IP subnet that does not overlap with another IP subnet. 

These IP network address are given to you by your Internet Service Provider, your leased line carrier or by the Internic (http://www.internic.net/). 
If you do not plan to connect your network to the Internet you can use an IP network address set aside for private use. The IP network address for private use can be found in RFC1597. The most commonly used network address is IP 192.168.0.0. 
3) Verify that you are using V.35 cable to connect the PortMaster synchronous port to the CSU/DSU 
4) Verify that the CSU/DSU is configured for external clock. 
5) Verify that you have a point to point line. 

CONFIGURING THE WAN PORTS: 

In this example assume the following: 
- PortMaster A has an ethernet IP address of 192.168.1.100 with a netmask of 255.255.255.0 
- PortMaster B has an ethernet IP address of 192.168.2.200 with a netmask of 255.255.255.0 
- PortMaster A is providing Internet access to PortMaster B. 
- The WAN ports on both PortMaster routers is represented by W1. 
- PortMaster  A has an ethernet IPX network of FEEDFEFE 
- PortMaster  B has an ethernet network of C0A80200 
- The WAN has an IPX network number of C0A86400. 
- Both PortMaster products are using ethernet 802.3 IPX framing type. 

The IP addresses used in this example are for example only, you will need to use an IP network provided to you by your Internet Service Provider. 

# PortMaster A

# sample ethernet configuration:
Command> set address 192.168.1.100                 
# set ethernet IP address
Command> set netmask 255.255.255.0
Command> set ether0 ipxnet FEEDFEFE                
# set IPX network for ethernet 
Command> set ether0 ipxframe _802.3        
# set IPX framing type

# sample WAN configuration 
Command> set w1 network hardwire
Command> set w1 address 0.0.0.0                    
# this is for unnumbered, no address required for WAN port
Command> set w1 destination 192.168.2.200          
# set the destination to the 0
# port of the router at opposite end
Command> set w1 ipxnet C0A86400                    
# The WAN IPX network number
Command> set w1 netmask 255.255.255.0
Command> set w1 modem on                           
# This can be on or off
Command> set w1 protocol ppp
Command> set w1 routing on                         
# This defines Routing Information Protocol (RIP)
Command> set w1 mtu 1500                           
# Maximum Transfer Unit

Command> save all
Command> reboot                                    
# 0 need to reboot to load IPX module. 

# PortMaster B

Command> set address 192.168.2.200                 
# set ethernet ip address
Command> set netmask 255.255.255.0
Command> set ether0 ipxnet C0A80200                
# set IPX network for ethernet  
Command> set ether0 ipxframe _802.3        
# set IPX framing type

Command> set gateway 192.168.1.100                 
# IP address of upstream router
 
Command> set w1 network hardwire
Command> set w1 address 0.0.0.0                    
# this is for 1, no address required for wan port
Command> set w1 destination 192.168.2.200            
# set the destination to the ethernet port of the router at opposite end
Command> set w1 ipxnet C0A86400                    
# The WAN IPX network number
Command> set w1 netmask 255.255.255.0
Command> set w1 modem on                           
# This can be on or off
Command> set w1 protocol ppp
Command> set w1 routing on                         
# This defines RIP
Command> set w1 mtu 1500                           
# Maximum Transfer Unit

Command> save all
Command> reboot                                    
# PortMaster needs to reboot to load IPX module

DEBUGGING TOOLS: 

Point To Point Protocol (PPP) Negotiation Debug 

The following debug will allow you to watch the WAN ports negotiate Point to Point Protocol (PPP). PPP  negotiates Line Control Protocol  (LCP) first, then negotiates Network Control Protocol (NCP) including IPX Control Protocol (IPXCP). 

Command> set console
Command> set debug 0x51

To turn the debug off: 

Command> reset console
Command> set debug

Packet filter to watch Internetwork Packet eXchange (IPX) packets. 

This packet filter will show all Internetwork Packet eXchange (IPX) packets passing through the 0. It will NOT show IPX packets 1 from the 0. 

Command> add filter seeipx
New Filter successfully added
Command> set ipxfilter seeipx 1 permit
Filter seeipx updated
Command> set console
Setting CONSOLE to admin session
Command> ptrace seeipx
Packet Tracing Enabled

# Example of a ptrace output:
IPX from 00000008:0000C06F195C:0455 to 00000008:
FFFFFFFFFFFF:0455
IPX from 00000008:0000C06F195C:0553 to 00000008:
FFFFFFFFFFFF:0553
IPX from 00000008:0000C06F195C:0455 to 00000008:
FFFFFFFFFFFF:0455
IPX from 00000008:0000C06F195C:0553 to 00000008:
FFFFFFFFFFFF:0553

To turn the filter off: 

Command> ptrace
Packet Tracing Disabled
Command> reset console
Console RESET

IPX packets are represented in the following format: 
[8 digit network number]:[12 digit node address]:[4 digit socket number] 
- All F's for a "to" address represents a broadcast to entire network. 

Common Socket Numbers: 
0451 = Netware Core protocol 
0452 = SAP 
0453 = RIP (Routing protocol) 
0455 - Netbios packet 
0457 = Serialization (Novell Licensing) 
0456 = Diagnostic Packet 
4000-8000 = Source sockets dynamically assigned by workstations 

Packet filter to watch pings (Internet Control Message Protocol (ICMP) packets). 

This packet filter will show all pings passing through the PortMaster it is running on. It will NOT show pings originating from the PortMaster. 

Command> add filter p
New Filter successfully added
Command> set filter p 1 permit icmp
Filter p updated
Command> set console
Setting CONSOLE to admin session
Command> ptrace p
Packet Tracing Enabled

# Example of a ptrace output:
icmp from 10.0.0.10 to 10.0.0.1 type Echo Request
icmp from 10.0.0.10 to 10.0.0.1 type Echo Request
icmp from 10.0.0.10 to 10.0.0.1 type Echo Request
icmp from 10.0.0.10 to 10.0.0.1 type Echo Request

To turn the ptrace  off: 

Command> ptrace
Packet Tracing Disabled
Command> reset console
Console RESET

TROUBLESHOOTING: 

If the port does not have an "ESTABLISHED" status do the following: 

Command> set console
Setting CONSOLE to admin session
Command> set debug 0x51
Setting debug value to 0x51

If you see LCP Configure Request packets being transmitted but none being received, do the following: 

Put the CSU/DSU into a local loopback. This will cause each packet sent to the CSU/DSU to be reflected back to the WAN port. This is for testing purposes only, the line will not function while the CSU/DSU is in a local loopback.  "LCP: Apparent Loop" will verify that you know the following: 
1 - The WAN port on the PortMaster is transmitting and receiving data. 
2 - The cable and connectors between the PortMaster and the CSU/DSU are OK. 
3 - The Data Terminal Equipment (DTE) port on the CSU/DSU is OK.. 
4 - THE PORTMASTER IS FUNCTIONING AS IT SHOULD. 

If you do not get apparent loops: 
1 - Verify that the RS232-V.35 dip switch next to the WAN port is set correctly, (usually v.35) 
2 - Verify that all cables are securely connected. 
3 - Verify that the V.35 cable that came with the unit is being used. 
4 - Swapping cables, CSU/DSU equipment, etc. is another method used to isolate trouble. 

If you get apparent loops and the status is not "ESTABLISHED" 
1 - Check the CSU/DSU settings, clocking, etc. In most cases the CSU/DSU should be set for external clocking. The Telco provides the clock source.  Verify the CSU/DSU settings with the manufacturer. 
2 - Have the telephone carrier test the line. 

If the port status is "ESTABLISHED" but you cannot ping the other side. 
1 - Verify that the IP address for the WAN ports on both sides are in the same subnet if doing Point To Point (PTP) numbered. 
2 - Traceroute from your workstation at PortMaster to the router in trouble. Then  traceroute from the router in trouble (assuming you can get to it) back to your workstation. The problem will lie in the gap between the two traceroutes. 
3 - Verify that  the "set gateway" is set to the upstream router. 

Cannot see IPX over link or cannot get a Server List (SLIST=Novell terminology) of Netware servers. 
1 - List the IPX routing table. 
You should see a list of IPX routes and where they are being routed to. 

Command> show ipxroute
Network   Gateway               Flag Met Ticks Interface
--------  --------------------- ---- --- ----- ---------
00000008  00000008:00C005001C19 NLC    1     1 ether0
0A000100  0A000100:00C005001C19 NLC    1     1 ether1

Routing Table Flags: 
H = Host route 
N = Network route 
L = Network is directly connected 
S = Route was added manually 
D = Route was learned by using RIP (IP udp/520, IPX 0453) 
C = Changed recently but not yet propagated using RIP 
O = Obsolete, Marked for deletion 

2 - If the first entry has 'NS' flags (standing for network static) then reset your IPX gateway. It is rare to set and IPX  gateway. 

NOTE: After resetting the IPX gateway "reboot" to clear the routing table. 

Command> show ipxroute
Network   Gateway               Flag Met Ticks Interface
--------  --------------------- ---- --- ----- ---------
00000000  00000008:00C005001C19 NS     1     0 ether0
00000008  00000008:00C005001C19 NLC    1     1 ether0
0A000100  0A000100:00C005001C19 NLC    1     1 ether1
Command> set ipxgateway 00000000:000000000000
IPX gateway reset
Command> save all
Command> reboot

3 - Show Service Access Protocol (SAP) table and check for entries coming from other side. 
The "Interface" column will show where the SAP packet came from.  [WAN network,  ethernet or from itself]. 

Command> show sap
Server       Svc Network  Host         Sock Hops Interface
------------ --- -------------------------- ---- ---------
tie          5F2 000000AA:00C0050101B2:066B    1 ptp1
ywing        5F2 00000008:00C0050161A7:066B    1 ether0
xwing        5F2 00000008:00C00501200E:066B    1 ether0
falcon       5F2 000000AA:00C005021D12:066B    1 ptp1
calamari     5F2 00000008:00C005001C19:066B    0 Internal

If you see SAP's from the other side  you have your PortMasters configured correctly. 

4 - Set up IPX packet traces (see above) on both ends of the WAN to verify exactly what the packets are doing.