*** UNIX MANUAL PAGE BROWSER ***

A Nergahak database for man pages research.

Navigation

Directory Browser

1Browse 4.4BSD4.4BSD
1Browse Digital UNIXDigital UNIX 4.0e
1Browse FreeBSDFreeBSD 14.3
1Browse MINIXMINIX 3.4.0rc6-d5e4fc0
1Browse NetBSDNetBSD 10.1
1Browse OpenBSDOpenBSD 7.7
1Browse UNIX v7Version 7 UNIX
1Browse UNIX v10Version 10 UNIX

Manual Page Search

Manual Page Result

0 Command: me | Section: 4 | Source: FreeBSD | File: me.4.gz
ME(4) FreeBSD Kernel Interfaces Manual ME(4) NAME me - encapsulating network device SYNOPSIS To compile the driver into the kernel, place the following line in the kernel configuration file: 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 Andrey V. Elsukov <[email protected]> FreeBSD 14.1-RELEASE-p8 November 7, 2014 FreeBSD 14.1-RELEASE-p8

Navigation Options