IPv6 Greenfield

Click here to download this powerpoint template : Colorful Networks Free Powerpoint Template
For more : Powerpoint Template Presentations
Page 1
Free Powerpoint Templates
IPv6 Greenfield
Md. Zobair Khan
AS 58587
kzobair@gmail.com

Page 2
Topics:
 Goals
 Network Topology
 Test Bed
 Result
 Observation

Page 3
NAT64:
NAT64
Stateful NAT64 is a mechanism for translating IPv6 packets to IPv4
packets and vice versa. The translation is done by translating the packet
headers according to the IP/ICMP Translation Algorithm. The IPv4
addresses of IPv4 hosts are algorithmically translated to and from IPv6
addresses by an IPv6 prefix assigned to the stateful NAT64 for this
specific purpose. The IPv6 addresses of IPv6 hosts are translated to and
from IPv4 addresses by installing mappings in the normal Network
Address Port Translation (NAPT) manner. [RFC6146]

Page 4
DNS64:
DNS64
DNS64 is a mechanism for synthesizing AAAA resource records (RRs)
from A RRs. The IPv6 address contained in the synthetic AAAA RR is
algorithmically generated from the IPv4 address and the IPv6 prefix
assigned to a NAT64 device. [RFC6146]

Page 5
Working Principle:

Page 6
Summary Steps:
Step 1: IPv6 only hosts triggers DNS query (AAAA: example.com)
Step 2: DNS64 server receives AAAA query to resolve example.com
Step 3: DNS64 triggers AAAA query to the internet authoritative server to resolve the
example.com. DNS64 receives an empty AAAA response
Step 4: Upon receiving an empty AAAA response, DNS64 triggers a DNS A record
query for the example.com to authoritative server.

Page 7
Summary Steps:
Step 5: DNS64 receives DNS A record for the example.com (A: example.com –
192.0.2.1)
Step 6: DNS64 synthesizes the IPv6 DNS AAAA record by embedding the IPv4
address in this network’s NAT64 prefix.
Step 7: IPv6 only host connects to the service at example.com by using the IPv6
address received in the AAAA DNS response

Page 8
Summary Steps:
Step 8: NAT64 interface receives the IPv6 packet (default router for IPv6 hosts) and
perform the translation
Step 9: NAT64 sends the IPv4 packet to example.com (in v4 Internet)
Step10: The service hosted at example.com receives, processes the request and the
communication is established

Page 9
Goals

Page 10
Goals:
The exhaustion of IPv4 has motivated us to use IPv6. But still there are
lots of web sites who are running only on IPv4. Moreover, some
applications are also hard-coded for IPv4 only. Our goal was to get a
broad view over the situation and try to finding a work around for these
applications.

Page 11
Network Topology

Page 12
Network Topology:

Page 13
Test Bed

Page 14
Test Bed:
To implement the Network with Cisco router, the IOS must be IOS-XE or
IOS-XR.
To implement the Network with Juniper router, the JUNOS must be 14.1
R1/2.
We have used an Ubuntu 12.4 Server, with some applications.

Page 15
Test Bed - Applications:
The applications we used are –
1. DHCPD6
2. RADVD
3. DNS64
4. TAYGA

Page 16
Test Bed – DHCPD6:
DHCPD6 configurations are as below –
vi /etc/dhcp/dhcpd6.conf
default-lease-time 600;
max-lease-time 7200;
log-facility local7;
subnet6 2403:9300:2:1::/64 {
range6 2403:9300:2:1::100 2403:9300:2:1::500 ;
option dhcp6.name-servers 2403:9300:0:20::3;
option dhcp6.domain-search "domain.example";
}
Also enable ip routing for both IPv4 & IPv6
echo 1 > /proc/sys/net/ipv4/conf/all/forwarding
echo 1 > /proc/sys/net/ipv6/conf/all/forwarding

Page 17
Test Bed - RADVD:
RADVD configurations are as below –
vi /etc/radvd.conf
interface eth1
{
AdvSendAdvert on;
AdvManagedFlag off;
AdvOtherConfigFlag on;
MaxRtrAdvInterval 10;
prefix 2403:9300:2:1::/64
{
AdvOnLink on;
AdvAutonomous on;
};
RDNSS 2403:9300:0:20::3
{
};
};

