mrtg-ipv6(1) [suse man page]

MRTG-IPV6(1)							       mrtg							      MRTG-IPV6(1)

NAME

       mrtg-ipv6 - IPv6 support in MRTG

OVERVIEW

       MRTG and cfgmaker support SNMP over IPv6. IPv6 targets can be specified by hostname or IPv6 address, and if the required libraries are
       present (see below), queries will use IPv6.

USAGE

       Enabling IPv6

       IPv6 is currently disabled by default and must be explicitly enabled. In MRTG this is done by turning on the EnableIPv6 global option in
       the configuration file. In cfgmaker, it is enabled with the --enable-ipv6 command-line option.

       If IPv6 is disabled, MRTG and cfgmaker should behave in exactly the same way as previous versions. So the addition of IPv6 support should
       have no effect on existing MRTG setups unless IPv6 is enabled.

       IPv6 support requires the Socket6 and INET6 libraries (see below). If MRTG can't find them, IPv6 is disabled.

       Specifying IPv6 targets

       IPv6 targets may be specified by name or IPv6 address. Numeric IPv6 addresses may be used with both cfgmaker and MRTG, but they must be
       enclosed in square brackets.

       For example, a target could be specified as:

	public@[2001:760:4::]:161

       Hostnames work as expected: first an IPv6 name lookup is tried, then an IPv4 lookup.

       Targets that do not support SNMP over IPv6

       Many targets (this currently includes all Cisco routers) do not yet support SNMP over IPv6 and must be monitored over IPv4. This can cause
       problems if you specify a target through its DNS name and the name maps to both the IPv6 address and the IPv4 address of the target: MRTG
       will only try IPv6, and will fail.

       To query these targets, use the IPv4Only per-target option, which tells MRTG not to use SNMP over IPv6 for the target.

       MRTG does not fall back to IPv4 for performance and correctness reasons. If there are many routers to query, a timeout for every router
       would make MRTG take too long to query them all. And if, for some reason, IPv6 connectivity to the target is lost, MRTG's error messages
       can help figure out what is wrong.

       cfgmaker does fall back from IPv6 to IPv4. If IPv6 is enabled and cfgmaker is given a hostname that resolves to both an IPv6 and an IPv4
       address, it first tries to query the target over IPv6. If it receives no answer, it tries again using IPv4. If the target answers, cfgmaker
       sets the IPv4Only option in the generated config file.

IPv6 LIBRARIES
       Libraries required

       IPv6 support requires the Socket6 and INET6 Perl modules. Both can be downloaded from CPAN:

       http://search.cpan.org/author/UMEMOTO/Socket6/

       http://search.cpan.org/author/MONDEJAR/INET6/

       If you use Debian, you will need the packages libsocket6-perl and libio-socket-inet6-perl, which are (or should soon be) in unstable.

       So far, IPv6 support has been tested on Linux only, and only with Socket6 version 0.12. Also note that IPv6 won't work at all if you don't
       have INET6.pm version 2.00 or newer.

       Installing the libraries

       Building and installing Socket6 and INET6 is very simple. For each module, just unpack the archive and then do:

	perl Makefile.PL
	make

       and then:

	su
	make install

       If you have installed the libraries successfully, cfgmaker and mrtg should automatically detect them and allow IPv6 support to be enabled.

AUTHOR

       Lorenzo Colitti <lorenzo location colitti.com>

2.16.2								    2008-05-16							      MRTG-IPV6(1)

Check Out this Related Man Page

FAITH(4)						   BSD Kernel Interfaces Manual 						  FAITH(4)

NAME

     faith -- IPv6-to-IPv4 TCP relay capturing interface

SYNOPSIS

     device faith

DESCRIPTION

     The faith interface captures IPv6 TCP traffic, for implementing userland IPv6-to-IPv4 TCP relay like faithd(8).

     Each faith interface is created at runtime using interface cloning.  This is most easily done with the ifconfig(8) create command or using
     the cloned_interfaces variable in rc.conf(5).

     Special action will be taken when IPv6 TCP traffic is seen on a router, and the routing table suggests to route it to the faith interface.
     In this case, the packet will be accepted by the router, regardless of the list of IPv6 interface addresses assigned to the router.  The
     packet will be captured by an IPv6 TCP socket, if it has the IN6P_FAITH flag turned on and matching address/port pairs.  As a result, faith
     will let you capture IPv6 TCP traffic to some specific destination addresses.  Userland programs, such as faithd(8) can use this behavior to
     relay IPv6 TCP traffic to IPv4 TCP traffic.  The program can accept some specific IPv6 TCP traffic, perform getsockname(2) to get the IPv6
     destination address specified by the client, and perform application-specific address mapping to relay IPv6 TCP to IPv4 TCP.

     The IN6P_FAITH flag on a IPv6 TCP socket can be set by using setsockopt(2), with level IPPROTO_IPV6 and optname IPv6_FAITH.

     To handle error reports by ICMPv6, some ICMPv6 packets routed to an faith interface will be delivered to IPv6 TCP, as well.

     To understand how faith can be used, take a look at the source code of faithd(8).

     As the faith interface implements potentially dangerous operations, great care must be taken when configuring it.	To avoid possible misuse,
     the sysctl(8) variable net.inet6.ip6.keepfaith must be set to 1 prior to using the interface.  When net.inet6.ip6.keepfaith is 0, no packets
     will be captured by the faith interface.

     The faith interface is intended to be used on routers, not on hosts.

SEE ALSO

     inet(4), inet6(4), faithd(8)

     Jun-ichiro itojun Hagino and Kazu Yamamoto, An IPv6-to-IPv4 transport relay translator, RFC3142.

HISTORY

     The FAITH IPv6-to-IPv4 TCP relay translator first appeared in the WIDE hydrangea IPv6 stack.

BSD
								  April 10, 1999							       BSD

Linux and UNIX Man Pages

mrtg-ipv6(1) [suse man page]

Check Out this Related Man Page