Filter
Top Products
Prestige 782R G.SHDSL Router
4-2 Remote Node Configuration
4.1.2 Encapsulation and Multiplexing Scenarios
For Internet access you should use the encapsulation and multiplexing methods used by your ISP. For
LAN-to-LAN applications, e.g., branch office and corporate headquarters, prior agreement on methods is
necessary because encapsulation and multiplexing cannot be automatically determined. Which methods to
use depends on how many VCs you have and how many different network protocols you need. The extra
overhead that 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.
Scenario 1. One VC, Multiple Protocols
PPP (RFC-2364) encapsulation with VC-based multiplexing is the best combination because no extra
protocol identifying headers are needed. The PPP protocol already contains this information.
Scenario 2. One VC, One Protocol (IP)
Selecting 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 do not need to reconfigure either computer later.
Scenario 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= RFC-1483
Multiplexing= LLC-based
Incoming:
Rem Login= N/A
Rem Password= N/A
Outgoing:
My Login= N/A
My Password= N/A
Authen= N/A
Route= IP
Bridge= No
Edit PPP Options= No
Rem IP Addr= 0.0.0.0
Edit IP/IPX/Bridge= No
Edit ATM Options= No
Session Options:
Edit Filter Sets= No
Press ENTER to Confirm or ESC to Cancel:
Press Space Bar to Toggle.