Export (0) Print
Expand All

Creating a Static Routing Infrastructure in the IPv6 Test Lab (Windows Embedded CE 6.0)

1/6/2010

You can configure a static routing infrastructure so that all test lab nodes are reachable using IPv6 traffic. The following procedure shows how to configure and verify the routing infrastructure.

  1. On CLIENT1, type ipconfig, and then capture the following information for use later in these procedures:

    • Link-local address
  2. On the development system, perform the following steps:

    1. If ROUTER1 is not running on the CEPC, on the Target menu, choose Attach Device.
      You may have to restart the CEPC for the download to occur.
    2. On the Target menu, choose CE Target Control.
    3. To obtain the link-local address of the Subnet1 interface, in the Target Control window, type s ipconfig, and then capture the following information for use later in these procedures:
    • Subnet1 interface index
    • Subnet2 interface index
    • Link-local address of the ROUTER1 interface on Subnet2
  3. On ROUTER2, type ipconfig, and then capture the following information for use later in these procedures:

    • Subnet2 interface index
    • Subnet3 interface index
    • Link-local address of the ROUTER2 interface on Subnet2
  4. On CLIENT2, type ipconfig, and then capture the following information for use later in these procedures:

    • Link-local address
  5. On the development system, perform the following steps:

    1. Connect to ROUTER1.
    2. On the Target menu, choose CE Target Control.
    3. In the Target Control window, type the following commands:
      s iPv6 –d ifc <Subnet1 Interface Index> forwards advertises
      s iPv6 –d ifc <Subnet2 Interface Index> forwards advertises
      s ipv6 –d rtu 2000:0:0:1::/64 <Subnet1 Interface Index> publish
      s ipv6 –d rtu 2000:0:0:2::/64 <Subnet2 Interface Index> publish
      s ipv6 –d rtu ::/0 <Subnet2 Interface Index>/<ROUTER2 Address On Subnet2> publish

    In these commands:

    • <Subnet1 Interface Index> is the interface index of the ROUTER1 interface on Subnet 1.
    • <Subnet2 Interface Index> is the interface index of the ROUTER1 interface on Subnet 2.
    • <ROUTER2 Address On Subnet2> is the link-local address of the ROUTER2 interface on Subnet 2.

    For example, if the Subnet 1 interface index is 4, the Subnet 2 interface index is 3, and the link-local address of the ROUTER2 Subnet 2 interface is FE80::2AA:FF:FE87:4D5C, the commands should be typed as follows:

    s iPv6 –d ifc 4forwards advertises

    s iPv6 –d ifc 3forwards advertises

    s ipv6 –d rtu 2000:0:0:1::/64 4 publish

    s ipv6 –d rtu 2000:0:0:2::/64 3 publish

    s ipv6 –d rtu ::/0 3/FE80::2AA:FF:FE87:4D5C publish

  6. On ROUTER2, type the following commands:

    IPv6 –d ifc <Subnet2 Interface Index> forwards advertises

    IPv6 –d ifc <Subnet3 Interface Index> forwards advertises

    ipv6 –d rtu 2000:0:0:2::/64 <Subnet2 Interface Index> publish

    ipv6 –d rtu 2000:0:0:3::/64 <Subnet3 Interface Index> publish

    ipv6 –d rtu ::/0 <Subnet2 Interface Index>/<ROUTER1 Address On Subnet2> publish

    For example, if the Subnet 2 interface index is 4, the Subnet 3 interface index is 3, and the link-local address of the ROUTER1 Subnet 2 interface is FE80::2AA:FF:FE9A:203F, the commands should be typed as follows:

    IPv6 –d ifc 4forwards advertises

    IPv6 –d ifc 3forwards advertises

    ipv6 –d rtu 2000:0:0:2::/64 4 publish

    ipv6 –d rtu 2000:0:0:3::/64 3 publish

    ipv6 –d rtu ::/0 4/FE80::2AA:FF:FE9A:203F publish

    For Windows Server 2003 and later versions of Windows Server, you must use the netsh tool instead of the ipv6 tool. For more information, search for netsh at this Microsoft Web site.

  7. On CLIENT1, to view a new address on the LAN interface that is based on the Subnet1 global prefix of 2000:0:0:1::/64, type the ipconfig command.

  8. On CLIENT1, to view new routes for Subnet1, Subnet2, and the default subnet, type the following command:

    ipv6 –d rt

  9. On CLIENT2, to view a new address on the LAN interface that is based on the global prefix of 2000:0:0:3::/64, type the ipconfig command.

  10. On CLIENT2, to view new routes for Subnet2, Subnet3, and the default subnet, type the following command:

    ipv6 –d rt

  11. On CLIENT1, to ping the CLIENT2 global address, type the following command:

    ping <CLIENT2 Global Address>

  12. On the development system, perform the following steps:

    1. If ROUTER1 is not running on the CEPC, on the Target menu, choose Attach Device.
      You may have to restart the CEPC for the download to occur.
    2. On the Target menu, choose CE Target Control.
    3. To view the entries in the ROUTER1 neighbor cache for CLIENT1 and ROUTER2, in the Target Control window, type the following commands:
      s ipv6 –d nc <Subnet1 Interface Index>
      s ipv6 –d nc <Subnet2 Interface Index>
  13. To view the entries in the ROUTER1 route cache for ROUTER1 and ROUTER2, in the Target Control window, type the following command:

    s ipv6 –d rc

    Ee494527.note(en-US,WinEmbedded.60).gifNote:
    The IPv6 protocol currently advertises off-link prefixes in Router Advertisement messages. Prefix Information options for off-link prefixes become routes in the routing table of the receiving host.

Community Additions

ADD
Show:
© 2014 Microsoft