Activity Summary -...
22
Transcript of Activity Summary -...
Global View
• MANEMO for future Mobile Ad-Hoc Network • Thing, Human, Space will be connected to the Internet
in Future• Unlimited infrastructure extensibility
• Electric: Extend usable area by Multi-tap• Water Supply: Bucket Brigade• IP (Internet)：by Multi-hop, Ad-Hoc node?
2
A B C
IP
IP
IP
IP
IPIP
IP
IP
What’s MANEMO?
• MANET for NEMO• Bar-BOF @IETF 68th (May, 2007)
• Established by Ryuji Wakikawa (Keio), Pascal Thubert (Cisco FR), others.
• Problem Statement• Nested NEMO problem• MANET global reachability difficulty
• draft-wakikawa-manemo-problem-statement - MANEMO Problem Statement
• http://mobilegravity.sfc.wide.ad.jp/MANEMO/
• (Failed to agree the Problem Statement)
3
Fig!
Problem Statement of MANEMO
4
Internet
HA2
MNN
MR1
MR2
HA3
CN
MR3
MR4
HA1
HA4
RedundantPath
MR1-HA1Tunnel
MR2-HA2Tunnel
MR3-HA3Tunnel
MultipleEncapsulation
MR4-HA4Tunnel
Nested NEMOProblem
Internet
MN
MNMN
MN
MN
MN
MN
MNMN
MNMN
MANET 1 MANET 2
MANET Global Reachability Problem
Outline
• DUMBO II Project
• Disaster Recovery Network deployment
• NEMO Route Optimization
• Network Mobility (NEMO) for more complicated scenario
• Simulator (ns-3)
• Reliable Network Simulation using Actual Running Code
5
DUMBO 2 project
• Digital Ubiquitous Mobile Broadband OLSR(DUMBO), since 2006, Thailand• Held at Asian Institute of Technology (AIT), 2008
• Disaster response network deployment• Network (OLSR, MANEMO)• Commander Application (for rescue operation)• Disaster area to Infrastructure communication
• http://dumbo2.interlab.ait.ac.th/
6
Scenario of Disaster Recovery Operation
• Most communication is directed to Headquarters
• NEMO serves Group Movement with vehicular
• Mobile Router (MR) installed inside vehicular, as a MANET node
• MANEMO (MANET for NEMO) can be a solution
HomeAgent
MR
MR
MRMR
MR
MR
MR
MRMR
MR
Headquarters
Disaster Area 1 Disaster Area 2
MNN
MNN MNN
MNN
GatewayGateway
MRMR
MR
Help!
7
Overview of TDP/NINA
• Extension of Neighbor Discovery Protocol (IPv6)
• Tree Discovery (TDP *1)
• Tree formation in MRs
• NINA (*2)
• Advertise Mobile Network Prefix (MNP)
• Advertise to parent node in the tree
*1 draft-thubert-tree-discovery-06*2 draft-thubert-nina-02
MR
MR
MR
MR
MR
MR
MR
ARWireless Network
MNN MNN
MNNMNN
TDP
NINA
8
Implementation of TDP and NEMO
• Developed under NetBSD-current(4.99.x)• TDP and NINA is developed as extension of zebra• Implementation is available at http://www.sfc.wide.ad.jp/~tazaki/zebra-mndpd
Kernel-space
User-space
TDP/NINA(Routing Protocol)
Tunnel Optimization Control
NEMO(SHISA)
Mobility Socket
BindingCache
RoutingTable
Eth
IP
tunnel
Eth
IP
tunnel
Lookup
Routing Socket
DevelopmentTarget
9
• Thailand, November 2008
• 5 Mobile Routers, 3 Mobile Network Nodes
• External connectivity is provided by Home Agent (HA)
In-Field ExperimentBatteryDC 12V
DC-DCConverter
MicroClient(MR)
LinksysWSUB54G(Ingress)
Atheros(mini-PCI)+ 2dBi Gain
AntennaBuilding
Field(70m x 60m)
MNN3
MNN2MNN1
802.11AP
HAIPv6Router
MR2
MR3
MR1
MR5
MR4
Building
Field(70m x 60m)
MNN3
MNN2MNN1
802.11AP
HAIPv6Router
MR2
MR3
MR1
MR5
MR4
10
0
500
1000
1500
2000
2500
3000
3500
0 10 20 30 40 50 60 70 80
Cont
rol O
verh
ead
(byt
es/s
ec)
Time (sec)
mean: 539.43
Handover
(theoretical) before handover: 669(theoretical) after handover: 614(theoretical) during handover: 1109
200m
NestedMR
11
Demonstration @ ITST2008
12
NEMO Route Optimization for MANEMO
(IPSJ Journal Under review, May 2010)
Network Mobility(NEMO)
InternetCN: Correspondent NodeMR: Mobile RouterHA: Home AgentMNN: Mobile Network Node
CN
HA
Home Link
Foreign Link
Moving...
MNNMNNMNNMNN
MR
Mobile Network
MR-HA tunnel
MNN-CNcommunication
Address(Home Address)2001:d30:1a:ff00::1
Address(Home Address)2001:d30:1a:ff00::1
CN can communicatewith SAME address
during MR's movement
14
Nested NEMO Problem
15
Internet
HA2
MNN
MR1
MR2
HA3
CN
MR3
MR4
HA1
HA4
RedundantPath
MR1-HA1Tunnel
MR2-HA2Tunnel
MR3-HA3Tunnel
MultipleEncapsulation
MR4-HA4Tunnel
CoA of MR2,3,4 is dependent on upper MR
(Thus, Hair-pin path)
NAT-MANEMO
NAT eliminates redundant pathMNN originated packet doesn’t affect NAT
(application transparent)16
Internet
MNN
HA1
CN
MR2i
ea
MR1i
e
a
e: Egress Interface (managed mode)i: Ingress Interface (hostap mode)a: Other Interface (ad-hoc mode)
HA2
MR2-HA2 tunnelvia HA1
AR
Internet
MNN
HA1
CN
MR2i
ea
MR1i
e
a
e: Egress Interface (managed mode)i: Ingress Interface (hostap mode)a: Other Interface (ad-hoc mode)
HA2
MR2-HA2 tunnel
AR
NAT
NAT-MANEMO (cont.d)
17
MNN MR2 MR1 AR HA1 HA2 CN1. pCoA advertisement
2. Role of root-MR advertisement
3. oCoA advertisement
Rou
ting
Prot
ocol
Ope
ratio
n
Update NAT table
Alt-CoA option
with pCoA4. Binding update
5. Source address translation
6. Binding ack7. Destination address translation
Store Binding
Information
8. Address Translation
Optimized Path
mobile networkmulti-hop mobile ad-hoc network wireless uplink Internet
TunnelEndpoint
TunnelEndpoint
Benefit
18
• NAT only involves minimum modification• No modification needs for Home Agent
• DHCP Prefix Delegation is not required• Minimum Access Network dependency• MR can use any address (e.g. ULA, private address) as Care-of-
Address
• Limited use of NAT• Will not perform deep packet inspection• Application keeps its transparency
ns-3 (open-source project)
19
Virtualization in Simulator
• Avoiding Re-invention of the code
• Each zebra (application) instance on the virtual node
• Can be use real world program AS-IS!
• Minimum overhead of virtualization
• No need to virtualize hardware
• Required resources is only virtualized Physical Machine
Operating System
Simulator
Emulationmalloc(), sendmsg()
Application(e.g. zebra w/ PIE file)
malloc(), sendmsg()(usual) libc
n1 n2 n10
Load elf file by hand
override withweak_alias ()
Instance per (simulated) node
[1] ns-3 POSIX/socket emulation branch by Mathieu Lacage:http://code.nsnam.org/mathieu/ns-3-simu/
20
Demonstration @ WNS3
• 10 nodes (OLSR, RWP)
• 2 nodes (bgp)
• 10 nodes (TD, RWP)
• All the routing protocol application with zebra
• Ping for connectivity
• Reset BGP session
PowerBook G4
AdHoc
AdHoc
OLSR
BGP
TD
Emu
Tap
P2P
MacBook
Ubuntu on VMWare
:27
:10
:15:16
:17
:18
:ffc3:ffc0
:ffc5
:ffc1
:ffc2
:ffc6
:ffc4
21
WNS3 (Workshop on ns-3), March 2010, http://wns3.org/techprog.html
References• DUMBO 2
• http://dumbo2.interlab.ait.ac.th/
• My Publications• http://www.sfc.wide.ad.jp/~tazaki/l/Publications.html
• Software• ns-3 zebra support
• http://www.sfc.wide.ad.jp/~tazaki/ns3
• zebra-mndpd• http://www.sfc.wide.ad.jp/~tazaki/zebra-mndpd/
• ns-3-simu (by Mathieu Lacage, INRIA)• http://code.nsnam.org/mathieu/ns-3-simu/
• Paper• Selecting an Appropriate Routing Protocol for In-Field MANEMO
Experiments• http://doi.acm.org/10.1145/1641876.1641895
• Contact• Hajime Tazaki (tazaki at sfc.wide.ad.jp)
22
