IPv6 R

1
IPv6 RD at the WSLH

• James Leinweber
• Hygiene Lab / UW-MIST

2
Its easier than you think

• UW-Madison departments can just ask for an IPv6
  prefix and get a /48
• probably any WISCNET client can
• All Tier-1 ISPs have it on their backbone
• Your existing hosts mostly support it
• hardware support in recent switches, routers,
  firewalls
• OS support in windows, Mac OS-X, Linux,
• routing gets much easier
• one of the design goals

3
Conceptual Hurdles

• mixing IPv4 and IPv6 is like mixing IPv4 and
  Netware IPX
• they run in parallel, not together
• some differences from IPv4
• multicast required
• broadcast and ARP gone
• all subnets are /64 at the LAN (even point to
  point)
• after 15 years, RFCs are still mutating
• deprecated almost as fast as you can read them,
  e.g. site-local gone, DNAME unimplemented,

4
WSLH addressing and routing

• subnets I have 16 bits to play with
• host part colon quad from static IPv4
• 14492248138
• route entire buildings as a single /52

5
practical hurdles network infrastructure

• Cisco firewall
• need parallel IPv4 and IPv6 access lists
• ASA does v4, v6, ethertype, policy map in
  parallel per interface
• no ASDM GUI support for v6 yet
• no IPSEC support for v6 yet ????
• Cisco routers have it, though
• Cisco Switches
• reallocate TCAM for v4v6 split
• global unicast only (no ULA, site-local gone)
• UW campus isnt routing ULA anyway
• bigger IPv6 headers costs 4 of throughput