Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 [Lab] 6to4 Tunnels. 2 Pre-requisite Reading RFC 3056 – Connection of IPv6 Domains via IPv4 Clouds Y. Hei and K. Yamazaki, " Traffic analysis and worldwide.

Similar presentations


Presentation on theme: "1 [Lab] 6to4 Tunnels. 2 Pre-requisite Reading RFC 3056 – Connection of IPv6 Domains via IPv4 Clouds Y. Hei and K. Yamazaki, " Traffic analysis and worldwide."— Presentation transcript:

1 1 [Lab] 6to4 Tunnels

2 2 Pre-requisite Reading RFC 3056 – Connection of IPv6 Domains via IPv4 Clouds Y. Hei and K. Yamazaki, " Traffic analysis and worldwide operation of open 6to4 relays for IPv6 deployment", Proceedings of 2004 International Symposium on Applications and the Internet (SAINT 2004), pp.265-268. Traffic analysis and worldwide operation of open 6to4 relays for IPv6 deployment –Authors from KDDI, Japan.

3 3 Network Environment If you get a native IPv6 address, you don’t need a 6to4 tunnel. If you get a private IPv4 address, 6to4 tunnel cannot be created. –Configure your IPv4 address to 163.22.30.xx. –Now you see the 6to4 interface.

4 4 6to4 Tunnel Interface 163.22.30.8 192.88.99.1 (RFC 3068)

5 Try to ping each other Capture the ICMPv6 packets, and mail to me. What is your capture filter? –ip6? –ip?

6 6 Routing to 2002:: is easy IPv4 IPv6 Network 6to4 Router2 6to4 Router1 131.243.129.44140.110.199.250 Network prefix: 2002:83F3:812C::/48 Network prefix: 2002:8C6E:C7FA::/48 E0 2002:83F3:812C:1::3 2002:8C6E:C7FA:2::5 IPv6 SRC 2002:83F3:812C:1::3 Data IPv6 DEST 2002:8C6E:C7FA:2::5 IPv6 SRC 2002:83F3:812C:1::3 Data IPv6 DEST 2002:8C6E:C7FA:2::5 IPv6 SRC 2002:83F3:812C:1::3 Data IPv6 DEST 2002:8C6E:C7FA:2::5 IPv4 SRC 131.243.129.44 IPv4 DEST 140.110.199.250

7 How about 2001:: ? IPv4 IPv6 Network 6to4 Relay Router 6to4 Router1 192.88.99.1 2002:83F3:812C:1::3 2001:48a8:68fe::151 192.88.99.1 6to4 Relay Router IPv4 2002::/16

8 8 ping6 www.ncnu.edu.tw

9 9 Capture Filter of Wireshark ip host 192.88.99.1 host 192.88.99.1 or host 192.88.115.135 ip[9]==41

10 10 traceroute6 Tracing route to www.ncnu.edu.tw [2001:e10:6840:67:4c33:e188:4d59:364f] from 2002:a316:1e08::a316:1e08 over a maximum of 30 hops: – 1 15 ms 14 ms 19 ms 2002:a319:f6fb::1 – 2 18 ms 24 ms 23 ms 2001:288:0:1659:192:83:196:111 – 3 22 ms 18 ms 23 ms 2001:288:0:f:111::1 – 4 231 ms 301 ms 283 ms 2001:e10:ffff:101::1 – 5 236 ms 230 ms 231 ms 2001:e10:ffff:1a00::1 – 6 228 ms 234 ms 228 ms 2001:e10:ffff:1a01::2 – 7 291 ms 319 ms 229 ms www.ncnu.edu.tw [2001:e10:6840:67:4c33:e188:4d59:364f] traceroute6 to 2002:a316:1e08::a316:1e08 (2002:a316:1e08::a316:1e08) from 2001:e10:6840:20:204:76ff:fee2:b1bd, 64 hops max, 12 byte packets – 1 2001:e10:6840:20::1 0.867 ms 0.743 ms 1.191 ms – 2 2001:e10:6840:1::1 0.707 ms 0.699 ms 0.636 ms – 3 2001:e10:ffff:1a01::1 0.699 ms 0.748 ms 0.966 ms – 4 2001:e10:ffff:1100::2 201.968 ms 197.438 ms 208.527 ms – 5 2001:e10:ffff:300::1 240.724 ms 196.756 ms 287.042 ms – 6 2001:e10:ffff:304::2 182.370 ms 182.350 ms 182.361 ms – 7 xe-0-1-3.0.rtr.wash.net.internet2.edu 341.875 ms 425.605 ms 343.927 ms – 8 internet2-virt-internet2-xe-0-0-0-506.3rox.net 213.375 ms 213.238 ms 213.274 ms – 9 bar-internet2-ge-1-2-0-585.3rox.net 213.523 ms 214.209 ms 213.940 ms –10 6to4-bar-f4-0.3rox.net 213.620 ms 213.494 ms 218.251 ms –11 2002:a316:1e08::a316:1e08 236.394 ms 229.709 ms 230.471 ms

