Академический Документы
Профессиональный Документы
Культура Документы
Abstract - A wireless mesh network (WMN) is a There are a large number of protocols that can be
communications network made up of radio nodes implemented in mesh networking depending on the goals
organized in a mesh topology. Mesh topology is a type of and design criteria. The most common protocols, standards
networking wherein each node in the network may act as and systems in the field of wireless mesh networks are
an independent router, regardless of whether it is briefly described below:
connected to another network or not. It allows for
continuous connections and reconfiguration around
broken or blocked paths by “hopping” from node to node AODV - Ad hoc On Demand Distance Vector:
until the destination is reached. In this project we intend to
implement a wireless mesh network by configuring Alpine It is routing protocol designed for ad hoc mobile networks.
Linux on a laptop as a mesh node for wireless clients. This It builds routes between nodes only as desired by source
will enable the users in vicinity to connect to the network nodes and hence it’s an on demand algorithm. It maintains
wirelessly and gain access to internet. these routes as long as they are needed by the sources.
Mobile ad hoc networking allows users to exchange MMRP is based upon the link state approach and allows us
information in a wireless environment without the need for a to build least cost paths between any source and
fixed infrastructure. Each user (or node), equipped with one destination. Each "Link State Packet" (LSP) contains
various information including a unique router id and a list of nodes to communicate with other mobile nodes across the
lists that contains each local interface address and a list of fixed network. This can be accomplished by setting up
the neighbor interface addresses which have links to it and tunnels between the border routers across the fixed
their corresponding costs. Also in the LSP are a list of network. The Mobile Mesh Border Discovery Protocol
"External Route Advertisements" which enable the node to (MMBDP) is intended to run on a wired (or fixed network)
advertise routes into the mobile cloud. One use of this is to interface and enables a border router to discover other
allow routers that have a wired connection to a fixed border routers. This information can then be used to setup
network to advertise a default route for the mobile nodes. tunnels amongst the border routers. These tunnels can then
Thus, we provide a mechanism for allowing mobile nodes to be leveraged by a mobile adhoc routing protocol to
gain external connectivity. Also, this mechanism can be disseminate topology information as well as to forward
used by a wireless router to advertise a route for a collection packets.
of hosts which are directly connected to it.
MMBDP is one protocol in a set of related Mobile Mesh
The Mobile Mesh Routing Protocol (MMRP) is a robust, protocols that also includes the Mobile Mesh Link
scalable, efficient mobile adhoc routing protocol based upon Discovery Protocol (MMLDP) and the Mobile Mesh
the "link state" approach. MMRP is one protocol in a set of Routing Protocol (MMRP). Each of these are described in
related Mobile Mesh protocols that also includes the Mobile separate Internet Drafts. An aesthetically pleasing aspect of
Mesh Link Discovery Protocol (MMLDP) and the Mobile these protocols is that they each contain only a single
Mesh Border Discovery Protocol (MMBDP). Together, message type. This form of simplicity, we believe, will
these protocols provide a flexible, extensible mobile adhoc enable others to easily understand and implement the
networking capability. protocols. The process of setting up a tunnel with a peer
creates a new IP interface on a border router; this interface is
The Mobile Mesh Routing Protocol (MMRP) is a robust, a point-to-point tunnel interface that tunnels all packets sent
scalable, and efficient mobile adhoc routing protocol based on it to the peer.
upon the "link state" approach. A node periodically
broadcasts its own Link State Packet (LSP) on each After discovering a peer and setting up a tunnel to it, an
interface participating in the protocol. LSP's are relayed by implementation of MMBDP starts the Mobile Mesh Link
nodes, thus allowing each node to have full topology Discover Protocol on the tunnel interface. MMBDP then
information for the entire adhoc network. From its topology adds the tunnel interface to the Mobile Mesh Routing
database, a node is able to compute least cost unicast routes Protocol. The tunnel interface appears to MMLDP and
to all other nodes in the mobile adhoc network. MMRP to be just another IP interface; the fact that it is a
tunnel interface is not exposed. MMLDP discovers "virtual
An LSP indicates for each interface on the router, the links" from the tunnel interfaces of other border routers and
addresses of neighbor interfaces that have links to it, and the reports them and their associated costs to MMRP. MMRP
associated cost of these links. Also in the LSP are a list of includes in its LSP the IP address of the tunnel interface and
"External Route Advertisements" which enable the node to its associated links and link costs. Thus, MMRP computes
advertise routes into the mobile adhoc cloud for destinations least cost paths that can include both wireless links and
that are "outside" of the mobile adhoc cloud. One use of "virtual links".
this mechanism is to allow routers possessing a wired
connection to a fixed network to advertise a default route. By configuring MMLDP to report the cost of the "virtual
This provides a mechanism for allowing mobile nodes to links" to be much less than the cost of a wireless link, routes
gain external connectivity. Also, this mechanism can be between wireless nodes that traverse the wired/fixed
used by a wireless router to advertise a route for a collection network will be preferred over those that don't. Thus, the
of hosts which are directly connected to it. goal of offloading traffic from the bandwidth constrained
wireless links to the higher capacity wired links is achieved.
To enhance scalability, MMRP performs a technique known
as fish-eye routing in which the resolution of a node's map
of the network decreases as a function of hop distance from SOFTWARE TOOLS:
the node. This is achieved by decreasing the rate at which
LSP's propagate across the network as they get farther away
from their source. This effectively decreases the overhead 1. mmdiscover − Mobile Mesh Link Discovery
associated with disseminating topology information. Also,
this allows more recent LSP's to "catch up" and overwrite mmdiscover speaks the Mobile Mesh Link Discovery
older LSP's as they propagate. Protocol on an individual IP interface and reports neighbor
interface addresses and associated costs for any discovered
links. Links that go down are also detected and reported.
3. Border Discovery Client programs may receive link reports by connecting to a
well-known Unix socket created by mmdiscover whose
Mobile Mesh Border Discovery Protocol (MMBDP) is a name is based upon the name of the IP interface prepended
novel mechanism that enables flow existing outside the with "ln-". For example, if mmdiscover is bound to interface
mobile cloud to be utilized. Other approaches to mobile ad "eth0", the well-known Unix socket name will be "ln-eth0".
hoc networking ignore this possibility. mmdiscover does not have prior knowledge of potential
clients. Clients simply send a message asking for the current
If two or more nodes in a mobile adhoc network each have a list of links. This allows mmdiscover to dynamically learn
connection into a fixed network (let's call these nodes who its clients are. Then, when a link goes up or down, it
"border" routers), then the opportunity exists for mobile sends the event to all clients who have previously requested
a list of links. A failure when sending an event to a client tunnel is created, mmborder dynamically adds the
implies that the client has stopped listening and thus corresponding IP interface to the mobile mesh router mmrp.
mmdiscover removes the client from its dynamically Similary, when the tunnel is destroyed, mmborder
managed set of clients. dynamically removes the IP interface from the mobile mesh
router.
mmdiscover is responsible for determining when links go up
and down. Periodically, it broadcasts a Hello message on a
Udp socket bound to the IP interface. mmdiscover can be
configured to report either unidirectional or only bi- III. Configuring Alpine to connect to Wireless
directional links. The Hello message includes a list of the networks
interface addresses of the senders of Hello messages that
have been heard by the interface in the last DeadInterval. If
We have been able to configure wireless on alpine to
mmdiscover reports uni-directional links, then whenever it
connect to available networks via network authentication
receives a Hello from another node’s interface that it does and WPA encryption.
not have a link from, it reports the new link. If mmdiscover
only reports bi-directional links, then it checks a neighbor
Alpine Linux comes with minimum packages installed so to
list within the received Hello message for the address of the
enable the wireless interface some drivers and packages
interface that heard the Hello. Note, if mmdiscover is
needs to be installed. The steps for configuring Alpine to act
configured to report bi-directional links, then it must report
as a wireless client are:-
that a link went down if it changes from bi-directional to
uni-directional; similarly, it reports that a link came up if it 1. Install the drivers if alpine 1.10 is not able to recognize
changes from uni-directional to bi-directional. If a Hello
the wireless NIC. Once the NIC is identified as wlan0
message for a link which is declared to be up is not received
or eth1 check with ifconfig command to see if any of
within a DeadInterval , mmdiscover reports that the link is
the devices have a wireless interface.
down.
2. Then the wireless_tools package needs to be installed.
This package contains all the wireless utility
2. mmrp − Mobile Mesh Router commands like iwconfig, iwlist. The command for
adding wireless_tools is :-
mmrp speaks the Mobile Mesh Routing Protocol on one or
more IP interfaces. It computes least cost unicast paths to all
apk add wireless_tools
other nodes within the Mobile Mesh cloud and modifies the
IP routing table accordingly. Interfaces and external route
3. The interfaces file needs to be updated to connect to a
advertisements may be specified in a config file or
wireless network and setup the wlan0
dynamically.
Edit /etc/network/interfaces to:-
mmrp learns of link events by connecting to the well known
Unix socket associated with each interface. A link discovery
auto wlan0
program like mmdiscover must be running on an interface
iface wlan0 inet dhcp
prior to informing mmrp to use the interface.
pre-up iwconfigwlan0 essid NetworkName
To enhance scalability mmrp performs a technique called
pre-up iwconfig wlan0 key password
fish-eye routing where the resolution of a node’s map of the
pre-up iwconfig wlan0 channel 11
network is a function of distance. This reduces the overhead
pre-up iwconfig wlan0 mode managed
associated with the flooding of LSP’s.
4. Set the wlan0 up by typing the command
dhcpd wlan0
You will get an IP address after this. Testing the Mesh Network
external <ip address> <netmask> <metric> The page asks for an username & password which
external 0.0.0.0 255.255.255.0 7 is by default in all routers set to:-
This will create a gateway and advertise it for all other Login: admin
nodes on the network. We tried this method but were not Password: password
able to connect to internet from any of the other laptops.
Then we tried changing the netmask to 0.0.0.0. The ping
The next step is to change the ip address send out
command was able to route through our mesh but was not
by router to 192.168.254.X from default
able to receive any packets back.
192.168.1.X. This is done by changing the LAN IP
default to 192.168.254.X in the menu options.
For getting the internet to work in other nodes we also tried
to bridge the wired and wireless interfaces so that the
Then we can check by connecting to the router to
internet can be given to all other nodes via this bridged
see the ip addresses it is sending out whether they
network. For setting up the bridge connection we tried the
are in range.
following setup:-
b. Modify the /etc/network/ interfaces file to: Now we were able to connect to the mesh router
which is just powered and while trying to connect
auto br0 to internet it redirects to the default QCS Mesh
iface br0 inet dhcp login.
pre-up ip link set dev eth0 up
pre-up ip link set dev wlan0 up Using the login and password provided we were
pre-up iwconfig wlan0 mode ad-hoc able to login in the QCS portal. Then the internet
pre-up iwconfig wlan0 essid mesh was working and we were able to connect many
pre-up iwconfig wlan0 key off laptops to this node and get the internet working in
bridge-ports eth0 wlan0 all of the laptops.
pre-down ip link set dev br0 down
down brctl delbr br0
VI. CONCLUSION