Differences

This shows you the differences between two versions of the page.

--- training:sanog32:d-static [2018/07/24 15:24] – [Static Customer Configuration] philip
+++ training:sanog32:d-static [2018/07/26 10:09] (current) – [Default route on Customer Router] philip
@@ Line 1: / Line 1: @@
-====== IPv6 Lab - Statics ======
+====== IPv6 Lab - Customer Connections ======
-===== Static Customer Configuration =====
+===== Background =====
 This series of small labs is going to focus on how to deploy IPv6 into a customer’s network. Several technologies will be examined, including:
@@ Line 13: / Line 13: @@
 {{:training:sanog32:peering-0-cust.png?600|}}
+===== Static Configuration =====
+This first lab looks at how to set up a static configuration between network operator and the end-user. This is the traditional method the industry has used for years for IPv4, and is also used for IPv6 in the case of a dual-stack connection from operator to customer and within the customer’s own network.
 ===== Configuring the Customer Router =====
@@ Line 74: / Line 78: @@
 ===== Configuring Interfaces on Customer Router =====
-Now that the basic configuration is in place, we need to configure the interface linking the Customer router to our Access router. Refer to the [IP address plan](address-plan.md) for the lab to find out the point-to-point link addresses for both IPv4 and IPv6.
+Now that the basic configuration is in place, we need to configure the interface linking the Customer router to our Access router. Refer to the [[training:sanog32:address-plan|ip address plan]] for the lab to find out the point-to-point link addresses for both IPv4 and IPv6.
 Here is a configuration example:
@@ Line 131: / Line 135: @@
   show ip bgp
   show bgp ipv6 unicast
 ===== Default route on Customer Router =====
@@ Line 151: / Line 154: @@
   !
-With this in place it should be possible to reach the Internet from the Customer router. Check connectivity from your AS towards the Customer router too, using the newly created Loopback interface as a target.
+With this in place it should be possible to reach the Internet from the Customer router. Check connectivity from:
+  * your AS towards the Customer router too, using the newly created Loopback interface as a target.
+  * our Customer router, using the newly created Loopback interface as the source, towards the Internet, eg to 8.8.8.8.
+**Note:** Can you explain why, in the latter case, we are running the traceroute from the Loopback interface, and not using the default (which would be the point-to-point link to the network operator’s Access router)?
 Once complete, make sure you save a copy of the configuration on the Access and Customer routers - simple copy and paste into a text document is easiest. We will need to revert to this configuration at a future stage in the lab.
+[[:training:sanog32:agenda| Back to Agenda page]]