IPv6 Trace Analysis using Wireshark - Sharkfest - Wireshark
IPv6 Trace Analysis using Wireshark - Sharkfest - Wireshark IPv6 Trace Analysis using Wireshark - Sharkfest - Wireshark
Reply messagefrom server
6to4 Tunnels6to4Tunnel6to4TunnelIPv6IPv6 SiteAIPv6 toIPv4RouterIPv4BackboneRouterIPv4IPv4RouterIPv6 SiteBIPv6 toIPv4IPv6• 6to4 tunnels allow IPv6 packets over an IPv4 network.• RFC 3056: Connection of IPv6 Domains via IPv4 Clouds.• 6to4 is transition mechanism• Operational differences– 6to4 interface automatically created in Windows XP and above– Most Unix implementations support 6to4– Cisco routers support 6to4 tunnels– z/OS Communications Server mainframe cannot be tunnel endpoint
- Page 1 and 2: 1IPv6 Trace Analysis using Wireshar
- Page 3 and 4: What has not changed• Packets tra
- Page 5 and 6: Common IPv6 Extension HeadersNextHe
- Page 8 and 9: Sample Fragment Header
- Page 10 and 11: IPv6 Destination OptionsUse of Dest
- Page 12: RFC5095 (Deprecation of Type 0 Rout
- Page 15 and 16: Crafted Packet• Crafted IPv6 pack
- Page 17 and 18: Trace Packet With Flow Label
- Page 19 and 20: Neighbor Discovery
- Page 21 and 22: Router Advertisement ContentsRouter
- Page 23 and 24: Router Solicitation (RS)- Sent duri
- Page 25 and 26: Neighbor Advertisement (NA)Neighbor
- Page 27 and 28: Neighbor Solicitation (NS)- Neighbo
- Page 29 and 30: NS Packet (Reachability)Neighbor So
- Page 31 and 32: Multicast Listener Discovery• RFC
- Page 33 and 34: Multicast Listener Report
- Page 35 and 36: AAAA RecordAAAA (or quad A) record
- Page 37 and 38: DNS Response - IPv6
- Page 39 and 40: DIG Command Samples• # get the IP
- Page 41 and 42: Query response packetgenerated by :
- Page 43 and 44: DHCPv6 Basic CommandsSolicit,Reques
- Page 45 and 46: DHCPv6 Flow - Continue / End1. Clie
- Page 47 and 48: Solicit messagefrom client
- Page 49 and 50: 2 nd part ofAdvertisemessage fromse
- Page 51: Server IdentiefrRequestmessage from
- Page 55 and 56: Why Teredo?• Teredo does not need
- Page 57: Other IPv6 Sessions• Sunday: 3:00
6to4 Tunnels6to4Tunnel6to4Tunnel<strong>IPv6</strong><strong>IPv6</strong> SiteA<strong>IPv6</strong> toIPv4RouterIPv4BackboneRouterIPv4IPv4Router<strong>IPv6</strong> SiteB<strong>IPv6</strong> toIPv4<strong>IPv6</strong>• 6to4 tunnels allow <strong>IPv6</strong> packets over an IPv4 network.• RFC 3056: Connection of <strong>IPv6</strong> Domains via IPv4 Clouds.• 6to4 is transition mechanism• Operational differences– 6to4 interface automatically created in Windows XP and above– Most Unix implementations support 6to4– Cisco routers support 6to4 tunnels– z/OS Communications Server mainframe cannot be tunnel endpoint
Change language