embedaddon/mpd/doc/mpd19.html - view

File: [ELWIX - Embedded LightWeight unIX -] / embedaddon / mpd / doc / mpd19.html
Revision 1.1.1.4 (vendor branch): download - view: text, annotated - select for diffs - revision graph
Wed Mar 17 00:39:23 2021 UTC (3 years, 3 months ago) by misho
Branches: mpd, MAIN
CVS tags: v5_9p16, v5_9, HEAD

mpd 5.9

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>Mpd Layers</TITLE> </HEAD> <BODY text="#000000" bgcolor="#ffffff"> <A HREF="mpd.html">Mpd 5.9 User Manual</A> : <A HREF="mpd17.html">Configuring Mpd</A> : Mpd Layers  Previous: <A HREF="mpd18.html">General mpd commands</A>  Next: <A HREF="mpd20.html">Link layer</A> <HR NOSHADE> <H2><A NAME="19"></A>4.2. Mpd Layers<A NAME="layers"></A></H2> Mpd consists of several layers, corresponding to the layered nature of the PPP protocol. There are two types of layers hierarchy connected with two different operation modes as "ppp terminator" and "ppp repeater". Operation mode is getting chosen dynamically depending on link configuration and user auth name (see 'set link action ...' command). In "ppp terminator" mode such hierarchy used:  <A HREF="mpd28.html#interface">Interface</A> ->  <A HREF="mpd26.html#ipcp">NCPs</A> ->  <A HREF="mpd24.html#compression">Compression</A> ->  <A HREF="mpd23.html#encryption">Encryption</A> ->  <A HREF="mpd22.html#bundle">Bundle</A> ->  <A HREF="mpd20.html#links">Links</A> In "ppp repeater" mode different hierarchy used:  <A HREF="mpd20.html#links">Link1</A> -> Repeater ->  <A HREF="mpd20.html#links">Link2</A> A  <A HREF="mpd20.html#links">link</A> is a single point-to-point connection between the local machine and a remote peer machine, implemented by some kind of physical device, such as a serial modem connection or a virtual PPTP connection. Link parameters include whether authentication is enabled in either direction, the authentication type (PAP or CHAP) used, keep-alive packets, multilink negotiation options and various other link specific parameters. Lower half of the link layer is the physical devices layer. Configuration of device type specific parameters happens at this layer. Each device has a specific type corresponding to one of the supported device types in mpd. The type dictates how the device dependent part is configured and what it's capabilities are. A  <A HREF="mpd22.html#bundle">bundle</A> is a collection of one or more links, all connecting to the same remote peer, that together form a single multi-link PPP connection whose effective bandwidth is the sum of the bandwidths of the individual links. The bundle layer in effect lies just above the link layer. The bundle layer handles the task of making multiple physical links appear as a single virtual link. At the bundle layer you configure multi-link PPP settings and the link management policy. The link management policy determines whether mpd tries to keep all the links connected all the time, or whether it adds and subtracts links depending on demand, and if so, according to what parameters. With each bundle is a corresponding  <A HREF="mpd28.html#interface">interface</A> layer, which corresponds directly to a system network interface accessible via <code>ifconfig(8)</code>, such as <code>ng0</code>. The interface layer handles configuring the interface, bringing it up or down as appropriate, assigning IP addresses, setting up static routes and configuring proxy-ARP. The interface layer is also responsible for implementing Dial-on-Demand and idle timeout functionality. Each bundle has several corresponding NCP layers as  <A HREF="mpd26.html#ipcp">IP Control Protocol (IPCP)</A> and  <A HREF="mpd27.html#ipv6cp">IPv6 Control Protocol (IPv6CP)</A>, which manages the protocol specific configuration of the interface. This layers handle the negotiation of local and remote addresses and TCP header compression, as well as other optional IP related information such as DNS servers and NBNS servers. Each bundle also has corresponding  <A HREF="mpd24.html#compression">compression (CCP)</A> and  <A HREF="mpd23.html#encryption">encryption (ECP)</A> layers, which allow you to enable and configure compression and encryption for data sent and received over the bundle. A repeater is a collection of two physical devices (links). It is getting created when there is need to forward connection coming from one physical device to another without modification. This technology is also known as LAC (L2TP Access Concentrator) and PAC (PPTP Access Concentrator). While the combination of all the various layers presents a large number of configuration options, mpd tries to have reasonable defaults for everything. <HR NOSHADE> <A HREF="mpd.html">Mpd 5.9 User Manual</A> : <A HREF="mpd17.html">Configuring Mpd</A> : Mpd Layers  Previous: <A HREF="mpd18.html">General mpd commands</A>  Next: <A HREF="mpd20.html">Link layer</A> </BODY> </HTML>