Pinging IPV6 between Windows XP and Cisco Router

Discussion in 'Cisco' started by ConceptZone, Aug 24, 2006.

  1. ConceptZone

    ConceptZone Guest

    Hi Group,

    I am trying to do very simple thing but it is the first time I am doing
    it,

    I assigned my fastethernet 0/0 an ipv6 address of
    2001:DB8:1234:42::1/64

    Also I assigned My Windows XP manually an IPV6 of 2001:db8:1234:42::2



    then I tryed to ping from the router :

    Rack1R3#ping 2001:db8:1234:42::2

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 2001:DB8:1234:42::2, timeout is 2
    seconds:
    ......
    Success rate is 0 percent (0/5)


    I will appreciate if you can tell me where is my mistake, why it is not
    pinging !

    here is the configuration on Windows XP and the router

    netsh interface ipv6 add address "Local Area Connection"
    2001:DB8:1234:42::2

    c:>ipconfig

    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : 192.168.10.200
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IP Address. . . . . . . . . . . . : 2001:db8:1234:42::2
    IP Address. . . . . . . . . . . . : fe80::212:3fff:fed1:5985%5
    Default Gateway . . . . . . . . . :



    Rack1R3#sho run int fas0/0
    Building configuration...

    Current configuration : 220 bytes
    !
    interface FastEthernet0/0
    description Access link down to customers
    ip address 192.168.10.1 255.255.255.0
    no ip mroute-cache
    duplex auto
    speed auto
    ipv6 address 2001:DB8:1234:42::1/64
    ipv6 enable
    ipv6 nat
    end


    Conceptzone
     
    ConceptZone, Aug 24, 2006
    #1
    1. Advertising

  2. * ConceptZone wrote:
    > netsh interface ipv6 add address "Local Area Connection"
    > 2001:DB8:1234:42::2


    You need to set up an netmask, too.

    > interface FastEthernet0/0
    > ipv6 address 2001:DB8:1234:42::1/64
    > ipv6 enable


    .. ipv6 nd prefix 2001:db8:1234:42::/64
    enables autoconfiguration for the clients.
    This is the way an IPv6 network is set up.

    Futhermore, you should not assign the address by hand, use the default
    mechanism for this:
    .. ipv6 address 2001:DB8:1234:42::/64 eui-64

    > ipv6 nat


    And do not enven consider nat. This time is over.
     
    Lutz Donnerhacke, Aug 24, 2006
    #2
    1. Advertising

  3. ConceptZone

    Merv Guest

    1. I assume that you have confirmed conectivity between the router and
    the PC by pinging the IPv4 address of the Windows PC ?

    2. Is there a firewall enabled on the Windows PC ?

    3. From the router after you ping the global IP address assigned to the
    windows PC,
    what does the output of "sh ipv6 nei fa 0/0" display - there should
    be at least two entries one for the windows PC IPv6 link-local address
    and one for its IPv6 globaladdress

    4. can you ping the IPv6 link-local address of the Windows PC ?

    post your findings
     
    Merv, Aug 24, 2006
    #3
  4. ConceptZone

    ConceptZone Guest

    Okay, Thanks for your reply,


    I have done what you told me , but now how can I determin what ipv6
    address my windows XP took ?

    should I do some thing extra on my windows XP to enable the
    autoconfiguration ?


    here is the configuration of the router :

    interface FastEthernet0/0
    description Access link down to customers
    ip address 192.168.10.1 255.255.255.0
    no ip mroute-cache
    duplex auto
    speed auto
    ipv6 address 2001:DB8:1234:42::/64 eui-64
    ipv6 enable
    ipv6 nd prefix 2001:DB8:1234:42::/64
    end


    and I made sure that nd is going out fastethernet 0/0 :


    ICMPv6-ND: Sending NS for FE80::20F:90FF:FE6E:81E0 on FastEthernet0/0
    ICMPv6-ND: DAD: FE80::20F:90FF:FE6E:81E0 is unique.
    ICMPv6-ND: Sending NS for 2001:DB8:1234:42:20F:90FF:FE6E:81E0 on
    FastEthernet0/0
    ICMPv6-ND: Sending NA for FE80::20F:90FF:FE6E:81E0 on FastEthernet0/0
    ICMPv6-ND: DAD: 2001:DB8:1234:42:20F:90FF:FE6E:81E0 is unique.
    ICMPv6-ND: Sending NA for 2001:DB8:1234:42:20F:90FF:FE6E:81E0 on
    FastEthernet0/0
     
    ConceptZone, Aug 24, 2006
    #4
  5. ConceptZone

    ConceptZone Guest

    Ya sure I can ping my machine IP address which is 192.168.1.200

    Rack1R3#ping 192.168.10.200

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 192.168.10.200, timeout is 2 seconds:
    !!!!!

    and the link local address of the fas0/0 is FE80::20F:90FF:FE6E:81E0

    now as you noticed I chaned it to nd instead of assgning ipv6 mannually
    to the XP, should I go back and assign it manually ?

    beside this , there is no output from the show ipv6 neighbors,


    Rack1R3#show ipv6 neighbors
    Rack1R3#


    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : 192.168.10.200
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IP Address. . . . . . . . . . . . : fe80::212:3fff:fed1:5985%5
    Default Gateway . . . . . . . . . :




    Rack1R3#show ipv6 int fas0/0
    FastEthernet0/0 is up, line protocol is up
    IPv6 is enabled, link-local address is FE80::20F:90FF:FE6E:81E0
    Description: Access link down to customers
    Global unicast address(es):
    2001:DB8:1234:42:20F:90FF:FE6E:81E0, subnet is
    2001:DB8:1234:42::/64
    Joined group address(es):
    FF02::1
    FF02::2
    FF02::1:FF6E:81E0
    MTU is 1500 bytes
    ICMP error messages limited to one every 100 milliseconds
    ICMP redirects are enabled
    ND DAD is enabled, number of DAD attempts: 1
    ND reachable time is 30000 milliseconds
    ND advertised reachable time is 0 milliseconds
    ND advertised retransmit interval is 0 milliseconds
    ND router advertisements are sent every 200 seconds
    ND router advertisements live for 1800 seconds
    Hosts use stateless autoconfig for addresses.
     
    ConceptZone, Aug 24, 2006
    #5
  6. ConceptZone

    Merv Guest


    > now as you noticed I chaned it to nd instead of assgning ipv6 mannually
    > to the XP, should I go back and assign it manually ?


    yes assign in manually on your Windows PC

    > beside this , there is no output from the show ipv6 neighbors


    not good - until ND is successful ping will fail - same as ARP failure
    for IPv4

    after you change back to manul IPv6 address on PC, turn of "debug ipv6
    nd" to seee what or what is not occuring.

    install Ethereal on PC to be able to capture packet from router to see
    what is actually being received and transmitted
     
    Merv, Aug 24, 2006
    #6
  7. ConceptZone

    ConceptZone Guest

    I can see the ipv6 address of windows XP listed under "show ipv6
    neighbor" but when Itried to ping it , it did not reply :


    Rack1R3#show ipv6 neighbors
    IPv6 Address Age Link-layer Addr State
    Interface
    FE80::212:3FFF:FED1:5985 0 0012.3fd1.5985 REACH
    Fa0/0




    Rack1R3#debug ipv6 packet detail

    Rack1R3#ping FE80::212:3FFF:FED1:5985
    Output Interface: fastethernet0/0
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to FE80::212:3FFF:FED1:5985, timeout is
    2 seconds:

    IPv6: SAS picked source FE80::20F:90FF:FE6E:81E0 for
    FE80::212:3FFF:FED1:5985 (FastEthernet0/0)
    IPV6: source FE80::20F:90FF:FE6E:81E0 (local)
    dest FE80::212:3FFF:FED1:5985 (FastEthernet0/0)
    traffic class 0, flow 0x0, len 100+0, prot 58, hops 64,
    originating
    IPv6: Sending on FastEthernet0/0.
     
    ConceptZone, Aug 24, 2006
    #7
  8. ConceptZone

    Merv Guest

    what is in the IPv6 neighbor cache on the winodws PC - use command
    "ipv6 nc"
     
    Merv, Aug 24, 2006
    #8
  9. ConceptZone

    Merv Guest

    you might want to try shorter addresses for testing purposes - like
    1::1/64 and 1::2/64
     
    Merv, Aug 24, 2006
    #9
  10. ConceptZone

    Merv Guest

    Merv wrote:
    > you might want to try shorter addresses for testing purposes - like
    > 1::1/64 and 1::2/64


    or DEAD:BEEF::1/64 and::2/64
     
    Merv, Aug 24, 2006
    #10
  11. ConceptZone

    ConceptZone Guest

    Okay, I abbreviated the addresses to 1::1 for the router and 1::2 for
    the XP, here is the config of XP:


    Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : 192.168.10.200
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    IP Address. . . . . . . . . . . . : 1::2
    IP Address. . . . . . . . . . . . : fe80::212:3fff:fed1:5985%5
    Default Gateway . . . . . . . . . :



    and here is the config of the router again (I removed the nd because we
    are doing it manually now):


    interface FastEthernet0/0
    description Access link down to customers
    ip address 192.168.10.1 255.255.255.0
    no ip mroute-cache
    duplex auto
    speed auto
    ipv6 address 1::1/64
    ipv6 enable
    end


    Here is the output from EtherPeek NX: ,


    Packet Info
    Flags: 0x00
    Status: 0x00
    Packet Length: 90
    Timestamp: 13:06:30.238618 08/24/2006
    Ethernet Header
    Destination: 33:33:FF:00:00:02
    Source: 00:0F:90:6E:81:E0
    Protocol Type: 0x86DD IPv6
    IP Version 6 Header - Internet Protocol Datagram
    Version: 6
    Priority: 14 Non-congestion-controlled Traffic
    Flow Label: 0x000000
    Payload Length: 32
    Next Header: 0x3A ICMPv6 - Internet Control Message
    Protocol for IPv6
    Hop Limit: 255
    Source Address: 0001:0000:0000:0000:0000:0000:0000:0001
    Destination Address: FF02:0000:0000:0000:0000:0001:FF00:0002
    ICMPv6 - Internet Control Messages Protocol Version 6
    ICMP Type: 135 Neighbor Solicitation
    Code: 0
    Checksum: 0x673A
    Reserved: 0x00000000
    Target Address: 0001:0000:0000:0000:0000:0000:0000:0002
    Source Link-Layer Address
    Option Type: 1 Source Link-Layer Address
    Option Length: 1
    Source Address: 00:0F:90:6E:81:E0

    FCS - Frame Check Sequence
    FCS (Calculated): 0x37D08B8E









    and here is the output of "ipvc nc" from the XP :





    C:\>ipv6 nc
    7: fe80::5445:5245:444f 0.0.0.0:0 permanent
    6: fe80::212:f0ff:fe76:8a9f 00-12-f0-76-8a-9f permanent
    6: 2001:2::1 incomplete (unreachable)
    6: 2001:2::11 incomplete (unreachable)
    6: 2001:2::16 incomplete (unreachable)
    6: 2001:192:168:1::1 incomplete (unreachable)
    6: 2001:db8:1234:42:20f:90ff:fe6e:81e0 incomplete
    (unreachable
    )
    6: 2001:db8:1234:42::1 incomplete (unreachable)
    6: 1::1 incomplete (unreachable)
    5: 2001:db8:1234:42::5 incomplete
    5: 2001:db8:1234:42:20f:90ff:fe6e:81e1 incomplete
    5: fe80::212:3fff:fed1:5985 00-12-3f-d1-59-85 permanent
    5: 2001:192:168:1::2 incomplete
    5: fe80::2 incomplete
    5: 2001:2::10 incomplete
    5: fe80::20f:90ff:fe6e:81e0 00-0f-90-6e-81-e0 stale
    5: 1::2 00-12-3f-d1-59-85 permanent
    4: fe80::210:c6ff:fe87:98c4 incomplete
    3: 2002:8201:1a0a::8201:1a0a 130.1.26.10 permanent
    3: 2002:c058:6301::c058:6301 192.88.99.1 permanent
    2: fe80::5efe:192.168.1.65 127.0.0.1 permanent
    2: fe80::5efe:192.168.1.200 192.168.1.200 permanent
    2: fe80::5efe:192.168.10.200 127.0.0.1 permanent
    1: fe80::1 permanent
    1: ::1 permanent
     
    ConceptZone, Aug 24, 2006
    #11
  12. ConceptZone

    ConceptZone Guest

    the packet is sourcing from 00:0F:90:6E:81:E0 ?

    this is my link-local address of the fastethernet 0/0 of my router

    link-local address is FE80::20F:90FF:FE6E:81E0

    The EtherPeek NX excerpt 00:0F:90:6E:81:E0 without prefixing FE80

    FE80::20F:90FF:FE6E:81E0

    what does this mean? does it mean that router should source the link
    local address with the same subnet of the link local address of XP ?

    what about the 33:33:FF:00:00:02 in the destination of the Ethernet
    header? is the router expecting to see this address on my windows XP
    machine ?

    how this address was generated ?

    I think I am lost
     
    ConceptZone, Aug 24, 2006
    #12
  13. ConceptZone

    Merv Guest

    the etherpeek trace shows that the router is sending a neighbor
    solicitation (NS ) and it looks like the PC is not sending a response


    flush the cache on Windows and try again - "ipv6 ncf"

    also what is the contents of the PC route cache - ipv6 rc

    Please confirm that the Windows firewall feature is not enabled or any
    other PC firewall enabled.
     
    Merv, Aug 24, 2006
    #13
  14. ConceptZone

    Merv Guest

    1. what service packs have been applied to the Windows PC

    2. post the output of show version from the rotuer
     
    Merv, Aug 24, 2006
    #14
  15. ConceptZone

    ConceptZone Guest

    Service Pack 2

    and here is the show version of the router


    Rack1R3#show version
    Cisco Internetwork Operating System Software
    IOS (tm) C2600 Software (C2600-JS-M), Version 12.2(15)T17, RELEASE
    SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2005 by cisco Systems, Inc.
    Compiled Fri 12-Aug-05 15:49 by kehsiao
    Image text-base: 0x80008098, data-base: 0x81D1B940

    ROM: System Bootstrap, Version 12.2(8r) [cmong 8r], RELEASE SOFTWARE
    (fc1)
    ROM: C2600 Software (C2600-JS-M), Version 12.2(15)T17, RELEASE SOFTWARE
    (fc1)

    Rack1R3 uptime is 16 hours, 28 minutes
    System returned to ROM by power-on
    System image file is "flash:c2600-js-mz.122-15.T17.bin"

    cisco 2621XM (MPC860P) processor (revision 0x300) with 93184K/5120K
    bytes of memory.
    Processor board ID JAE0813A4JB (428529633)
    M860 processor: part number 5, mask 2
    Bridging software.
    X.25 software, Version 3.0.0.
    SuperLAT software (copyright 1990 by Meridian Technology Corp).
    TN3270 Emulation software.
     
    ConceptZone, Aug 24, 2006
    #15
  16. ConceptZone

    ConceptZone Guest

    Guys :

    I am sure it is a very basic issue, but it is just because I did not
    try it before, and this is my first time to try playing with IPV6


    MY MACHINE : 1::2
    THE ROUTER : 1::1/64


    Let me break down the results from the EtherPeek NX:



    Target Address: 0001:0000:0000:0000:0000:0000:0000:0002

    and the source address is :

    Source Address: 0001:0000:0000:0000:0000:0000:0000:0001


    but in the Ethernet Header the source is :

    00:0F:90:6E:81:E0

    and the destination in the Ethernet Header is :

    33:33:FF:00:00:02





    Now I am doubting with the destination in the Ethernet header which is

    33:33:FF:00:00:02

    Why The destination address of the Ethernet Header is this address?




    By the way, I do not think it is a router version issue, I tried it on
    another router with the same results. I am missing something and I
    really need your help


    Sorry for my lack of IPV6 concepts
     
    ConceptZone, Aug 24, 2006
    #16
  17. ConceptZone

    Merv Guest

    I set this up on my 2600 and it works.

    Using XP SP2 and 2600 with 12.3(12a)


    HUB#ping 1::2

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 1::2, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms


    HUB#sh ipv6 nei
    IPv6 Address Age Link-layer Addr State
    Interface
    1::2 0 0008.749f.d08b REACH
    Fa1/0

    HUB#sh run int fa 1/0
    Building configuration...

    Current configuration : 95 bytes
    !
    interface FastEthernet1/0
    no ip address
    duplex auto
    speed auto
    ipv6 address 1::1/64
    end



    HUB#sh ver
    Cisco Internetwork Operating System Software
    IOS (tm) C2600 Software (C2600-IK9O3S3-M), Version 12.3(12a), RELEASE
    SOFTWARE (
    fc2)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2005 by cisco Systems, Inc.
    Compiled Thu 13-Jan-05 18:06 by kellythw
    Image text-base: 0x80008098, data-base: 0x819FA39C

    ROM: System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1)
    ROM: C2600 Software (C2600-IK9O3S3-M), Version 12.3(12a), RELEASE
    SOFTWARE (fc2)


    HUB uptime is 32 minutes
    System returned to ROM by power-on
    System image file is "flash:c2600-ik9o3s3-mz.123-12a.bin"


    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\>netsh interface ipv6 add address "Local Ethernet" 1::2
    Ok.


    C:\>
    C:\>
    C:\>netsh interface ipv6 show interface
    Querying active state...

    Idx Met MTU State Name
    --- ---- ----- ------------ -----
    5 0 1500 Connected Local Ethernet
    4 2 1280 Disconnected Teredo Tunneling Pseudo-Interface
    3 1 1280 Connected 6to4 Pseudo-Interface
    2 1 1280 Connected Automatic Tunneling Pseudo-Interface
    1 0 1500 Connected Loopback Pseudo-Interface


    C:\>ipv6 rc
    ::1 via 1/::1 (stale)
    src 1/::1
    PMTU 1500

    C:\>ipv6 nc
    5: 1::1 00-b0-64-4c-e5-50 stale
    5: fe80::201:96ff:fee0:6e30 incomplete
    5: fe80::208:74ff:fe9f:d08b 00-08-74-9f-d0-8b permanent
    5: 1::2 00-08-74-9f-d0-8b permanent
    5: fe80::2b0:64ff:fe4c:e550 00-b0-64-4c-e5-50 stale
    4: fe80::5445:5245:444f 0.0.0.0:0 permanent
    2: fe80::5efe:192.168.1.2 192.168.1.2 permanent
    2: fe80::5efe:169.254.134.9 127.0.0.1 permanent
    1: ::1 permanent
    1: fe80::1 permanent



    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\>netsh interface ipv6 add address "Local Ethernet" 1::2
    Ok.


    C:\>
    C:\>
    C:\>netsh interface ipv6 show interface
    Querying active state...

    Idx Met MTU State Name
    --- ---- ----- ------------ -----
    5 0 1500 Connected Local Ethernet
    4 2 1280 Disconnected Teredo Tunneling Pseudo-Interface
    3 1 1280 Connected 6to4 Pseudo-Interface
    2 1 1280 Connected Automatic Tunneling Pseudo-Interface
    1 0 1500 Connected Loopback Pseudo-Interface


    C:\>ipv6 rc
    ::1 via 1/::1 (stale)
    src 1/::1
    PMTU 1500

    C:\>ipv6 nc
    5: 1::1 00-b0-64-4c-e5-50 stale
    5: fe80::201:96ff:fee0:6e30 incomplete
    5: fe80::208:74ff:fe9f:d08b 00-08-74-9f-d0-8b permanent
    5: 1::2 00-08-74-9f-d0-8b permanent
    5: fe80::2b0:64ff:fe4c:e550 00-b0-64-4c-e5-50 stale
    4: fe80::5445:5245:444f 0.0.0.0:0 permanent
    2: fe80::5efe:192.168.1.2 192.168.1.2 permanent
    2: fe80::5efe:169.254.134.9 127.0.0.1 permanent
    1: ::1 permanent
    1: fe80::1 permanent

    C:\>ipv6 rc
    1::1 via 5/1::1
    src 5/1::2
    PMTU 1500
    161 seconds since ICMP error
    fe80::201:96ff:fee0:6e30 via 5/fe80::201:96ff:fee0:6e30 (stale)
    (zone-specific)
    src 5/fe80::208:74ff:fe9f:d08b
    PMTU 1500
    257 seconds since ICMP error
    ::1 via 1/::1 (stale)
    src 1/::1
    PMTU 1500
     
    Merv, Aug 25, 2006
    #17
  18. ConceptZone

    Merv Guest

    These are the Windows command that I used in cmd window

    ipv6 ncf

    netsh interface ipv6 add address "Local Ethernet" 1::2

    netsh interface ipv6 show interface

    ipv6 nc

    ipv6 rc


    Get the interface name to use between the quotes by looking
    at name show in the output of ipconfig /all
     
    Merv, Aug 25, 2006
    #18
  19. ConceptZone

    ConceptZone Guest

    Merv,

    Can you imagin that it is working now , here is what happened :

    luckily My windows XP gave me a very cool Blue Screen , and the windows
    restarted.

    then I went again to check the connectivity and I am able to ping now !

    Rack1R3#show ipv6 neighbors
    IPv6 Address Age Link-layer Addr State
    Interface
    1::2 0
    0012.3fd1.5985 REACH Fa0/0
    FE80::212:3FFF:FED1:5985 104 0012.3fd1.5985 STALE
    Fa0/0


    Rack1R3#ping 1::2

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 1::2, timeout is 2 seconds:
    !!!!!


    I wondered like why every thing is okay now while before not, so I
    recaptured the traffic and I am going to list the result from NX Peek
    software :

    IP Version 6 Header - Internet Protocol Datagram :
    -----------------------------------------------------------------------


    Source Address: 0001:0000:0000:0000:0000:0000:0000:0001
    Destination Address: 0001:0000:0000:0000:0000:0000:0000:0002

    Ethernet Header :
    -------------------------


    Destination: 00:12:3F:D1:59:85
    Source: 00:0F:90:6E:81:E0

    Notice the 00:12:3F:D1:59:85 in the destination of the ethernet
    header , this is the link local address of the WINDOWS XP

    before this address was 33:33:FF:00:00:02 <---- I pulled my hair
    enough to know where this address came from but I could not figure it
    out.


    maybe I should blame MICROSOFT :)


    Thanks Merv and thanks for the rest
     
    ConceptZone, Aug 25, 2006
    #19
  20. ConceptZone

    Merv Guest

    this is the link local address of the WINDOWS XP
    >
    > before this address was 33:33:FF:00:00:02 <---- I pulled my hair
    > enough to know where this address came from but I could not figure it
    > out.


    NS requests can be multicast and unicast.

    The above address is an IPv6 multicast MAC address

    In IPv4 ARP requests are sent to broadcast MAC address

    In IPv6 there is no broadcast address and no broadcast MAC address

    so to send NS multicast a multicast MAC address is used

    IPv6
    multicast
    address Description
    FF02::1 The all-nodes address used to reach all nodes on the same
    link.

    FF02::2 The all-routers address used to reach all routers on the same
    link.

    so the multicast MAC address used to send to IPv6 multicast address
    FF02::2 is 33:33:00:00:00:02

    I do not know why windows would try to use a multicat MAC address of
    33:33:FF:00:00:02. If it is try to send out a router solication I
    would have thought it should use 33:33:00:00:00:02

    There is a new OUI format for IPv6 Multicast. The leading two bytes are
    set to 33:33, while the following 4 bytes/32bits are available for
    address mapping from the last 32 bits of the 128 bit Multicast address.


    According to this model, all routers would have the following address:

    33:33:xx:xx:xx:xx: where X is the last 32 bits of the address

    33:33:00:00:00:02
     
    Merv, Aug 25, 2006
    #20
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. atodd_109

    Router Pinging Devices

    atodd_109, Jul 9, 2003, in forum: Cisco
    Replies:
    1
    Views:
    2,027
    sPiDEr
    Jul 9, 2003
  2. Anand Mohabir
    Replies:
    1
    Views:
    1,162
    Johnny Routin
    Oct 22, 2004
  3. Oliverw

    Pinging between serial link.

    Oliverw, Jun 30, 2006, in forum: Hardware
    Replies:
    1
    Views:
    772
    scam3r
    Jul 6, 2006
  4. Replies:
    3
    Views:
    495
  5. timolthy
    Replies:
    0
    Views:
    2,199
    timolthy
    Oct 17, 2009
Loading...

Share This Page