GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  ME (4)

NAME

me - encapsulating network device

CONTENTS

Synopsis
Description
Notes
See Also
Authors

SYNOPSIS

To compile the driver into the kernel, place the following line in the kernel configuration file:


.Cd device me

Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

if_me_load="YES"

DESCRIPTION

The me network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they are decapsulated and further routed to their final destination.

me interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands.

This driver corresponds to RFC 2004. Datagrams are encapsulated into IP with a shorter encapsulation. The original IP header is modified and the modifications are inserted between the so modified header and the original payload. The protocol number 55 is used for outer header.

NOTES

For correct operation, the me device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop.

SEE ALSO

gif(4), gre(4), inet(4), ip(4), netintro(4), protocols(5), ifconfig(8), sysctl(8)

AUTHORS


.An Andrey V. Elsukov Aq Mt ae@FreeBSD.org
Search for    or go to Top of page |  Section 4 |  Main Index


Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.