Router - Cisco 887VA-Native-IPv6: Difference between revisions

(2 intermediate revisions by 2 users not shown)

Line 24:

At this point, you should be able to ping google.com and have it successfully resolve to an IPv6 address (provided your DNS is serving it) and receive a response.

The next step is to assign another IPv6 /64 range for your ‘internal’ computers. I have assigned multiple /64’s as I have multiple VLAN’s all with a different purpose, but one should be enough for most people. If like me you have a firewall sat behind the Cisco with ~~it’s~~ own external address then you’ll want to assign it an IPv6 address out of the /64 subnet you’re using in ‘vlan1′ as defined on your Cisco. For example, you’d assign 2001:xxx:xxxx:xxxx::2/64 to your firewall.

The next step is to assign another IPv6 /64 range for your ‘internal’ computers. I have assigned multiple /64’s as I have multiple VLAN’s all with a different purpose, but one should be enough for most people. If like me you have a firewall sat behind the Cisco with its own external address then you’ll want to assign it an IPv6 address out of the /64 subnet you’re using in ‘vlan1′ as defined on your Cisco. For example, you’d assign 2001:xxx:xxxx:xxxx::2/64 to your firewall.

In order to route another /64 range through to your internal hosts you’ll need to configure this on your internal LAN interface on your firewall then add a static route on the Cisco to tell it how to route it. Remember, in order to get to the /64 range in question your router needs to know where to send the packets.

Line 34:

I may expand on this but it really is this simple, if you have any questions please feel free to comment on http://blog.gamermatrix.co.uk/?p=333

[[Category:~~IPv6]]~~ ~~[[Category:~~Cisco]] [[Category:~~Router~~]]

[[Category:3rd Party Routers|Cisco]] [[Category:IPv6]]