ipv6 -- no longer optional · 2019. 2. 25. · basics: ipv4 vs. ipv6 thinking 18 thought ipv4 dogma...

4 September, 2011 Hurricane Electric

IPv6 -- No longer optional

Owen [email protected]

Thursday, September 15, 2011

mailto:[email protected]:[email protected]

4 Sep. 2011 Hurricane Electric Page

Why is this important? - Today

2

Today



RIR Free Pool ProjectionsGeoff Huston’s math:

3


RIRNon-Austerity

Free Pool(9/4/2011)

Austerity Date?

ARIN 7.75 /8s 3/2012?

AfriNIC 4.74 /8s 4/2012?

RIPE 2.26 /8s 11/2011?

LACNIC 2.81 /8s 4/2012?

APNIC 0.00 /8s OUT 4/15/11


RIR Free Pool UpdateMy speculation:

4



IPv4 Runout Process IANA runs out first, ~2011 February 3, 2011 RIRs start running out probably in 2012 around

June, 2011 APNIC ran out April 15, 2011 End-User providers start running out shortly

after RIR runout. Most likely, the larger ones first (APNIC happening now)

After ISPs start running out, an increasing number of your customers/users will have are experiencing limited or seriously degraded ability to connect via IPv4, possibly even no ability.

5



IPv6 Transition -- How ready are we? Things that are

readyBackbonesCMTS Systems (DOCSIS 3)MacOS (10.4+)Linux (2.6 Kernels)Windows (7, 2008, XP (limited))

WiMax (specification, head end equipment)LTE (some)CPE (very limited)Early Adopters and some industry expertsHurricane ElectricMe

6



IPv6 Transition -- How ready are we? Things that are

NOT readyPON SystemsDSL SystemsCMTS Systems (DOCSIS 2)WDS/EVDO/HSPAWIMAX (handsets, providers)

Older Windows (XP and earlier)Embedded systemsPrintersHome entertainment devicesCPE (most)Most IT staff and management

7



Quick survey

8



Quick survey

How many of you have started planning IPv6 in your organization?

8



Quick survey

How many of you have started planning IPv6 in your organization?How many of you have IPv6 running in a test environment?

8



Quick survey

How many of you have started planning IPv6 in your organization?How many of you have IPv6 running in a test environment?How many of you have started deploying IPv6 to your organization?

8



Quick survey

How many of you have started planning IPv6 in your organization?How many of you have IPv6 running in a test environment?How many of you have started deploying IPv6 to your organization?How many of you have a fully production dual-stack environment running in your organization?

8



This is a room full of IPv6 proponents. Results from other rooms:

Planning? -- average about 5% Test environment? -- average about 2% Deploying? -- Average 1-2 hands Full production? -- Usually just my hand.

We have to do better! If you’re not planning, why? If you’re deploying, keep moving. Full Production? Help the others!

9



LoL Kitteh sez:

10

More IPv4 NATAre you fscking kidding me?



Shared Network, Shared Fate

I hear a lot of people say “I don’t need to do IPv6, I have enough IPv4 addresses for years to come.” Are you really on the internet just to talk to your

own organization? There simply aren’t enough addresses for

everyone that wants/needs to be on the internet in IPv4. If you want to be able to reach new participants, that’s going to require IPv6.

Workarounds all come with bad tradeoffs.

11



The real questions...

How many of you think your organization will be fully IPv6 ready by February, 2012?What do you plan to do to fix that?How do you plan to cope with a world where there are no more IPv4 addresses available?How do you plan to cope with a world where some of your customers have only IPv6 connectivity, or, severely degraded IPv4 connectivity?

12



The final question...

Which Approach will you take?

13

IPv4/IPv6 Dual Stack NowIPv4 is just fine.

We just need MOAR NAT!!My dual stack

network is runninggreat!



What we’ll cover

Basics of IPv6 IPv6 Addressing Methods

SLAAC DHCP Static Privacy

Linux Configuration for Native Dual Stack IPv6 without a native backbone available Free IPv6?

14



Some additional topics

Routing Firewalls DNS Reverse DNS Troubleshooting Staff Training

15



Basics: IPv4 vs. IPv6

16

Property IPv4 Address IPv6 Address

Bits 32 128Total address space