11 11 traceroute tracert 192.88.99.1 –1 9 ms 5 ms 10 ms 10.102.1.254 –2 7 ms 5 ms 5 ms ip098.puli255-64-203.ncnu.edu.tw [203.64.255.98] –3 5 ms 10 ms 4 ms ip091.puli255-64-203.ncnu.edu.tw [203.64.255.91] –4 14 ms 16 ms 16 ms 192.88.99.1 tracert 192.88.115.135 (6to4-bar-f4-0.3rox.net) – 1 4 ms 7 ms 4 ms 10.102.1.254 – 2 5 ms 6 ms 4 ms ip098.puli255-64-203.ncnu.edu.tw [203.64.255.98] – 3 5 ms 4 ms 4 ms ip091.puli255-64-203.ncnu.edu.tw [203.64.255.91] – 4 10 ms 9 ms 11 ms bb-MOE-TWAREN.TANet.edu.tw [192.83.196.111] – 5 10 ms 15 ms 10 ms 202.169.174.58 – 6 11 ms 10 ms 10 ms 202.169.174.110 – 7 44 ms 44 ms 41 ms 202.169.174.149 – 8 42 ms 41 ms 52 ms tpr5-taiwan.jp.apan.net [203.181.248.154] – 9 155 ms 158 ms 170 ms losa-tokyo-tp2.transpac2.net [192.203.116.145] – 10 193 ms 155 ms 155 ms abilene-1-lo-jmb-702.lsanca.pacificwave.net [207.231.240.131] – 11 187 ms 296 ms 188 ms xe-0-1-0.0.rtr.hous.net.internet2.edu [64.57.28.97] – 12 320 ms 210 ms 208 ms xe-1-0-1.0.rtr.atla.net.internet2.edu [64.57.28.113] – 13 325 ms 308 ms 306 ms xe-1-1-3.0.rtr.wash.net.internet2.edu [64.57.28.7] – 14 232 ms 301 ms 229 ms internet2-virt-internet2-xe-0-0-0-506.3rox.net [192.88.115.24] – 15 252 ms 231 ms 276 ms bar-internet2-ge-1-2-0-585.3rox.net [192.88.115.54] – 16 230 ms 235 ms 306 ms 6to4-bar-f4-0.3rox.net [192.88.115.135]

12 ping www.ipv6.tw Does your Windows 7/XP prefer to send packets via IPv4 or IPv6? ping iptv.bupt.edu.cn 12

13 13 Further Reading Advisory Guidelines for 6to4 Deployment draft-ietf-v6ops-6to4-advisory-01 draft-ietf-v6ops-6to4-advisory-01 Request to move Connection of IPv6 Domains via IPv4 Clouds (6to4) to Historic status draft-ietf-v6ops-6to4-to-historic-03 draft-ietf-v6ops-6to4-to-historic-03


Download ppt "1 [Lab] 6to4 Tunnels. 2 Pre-requisite Reading RFC 3056 – Connection of IPv6 Domains via IPv4 Clouds Y. Hei and K. Yamazaki, " Traffic analysis and worldwide."

Similar presentations


Ads by Google