IPv6 address question

Good morning everyone,
I need to find this address:
fe80::404d:9415:115a:f39c
It looks like a link local address.  But there is no ffee inserted between the 6th and 10th bits where the mac address would be inserted.  Can I find the mac address from this IP address?
Thanks
Shane

If the address is being seen on a span port, your best bet might be snooping ICMPv6 neighbor solicitation packets with that address as the source.  It's probably a windows-7 box somewhere; other vendors such as Apple or Linux tend to use the EUI-64 mappings on their link-local addresses.   In an Active Directory environment you can use group policy to discourage use of v6 privacy addresses by windows systems.
Depending on your DNS infrastructure, the dual-stack (presumably) box might be registering 6to4 or other AAAA records.   The 6to4 case is only likely if it's IPv4 address is public, rather than rfc-1918 private.
For SNMP, I shouldn't have said ports; you want the MIB that lets you query the neighbor discovery table of whatever is doing the vlan routing; be that a switch, firewall, or an actual router.
An example of a European university doing this sort of monitoring is described at:
  http://www.terena.org/activities/campus-bp/pdf/gn3-na3-t4-cbpd132.pdf
FYI, if you have dual-stack devices on your network, I presume you are filtering for rogue RA devices and rogue DHCPv6 servers, e.g. on our client switchs we define:
ip access-list extended v4client
deny   udp any eq bootps any eq bootpc
deny   icmp any any redirect
permit ip any any
ipv6 access-list v6client
  deny udp any eq 547 any eq 546
  deny icmp any any router-advertisement
  deny icmp any any redirect
  permit ipv6 any any
and then on the client device interface switchports we filter:
ip access-group v4client in
ipv6 traffic-filter v6client in
This requires v6 allocations in the TCAM of course, e.g.
   sdm prefer dual-ipv4-and-ipv6 default
-- Jim Leinweber, WI State Lab of Hygiene