3,758,096,384 unicast268,435,456 multicast268,435,456 Experimental/other (Class E, F, G)

42+ Undecilion assignable1

297+ Undeciliion IANA reserved2

Most prevalent network size

/24 (254 usable hosts) /64 (18,446,744,073,709,551,616 host addresses)

Notation Dotted Decimal Octets(192.0.2.239)

Hexidecimal Quads(2001:db8:1234:9fef::1)

Shortening Suppress leading zeroes per octet

Suppress leading zeroes per quad, longest group of zeroes replaced with ::

142,535,295,865,117,307,932,921,825,928,971,026,432 assignable unicast (1/8th of total)2297,747,071,055,821,155,530,452,781,502,797,185,024 IANA reserved (7/8th of total)





Network Size and Number of networks (The tasty version)

17

One IPv4 /24 -- 254 M&Ms

One IPv6 /64 -- Enough M&Ms to fill all 5of the great lakes.

Full Address Space, One M&M per/64 fills all 5 great lakes.

Full Address Space, One M&M per/24 covers 70% of a football field

he.net

he.net

Comparison based on Almond M&Ms, not plain. Caution! Do not attempt to eat a /64 worth of any style of M&Ms.



Basics: IPv4 vs. IPv6 thinking

18

Thought IPv4 dogma IPv6 dogma

Assignment Unit Address (/32) Network (/64)

Address Optimization

Tradeoff -- Aggregation, Scarcity

Aggregation (At least for this first 1/8th of the address space)

Address Issue Methodology

Sequential, Slow Start, frequent fragmentation

Bisection (minimize fragmentation), issue large, minimal requests for more, aggregate expansions.

NAT Necessary for address conservation

Not supported, Not needed -- Breaks more than it solves (other than possible NAT64)

Address Configuration

Static, DHCP Stateless Autoconf, Static, some DHCP (needs work), DHCP-PD (NEW!!)



Example: v6 only clients with v4 only servers

19

IPv6 only Clients IPv4 Only Server


4 Sep. 2011 Hurricane Electric Page 20

This is the Internet

This is the Internet on IPv4 (2012)

Any quesitons?



Basics Address Scopes

Link Local -- fe80::ff:fe only valid on directly attached subnet.

Site Local (deprecated) -- Only valid within site, use ULA or global as substitute.

Unique Local Addresses (ULA) -- Essentially replaces IPv4 RFC-1918, but, more theoretical uniqueness.

Global -- Pretty much any other address, currently issued from 2000::/3, globally unique and valid in global routing tables.

21



Basics: Stateless Autoconfiguration Easiest configuration No host configuration required Provides only Prefix and Router information,

no services addresses (DNS, NTP, etc.) Assumes that all advertising routers are

created equal, rogue RA can be pretty transparent to user (RA guard required on switches to avoid)

22



RA Guard -- PUSH YOUR VENDORS!! RA has a serious vulnerability

Compare to rogue DHCP Accidental Rogue RA

breaks stuff easy to find easy to mitigate

Malicious Rogue RA Virtually undetectable All your packets are belong to us Coffee Shop nightmare

23



Stateless Autoconfiguration Process Host uses MAC address to produce Link

Local Address. If MAC is EUI-48, convert to EUI-64 per IEEE process: invert 0x02 bit of first octet, insert 0xFFFE between first 24 bits and last 24 bits fe80::

IPv6 shutdown on interface if duplicate detected.

ICMP6 Router Solicitation sent to All Routers Multicast Group

24



Stateless Autoconfigration Process (cont.) Routers send ICMP6 Router Advertisement to link local

unicast in response. Also sent to All Hosts Multicast group at regular intervals.

Router Advertisement includes Prefix(es), Preference, Desired Lifetime, Valid Lifetime.

Host resets applicable Lifetime counters each time valid RA received.

Address no longer used for new connections after Desired lifetime expires.

Address removed from interface at end of Valid lifetime. Prefix(es)+EUI-64 = Host EUI-64 Global Address, netmask

always /64 for SLAAC.

25



If you think IPv6 is hard, wait until you try any of these.

26

Multiple Layer NAT (Carrier Grade NAT)

Dual Stack Lite (ISC)

