Prestige P645 ADSL Internet Access Router

VC-Based Multiplexing

Remember that for VC-basedmultiplexing, by prior mutual agreement, a protocol is assigned a specific virtual circuit, e.g., VC1 will carry IP, VC2 will carry IPX etc.

Menu 11.3 - Remote Node Network Layer Options

 

 

IPX Options :

 

 

Rem LAN Net #= N/A

 

 

My WAN Net #= N/A

IP Options:

 

Hop Count= N/A

Rem IP Addr: 0.0.0.0

Tick Count= N/A

Rem Subnet Mask= 0.0.0.0

W/D Spoofing(min)= N/A

IP Address Assignment = Dynamic

SAP/RIP Timeout(min)=N/A

My WAN Addr= 0.0.0.0

Dial-On-Query= N/A

Single User Account= No

VPI #= N/A

Metric= 2

 

VCI #= N/A

Private= No

 

 

RIP Direction= Both

Bridge Options:

Version= RIP-2B

Dial-On-Broadcast= N/A

Multicast= None

 

Ethernet Addr Timeout(min)= N/A

IP Policies=

 

VPI #= N/A

VPI #= 0

 

VCI #= N/A

VCI #= 35

Enter here to Confirm

Or ESC to Cancel:

Press Space Bar to Toggle.

Figure 5-2 Menu 11.3 for VC-based multiplexing with RFC 1483 and ENET ENCAP

In this case, separate VPI and VCI numbers must be specified for each protocol.

LLC-based multiplexing

For LLC-basedmultiplexing, one VC carries multiple protocols with protocol identifying information being contained in each packet header.

5-2

Remote Node TCP/IP Configuration