Lines Matching refs:encapsulation

1 Description of the "concap" encapsulation protocol interface
5 drivers that need to process an encapsulation protocol. 
22 The encapsulation protocol used on top of WAN connections or permanent
25 several different encapsulation protocols at once.
28 encapsulation protocols. The encapsulation protocol is configured by a
31 depending on the currently configured encapsulation protocol.
33 In contrast, LAN network interfaces always used a single encapsulation
35 encapsulation is usually done by just sticking a header on the data. Thus,
37 encapsulation protocol directly (usually by just providing a hard_header()
43    The configurability of the encapsulation protocol to be used
53 Such encapsulation protocols for WAN devices are typically more complex
54 than encapsulation protocols for lan devices. Thus, network interface
63 interface between the network interface code and the encapsulation
68 Likewise, a similar encapsulation protocol will frequently be needed by
72 similar code in them. By cleanly separating the encapsulation protocol
79 encapsulation protocols will need to control the connection. Therefore,
83 the encapsulation protocol used, e.g. for a ppp module using our service
91 The encapsulation protocol currently provides the following
94 - create a new encapsulation protocol instance
95 - delete encapsulation protocol instance and free all its resources
96 - initialize (open) the encapsulation protocol instance for use.
97 - deactivate (close) an encapsulation protocol instance.
105 provided by the encapsulation protocol instance within a
110 	/* create a new encapsulation protocol instance of same type */
113 	/* delete encapsulation protocol instance and free all its resources.
119 	   encapsulation protocol may be used after this*/
124 	/* deactivate an encapsulation protocol instance. The encapsulation
145 A Network interface using encapsulation protocols must also provide
146 some service primitives to the encapsulation protocol:
152 The encapsulation protocol accesses those primitives via callbacks
170 because the encapsulation protocol directly calls netif_rx(). 
175 An encapsulation protocol itself is actually the
199 encapsulation services could look like this:
254 as its hard_start_xmit() method when a zero layer encapsulation
257 Nevertheless, the device remains able to support encapsulation