http://www.youtube.com/watch?v=1rE7oiIQ7fY&feature=player_embedded

Posted by Peter Kurdziel on March 16, 2011
http://www.youtube.com/watch?v=1rE7oiIQ7fY&feature=player_embedded

Posted in BGP, IPV6, Service Provider | Leave a Comment »
Posted by Peter Kurdziel on February 3, 2011
APNIC has requested and received two IPv4 /8s (39/8 & 106/8), which has in turn triggered the “last five” policy at IANA giving each Regional Internet Registry (RIR) one additional /8 and depleting the global free pool of IPv4 forever.
The final five went out like this just moments ago:
102/8 AfriNIC 2011-02 whois.afrinic.net ALLOCATED
103/8 APNIC 2011-02 whois.apnic.net ALLOCATED
104/8 ARIN 2011-02 whois.arin.net ALLOCATED
179/8 LACNIC 2011-02 whois.lacnic.net ALLOCATED
185/8 RIPE NCC 2011-02 whois.ripe.net ALLOCATEDIn order to continue to grow the Internet, we must deploy IPv6.

Posted in IPV6 | Leave a Comment »
Posted by Peter Kurdziel on April 19, 2010
Configuring an IPv6 Multiprotocol BGP Peer Group and advertising a route example.
Scenario
Configure R1 & R2 for IPv6 Multiprotocol BGP using a Peer Group and
advertising R1 & R2′s loopbacks.
Simple two router network for demonstration purposes.
R1<—->FR<—–>R2
Configuration
r1
ipv6 unicast-routing
interface Loopback99
no ip address
ipv6 address 2001:DB8:1111::1/48
interface Serial2/0
ipv6 address 2001:DB8:0:CC00::1/48
router bgp 65100
no bgp default ipv4-unicast
neighbor group1 peer-group
neighbor 2001:DB8:0:CC00::2 remote-as 65100
neighbor 2001:DB8:0:CC00::2 peer-group group1
address-family ipv6
neighbor group1 activate
neighbor 2001:DB8:0:CC00::2 peer-group group1
network 2001:DB8:1111::1/48
exit-address-family
r2
ipv6 unicast-routing
interface Loopback99
no ip address
ipv6 address 2001:DB8:1111::2/48
interface Serial2/0
ipv6 address 2001:DB8:0:CC00::2/48
router bgp 65100
no bgp default ipv4-unicast
neighbor group1 peer-group
neighbor 2001:DB8:0:CC00::1 remote-as 65100
neighbor 2001:DB8:0:CC00::1 peer-group group1
address-family ipv6
neighbor group1 activate
neighbor 2001:DB8:0:CC00::1 peer-group group1
network 2001:DB8:1111::2/48
exit-address-family
Verification
R1#sh ipv6 int br
Serial2/0 [up/up]
FE80::C804:12FF:FEDC:8
2001:DB8:0:CC00::1
Loopback99 [up/up]
FE80::C804:12FF:FEDC:8
2001:DB8:1111::1
R2#sh ipv int b
Serial2/0 [up/up]
FE80::C805:12FF:FEDC:8
2001:DB8:0:CC00::2
Loopback99 [up/up]
FE80::C805:12FF:FEDC:8
2001:DB8:1111::2
R1#
sh bgp ipv6 unicast sum
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
2001:DB8:0:CC00::2
4 65100 6 6 2 0 0 00:02:17 1
R2#
sh bgp ipv6 unicast sum
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
2001:DB8:0:CC00::1
4 65100 6 6 2 0 0 00:02:41 1
R1#
sh bgp ipv6 unicast neighbors 2001:DB8:0:CC00::2 advertised-routes
BGP table version is 2, local router ID is 1.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i – internal,
r RIB-failure, S Stale
Origin codes: i – IGP, e – EGP, ? – incomplete
Network Next Hop Metric LocPrf Weight Path
*> 2001:DB8:1111::1/48
:: 0 32768 i
R2#
sh bgp ipv6 uni nei 2001:DB8:0:CC00::1 adver
BGP table version is 2, local router ID is 2.2.2.2
Status codes: s suppressed, d damped, h history, * valid, > best, i – internal,
r RIB-failure, S Stale
Origin codes: i – IGP, e – EGP, ? – incomplete
Network Next Hop Metric LocPrf Weight Path
*> 2001:DB8:1111::2/48
:: 0 32768 i
R1#
sh bgp ipv6 unicast neighbors 2001:DB8:0:CC00::2 routes
BGP table version is 2, local router ID is 1.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i – internal,
r RIB-failure, S Stale
Origin codes: i – IGP, e – EGP, ? – incomplete
Network Next Hop Metric LocPrf Weight Path
* i2001:DB8:1111::1/48
2001:DB8:0:CC00::2
0 100 0 i
R2#
sh bgp ipv6 uni nei 2001:DB8:0:CC00::1 routes
BGP table version is 2, local router ID is 2.2.2.2
Status codes: s suppressed, d damped, h history, * valid, > best, i – internal,
r RIB-failure, S Stale
Origin codes: i – IGP, e – EGP, ? – incomplete
Network Next Hop Metric LocPrf Weight Path
* i2001:DB8:1111::2/48
2001:DB8:0:CC00::1
0 100 0 i
Troubleshooting
R2#deb bgp ipv6 unicast updates
R2#clear bgp ipv6 unicast * soft
R2#
00:22:50: BGP(1): 2001:DB8:0:CC00::1 send UPDATE (format) 2001:DB8:1111::2/48, next 2001:DB8:0:CC00::2, metric 0, path
00:22:50: BGP(1): updgrp 1 – 2001:DB8:0:CC00::1 enqueued 1 updates, average/maximum size (bytes) 75/75
00:22:50: BGP(1): 2001:DB8:0:CC00::1 rcvd UPDATE w/ attr: nexthop 2001:DB8:0:CC00::1, origin i, localpref 100, metric 0
00:22:50: BGP(1): 2001:DB8:0:CC00::1 rcvd 2001:DB8:1111::/48
Everything is as expected.
More info: Cisco IOS IPv6 Configuration Guide, Release 12.4 Implementing Multiprotocol BGP for IPv6
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-mptcl_bgp.html#wp1027258

