route.conf(5) [netbsd man page]

ROUTE.CONF(5)						      BSD File Formats Manual						     ROUTE.CONF(5)

NAME

     route.conf -- static routes config file

DESCRIPTION

     The route.conf file is read by the staticroute rc.d script during system start-up and shutdown, and is intended for adding and removing
     static routes.

   FILE FORMAT
     Lines starting with a hash ('#') are comments and ignored.  Lines starting with a plus sign ('+') are run during start-up, while lines start-
     ing with a minus sign ('-') are run during system shutdown.  If a line starts with a '!', the rest of the line will get evaluated as a shell
     script fragment.  All other lines are passed to route(8).	During start-up, they are passed behind a ``route add -'' command and during shut-
     down behind a ``route delete -'' command.

FILES

     /etc/route.conf	 The route.conf file resides in /etc.

     /etc/rc.d/staticroute
			 rc.d(8) script that parses route.conf.

EXAMPLES

     In this example, the interface for the desired routing changes is set, the IP address on that interface is determined, and a route is added
     during startup, or deleted during system shutdown.

	   # Set interface and determine current IP address for added route.
	   !ifname=bnx0
	   !ipaddr=$(/sbin/ifconfig ${ifname} | awk '$1 == "inet" {print $2}')
	   net 10.10.1 -interface ${ipaddr}

     In this example, IP forwarding is turned on during start-up, and a static route added for 192.168.2.0.  During system shutdown, the route is
     removed and IP forwarding turned off.

	   # Turn on/off IP forwarding.
	   +sysctl -w net.inet.ip.forwarding=1
	   -sysctl -w net.inet.ip.forwarding=0
	   net 192.168.2.0 -netmask 255.255.255.0 192.168.150.2

SEE ALSO

     rc.conf(5), rc(8), route(8)

BSD
								    May 1, 2012 							       BSD

GRE(4)							   BSD Kernel Interfaces Manual 						    GRE(4)

NAME

     gre -- encapsulating network device

SYNOPSIS

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

	   device gre

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

	   if_gre_load="YES"

DESCRIPTION

     The gre 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.  The ``tunnel'' appears to the inner datagrams as one hop.

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

     This driver corresponds to RFC 2784.  Encapsulated datagrams are prepended an outer datagram and a GRE header.  The GRE header specifies the
     type of the encapsulated datagram and thus allows for tunneling other protocols than IP.  GRE mode is also the default tunnel mode on Cisco
     routers.  gre also supports Cisco WCCP protocol, both version 1 and version 2.

     The gre interfaces support a number of additional parameters to the ifconfig(8):

     grekey	  Set the GRE key used for outgoing packets.  A value of 0 disables the key option.

     enable_csum  Enables checksum calculation for outgoing packets.

     enable_seq   Enables use of sequence number field in the GRE header for outgoing packets.

EXAMPLES

     192.168.1.* --- Router A  -------tunnel-------- Router B --- 192.168.2.*
						       /
			 			      /
			  +------ the Internet ------+

     Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal
     address 192.168.2.1, the following commands will configure the tunnel:

     On router A:

	   ifconfig greN create
	   ifconfig greN inet 192.168.1.1 192.168.2.1
	   ifconfig greN inet tunnel A B
	   route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1

     On router B:

	   ifconfig greN create
	   ifconfig greN inet 192.168.2.1 192.168.1.1
	   ifconfig greN inet tunnel B A
	   route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1

NOTES

     The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers.  This may not be an optimal value, depending
     on the link between the two tunnel endpoints.  It can be adjusted via ifconfig(8).

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

     The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero.

SEE ALSO

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

     A description of GRE encapsulation can be found in RFC 2784 and RFC 2890.

AUTHORS

     Andrey V. Elsukov <ae@FreeBSD.org>
     Heiko W.Rupp <hwr@pilhuhn.de>

BUGS

     The current implementation uses the key only for outgoing packets.  Incoming packets with a different key or without a key will be treated as
     if they would belong to this interface.

     The sequence number field also used only for outgoing packets.

BSD
								 November 7, 2014							       BSD