Similar Messages

  • IPv6 address questions

    I'm having trouble understanding IPv6 addresses. In IPv4 the CIDR slash notation means what subnet the address is in. But a /48 in IPv6 does not mean subnet. I have no idea what it means. For instance I've seen the address 2001:0:1:5::1/64, and I have no idea what the /64 means. Can someone explain it?
    Link local address: it's not enough to put an FE80 to identify this kind of address, but for some reason, they decided to put FFFE in the middle of the ipv6 address. What were they thinking? Why do they need to identify this kind of address TWICE within the address, AND why couldn't they put the FFFE at the end or the beginning, but instead they put it right in the middle? WTF?
    3 types of addresses? What why? with that many bits in an address there's no reason to have 3 of them. Theres enough for everyone.
    Illogical allocation of bits. A global ip address reserves the last 64 bits for the host ip. This is equivalent to 18 quintillion hosts on ONE SUBNET! YEAH RIGHT! There's no way that's even remotely logical, feasible, or practical. The more I look at IPv6 notation, the more I think my 5th grader could have come up with a better design.
    Also, why didn't they adopt the OSI model of addressing, like in ISIS. That has more than enough addresses for everyone.
    Obviously i'm missing the point completely on IPv6. It sounds like the most unthoughtful pile of rubbish ever conceived. So can someone please direct me to a place or explain what the thought process was when creating this new addressing scheme?
    bonus points: what happened to ipv5, and what was ipv1,ipv2,ipv3? I think the inventor should have called it IPv2000, because he really went overboard.

    Hi Richee,
    ISPs generally give ipv6 addresses to companies with /48 prefix length.
    The company receiving this can create its own subnets within the /48 and /64 range.
    The last 64 for bits of the address are generally used to insert the mac-address of the local interface when using stateless auto-configuration, but you can use it for subnetting as well, if you configure your addresses manually.
    For the other questions I think this link could give you more info:
    http://www.cisco.com/en/US/tech/tk872/tsd_technology_support_protocol_home.html
    And one more little addition:
    Nothing is perfect in this universe. Everything can be considered good or bad, it is just a question of viewpoint.
    Try to look at ipv6 from both viewpoints. You will have surprises.
    Cheers:
    Istvan

  • IPv6 Address Management and Security Questions

    I'm trying to draft an IPv6-based version of our location's current routing configuration in anticipation of when our ISP will finally roll it out, and address management has been giving me the biggest headache - ironic, considering IPv6 was supposed to simplify address allocation.
    My first config draft was made assuming that I would be getting a static /56 or /60 prefix from the ISP, and I was just going to insert the prefix into my DHCP pools and there would be no issues. That was before reading around and discovering that some ISPs are considering prefix delegation (PD) for both residential and business accounts instead of static blocks. Now I have questions about how to stick as close to the current IPv4 configuration as possible.
    For the PD scenario, what I am looking at now are two addresses ranges for each network - a ULA /120 space that I want to control using stateful DHCPv6, and the global space which can be /64 and auto-configured. That way there will be a "private" address space for internal routing in the event of a prefix change or an extended outage. But I'm not sure how the config should look for such a scenario. What I have drafted so far is this:
    ipv6 dhcp pool DHCP6_INTERNAL
     address prefix FDAB::1:0/120
     domain-name whatever.net
     dns-server FDAB::1:1
    ipv6 dhcp pool DHCP6_DMZ-WIFI
     address prefix FDAB::2:0/120
     domain-name guest.whatever.net
     dns-server FDAB::2:1
    interface GigabitEthernet0
     description WAN-LINK
     ipv6 enable
     ipv6 address dhcp
     no ipv6 unreachables
     no ipv6 redirects
     ipv6 flow ingress
     ipv6 flow egress
     ipv6 virtual-reassembly in
     ipv6 nd autoconfig default-route
     ipv6 dhcp client pd hint ::/56
     ipv6 dhcp client pd ISP-PREFIX
     zone-member security OUTSIDE
     speed auto
     duplex auto
     no cdp enable
    interface FastEthernet8.1
     description VLAN_1-INTERNAL
     encapsulation dot1Q 1 native
     ipv6 enable
     ipv6 address FDAB::1:1/120
     ipv6 address ISP-PREFIX ::1:0:0:0:1/64
     ipv6 flow ingress
     ipv6 flow egress
     ipv6 virtual-reassembly in
     zone-member security INSIDE
     ip tcp adjust-mss 1300
     ipv6 dhcp server DHCP6_INTERNAL
     ipv6 nd managed-config-flag
     ipv6 nd other-config-flag
    interface FastEthernet8.2
     description VLAN_2-DMZ-WIFI
     encapsulation dot1Q 2
     ipv6 enable
     ipv6 address FDAB::2:1/120
     ipv6 address ISP-PREFIX ::2:0:0:0:1/64
     ipv6 flow ingress
     ipv6 flow egress
     ipv6 virtual-reassembly in
     zone-member security DMZ
     ip tcp adjust-mss 1300
     ipv6 dhcp server DHCP6_DMZ-WIFI
     ipv6 nd managed-config-flag
     ipv6 nd other-config-flag
    Will this config work? By which I mean: will the DHCPv6 servers provide ULA addresses, and will SLAAC work for global address allocation? If not, what needs to be changed?
    Also, another question. I found a few references to a prefix name (the "ISP-PREFIX") which can be used as part of a static IPv6 address on an interface, which is a good idea in case the prefix changes. But that brings up another concern - if the prefix changes, that will invalidate ACLs referencing the global addresses using the previous prefix. Is there anything similar to the prefix name string that can be used in ACLs to keep this from occurring?

    DHCPv6-PD is not necessarily dynamic the same way as DHCP was with the public IPv4 addresses in the IPv4 world.
    While the outside network (PPPoE, DHCPv6, anything) might be truly dynamic and changing with possibly every login session, the DHCPv6 delegated prefix might be tied to your login credentials or DHCPv6 client's DUID after the first connection. A bit like a DHCP lease reservation.
    If that is the case, there is some possibility that your ISP will run reverse route injection, and will always route your "fixed" prefix  to the currently active dynamic "outside" address.
    Talk to your ISP and have them confirm that, once the PD'd /48 or /56 is initially assigned, it won't change, and that the same prefix will be delegated every time. Then you can treat it as if it were fully static, and you won't have to go down the ULA path.
    I contacted one of our local ISPs, and they're doing it exactly that way: PPPoE for IPv4 and IPv6 (fully dynamic), and DHCPv6-PD with the /48 tied to the PPPoE login credentials. I might change to that ISP sooner or later.
    With my current ISP, my IPv6 access is 6RD based. I get a /60, with my current public ipv4 address (by DHCP) embedded into those 60 bits. Readressing is bound to happen sooner or later, and it happens every so often, and it breaks my IPv6 ACLs.
    I'm also looking for a way to write IPv6 ACLs with wildcard bits, not prefix/mask, so I can use them with ZBFW. So far, no sign of it.
    A few more comments:
    ULA addressing: 
    It may look tempting, plausible and intuitive to use dual global and ULA addressing. 
    I started this way as well. However, it turns out that Windows 7 has (had?) some issues with proper source address selection. The "longest common prefix" rule never seemed to work properly. In some cases, it would pick the global address to talk to ULA hosts, or stubbornly insist to use the ULA address to talk to an IPv6 internet host. It was a frustrating experience. Be sure to test this to the full extent (and back, and again and then some more) with every operating system you intend to use.
    Using /120:
    Be sure to test this as well, and very thoroughly. Subnet masks longer than /64 are sometimes called "uncharted territory" in IPv6. Longer subnet masks will break SLAAC, and there may be (embedded) devices that will not react benevolently to a subnet mask other than /64, or simply lack support for DHCPv6.
    adjust-mss
    I see you have "ip tcp adjust-mss 1300". While PMTUd may be mandatory with IPv6, I found it being broken already :-( . "ipv6 tcp adjust-mss .... " is now a separate command since IOS 15.4(1). I would suggest considering it, depending with your experience with PMTUd on IPv6.

  • Question about configuring Global IPv6 address on interface

    It seems when configuring a global IPv6 address on a layer 3 interface, we cannot specify the whole 128 bit address. We can only specify the prefix and leave the last 64 bits to be generated by the router:
    http://www.cisco.com/en/US/docs/ios-xml/ios/ipv6/configuration/12-2sx/ip6-addrg-bsc-con.html#GUID-70188E8F-16D2-4DD1-8DE2-70073FF37CC8
    Then how can I specify the router address to the client using DHCPv6? Do I have to keep the router RAs while using DHCPv6 together?
    Thanks.
    zhenning

    Hi Leo,
    Where is it stated in this doc that you can't configure a /128 ?
    Router(config-if)#ipv add 2001::1/128
    Router(config-if)#do sh ipv int lo0
    Loopback0 is up, line protocol is up
      IPv6 is enabled, link-local address is FE80::9CD7:2EFF:FEF0:99FA
      Global unicast address(es):
        2001::1, subnet is 2001::1/128
      Joined group address(es):
        FF02::1
        FF02::2
        FF02::1:FF00:1
        FF02::1:FFF0:99FA
      MTU is 1514 bytes
      ICMP error messages limited to one every 100 milliseconds
      ICMP redirects are enabled
      ND DAD is not supported
      ND reachable time is 30000 milliseconds
    The IOS accepts it on any interface but it will only work for Loopbacks.
    I configured a /126 between 2 serials and it worked without any problem but for prefix-advertisement through RA  to work then you must configure a /64.
    Regards.
    Alain

  • Connect to server using IPv6 address in afp URL

    I'm not sure whether this is the correct forum for this question, but does anyone know whether I can specify an IPv6 address in the "Connect to Server" dialog?
    I've setup IPv6 over direct-wired ethernet between my MBP and Mini. Using ping6, I can ping one from the other (but only when I specify -I en0)
    I've tried the following URLs:
    afp://[fe80::0216:cbff:dead:beef]
    afp://[fe80::0216:cbff:dead:beef%en0]
    I think the problem might be because I don't have an IPv6 router between the two hosts.
    Thanks.
    MacBook Pro 15 2.0GHz   Mac OS X (10.4.8)   mini 1.83GHz

    I have the same problem and for me it extends to everything from SSH to HTTP. I think that mac has a bug in it networking. I can't get it to work on any mac I've tried. Can your mini connect to your laptop?
    I've been googling for 3 days and can't find any solution.
    MBP   Mac OS X (10.4.9)  

  • Is it normal?(NetworkManager applet's strange output & 3 IPv6 address)

    1) label ppp0 appears in NetworkManager applet every time when I up vpn-connection
    2) Also something strange with enp5s0. Output of "ip addr":
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
        inet6 ::1/128 scope host
           valid_lft forever preferred_lft forever
    2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
        link/ether 10:bf:48:20:61:a4 brd ff:ff:ff:ff:ff:ff
        inet 10.0.122.144/8 brd 10.255.255.255 scope global dynamic enp5s0
           valid_lft 9283sec preferred_lft 9283sec
        inet6 2002:5be2:8e63:b:12bf:48ff:fe20:61a4/64 scope global noprefixroute dynamic
           valid_lft 2592003sec preferred_lft 604803sec
        inet6 fec0::b:12bf:48ff:fe20:61a4/64 scope site noprefixroute dynamic
           valid_lft 2592003sec preferred_lft 604803sec
        inet6 fe80::12bf:48ff:fe20:61a4/64 scope link
           valid_lft forever preferred_lft forever
    3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
        link/ether 00:08:ca:67:17:e9 brd ff:ff:ff:ff:ff:ff
    9: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1400 qdisc pfifo_fast state UNKNOWN group default qlen 3
        link/ppp
        inet 91.226.141.81 peer 1.1.1.1/32 scope global ppp0
           valid_lft forever preferred_lft forever
        inet 91.226.141.81/32 brd 91.226.141.81 scope global ppp0
           valid_lft forever preferred_lft forever
    Is it normal that this interface has three IPv6 addresses?

    Hi,
    We are hitting the software bug and the bug ID is CSCsz56711
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsz56711
    The issue is related to PCI componenet on the AP hardware and log that points to that is..
    bsnInitRcbSlot: slot 0 has venus radio(UNSUPPORT)
    The Replacement is the resolution and please contact your reseller or partner and if ur are the partner then RMA ids the resolution..
    Lemme know if this answered ur question and please dont forget to rate the usefull posts!!
    Regards
    Surendra

  • Why do the connected devices to the router have the smae IPV6 address?

    Hi,
    Now I meet the issue
    The operation steps on router (WRVS4400N):
    1.Set the IP mode as Dual-stack IP and then save
    2.Disable the IPV4 DHCP server
    3.Use other deivces to connect the router.
    The connected devices have the same IP address(2005:123:456:789::1),I am confused,why is it?
    please help.
    Thanks!

    Hello,
    The WRVS4400N is in fact assigning IPv6 addresses to all the devices connected to it, but the WRVS4400N does not show a table with the IPv6 addresses assigned to each device connected, it only shows the IPv4 addresses and the respective MAC address for each device. The IPv6 of the WRVS4400N is an aggregetable global unicast IPv6  address (See the image below)
    If you go to Setup > LAN you will see that you cannot modify the prefix of the IPv6 address, all you can modify is the postifx and prefix length field (As you can see in the image below).
    For more information about these fields and general IPv6 configuration,  please refer to the article IPv6 Configuration on WRVS4400N Wireless-N  Gigabit Security Routers
    The only way you have to see the IPv6 address assigned to each device connected to the WRVS4400N is to check on each device the IPv6 address assigned. The WRVS4400N does not provide this information. You can see from the below picture the IPv6 address assigned to my computer. As you can see, the WRVS4400N assign the the computer the prefix 2002:c0a8::/6. Then you can see the actual IPv6 address which is 2002:c0a8:0:b182:e6a:9b0e:cdcf.
    As you can see, the initial part (The prefix) remains the same, since these are the first 64 bits of the whole IPv6 address. The other 64 bits of the IPv6 address represents the interface ID, that is, the device that is connected to the WRVS4400N.
    I hope you find this information helpful. If you have further questions, don't hesitate to ask.
    Alejandro Moncada
    SBCD Engineer
    [email protected]

  • Static ipv6 address from a /64

    Hi all
    I have a cisco 6500 that i configured a /64 on int1/39 that has a linux server connected to it and supressed RAs. On this server i assigned a static ip, 
    2001:x:77:4::2. i can ping to/from the server with no issues. However when doing a show ipv6 neighbors i still see the auto config ipv6 on fast1/39.
    interface FastEthernet1/39
    ip address x.x.x.33 255.255.255.240
    ip flow ingress
    speed 100
    duplex full
    ipv6 address 2001:x:77:4::1/64
    ipv6 nd ra suppress
    spanning-tree portfast edge
    My question why is that attached server getting an auto config ipv6 address when i have the supress command under interface. Also is it correct to assign a /64 to an int/vlan and statically assign ips instead or should i move to a /56. I'm not really sure if what im doing is common or if it create issues.
    TIA, Paul

    Deepak, while i assigned a static ip to the server doing a show ipv6 neighbor shows this static ip and it also shows the auto config ip. Again based on my config above shouldnt it jsut show the static ip. Why is SLAAC in play here if i have
    ipv6 nd ra suppress on the interface, will this setup cause issues.
    sh ipv6 neighbors
    IPv6 Address                              Age Link-layer Addr State Interface
    2001:x:77:4::2                            1 0019.b9e6.5647  STALE Fa1/39
    2001:x:77:4:219:B9FF:FEE6:x     49 0019.b9e6.5647  STALE Fa1/39
    FE80::219:B9FF:FEE6:5647                    1 0019.b9e6.5647  STALE Fa1/39
    note i can ping the static and auto config ip and the server lists both of them.

  • IPv6 address allocation

    I've got a best practices question.
    We're planning our transition to IPv6.  We've gone to ARIN and aquired a /48 for the company.  My question is about the best way to manage that space.
    Our company already has one a second office location (which is international) in addition to our corporate offices.  I expect we will have more within the next couple of years.  I can allocate pieces of our /48 to these locations (trying to plan careful to support route aggregation) or I can have each of our international locations get their own /48 from their respective registries.
    What's the intent about the best way to handle this?
    Thx
    Patrick

    Hi Patrick,
    before jumping to provide an answer I would like you to consider the nature of the network you are building and whether or not you will be using own dedicated links or using the Internet as transmission infrastructure.
    In the first case you own provider independent IPv6 addressing could be a good idea if you run BGP. This also would allow you to be multihomed in different countries and could also become a transit AS.
    But if you only are forwarding own traffic and have a couple of connection in different countries with stable and reputable ISPs maybe the only thing you need is provider assigned space for each location and you do not even need to run BGP only an IGP to prevent your internal traffic from spilling on the Internet. This would prevent rerouting of traffico from a different link to a network with a failed ISP connection.
    You might also consider provider independent address space assigned by RIR in the country where you have your subsidiaries and use BGP to advertise the whole address space to the entire world and achieve redundancy.
    Fact is more parameters are needed to answer you question:
    Are you running BGP now (do you have an AS number)
    Are you (or willing to be) a transit network
    Are you looking for multihoming (in a single RIR area or multiple)
    How much money are investing to obtain resilience and reliability.
    I hope this question will help you better define your problem
    Cheers
    Fabio

  • Regarding the ipv6 address handling in oracle pl/sql

    Hi,
    This is regarding the ipv6 address handling in pl/sql.
    Can we use any c program inside the oracle as C/C++ provides more buitl in function for address handling.
    Are there are any similar functions in pl/sql.
    Kindly let me knoe if there is a way to calculate ipaddress masking.
    Are there any system functions in oracle similar to inet_ntop/inet_pton to validate ipv6 addresses.
    If not kindly let me know if there is any alternate way.
    Thanks and Regards,
    Anantha.

    Billy  Verreynne  wrote:
    Sven, he means converting a numeric network address to a presentation (character) address - and vice versa.Ok I understand. Validating for me had been either
    a) validate that the IP address does really exist. This could have been implemented by executing some kind of ping command.
    or
    b) validate that the string that hold the human readable IPv6 address is correct same a as string like "[email protected]" looks like a valid email address. This of cause would be implemented with some kind of regexp expression.
    However it seems he wants a conversion of the string (human readable ipv6) into a machine readable (hex) representation. Not sure why this is needed, But I agree that simply reusing the OS C routines seems to be the best way to do it.
    I strongly doubt that the result is very useful in Pl/sql. So the big question (as so often) would be what is the business case behind this requirement. Maybe some part of the logic needs to be implemented outside the database anyways. Then it could be useful to add this conversion to this outside part as well.

  • Getaddrinfo function returns IPv4-mapped IPv6 addresses in canonical name

    When I use the getaddrinfo function with flag AI_CANONNAME, then in ai_canonname  IPv4-mapped IPv6 addresses is returned even for IPV6 disabled machine.
    So my question is that from where this canonical name is returned, I didn't found in /etc/nodename /etc/hosts or in /etc/inet/hosts or in /etc/interfacefile files.

    It's only showing "unknown" for the IPv6 address.
    Go into your IPv6 properties, and set the IP and DNS address settings to be obtained automatically.
    Then in Manage network adapters windows, change the view options to show Menu, then click on Advanced, Advanced, and make sure IPv4 is on top instead of IPv6.
    Ace Fekay
    MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/
    This post is provided AS-IS with no warranties or guarantees and confers no rights.

  • IPv6 DNS Questions with DirectAccess

    Hey,
    I'm hoping someone can answer some fundamental questions that I am having around DirectAccess for a customer that I'm working with.  We are putting in Direct Access with a more complicated scenario, but there are some fundamental questions about IPv6
    that I cannot quite get answered.  We have the tunnel established over IPHTTPS, however, I am not able to resolve internal resources.
    We have a red x next to the DNS Monitoring in the Operations Console.  DNS64 is green. 
    1) I know that you don't need IPv6 on our internal servers to use DirectAccess.  However, in this situation they have IPv6 unbound from the NICs on all the servers except for the DA server (and the Windows 7 clients).
    2) Brings me to the DNS question.  Internal DNS servers do not have IPv6 bound to the NIC and they do not register AAAA records in DNS.  Does that pose any issues with the NRPT?
    Thanks for your help!
    Bob

    Hello,
    After talking with Microsoft support here was the actual issue.
    First, the issue around the DNS going red:
    Set-DAClientDnsConfiguration -DnsSuffix '.internal.company.com' -DnsIPAddress @('ipv6 address of the DA server') -Verbose -ComputerName 'DAServer.internal.company.com’
    That fixed that issue, however, we were still having issues with the routing to internal servers. 
    We did the following further troubleshooting with Microsoft,
    We checked if client was able to get to the IPv6 address of the server – failed
    Checked if the client was able to get to the IPHTTPS address of the server – worked
    On the DA server itself, we were unable to ping the IPv6 address of the server      (fd58:c2f1:4a56:5555::1). We tried pinging this IP address using the IPHTTPS address on the DA server and that failed
    as well.
    Since we were unable to get to the IP address on the server itself, we just removed and re-added      the IPv6 address of the server, on the Internal NIC, and we were then able to ping the server’s IPv6
    address.
    But, clients were still unable to connect.
    So we realized that the forwarding must have not been enabled on the NICs.
    We checked for Forwarding being enabled on the IPHTTPS and Internal interface of the DA server
    and found that this was not enabled on the Internal interface.
    Once we enabled this, client machine was then able to connect to internal resources over Direct Access.
    To enable forwarding on the NIC we ran the below command,
    netsh int ipv6 set int <interface_id> forwarding=enabled
    Thanks,
    Bob

  • 6to4 Addresses vs Regular IPv6 Addresses - Confusion

    Hi All, (Apologies if this question appears twice. Apparently I had an interface problem)
    I'm finishing up my studies on the IPv6 portion of the CCNA material, and my book seems to completly ignore the fact that 6to4 addresses seem to look different than how the rest of the chapter portrays IPv6 addressing. I've done google searches, and unfortunately I don't have anyone at work who is versed enough in this who will know, so I'm hoping someone can help.
    1. A normal IPv6 address:  2001:0db8:3c4d:0012:0000:0000:1234:56ab
       The same address in shorthand:  2001:db8:3c4d:12::1234:56ab
       A /64 of this space with autoconfiguration:  2001:db8:3c4d:12::/64 eui-64
       All of these addresses have, or will have 8 octets if written in long-hand, in other words - a valid IPv6 address.
    Here's my problem:  The addresses in the 6to4 section look like this:
       ipv6 address 2001:db8:2:2::1/64
    The book fails to mention what the "1" before the /64 is for, but I am assuming that it is an identifier and not part of the IPv6 address due to the " :: "   However, if this is the case, I only see 4 octets, and no eui-64 command, directing that the other 4 will be populated by the MAC padded.  And the "ipv6 address" syntax leads me to believe that this is a host address, and not a block/space statement (i.e. "ip address 192.168.0.1. 255.255.255.0," as opposed to "network 192.168.0.0 255.255.255.0)."
    If someone could shed some light on this, it would be most appreciated, as it is very confusing.

    Also, 6to4 IPv6 addresses have the IPv4 address of the 6to4 gateway embeded in them as well.  That is why they have a whole reseved block of 2002:/16.  Any gateway can algorithmically extract the IPv4 address for forwarding.
    2002:0b0c:0205:5/48 for example, would be correlated to IPv4 address 11.12.2.5 (which is the decimal of the IPv4 address 0b0c:2025 shown in hex)
    Earl Carter wrote a nice blog article on the general topic of IPv6 addresses at http://blogs.cisco.com/security/ipv6-addressing/
    And the commonutiy has settled on calling the 16-bit numbers between the colons "hextets."  In IPv4, each 8-bit portion between dotrs is called an "octet."  The truly pedantic will object taht a hextet should be 6 dits, bit "hextet" is easier to say than "hexadecitet." :-)
    Anotehr trivia point:  The letters in an IPv6 address should awalys be lower case.
    More arcana can be found at http://tools.ietf.org/html/draft-hartmann-6man-addresspartnaming-01, which is on track to become an RFC.

  • IPv6 - Newb Question (BGP Advertisement)

    Hi Everyone - Quick question on IPv6 subnetting
    If we are allocated a /32 from an RIR (eg 2001:0DB0::/32), and we advertise the /32 to our upstream Inet providers - Assigning
    2001:0DB0:0:10::1/64 to a loop Interface, we *should* be able to reach the Upstream providers IPv6 addresses with a source of the loop interface(As the /64 is within the /32 subnet)?
    Cheers.

    Hi John,
    Correct. You should be able to use that technique to perform initial testing for your ipv6 connectivity. You can use extended ping for instance to specify the loopback interface as the source address.
    Regards

  • Understanding IPv6 Address from RIR

    Hi Folks,
    I am very new to IPv6 and having some question need you guys advices as we are planning to integrate IPv6 to our existing network environment.
    RIR allocated 2300:1480::/32 to us, but they said the assignment windows is 2300:1480::/48.
    So what is the actual subnet to us? we don't quite understand the address assignment. How about 33-47 bits, it is belong to me or belong to RIR?
    (Actual IPv6 address has been removed/modified)
    Sent from Cisco Technical Support iPhone App

    Hi Sean,
    Further clarification with APNIC, this is their reply....
    Does it meant, bit /33-47 is my main subnet And /48-/63 id customer's subnet and /64 is interface id or host in generally?
    +++++
    For your own infrastructure, you can assign the IP as per your
    requirement. For your customers, you can only assign up to /48. If you
    need to assign more then /48 to your customers, you need to submit your
    APNIC second opinion request.
    +++++
    Sent from Cisco Technical Support iPhone App

Maybe you are looking for