Posted in BGP, IPV6, Service Provider | Leave a Comment »
Posted by Peter Kurdziel on July 16, 2009
Decimal 150 1 3 3 Binary 1001 0110 0000 0001 0000 0011 0000 0011 in hex, they are 16 digit groupings for hex representations, 1001=9 0110=6 so forth, The results is 9601:0303 http://blog.ru.co.za/2009/03/19/converting-ipv4-to-ipv6/Converting from IPv4 to IPv6
is so easy, yet everyone seem to convert a IPv4 address to binary, then to IPv6. Why? Why waste time and do things the long way? Not cool. When would you need to do this? One specific use is IPv6 6-to-4 tunnels, which always concatenates 2002::/16 with the IPv4 address embedded. With Automatic 6-to-4-tunnels, your address format is as follow: 2002:<32 bit IPv4 site address in Hex>:<16 bit network number in Hex>::/64 The question is how to do the conversion. Firstly before starting I will assume everyone knows the following:
| A | = | 10 |
| B | = | 11 |
| C | = | 12 |
| D | = | 13 |
| E | = | 14 |
| F | = | 15 |
Posted in IPV6, Routing & Switching Lab | Leave a Comment »
Posted by Peter Kurdziel on July 8, 2009
The following prerequisites apply to Cisco Express Forwarding and distributed Cisco Express Forwarding for IPv6: – To forward IPv6 traffic using Cisco Express Forwarding or distributed Cisco Express Forwarding, you must configure forwarding of IPv6 unicast datagrams globally on the router by using the ipv6 unicast-routing command, and you must configure an IPv6 address on an interface by using the ipv6 address command.
– You must enable Cisco Express Forwarding for IPv4 globally on the router by using the ip cef command before enabling Cisco Express Forwarding for IPv6 globally on the router by using the ipv6 cef command.
– To use Unicast Reverse Path Forwarding (RPF), enable Cisco Express Forwarding switching or distributed Cisco Express Forwarding switching in the router. There is no need to configure the input interface for Cisco Express Forwarding switching. As long as Cisco Express Forwarding is running on the router, individual interfaces can be configured with other switching modes.
Note For Unicast RPF to work, Cisco Express Forwarding must be configured globally in the router. Unicast RPF will not work without Cisco Express Forwarding.
Posted in IPV6, Routing & Switching Lab | Leave a Comment »
Posted by Peter Kurdziel on June 26, 2009
http://www.potaroo.net/ispcol/2008-08/ipv6addr.html
| ::1/128 | local host |
| ::FFFF:w.x.y.z | IPv4 mapped address – lookup IPv4 address w.x.y.z |
| FD00::/8 | Unique Local Addresses.
|
| FE80::/10 | Link Local Addresses
|
| 2001:0::/32 | Teredo address
Bits 33 – 64 of the address contain the Teredo server address Bits 65 – 80 contain flags: The field format is: CRAA AAUG AAAA AAAA Bits 81 – 96 contain the external IPv4 port address, XORed with 1′s Bits 97 – 128 contain the external IPv4 address XORed with 1′s For example, the Teredo IPv6 address : can be mapped as follows: |
| 2002::/16 | 6to4 address
Bits 17 – 48 contain the IPv4 address of the 6to4 gateway For example, the 6to4 address has the IPv4 gateway address of |
Posted in IPV6, Routing & Switching Lab | Leave a Comment »
Posted by Peter Kurdziel on April 13, 2009
The following is a summary of the steps a device takes when using stateless autoconfiguration:
1. Link-Local Address Generation: The device generates a link-local address. Recall that this is one of the two types of local-use IPv6 addresses. Link-local addresses have “1111 1110 10” for the first ten bits. The generated address uses those ten bits followed by 54 zeroes and then the 64 bit interface identifier. Typically this will be derived from the data link layer (MAC) address as explained in the topic on interface identifiers, or it may be a “token” generated in some other manner.
2. Link-Local Address Uniqueness Test: The node tests to ensure that the address it generated isn’t for some reason already in use on the local network. (This is very unlikely to be an issue if the link-local address came from a MAC address but more likely if it was based on a generated token.) It sends a Neighbor Solicitation message using the Neighbor Discovery (ND) protocol. It then listens for a Neighbor Advertisement in response that indicates that another device is already using its link-local address; if so, either a new address must be generated, or autoconfiguration fails and another method must be employed.
3. Link-Local Address Assignment: Assuming the uniqueness test passes, the device assigns the link-local address to its IP interface. This address can be used for communication on the local network, but not on the wider Internet (since link-local addresses are not routed).
4. Router Contact: The node next attempts to contact a local router for more information on continuing the configuration. This is done either by listening for Router Advertisement messages sent periodically by routers, or by sending a specific Router Solicitation to ask a router for information on what to do next. This process is described in the section on the IPv6 Neighbor Discovery protocol.
5. Router Direction: The router provides direction to the node on how to proceed with the autoconfiguration. It may tell the node that on this network “stateful” autoconfiguration is in use, and tell it the address of a DHCP server to use. Alternately, it will tell the host how to determine its global Internet address.
6. Global Address Configuration: Assuming that stateless autoconfiguration is in use on the network, the host will configure itself with its globally-unique Internet address. This address is generally formed from a network prefix provided to the host by the router, combined with the device’s identifier as generated in the first step.
Posted in IPV6, Real World | Leave a Comment »