Abstract: . . .  compiling and installing a kernel, however this document is about something else. If you run into problems at this stage, go and look for documentation about compiling a Linux kernel according to your own specifications. The file /usr/src/ linux /README might be a good start. After you accomplished all this, and rebooted with your brand new kernel, you might want to issue an ’/sbin/ifconfig -a’ and notice the brand new  . . .
. . .  needs of different people, who should be served differently. The routing policy database allows you to do this by having multiple sets of routing tables. If you want to use this feature, make sure that your kernel is compiled with the "IP: advanced router" and "IP: policy routing" features. When the kernel needs to make a routing decision, it finds out which table needs to be consulted. By default, there are three tables. The old ’route’ tool modifies the main and local tables, . . .
. . .  bits. And this provides us just with the thing we need: many, many IP-addresses: 340,282,266,920,938,463,463,374,607,431,768,211,465 to be precise. Apart from this, IPv6 (or IPng, for IP Next Generation) is supposed to provide for smaller routing tables on the Internet’s backbone routers, simpler configuration of equipment, better security at the IP level and better support for QoS. An example: 2002:836b:9820:0000:0000:0000:836b:9886 Writing down IPv6 addresses can be quite . . .
. . .  if you have to, otherwise use GRE. 5.3. GRE tunneling GRE is a tunneling protocol that was originally developed by Cisco, and it can do a few more things than IP-in-IP tunneling. For example, you can also transport multicast traffic and IPv6 through a GRE tunnel. In Linux , you’ll need the ip_gre.o module. 5.3.1. IPv4 Tunneling Let’s do IPv4 tunneling first: Let’s say you have 3 networks: Internal networks A and B, and intermediate network C . . .
. . .  Page 13 Chapter 3. Introduction to iproute2 Some parts of iproute require you to have certain kernel options enabled. It should also be noted that all releases of RedHat up to and including 6.2 come without most of the traffic control features in the default kernel. RedHat 7.2 has everything in by default. Also make sure that you have netlink support, should you choose to roll your own kernel. Iproute2 needs it. 3.4. Exploring your current configuration . . .
. . .  are literally dozens of implementations of tunneling outside the kernel. Best known are of course PPP and PPTP, but there are lots more (some proprietary, some secure, some that don’t even use IP) and that is really beyond the scope of this HOWTO. 19 Page 26 Chapter 6. IPv6 tunneling with Cisco and/or 6bone By Marco Davids <marco@sara.nl> NOTE to maintainer: As far as I am concerned, this IPv6-IPv4 tunneling . . .
--3000,6,250,3394,64766