As yet undefined/unimplemented Magic(TCP relay could be SSH tunnel)



DHCPv6 Can assign prefixes other than /64 -- Ideally

larger (/48) prefixes to routers which then delegate various networks automatically downstream, a few limited implementations of this feature.

Can assign addresses to hosts, cannot provide default router information.

Can provide additional information about servers (DNS, Bootfile, NTP, etc.)

Vendor support still lacking in some areas

27



Static Addressing

IPv6 can be assigned statically, same as IPv4 Common to use one of two techniques for IPv4

overlay networks: Prefix:: (first 12 bits of 64 bit must be 0) Either is IPv4 last octet(s) expressed as BCD,

or is IPv4 last octet(s) converted to hex. e.g. 192.0.2.154/24 -> 2001:db8:cafe:beef::154/64

(BCD) or 2001:db8:cafe:beef::9a/64 (Hex) These mappings won’t conflict with autoconfigured

addresses since autoconfigured addresses will never be 000x:xxxx:xxxx:xxxx.

28



Privacy Addresses Essentially a pathological form of Stateless

Address Autoconfiguration which uses a new suffix for each flow and obfuscates the MAC address.

RFC-3041 Uses MD5 Hash with random component to

generate temporary address Preferred and Valid lifetimes derived from

SLAAC address Unfortunate default in Lion and Vista/later

29



Multiple addresses per interface IPv4 has some support for this in most

implementations. IPv6 has full support for this in all

implementations. IPv4, multiple addresses/interface are

exception. IPv6, single address on an interface nearly

impossible in useful implementation (link local required, global optional)

30



IPSEC

In IPv4, IPSEC is add-on software. In IPv6, IPSEC is a required part of any IPv6

implementation IPv6 does NOT require IPSEC utilization IPSEC is considerably easier to configure in

IPv6. IPSEC automation may be possible in future

IPv6 implementations.

31



Configuring IPv6 Native on Linux Interface Configuration depends on your

distro. Debian based distros (Debian, Ubuntu, etc.)

use /etc/interfaces Red Hat based distros (RHEL, Fedora,

CentOS) use /etc/sysconfig/network-scripts/ifcfg-

32


IPv4 (Static)

IPv6 (Static)

IPv6 (Autoconf)


/etc/interfaces

33

iface eth0 inet staticaddress 192.0.2.127netmask 255.255.255.0gateway 192.0.2.1

iface eth0 inet6 staticaddress 2001:db8:c0:0002::7fnetmask 64gateway 2001:db8:c0:0002::1

iface eth1 inet6 auto



/etc/sysconfig/network-scripts/ifcfg-

34

DEVICE=eth0ONBOOT=yesIPADDR=192.159.10.2NETMASK=255.255.255.0GATEWAY=192.159.10.254

IPV6INIT=yesIPV6ADDR=2620:0:930::0200:1/64IPV6_DEFAULTGW=2620:0:930::dead:beefIPV6_AUTOCONF=noIPV6ADDR_SECONDARIES="\2001:470:1f00:3142::0200:1/64 \2001:470:1f00:3142::0200:2/64”

IPV6INIT=yesIPV6_AUTOCONF=yes

IPv4 (Static)

IPv6 (Static)

IPv6 (Autoconf)



IPv6 without a native connection Three options (In order of preference)

6in4 -- Tunnel your IPv6 in an IPv4 GRE Tunnel 6to4 -- Tunnel your IPv6 in an auto-tunnel using

an any-casted IPv6 mapping service Teredo -- Tunnel your IPv6 in an auto-tunnel using

a multi-server auto-configured process defined by Microsoft.

35



Why 6in4

GRE is well understood by most networkers Simple and deterministic No anycast magic -- Simplifies debugging Controlled by two endpoint adminsitrators --

Greatly simplifies debugging Disadvantage: Manual config, but, not hard.

36



Why 6to4

Automatic configuration When it works, it’s pretty clean and relatively

self-optimizing. May be good option for mobile devices

(laptop, cellphone, etc.) Hard to troubleshoot when it doesn’t work. Disadvantage: Anycast == Non-deterministic

debugging process.

37



Why Teredo?

Autoconfiguration May bypass more firewalls than 6to4 Enabled by default in Windows (whether you

want it or not) Meredo available for Linux (client and server) Disadvantage: Complicated and tricky to

