OpenNHRP 0.9.1 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News OpenNHRP 0.9.1 (Default branch)
# 1  
Old 12-31-2008
OpenNHRP 0.9.1 (Default branch)

OpenNHRP implements the NBMA Next Hop Resolution Protocol (as defined in RFC 2332). It makes it possible to create a dynamic multipoint VPN Linux router using NHRP, GRE, and IPsec. It aims to be Cisco DMVPN compatible. License: GNU General Public License v2 Changes:
A problem in peer cache enumeration that could crash opennhrp under special circumstances was fixed. The example opennhrp-script was updated to show how to add host routes with MTU. PID file locking is now done as the first thing to prevent accidental startup of opennhrp (which would make the initial instance unusable by overwriting the control socket). Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
ip6rtrd.conf(4) 					     Kernel Interfaces Manual						   ip6rtrd.conf(4)

NAME
ip6rtrd.conf - IPv6 router daemon (ip6rtrd) configuration file DESCRIPTION
The ip6rtrd.conf file contains configuration information that is read by the ip6rtrd daemon at initialization time. This file contains statements that control information sent in router advertisements and RIPng messages. The ip6rtrd.conf file consists of structured information for each interface in the following format: interface interface-name { # interface keyword-value pairs, one per line Prefix prefix/length { # prefix keyword-value pairs, one per line } } Comments begin with the number sign (#) and continue to the end of the line. The following table lists the keywords and range of accepted values. See RFC 2461 for complete descriptions of the keywords. --------------------------------------------------------------------- Keyword Values Default --------------------------------------------------------------------- AdvSendAdvertisements yes/no yes MaxRtrAdvInterval 4 - 1800 seconds 600 MinRtrAdvInterval 3 - (0.75 * MaxRtrAdvInterval) 200 AdvManagedFlag 0/1 0 AdvOtherConfigFlag 0/1 0 AdvLinkMTU non-negative integer 0 AdvReachableTime 0 - 3,600,000 milliseconds 0 AdvRetransTimer non-negative integer 0 AdvDefaultLifetime 0 or MaxRtrAdvInterval - 9000 secs 1800 --------------------------------------------------------------------- In addition, the following interface keywords are accepted: The value to be placed in the Cur Hop Limit field in the Router Advertisement messages sent by the router. The value zero means unspecified (by this router). Valid values are any non-negative integer. The default is 0. Sends the interface link-layer address option in outgoing router advertisements. Valid values are yes and no. The default is yes. Enables (yes) or disables (no) participation in RIPng on the interface. If enabled, RIPng updates are sent on the interface, and received RIPng updates are processed as defined in RFC 2080. You cannot specify yes for automatic tunnels (the tun0 interface). The default is yes (except for tun0). Enables (1) or disables (0) the Split Horizon algorithm as specified in RFC 2080. The default is 1. Enables (1) or disables (0) the Poisoned Reverse algorithm as specified in RFC 2080. The default is 1. Address Prefix Information Each address prefix to be configured on the interface must be defined within a prefix block that begins with the keyword Prefix followed by the prefix and length (separated by a slash (/)) and optionally followed by an additional address prefix information block of keyword-value pairs. The following table lists address prefix keywords and values that are described in RFC 2461: ------------------------------------------------- Prefix Keyword Values Default ------------------------------------------------- AdvValidLifetime integer 2592000 seconds AdvPreferredLifetime integer 604800 seconds AdvOnLinkFlag 0/1 1 AdvAutonomousFlag 0/1 1 ------------------------------------------------- The following table lists address prefix keywords and values that are described in RFC 2080: ---------------------------------------------- Prefix Keyword Values Default ---------------------------------------------- RouteMetric 1 - 16 (inclusive) 1 RouteTag integer 0 ---------------------------------------------- In addition, you can specify the following address prefix keywords: The ip6rtrd will configure the advertised prefix on the interface if ConfigureThisPrefix is specified and set to 1, or if ConfigureThisPrefix is not specified and AdvAutonomousFlag is set to 1. The prefix is not auto-configured in all other cases. Valid values are 0 and 1. The default value is the value of AdvAutonomous- Flag. RELATED INFORMATION
Daemons: ip6rtrd(8). RFC 2461, Neighbor Discovery for IP version 6 (IPv6), Narten, T.; Nordmark, E., Simpson W. A., December 1998 RFC 2462, IPv6 Stateless Address Autoconfiguration, Thompson, S.; Narten, T., December 1998 RFC 2080, RIPng for IPv6, Malkin, G., Minnear, R., January 1997. delim off ip6rtrd.conf(4)