me (4)

Leading comments

Copyright (c) Andrey V. Elsukov <ae@FreeBSD.org>
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
   notice, this list of conditions and the following disclaimer in the
   documenta...

(The comments found at the beginning of the groff file "man4/me.4freebsd".)

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.conf5:

if_me_load="YES"

DESCRIPTION

The 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.

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 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