13.07.2015 Views

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

Page 2 Lecture Notes in Computer Science 2865 Edited by G. Goos ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Extend<strong>in</strong>g Seamless IP Multicast Edge-Coverage 91nodes, may be received <strong>by</strong> all neighbours and processed <strong>in</strong>dependently, creat<strong>in</strong>gunnecessary paths.The MMARP protocol has been designed to avoid unnecessary generationof these messages. It <strong>in</strong>cludes a field <strong>in</strong> its header which facilitates the identificationof the node which actually triggered the send<strong>in</strong>g of the control message;this allows ad hoc nodes to identify all the MMARP packets which are triggered<strong>by</strong> a specific standard IP node, <strong>in</strong>dependently of the ad hoc neighbour whichactually generated it. Thus, ad hoc neighbours of standard IP nodes and <strong>in</strong>termediatead hoc nodes are able to detect these types of MMARP SOURCEand MMARP JOIN messages as duplicate and avoid the creation of unnecessarypaths.4 Empirical ResultsWe have set up an <strong>in</strong>door 802.11b multicast wired-to-wireless ad hoc networktestbed to evaluate the feasibility of our MMARP-based seamless IP multicastapproach for wireless ad hoc access networks. Our target is to evaluate the benefitsof MMARP-driven <strong>in</strong>frastructureless ad hoc access networks when comparedto traditional s<strong>in</strong>gle-hop wireless IP multicast <strong>in</strong> a realistic scenario.4.1 Testbed DescriptionAs it is shown <strong>in</strong> Fig. 3, the testbed consists of six x86-compatible PCs anda laptop. Different processor and memory configurations are used, s<strong>in</strong>ce thereare not any specific hardware requirements. In fact, all of these PCs are able tosupport the workload of the experiments. Three out of the six PCs are act<strong>in</strong>gas MMARP-enabled nodes runn<strong>in</strong>g Red Hat L<strong>in</strong>ux 7.2 with the 2.4.17 kernel.They have a Lucent 802.11b pcmcia card as unique NIC. The nodes labelled asWR (Wireless Router) and WWR(Wired-to-Wireless Router) are PCs runn<strong>in</strong>gFreeBSD 4.6 OS. The WWR node is equipped with two NICs, one of them be<strong>in</strong>ga Lucent WaveLan pcmcia card to provide coverage for the wireless area, whilethe other one is a 100 Mbps Ethernet NIC. The Wired Router (WR) conta<strong>in</strong>stwo 100 Mb/s Ethernet NICs, one connected to the WWR and the other one tothe rest of fixed networks. The Sender and Receiver nodes are both runn<strong>in</strong>g RedHat 7.2 with kernel 2.4.17. The sender is a x86-compatible desktop with a 100Mb/s Ethernet card whereas the receiver is a laptop PC equipped with a Lucent802.11b-compatible pcmcia wireless NIC. Wireless 2.422 GHz channel operat<strong>in</strong>gat the maximum capacity of 2 Mb/s has been used for the experiment. We havepreviously checked that this channel was not occupied <strong>by</strong> any other equipment.All the WaveLan NICs are operated <strong>in</strong> ad hoc mode.4.2 Description of the ExperimentsTo assess the effectiveness of our proposal, we have performed two different tests:s<strong>in</strong>gle-hop IP multicast and multihop ad hoc IP multicast. The former consists of

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!