Router - Cisco 887VA-Native-IPv6: Difference between revisions
mNo edit summary |
m (→top: clean up, typos fixed: with it’s → with its) |
||
| Line 24: | 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. |
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 |
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. |
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. |
||
Latest revision as of 23:58, 14 March 2017
From: http://blog.gamermatrix.co.uk/?p=333
...first of all, in order to get the Cisco up and running with IPv6, ensure you have a /64 assigned in AAISP’s control pages to your line. Then run the following commands on your Cisco:
ipv6 source-route ipv6 unicast-routing ipv6 cef ipv6 multicast-routing conf t int dialerX ipv6 enable ipv6 dhcp client pd myprefix rapid-commit int vlan1 ipv6 address 2001:xxx:xxxx:xxxx::1/64
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 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.
ipv6 route 2002:xxx:xxxx:xxxx::1/64 2001:xxx:xxxx:xxxx::2
The above command basically says ‘route 2002:xxx:xxxx:xxxx::1/64 via 2001:xxx:xxxx:xxxx::2′ which is resident on our external interface on our firewall.
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