debug if problems occur.

38



Configuring a 6in4 tunnel on Linux Not as straightforward as you would hope. Help available at http://tunnelbroker.net Example (route2, most 2.6+ kernels):

Doesn’t seem to be supported in Debian configuration files at this time.

39

modprobe ipv6ip tunnel add he-ipv6 mode sit remote 64.71.128.82 local 192.159.10.254 ttl 255ip link set he-ipv6 upip addr add 2001:470:1F02:BE2::2/64 dev he-ipv6ip route add ::/0 dev he-ipv6ip -f inet6 addr


http://tunnelbroker.nethttp://tunnelbroker.net


Configuring 6in4 continued

Example Net Tools (most 2.4 kernels, some 2.6)

Also not supported in configuration files

40

ifconfig sit0 upifconfig sit0 inet6 tunnel ::64.71.128.82ifconfig sit1 upifconfig sit1 inet6 add 2001:470:1F02:BE2::2/64route -A inet6 add ::/0 dev sit1



Fedora 12 Configuration Files

Example: /etc/sysconfig/network-scripts/ifcfg-sit1

/etc/sysconfig/network

41

DEVICE=sit1BOOTPROTO=noneONBOOT=yesIPV6INIT=yesIPV6TUNNELIPV4=64.71.128.82IPV6TUNNELIPV4LOCAL=192.159.10.2IPV6ADDR=2001:470:1f02:BE2::2/64

NETWORKING=yesNETWORKING_IPV6=yesHOSTNAME=myhost.example.comIPV6_ROUTER=yesIPV6FORWARDING=yes



Fedora 12 Configuration Files

Example: /etc/sysconfig/static-routes-ipv6

/etc/sysconfig/network-scripts/route6-sit1

42

sit1 ::/0

2001:470:1f00:3142::/64



IPv6 For Free? YES!!

Several tunnel brokers offer free IPv6. My favorite is the HE Tunnelbroker at

www.tunnelbroker.net If you or your organization has a presence at

an exchange point with Hurricane Electric, we currently offer free IPv6 Transit.

43


http://www.tunnelbroker.nethttp://www.tunnelbroker.net


Routing

Usual suspects OSPF (OSPFv3) BGP (BGP4 Address Family inet6) RA and RADVD Support in Quagga and others

44



Firewalls

ip6tables much like iptables Excerpt from my ip6tables configuration

45

-A RH-Firewall-1-INPUT -d 2620:0:930::200:2/128 -m state --state NEW -m tcp -p tcp --dport 3784 -j ACCEPT-A RH-Firewall-1-INPUT -d 2620:0:930::200:1/128 -m state --state NEW -m udp -p udp --dport 53 -j ACCEPT-A RH-Firewall-1-INPUT -d 2001:470:1f00:3142::200:1/128 -m state --state NEW -m udp -p udp --dport 53 -j ACCEPT-A RH-Firewall-1-INPUT -d 2620:0:930::200:2/128 -m state --state NEW -m udp -p udp --dport 53 -j ACCEPT



DNS

Forward DNS Instant IPv6 -- Just add AAAA

Reverse DNS Slightly more complicated ip6.arpa 2620:0:930::200:2 ->

2620:0000:0930:0000:0000:0000:0200:0002 2620:0000:0930:0000:0000:0000:0200:0002 ->

2000:0020:0000:0000:0000:0390:0000:0262 2000:0020:0000:0000:0000:0390:0000:0262 ->

2.0.0.0.0.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.3.9.0.0.0.0.0.0.2.6.2.ip6.arpa

46



DNS -- BIND Configuration

Current BIND versions ship with IPv6 template zones (hints, rfc1912, etc.)

IPv6 addresses valid in ACLs just like IPv4, same rules

Zone configuration identical except reverse zones for IPv6 ranges called “ip6.arpa”:

47

zone "0.3.9.0.0.0.0.0.0.2.6.2.ip6.arpa" IN {! type master;! file "named.2620:0:930::-48.rev";};



DNS -- BIND Configuration

In IPv6 Reverse Zone files, $ORIGIN is your friend!

Forward Zones A for IPv4, AAAA for IPv6, basically what you’re used to:

