IPv6 static routes

Posted on

IPv6 static routes – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.

But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about linux, networking, centos, routing, ipv6.

I am looking to configure a few hosts with IPv6 on my network. The router (running CentOS 5) is configured with an Hurricane Electric (HE) tunnel which works fine on that host.

However, I would like to statically add a few additional hosts on the same LAN to have IPv6 through this tunnel. No, I don’t want radvd or dhcpv6 to do the work for me in this case.

I already have IPv6 forwarding enabled in sysctl.conf. I am looking for help with the next steps (statically adding the routes).

Lets say the IP addresses are as follows:

Router: 2001:470:1b07:1::

Host1: 2001:470:1b07:2::

How would I go about making them see each other? Thanks in advance for the help.

Solution :

Basically you need:

  1. you need two /64 prefixes, one on the tunnel and one on the LAN
  2. the router needs an address on both the tunnel interface and the LAN interface in the corresponding /64 prefixes
  3. the router has a default route to the tunnel
  4. the router will automatically have a route for the LAN /64 to the LAN interface
  5. The PC on the LAN gets another address from the LAN /64
  6. The PC has a static default route towards the LAN address of the router

Now the IPv6 traffic from the PC will be sent to the router, which will send it to on tunnel. Return traffic from come from the tunnel to the router, which will then see that the destination is in the LAN /64 and it will send it to its LAN interface where the PC can receive it.

Thank you all very much for the help. All my troubles actually stemmed from a typo in my Network Configuration script for the interface. Put simply, I was over thinking this problem and doubting myself in this case.

When populated with IPV6INIT, IPV6ADDR and IPV6_DEFAULTGW (on both the router and other LAN machine) no further routes needed to be added. The static assignment/routes now work.

Leave a Reply

Your email address will not be published. Required fields are marked *