ZyXEL Communications 641 Encapsulation & Multiplexing Scenarios, Scene 2. One VC, One Protocol IP

Prestige 641 ADSL Internet Access Router

4.1.2Encapsulation & Multiplexing Scenarios

For Internet Access you should use the encapsulation and multiplexing methods used by your ISP. For a LAN-to-LAN application, e.g., branch office and corporate headquarters, prior mutual agreement on methods used is necessary because there is no mechanism to automatically determine encapsulation/multiplexing. Selection of which encapsulation and multiplexing methods to use depends on how many VCs you have and how many different network protocols you need. The extra overhead that PPP over Ethernet (PPPoE) and ENET ENCAP encapsulation entail makes them a poor choice in a LAN-to- LAN application. Here are some examples of more suitable combinations in such an application.

Scene 1. One VC, Multiple Protocols

PPP(RFC 2364) encapsulation with VC-basedmultiplexing is the best combination because the extra protocol identifying headers that LLC-basedmultiplexing uses is unneeded. The PPP protocol already contains this information.

Scene 2. One VC, One Protocol (IP)

Select RFC-1483encapsulation with VC-based multiplexing requires the least amount of overhead (0 octets). However, if there is a potential need for multiple protocol support in the future, it may be safer to select PPP encapsulation instead of RFC-1483, so you don’t need to reconfigure either machine when the time comes.

Scene 3. Multiple VCs

If you have an equal number (or more) of VCs than the number of protocols, then select RFC-1483encapsulation and VC-basedmultiplexing.

Menu 11.1 - Remote Node Profile

Rem Node Name= nodename	Route= None
Active= Yes	Bridge= No
Encapsulation= PPP	Edit PPP Options= No
Multiplexing= VC-based	Rem IP Addr= 0.0.0.0
Incoming:	Edit IP/IPX/Bridge= No
Rem Login=?
Rem Password=?	Session Options:
Outgoing:	Edit Filter Sets= No
My Login= oscar
My Password= ********
Authen= CHAP/PAP

Enter here to CONFIRM or ESC to CANCEL:

Enter a unique name of less than 8 characters for the remote name.

Enter the IP address of the remote gateway here.

Figure 4-2 Menu 11.1 Remote Node Profile

4-2 Remote Node Configuration