50 likes | 175 Views
IPv6 R&D at the WSLH. James Leinweber Hygiene Lab / UW-MIST. It’s 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 ISP’s have it on their backbone Your existing hosts mostly support it
E N D
IPv6 R&D at the WSLH James Leinweber Hygiene Lab / UW-MIST
It’s 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 ISP’s 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
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, RFC’s are still mutating • deprecated almost as fast as you can read them, e.g. site-local gone, DNAME unimplemented, …
WSLH addressing and routing • subnets: I have 16 bits to play with • host part – colon quad from static IPv4 • ::144:92:248:138 • route entire buildings as a single /52
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 v4+v6 split • global unicast only (no ULA, site-local gone) • UW campus isn’t routing ULA anyway • bigger IPv6 headers costs 4% of throughput