OLSR Workshop OLSR for IPv6 Ryuji Wakikawa Keio University/WIDE project
Antti J. Tuominen Helsinki University of Technology
Why OLSR6
RFC 3626 Experimental RFC
Ad-hoc network requires many addresses
Focus on IPv4 Personal Area Network Vehicles
Supporting IPv6 is urgent
Routing messages are changed to IPv6 address length NDP interaction Address Assignments Global Connectivity
Messages Changes
Address fields are changed to store IPv6 address space (already stated in RFC3626)
Packet format TC message HID message
Network address fields are changed to store IPv6 prefix address and its length
HNA message
Address Assignments
IPv6 has 3 different scope for IPv6 addresses
IPv6 allows to assign multiple addresses on an interface
global scope optional, only nodes who needs global connectivity link-local scope mandate, to all IPv6 nodes site-local scope (deprecated)
ex. link local address x 1, global address x 2
Which IPv6 address is used for
limited Broadcast address main address
Limited Broadcast Address
Limited broadcast address on IPv6 is
all-node multicast address (ff02::1) All IPv6 nodes joins to ff02::1 the link Link local address can not be used to transmit packets over multi-hop. Routers can not forward packets sent to/from link-local address.
OLSR simply uses ff02::1 as the limited broadcast address
source address: olsr node’s link local address destination address: ff02::1
Main address
main address is used to create routes for a node 4 options
link-local scope address as a main address global scope address as a main address Any scope address as a main address (ignore scope) manet address
Link-local as main address
all nodes have link-local scope address Even when a node-A gets a route (more than one hop away) for a node-B. it can not route packets with the route
packets meant for a Link Local scope address can not be routed on intermediate nodes Node D may route NS for NodeA using the route
NDP relies on link-local scope NDP is stateful complicated protocol
Receiving NA A
B
C
D sending NS
Global as main address
All nodes do not have a global address Two different global addresses
Home Address which is not topologically correct address Global address which is assigned by AR and is topologically correct address
OLSR node needs to get a global address to exchange routing messages
Need route to get a global address from a Gateway
Any scope as main address
same issues when link-local scope is used as a main address
Manet address as main address
New address block for manet
new manet scope new manet address block from global scope (ex. 2001:x:/16)
Concept of manet address
all nodes have a manet address generated by similar approach of LL address The manet address is only valid within manet
Each node exchanges routing messages using the manet address and creates routes for manet nodes using the manet address.
This address’s packet MUST NOT be leaked to the Internet
The manet address can be used communication within manet, but it is better to use global scope address if available
All manet node multicast address may be defined if necessary
OLSR6 Address Assignment
Link local address is an interface address of each OLSR node and is used to exchange OLSR messages (src/dst address of IP header) Manet address is a main address of each OLSR node global address is transmitted by MID messages and is used as communication
Scope
Validity
Protocol
Communicati on
Link Local
on-link
NDP
on-link
Manet address
within MANET
OLSR6
on-link, within manet
Global
Internet
(Global6)
Any
Global Connectivity
The Use of HNA message or New Defined message to exchange gateway information
Address generation is similar to Address Autoconfiguration (RFC2462)
stateless address assignment
Route Setup towards IGW
Current implementations behavior when receiving Router Advertisements
BSD has default router list. Pick one for default route Linux set all access routers as default routes
How to configure routes toward IGW is up to manet nodes
if a manet node often communicates with a lot of nodes located on the Internet, better to utilize the default route Otherwise, it can configure either host or network routes towards IGW
Conclusion
many possible issues when manet supporting IPv6
Adapting message with IPv6 Address length is not sufficient
each OLSR control packet with a digital signature for authenticating this ... especially considered for time synchronization problems, .... communication at all.
connections from the local host (127.0.0.1). V. CONCLUSION ... [8] A. Tønnesen, A Hafslund, P. Engelstad âIP Address Autoconfiguration for. Proactive Mobile ...
I don't know d2, send packet to my cluster head ... 0. 500. 1000. 1500. 2000. 2500. 0s. 150s. 300s. 600s. 900s. Pausing Time p a c k e ts. /s. HOLSR. Flat OLSR ...
Various reporting features. ... (link layer notification, medium power, high mobility). 0%. 20%. 40% ... development of ad hoc networks, and OLSR in particular.
ad-hoc network based on IPv6 and to deliver right specification to industry. ... a node has Internet connectivity (i.e. link-local address and global address).
Gateway Tunnelling (IP-in-IP encapsulation) of data packets. .... (127.0.0.1), not any socket. ... IP address of A, a nonce, the timestamp, the response signature.
Has non-standard command line options for research purposes. ⢠Nrlolsr is not fully rfc3626 ... Early development of nrlolsr helped test out early specifications.
address autoconfiguration, etc. Therefore, a modular ... ducing efficient binary code for a large variety of architectures. .... are common to any family (create, destroy, resolve, convert ... addresses, the choice between IPv4 and IPv6 is static (i.
Use Information (MPR, Routing Table) of OLSR. â Making Multicast ... Root: source. â Leaves ... â¢N : nodes distributed uniformly on square of size L x L unit ...
NEMO(Network Mobility)[3] is the network mobility sup- ... NEMO is the technol- ogy which realize such .... Users install the routing policy via the policy manage-.
dias such as wireless interfaces are useful in the situation vehicles are in tunnels lose its connectivity for the internet. This paper shows the problem statements ...
timer and limited maximum number of queries to control message load. ⢠Backward compatibility with OLSR nodes that do not support the SLE extension. Server.
Computer Science Department, Univ of Califinia, Los Angeles, CA 90095 ... deployed for disaster recovery, modern battlefields, homeland security, etc.,.
And on the other hand, when an organization grows in size, hierarchy and clustering have ... periodic exchange of control messages in order to accomplish topology discovery and ... from which a routing table can constructed. Basically, OLSR ...
routing table is built and maintained based on the information of neighbor table. ... proactive link state routing protocol, employing periodic message exchange to ...
interfaces, protocols governing the connectivity and op- eration of such MANETs ... perform bidirectionally checks of links, and are thus ex- changed between ...
Abstractâ. Commonly, duplicate address detection is performed when configuring network interfaces in order to ensure that unique addresses are assigned to ...
protocol, OLSR employs the periodic exchange of control messages in order to accomplish ... routing table can constructed. Basically, OLSR employs two types ...
routing protocols could scale in this environment. However, none ... its direct neighbors as about any node in the network, however remote it ... of finite size: N nodes uniformly distributed on a finite portion of plane. .... The surface covered by
VoIP. â Web browsing ... Strongly optimized for ad hoc networks. â« Via the use of .... with different constraints, i.e. need for more link advertisements. â« Without ...
OLSR is a proactive link-state protocol that uses an op- timization called Multi-Point ..... is clearly seen at high density where the average TC size ex- plodes with ...
... Communications and Security. Contents. 19.1 Introduction and Motivations ........................................................................................ 568. 19.2 State of the Art ..