Reverse Zones PTR records, as described above:

48

mailhost! ! IN! A! 192.159.10.2! ! ! IN! AAAA! 2620:0:930::200:2

$ORIGIN 0.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.3.9.0.0.0.0.0.0.2.6.2.ip6.arpa.1.0.0.0! ! ! IN! PTR! ns.delong.sj.ca.us.2.0.0.0! ! ! IN! PTR! owen.delong.sj.ca.us.4.0.0.0! ! ! IN! PTR! irkutsk.delong.sj.ca.us.



DNS -- Reverse DNS Details

In this example, we see:

$ORIGIN saves us lots of typing for 2620:0:930::200:

Each entry contains the 4 hex digits for the last quad (0001, 0002, 0004)

Note each nibble is a zone boundary

49

$ORIGIN 0.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.3.9.0.0.0.0.0.0.2.6.2.ip6.arpa.1.0.0.0! ! ! IN! PTR! ns.delong.sj.ca.us.2.0.0.0! ! ! IN! PTR! owen.delong.sj.ca.us.4.0.0.0! ! ! IN! PTR! irkutsk.delong.sj.ca.us.



DNS -- Common Reverse DNS mistakes Not enough zeroes -- 2620:0:930::200:2 is

much easier to type, but, remember for reverse DNS you have to expand all those suppressed zeroes before you reverse the address.

Missing dots (.) -- Every nibble gets one. 2.0.0.0.0.0.2.0.0.0.0.0.0.00.0.0.3.9.0.0.0.0.0.0.2.6.2 Do you see the error in the previous line?

Reversing first then expanding 0.0.0.2.0.2.0.0.0.0.0.0.0.0.0.0.0.3.9.0.0.0.0.0.2.6.2.0

50



Troubleshooting

Mostly like troubleshooting IPv4 Mostly the same kinds of things go wrong Just like IPv4, start at L1 and work up the

stack until it all works. If you are using IPv4 and IPv6 together, may

be easier (due to familiarity) to troubleshoot L1-2 on IPv4.

51



Troubleshooting

Common problems Cannot ping remote IPv6 address on Tunnel Cannot ping remote IPv6 address on ethernet Cannot ping MY IPv6 address (tunnel or ethernet) Cannot reach IPv6 Internet

Long waits for IPv6 enabled websites Long delays in host resolution

Why don’t my IPv6 neighbors show up in ARP?

52



A wee bit about Neighbor Discovery and other tools No broadcasts, no ARP This is one of the key differences with IPv6. Instead an all hosts multicast address is used. IPv4: arp 192.0.2.123 IPv6: ip -f inet6 neigh show 2620:0:930::200:2 ping -> ping6 traceroute -> traceroute6 telnet, ssh, wget, etc. just work

53



Cool SSH trick

Special for those that made it through the whole presentation:

If you have a dual stack host you can SSH to in between an IPv4 only and an IPv6 only host that need to talk TCP, then, you can do this from the client:

ssh user@dshost -L :server: Then, from the client, connect to

localhost:lport and the SSH tunnel will actually protocol translate the session.

54



SSH trick example

myhost -- IPv6-only host 2620:0:930::200:f9 dshost -- IPv4/v6 dual stack host: 192.159.10.2

and 2620:0:930::200:2 desthost -- IPv4-only host 192.159.10.100 On myhost I type:

ssh owen@2620:0:930::200:2 -L 8000:192.159.10.100:80 Then, I can browse to http://[::1]:8000

My browser will connect to the ssh tunnel via IPv6, and, the SSH daemon at dshost will pass the contents along via IPv4.

55



Staff Training

Hopefully this presentation works towards that.

You’ll need more. Plan for it. Budget for it. Allocate time for it. If possible, have the staff being trained leave

their pagers/blackberries/iPhones/etc. in the car during training.

56



Q&A

Contact:

Owen DeLong

IPv6 Evangelist

Hurricane Electric

760 Mission Court

Fremont, CA 94539, USA

http://he.net/

owend at he dot net

+1 (408) 890 7992

?

57

http://he.net/http://he.net/

ipv6 -- no longer optional · 2019. 2. 25. · basics: ipv4 vs. ipv6 thinking 18 thought ipv4 dogma...

Documents