Page 18
Test Bed – DNS64:
DNS64 configurations are as below –
vi /etc/bind/named.conf.options
options {
directory "/var/cache/bind";
dnssec-validation auto;
auth-nxdomain no;
listen-on-v6 { any; };
allow-query { any; };
dns64 2403:9300:2:2::/64 {
clients { any; };
};
allow-recursion {127.0.0.1; 163.47.156.0/22; 2403:9300::/32; };
};

Page 19
Test Bed – TAYGA:
TAYGA configurations are as below –
vi /etc/taiga.conf
tun-device nat64 //name of the NAT64 tunnel device
ipv4-addr 163.47.159.1 //IP address of the remote tunnel endpoint
prefix 2403:9300:2:2::/64 //IPv6 prefix of translated IPv4 addresses
dynamic-pool 163.47.159.0/24 //pool for mapping IPv6 client <-> IPv4

Page 20
Test Bed – TAYGA:
Now make the nat64 tunnel
tayga --mktun //create tunnel devices
ip link set nat64 up
ip addr add 103.7.251.164 dev nat64 //local endpoint of the tunnel
ip addr add 2403:9300:2:1::1 dev nat64 //same IP as GW
ip route add 163.47.159.0/24 dev nat64 //send through tunnel
ip route add 2403:9300:2:2::/64 dev nat64 //send through tunnel
tayga -d

Page 21
Test Bed – eth0:
ifconfig eth0
eth0 Link encap:Ethernet HWaddr d4:ae:52:6e:af:fd
inet addr:103.7.251.164 Bcast:103.7.251.191 Mask:255.255.255.224
inet6 addr: 2403:9300:0:20::3/64 Scope:Global
inet6 addr: fe80::d6ae:52ff:fe6e:affd/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22090986 errors:0 dropped:3150 overruns:0 frame:0
TX packets:969432 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:24843798090 (24.8 GB) TX bytes:162670268 (162.6 MB)
Interrupt:16 Memory:da000000-da012800

Page 22
Test Bed – eth1:
ifconfig eth1
eth1 Link encap:Ethernet HWaddr d4:ae:52:6e:af:fe
inet6 addr: fe80::d6ae:52ff:fe6e:affe/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX bytes:27228550 (27.2 MB) TX bytes:112002510 (112.0 MB)
Interrupt:17 Memory:dc000000-dc012800

Page 23
Test Bed – nat64:
ifconfig nat64
nat64 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-
00-00-00
inet addr:103.7.251.164 P-t-P:103.7.251.164 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX bytes:9698356 (9.6 MB) TX bytes:9553482 (9.5 MB)

Page 24
Result

Page 25
Result:
Application/Websites Working Not Working
skype x o
viber x o
youtube o x
vimeo o x
dailymotion o x
pptp x o
miniclip o x
ssh o x
telnet o x
winmtr x o
connectify hotspot x o
teamviewer x o

Page 26
Result:
Packet 1 Packet 2 Packet 3 Hostname
7.045 ms 0.189 ms 0.179 ms ge5-19.core1.fmt2.he.net (2001:470:0:45::1)
6.369 ms 0.793 ms 0.807 ms 10ge8-2.core1.pao1.he.net (2001:470:0:30::2)
13.271 ms 13.24 ms 13.228 ms eqix-sv8.bhartiairtel.com (2001:504:d::9498:1)
179.734 ms 181.731 ms 186.668 ms 2404:a800::146
179.8 ms 179.802 ms 179.741 ms 2404:a800:2:1e::5a:122
271.827 ms 272.01 ms 271.783 ms 2403:9300:0:7::e
256.499 ms 255.206 ms 255.35 ms 2403:9300:0:6::e
254.166 ms 254.089 ms 254.046 ms 2403:9300:0:20::3
275.529 ms 269.016 ms 269.95 ms 2403:9300:2:1:4f5:1534:3113:9a0a

Page 27
Result:
C:UserszobAir>tracert www.he.net
Tracing route to he.net [2001:470:0:76::2]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 2403:9300:2:1::1
2 <1 ms <1 ms <1 ms ge-ag1-1-srvsw-0-2-0.pico.net.bd [2403:9300:0:20::1]
3 <1 ms <1 ms <1 ms xe-ig1-1-ag1-0-0-0.pico.net.bd [2403:9300:0:6::1]
4 66 ms 57 ms 57 ms pos-sg1-1-ig1-0-1-0.pico.net.bd [2403:9300:0:4::2]
5 75 ms 75 ms 75 ms 10gigabitethernet1-1.core1.sin1.he.net [2001:de8:4::6939:1]
6 107 ms 114 ms 107 ms 10ge6-1.core1.hkg1.he.net [2001:470:0:29f::1]
7 167 ms 157 ms 167 ms 10ge3-1.core1.tyo1.he.net [2001:470:0:26a::1]
8 252 ms 249 ms 249 ms 10ge15-2.core1.lax2.he.net [2001:470:0:294::1]
9 254 ms 254 ms 254 ms 10ge9-5.core1.sjc2.he.net [2001:470:0:16a::1]
10 254 ms 266 ms 254 ms 10ge1-1.core1.fmt1.he.net [2001:470:0:2f::1]
11 254 ms 254 ms 254 ms he.net [2001:470:0:76::2]
Trace complete.

