ZyXEL Communications Prestige 642 - Manual (Page 73)

Prestige 642 ADSL Internet Access Router
4-2 Remote Node Configuration
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-based multiplexing is the best combination because the extra
protocol identifying headers that LLC-based multiplexing uses is unneeded. The PPP protocol already
contains this information.
Scene 2. One VC, One Protocol (IP)
Select RFC-1483 encapsulation 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-1483
encapsulation and VC-based multiplexing.
Figure 4-2 Menu 11.1 Remote Node Profile
Menu 11.1 - Remote Node Profile
Rem Node Name= nodename
Active= Yes
Encapsulation= PPP
Multiplexing= VC-based
Incoming:
Rem Login=
Rem Password=********
Outgoing:
My Login= oscar
My Password= ********
Authen= CHAP/PAP
Route= IP
Bridge= No
Edit PPP Options= No
Rem IP Addr= 0.0.0.0
Edit IP/IPX/Bridge= No
Session Options:
Edit Filter Sets= No
PPPoE Idle Timeout(sec)= 100
PPPoE Service Name= N/A
Enter here to CONFIRM or ESC to CANCEL:
Enter the IP address
of the remote
gateway here.
Enter a unique name
of less than 8
characters for the
remote name.