Page 28
Result:
C:UserszobAir>tracert www.twitter.com
Tracing route to twitter.com [2403:9300:2:2:c7:3b94:5200:0]
1 <1 ms <1 ms <1 ms 2403:9300:2:1::1
2 <1 ms <1 ms <1 ms 2403:9300:2:2:a3:2f9f:100:0
3 <1 ms <1 ms <1 ms 2403:9300:2:2:67:7fb:a400:0
4 <1 ms <1 ms <1 ms 2403:9300:2:2:67:7fb:a100:0
5 <1 ms <1 ms <1 ms xe-ig1-1-ag1-0-0-0.pico.net.bd [2403:9300:2:2:67:7fb:7d00:0]
6 57 ms 57 ms 57 ms pos-sg1-1-ig1-0-1-0.pico.net.bd [2403:9300:2:2:67:7fb:7600:0]
7 75 ms 75 ms 75 ms 13414.sgw.equinix.com [2403:9300:2:2:ca:4fc5:7100:0]
8 260 ms 259 ms 260 ms xe-0-1-1.lax1-cr1.twttr.com [2403:9300:2:2:c7:109f:9800:0]
9 273 ms 273 ms 273 ms xe-1-2-1.sjc2-cr1.twttr.com [2403:9300:2:2:c7:109f:5d00:0]
10 279 ms 279 ms 279 ms ae53.smf1-er1.twttr.com [2403:9300:2:2:c7:109f:2500:0]
11 278 ms 277 ms 277 ms r-199-59-148-82.twttr.com [2403:9300:2:2:c7:3b94:5200:0]
Trace complete.

Page 29
Result:
C:UserszobAir>tracert www.bdix.net
Tracing route to www.bdix.net [2403:9300:2:2:ca:3bd0:1500:0]
1 <1 ms <1 ms <1 ms 2403:9300:2:1::1
2 <1 ms <1 ms <1 ms 2403:9300:2:2:a3:2f9f:100:0
3 <1 ms <1 ms <1 ms 2403:9300:2:2:67:7fb:a400:0
4 <1 ms <1 ms <1 ms 2403:9300:2:2:67:7fb:a100:0
5 1 ms 1 ms 1 ms 2403:9300:2:2:67:7f8:3e00:0
6 1 ms 1 ms 1 ms 210-4-78-218-office.bdcom.com [2403:9300:2:2:d2:44e:da00:0]
7 1 ms 1 ms 1 ms 210-4-78-228-office.bdcom.com [2403:9300:2:2:d2:44e:e400:0]
8 1 ms 1 ms 1 ms pantha.bdcom.com [2403:9300:2:2:d2:448:200:0]
9 2 ms 2 ms 2 ms 210-4-79-66-loopback.bdcom.com [2403:9300:2:2:d2:44f:4200:0]
10 4 ms 4 ms 6 ms www.bdix.net [2403:9300:2:2:ca:3bd0:1500:0]
Trace complete.

Page 30
Observation

Page 31
Observation:
 Major amount of sites ate not available in IPv6 like cnn, twitter etc.
 Major amount of local sites are not available in IPv6.
 Still lots of applications are hard coded IPv4.
 To overcome the issues, some awareness is required, but because of very few
requirement, nobody bothers.
 Still some dependencies are there like 464XLAT needs Android 4.3 + rooted
phone or Windows 8.1 Mobile phone.

Page 32
Mentors
Sumon Ahmed Sabir
Simon Sohel Baroi
Thanks
Anirban Datta
Md. Mesbha Uddin

Page 33
Thank You … 

IPv6 Greenfield

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Viewers also liked

Viewers also liked (20)

Similar to IPv6 Greenfield

Similar to IPv6 Greenfield (20)

More from Bangladesh Network Operators Group

More from Bangladesh Network Operators Group (20)

Recently uploaded

Recently uploaded (17)

IPv6 Greenfield