This data set contains a collection of wireless traces from the University of Puerto Rico. Wireless signal strength measurements for Dell and Thinkpad laptops were performed over distances of 500 feet and one mile. The data is presented in .cap files giving TCP dump packet headers.last modified : 2008-09-24release date : 2006-04-12date/time of measurement start : 2006-01-24date/time of measurement end : 2006-01-24collection environment : A collection of wireless traces from Jan 24th 2006 at the University of Puerto Rico. Contains wireless signal strength measurements for Dell and Thinkpad laptops. These traces were gathered as part of an undergraduate course taught by Jim Kurose and Mike Zink.network configuration : Wireless signal strength was measured between two Linux laptops - Dell and Thinkpad. Each machine is equippted with a Proxim Orinoco 11b/g PC Card, an antenna of either Yagi 14 dBi, Parabolic Disk 24 dBi, or Parabolic Disk 30 dBi.data collection methodology : Tests were performed over distances of 500 feet and one mile. Data is presented in .cap files giving tcpdump packet headers.Tracesetuprm/wireless/short_linkTraceset of wireless signal strength measurements over distances of 500 feet from the University of Puerto Rico.description: This traceset contains a collection of wireless traces from the University of Puerto Rico, where wireless signal strength measurements for Dell and Thinkpad laptops were performed over distances of 500 feet.measurement purpose: Network Performance Analysismethodology: We began this experiment at ~ 10:00. Tests 1 to 8 were performed from rooftop to rooftop of 2 close buildings, approx. 500' apart. The goal was essentially to get everyone familiar with the equipment and go over Linux commands, and make sure the equipment was working properly. We performed some iperf tests over this link with several different scenarios.uprm/wireless/short_link Tracestrace_1: Trace of wireless signal strength measurement - test 1 - over distances of 500 feet.configuration: This was our first test, with the default wireless settings. Link Quality was around 30/94. We performed iperf with default settings also. Files: thinkpad/test1_tcp, dell/initial_default.capformat:tcpdumptrace_2: Trace of wireless signal strength measurement - test 2 - over distances of 500 feet.configuration: We noticed approx. 20 other access points when doing a scan, so we decided to switch to ch11. Signal strength improved to about 50/94, used default iperf commands. Files: thinkpad/test2_ch11_tcp, dell/default_ch_11.capformat:tcpdumptrace_3: Trace of wireless signal strength measurement - test 3 - over distances of 500 feet.configuration: In this test we performed an iperf test with UDP, signal strength at 50/94. During the test we realized that we lost the connection. Files: thinkpad/test3_ch11_udp, dell/ch_11_udp.capformat:tcpdumptrace_4: Trace of wireless signal strength measurement - test 4 - over distances of 500 feet.configuration: We reset the cards and ran the previous test again. This time it was successful, we utilized almost all the bandwidth. Files: thinkpad/test4_ch11_udp, dell/ch_11_udp_2nd_try.capformat:tcpdumptrace_5: Trace of wireless signal strength measurement - test 5 - over distances of 500 feet.configuration: For this test, we set the distance for the wireless drivers with the athctrl utility to 1 meter. We ran iperf with UDP. We realized that the utility had not been run on both sides of the link. Signal strength was around 54/94. Files: thinkpad/test5_ch11_udp, dell/udp_1_meter.capformat:tcpdumptrace_6: Trace of wireless signal strength measurement - test 6 - over distances of 500 feet.configuration: Here we corrected for the issue in trace_5, both sides of the link now had the distance for the drivers set to 1 meter. Signal strength was around 54/94. Files: thinkpad/test6_ch11_udp_1meter, dell/udp_1_meter_both_sides.capformat:tcpdumptrace_7: Trace of wireless signal strength measurement - test 7 - over distances of 500 feet.configuration: We ran the previous test (test_6), with the drivers for both cards set to 1 meter, and ran iperf with TCP. Signal strength was around 54/94. Files: thinkpad/test7_ch11_tcp_1meter, dell/tcp_1_meter_both_sides.capformat:tcpdumptrace_8: Trace of wireless signal strength measurement - test 8 - over distances of 500 feet.configuration: In this trace we tested the strength of the signal of the side lobes by turning the antennas 90 degrees in one direction, and then 90 degrees in the other direction. Our signal strength at 90 degrees was around 39/94 and the direct signal strength averaged 55/94. Files: thinkpad/test8_ch11_tcp_1meter_side, dell/tcp_1_meter_side_lobe.capformat:tcpdumpuprm/wireless/long_distance_linkTraceset of wireless signal strength measurements over distances of one mile from the University of Puerto Rico.description: This traceset contains a collection of wireless traces from the University of Puerto Rico, where wireless signal strength measurements for Dell and Thinkpad laptops were performed over distances of one mile.measurement purpose: Network Performance Analysismethodology: Wireless traces from Jan 24th 2006 at UPRM Mayaguez Puerto Rico. After lunch we performed tests 9 - 22 from rooftop to rooftop over a link approx. 1 mile. We made measurements using iperf, and recorded two sessions transferring some radar data.uprm/wireless/long_distance_link Tracestrace_9: Trace of wireless signal strength measurement - test 9 - over distances of one mile.configuration: - we had trouble with this one (no connection/signal faded). There is no corresponding trace on the dell. We had some setup issues when trying to get the long distance link up. Files: thinkpad/longtest9_tcp_2000mformat:tcpdumptrace_10: Trace of wireless signal strength measurement - test 10 - over distances of one mile.configuration: This was our first test after making a connection on the long distance link. We set the drivers of both wireless cards to 2,000 meters using the athctrl utility. Signal strength was around 30/94. We ran iperf with TCP. Files: thinkpad/longtest10_tcp_2000m, dell/longdistance/first_test.capformat:tcpdumptrace_11: Trace of wireless signal strength measurement - test 11 - over distances of one mile.configuration: We tested setting the distance higher, this time we set it to 5000 meters over-shooting the distance to see what would happened. Signal strength dropped slightly. We ran iperf with TCP Files: thinkpad/longtest11_tcp_5000m, dell/longdistance/tcp_5000.capformat:tcpdumptrace_12: Trace of wireless signal strength measurement - test 12 - over distances of one mile.configuration: Now we adjusted the distance to 1600 meters, which was more accurate. We ran iperf with TCP. Files: thinkpad/longtest12_tcp_1600m, dell/longdistance/tcp_1600.capformat:tcpdumptrace_13: Trace of wireless signal strength measurement - test 13 - over distances of one mile.configuration: We tested setting the distance at various intervals, here it was set to 1000 meters and we ran iperf with TCP. Files: thinkpad/longtest13_tcp_1000m, dell/longdistance/tcp_1000.capformat:tcpdumptrace_14: Trace of wireless signal strength measurement - test 14 - over distances of one mile.configuration: In this test the distance was set to 1000 meters and we ran iperf with TCP. Files: thinkpad/longtest13_tcp_500m, dell/longdistance/tcp_500.capformat:tcpdumptrace_15: Trace of wireless signal strength measurement - test 15 - over distances of one mile.configuration: For this test we set the distance back to 1600 meters, where we had seen the best performance. This time we transferred 40MB of data with iperf using TCP. Signal strength was approx. 39/94 Files: thinkpad/longtest14_tcp_1600m_40MB, dell/longdistance/tcp_40m_1600.capformat:tcpdumptrace_16: Trace of wireless signal strength measurement - test 16 - over distances of one mile.configuration: For this test, we used the same distance, 1600 meters and with 40MB of data, using UDP. There were some issues on the Dell side which required a reboot. Files: thinkpad/longtest15_udp_1600m, dell/longdistance/udp_1600_2.capformat:tcpdumptrace_17: Trace of wireless signal strength measurement - test 17 - over distances of one mile.configuration: We ran the previous test (trace_16) over again. Files: thinkpad/longtest16_udp_1600m, dell/longdistance/udp_1600_3.capformat:tcpdumptrace_18: Trace of wireless signal strength measurement - test 18 - over distances of one mile.configuration: something went wrong and not enough data was captured in the trace. Files: thinkpad/longtest17_udp_1600m, dell/longdistance/udp_1600_chan_11.capformat:tcpdumptrace_19: Trace of wireless signal strength measurement - test 19 - over distances of one mile.configuration: something went wrong and not enough data was captured in the trace. Files: thinkpad/longtest19_udp_800m_ch11, dell/longdistance/afterreboot/udp_800.capformat:tcpdumptrace_20: Trace of wireless signal strength measurement - test 20 - over distances of one mile.configuration: something went wrong and not enough data was captured in the trace. Files: thinkpad/longtest20_udp_1600m_ch11format:tcpdumptrace_21: Trace of wireless signal strength measurement - test 21 - over distances of one mile.configuration: We transferred a large file consisting of radar data using ftp over the link. Signal strength was about 39/94 and we had both cards set to a distance of 1600 meters. Files: thinkpad/longtest21_radardata_1600m_ch11, dell/longdistance/ftp_xfr.capformat:tcpdumptrace_22: Trace of wireless signal strength measurement - test 22 - over distances of one mile.configuration: In this test we transferred 1GB of radar data via ftp with the drivers set to a distance of 1600 meters. There was an issue on the Dell side which resulted in no capture, but we have data from the ThinkPad side. Files: thinkpad/longtest22_1GB_radardata_1600m_ch11format:tcpdump

Our experiments consisted of 802.11g wireless network throughput measurements in various overlapping ad-hoc node configurations in order to better understand interference when using yagi antennas to extend the range of the wireless transmission.last modified : 2008-06-05release date : 2007-06-01date/time of measurement start : 2006-10-10date/time of measurement end : 2006-12-09collection environment : With the increasing popularity of 802.11 wireless technology, such equipment has recently been used to set up long distance links for wireless mesh networks. To be able to increase the range of 802.11 equipment directional antennas are required. We measured the effects of wireless interference on throughput. Our experiments consisted of 802.11g wireless network throughput measurements in various overlapping ad-hoc node configurations in order to better understand interference when using yagi antennas to extend the range of the wireless transmission. We were particularly interested in the behavior at the multi-hop node, which has 2 antennas in close proximity as would be required on a communications tower.network configuration : The test equipment consists of 4 Lenovo T60 notebooks running slackware Linux with the 2.6 kernel, and using ProximWLAN adapters (atheros chipset), and we are using the opensourceMadWifi drivers for the wireless cards. These PCMCIA cards are connected to an external Hyperlink Yagi antenna to extend their range. We make a special point to note that MadWifi driver includes a proprietary HAL that controls many key aspects of the adapters, one of which being the use of measured RSSI values to sense whether the channel is in use, contrasted with the RTS/CTS scheme that other wireless cards use to sense the channel. We suspect that this channel contention scheme leads to some unexpected behavior in our ad-hoc test network.data collection methodology : We used Iperf3, a tool to measure maximum TCP bandwidth, to investigate how the different setups would change the overall performance of the multi-hop link. Additional tcpdump4 traces were taken in order to obtain more detailed information on a per-packet level. Each measurement ran for 30 seconds and was repeated 10 times. We decided to repeat each measurement 10 times to average out the effects of any short-term artifacts on the wireless channel. For each test we vary the channels 1-6 on pair2 while keeping pair1 on channel 1. It should be noted that we tested overlap up to 5 channels of separation because after that there is such minimal overlap in the spectrum, that the results would not vary.Tracesetumass/long_distance/interferenceTraceset of 802.11g long-distance measurements over ad-hoc nodes using directional antennas.description: Our experiments consisted of 802.11g wireless network throughput measurements in various overlapping ad-hoc node configurations in order to better understand interference when using yagi antennas to extend the range of the wireless transmission.measurement purpose: Network Performance Analysis, Routing Protocolmethodology: Our experiments consisted of 802.11g wireless network throughput measurements in various overlapping ad-hoc node configurations in order to better understand interference when using yagi antennas to extend the range of the wireless transmission. A. Node Location and Spatial Separation As shown in [Figure: Measurement setup], Node 4 was set up in 3 different locations while Node 1 and the multi-hop node (composed of Nodes 2 and 3) stayed in fixed locations. In the multi-hop node the only change that was made for the different setups was the orientation of Node 3's antenna to line it up with Node 4's antenna. For all measurements except one the two antennas at the multi-hop node were placed 4 feet from each other in the horizontal plane, with no separation in the vertical plane. In the setup for the final measurement we also separated the two antennas at the middle node by 4 feet in the vertical plane. We assumed that a distance of 4 feet would be a separation distance typical of installations on communication towers. Five different setups, which are explained in more detail in the following, were used for the throughput measurements. In setup 1, all nodes are located along a virtual line. The two antennas at the multi-hop node are mounted in a way that they point directly away (180 ) from each other. In setup 2, link 2 is shifted by 45, resulting in a 135 angle between the main lobes of the two antennas at the multi-hop node. Link 2 is shifted by 90 in setup 3, which also results in a 90 separation of the antennas. Setup 4 is identical to setup 3 with the difference that the polarization of the antennas of link 2 is changed from horizontal to vertical. This is achieved by rotating the mounting of the Yagi antennas by 90 in the horizontal plane. Setup 5 is identical to setup 1 with the difference that the antennas were not only separated by 4 feet in the horizontal but also by 4 feet in the vertical plane. B. Transport Scenario We performed measurements where data was transmitted in two different ways. - N4 -> N3 | N2 -> N1: Here, N4 and N2 are sending data simultaneously to N3 and N1, respectively. - N4 -> N3 -> N2 -> N1: N4 is sending data all the way to N1 in this scenario. Thus, routing between N2 and N3 is enabled. We chose this specific routing configuration for several reasons. In the first scenario we want to investigate the interference that is caused at a multi-hop node with directional antennas when one radio is receiving while the other one is sending. In the second scenario, we were interested in studying the effects of concurrent forwarding on the N1-N2 and N3-N4 links, as well as the effects of routing on the wired link 3 in the multi-hop node. The second case is interesting since in many cases data will be routed through the multi-hop node between the two end nodes. For example, in the case where such a multi-hop node is used to allow data transmission from a remote sensor network. Here, the multi-hop node is neither a source nor a sink. The first case reflects a scenario in which the multi-hop node also acts as a source or a sink. C. Baseline Measurements We performed two preliminary measurements in a single link setup to measure the maximum throughput on that link without any interference from the other link. The first measurement was executed in the same open field where all multi-link measurements were performed. We ran an Iperf measurement on one link only, while the other one was idle, which resulted in 27 Mbps of average throughput. This throughput value is the upper limit for the multi-hop measurements. In the second setup we were interested how the throughput would change on a much longer link. Therefore, we set up a link of approximately 1 Mile in hilly terrain. Here, the Iperf measurement resulted in an average throughput of 25.54 Mbps.umass/long_distance/interference Tracestest1: Trace of 802.11g long-distance measurements using directional antennas.configuration: In each of 13 tests, nodes 1 and 2 are on essid pair1, and nodes 3 and 4 are on essid pair2, this allows us to force the traffic to be routed through the multi-hop node instead of the overlap just reaching the far reciever in some cases. For each of 5 network configurations, we conducted 2 experiments; we tested througput in a 2-hop routing configuration (where we consider the middle node as a virutal single node), and we tested throughput in a non-routing configuration where 2 nodes, one from each essid, are sending at the same time. In the non-routing test the multi-hop node is sending on one interface and recieving on the other. Test 1: N4 -> N3 | N2 -> N1 In this test we look at the interference when two nodes are sending towards a multi-hop node and the multi-hop node is recieving on both interfaces. The nodes are in a straight line, 180 degree. Nodes 1 and 4 transmit at the same time towards the center node. We see a steady increase in throughput as we extend the channel seperation. The signal strength did not match the throughput results exactely, it increased at a separation of 2 and 3, and dropped down to 20-30 RSSI for the remainder.format: test2: Trace of 802.11g long-distance measurements using directional antennas.configuration: In each of 13 tests, nodes 1 and 2 are on essid pair1, and nodes 3 and 4 are on essid pair2, this allows us to force the traffic to be routed through the multi-hop node instead of the overlap just reaching the far reciever in some cases. For each of 5 network configurations, we conducted 2 experiments; we tested througput in a 2-hop routing configuration (where we consider the middle node as a virutal single node), and we tested throughput in a non-routing configuration where 2 nodes, one from each essid, are sending at the same time. In the non-routing test the multi-hop node is sending on one interface and recieving on the other. Test 2: N4 -> N3 | N2 -> N1 In this test we look into interference when two nodes transmit at the same time. Nodes 2 and 4 transmit at the same time and the multi-hop node is sending on one interface and recieving on the other. The antennas at the center node are separated by 5 minutes. The nodes are in a straight line, 180 degree. We noticed that there was a lot of variance in the throughput on this test, and we suspect that this may be due to the way that the wireless interfaces contend for the channel. Another reason for the variance could be that node 4 is overshooting the multi-hop node and is being sensed at node 1 as node1 is recieving from node2. The throughput is consistently higher on the pair2 network which seems to support this idea. Also, on channel 4 pair2 had throughput upwards of 24 Mbps, but all of a sudden around run 7 of 10 it seemed to lose the channel and pair1 started to take over. This is why there is such a large variation at a channel seperation of 3.format: test3: Trace of 802.11g long-distance measurements using directional antennas.configuration: In each of 13 tests, nodes 1 and 2 are on essid pair1, and nodes 3 and 4 are on essid pair2, this allows us to force the traffic to be routed through the multi-hop node instead of the overlap just reaching the far reciever in some cases. For each of 5 network configurations, we conducted 2 experiments; we tested througput in a 2-hop routing configuration (where we consider the middle node as a virutal single node), and we tested throughput in a non-routing configuration where 2 nodes, one from each essid, are sending at the same time. In the non-routing test the multi-hop node is sending on one interface and recieving on the other. Test 3: N4 -> N3 -> N2 -> N1 In this test we have configured the multi-hop node as a gateway for each end node, and so node 4 is running the iperf client, and node 1 is running the iperf server. The nodes are in a straight line, 180 degree. And the two nodes at the center are spaced about 5 minutes apart. We experienced a throughput of 4.3 Mbps on channel 1, poor in comparison, but as the channels separate the throughput steadily grows to 27 Mbpsformat: test4: Trace of 802.11g long-distance measurements using directional antennas.configuration: In each of 13 tests, nodes 1 and 2 are on essid pair1, and nodes 3 and 4 are on essid pair2, this allows us to force the traffic to be routed through the multi-hop node instead of the overlap just reaching the far reciever in some cases. For each of 5 network configurations, we conducted 2 experiments; we tested througput in a 2-hop routing configuration (where we consider the middle node as a virutal single node), and we tested throughput in a non-routing configuration where 2 nodes, one from each essid, are sending at the same time. In the non-routing test the multi-hop node is sending on one interface and recieving on the other. Test 4: N4 -> N3 | N2 -> N1 In this configuration we create a 135 degree angle between nodes 3 and 4 by rotating node 4 by 45 degree. No routing is used in this test and nodes 4 and 2 transmit at the same time. The antenna's at the center are spaces 5 minutes apart. The performace is slightly better, definately more consistent at this angle, rather than directly facing each other yet it is worse on channel 2. Overall this angle is much better than the 90 degree setup which had 5 Mbps on channel 1.format: test5: Trace of 802.11g long-distance measurements using directional antennas.configuration: In each of 13 tests, nodes 1 and 2 are on essid pair1, and nodes 3 and 4 are on essid pair2, this allows us to force the traffic to be routed through the multi-hop node instead of the overlap just reaching the far reciever in some cases. For each of 5 network configurations, we conducted 2 experiments; we tested througput in a 2-hop routing configuration (where we consider the middle node as a virutal single node), and we tested throughput in a non-routing configuration where 2 nodes, one from each essid, are sending at the same time. In the non-routing test the multi-hop node is sending on one interface and recieving on the other. Test 5: N4 -> N3 -> N2 -> N1 This setup is a 135 degree test similar to test 4, except that we have enabled routing via the multi-hop node. The antenna's at the center are about 5 minutes apart. The iperf server is run on node 1 and node 4 is the client. At this antenna orientation we have much better performance that in the 180 degree case, 13 Mbps vs. 4 Mpbs on channel 1. We think that this is due to the fact that the antenna pattern of the yagi's has a weak spot right at the 135 degree section (off center), and so we are not causing as much interference with the sender at the multi-hop node (node 2).format: test6: Trace of 802.11g long-distance measurements using directional antennas.configuration: In each of 13 tests, nodes 1 and 2 are on essid pair1, and nodes 3 and 4 are on essid pair2, this allows us to force the traffic to be routed through the multi-hop node instead of the overlap just reaching the far reciever in some cases. For each of 5 network configurations, we conducted 2 experiments; we tested througput in a 2-hop routing configuration (where we consider the middle node as a virutal single node), and we tested throughput in a non-routing configuration where 2 nodes, one from each essid, are sending at the same time. In the non-routing test the multi-hop node is sending on one interface and recieving on the other. Test 6: N4 -> N3 | N2 -> N1 In this test we alter the antenna orientation to 90 degree off center, between node 3 and 4. The antenna's at the center are 5 minutes apart. Again, both nodes are transmitting simultanously. Pair 1 seems to dominate the channels this time, and has much higher throughput (25 Mbps for pair1 vs. 5 Mbps for pair2). The sidelobes of the antenna are largest at 90 degree so this could account for the poor performance on pair2. It seems thought that in the scenario's where there are 2 simultaneous transmissions and no routing, that one side seems to dominate.format: test7: Trace of 802.11g long-distance measurements using directional antennas.configuration: In each of 13 tests, nodes 1 and 2 are on essid pair1, and nodes 3 and 4 are on essid pair2, this allows us to force the traffic to be routed through the multi-hop node instead of the overlap just reaching the far reciever in some cases. For each of 5 network configurations, we conducted 2 experiments; we tested througput in a 2-hop routing configuration (where we consider the middle node as a virutal single node), and we tested throughput in a non-routing configuration where 2 nodes, one from each essid, are sending at the same time. In the non-routing test the multi-hop node is sending on one interface and recieving on the other. Test 7: N4 -> N3 -> N2 -> N1 This is a routing test which was conducted with a 90 degree antenna orientation between nodes 3 and 4. The antenna's at the center are 5 minutes apart. Routing is enabled this time, with node 4 as the iperf client and node 1 as the server. The throughput here was a little worse than the 135 degree case, 10 Mbps here vs. 14 Mbps at 135 degree, yet much better than the 180 degree case which had a throughput of 3.5 on channel 1. We believe that the better results at low channel separations is due to orientation angle, and also in that when routing is enabled, the networks negotiate the channel better and share the bandwidth more evenly even with the side-lobe overlap.format: test8: Trace of 802.11g long-distance measurements using directional antennas.configuration: In each of 13 tests, nodes 1 and 2 are on essid pair1, and nodes 3 and 4 are on essid pair2, this allows us to force the traffic to be routed through the multi-hop node instead of the overlap just reaching the far reciever in some cases. For each of 5 network configurations, we conducted 2 experiments; we tested througput in a 2-hop routing configuration (where we consider the middle node as a virutal single node), and we tested throughput in a non-routing configuration where 2 nodes, one from each essid, are sending at the same time. In the non-routing test the multi-hop node is sending on one interface and recieving on the other. Test 8: N4 -> N3 | N2 -> N1 This test was conducted at a 90 degree orientation, and also the pair2 network has changed polarization of the yagi antennas from vertical to horizontal. The pair1 network is still at the vertical orientation. The antenna's at the multi-hop node are separated by 5 minutes. Both Nodes 2 and 4 transmit simultaneously. In this case the channel is shared a little better than in test 7 where the only difference was in the polarization. But here pair2 dominates the channels an has higher throughput, except on channel 1 they are both right at 15 Mbps. In test 7 on channel 1 both pairs were at a difference of 20 Mbps. This suggests that the polarization has a large effect when operating on the same channel.format: test9: Trace of 802.11g long-distance measurements using directional antennas.configuration: In each of 13 tests, nodes 1 and 2 are on essid pair1, and nodes 3 and 4 are on essid pair2, this allows us to force the traffic to be routed through the multi-hop node instead of the overlap just reaching the far reciever in some cases. For each of 5 network configurations, we conducted 2 experiments; we tested througput in a 2-hop routing configuration (where we consider the middle node as a virutal single node), and we tested throughput in a non-routing configuration where 2 nodes, one from each essid, are sending at the same time. In the non-routing test the multi-hop node is sending on one interface and recieving on the other. Test 9: N4 -> N3 -> N2 -> N1 This test was conducted at a 90 degree orientation with opposite polarizations on each network. Pair2 is set to horizontal polarization while pair1 is vertical. The antenna's at the multi-hop node are separated by 5 minutes. Node 4 transmits to Node 1 by routing through the multi-hop node. This result is very similar to the 135 degree test when routing is enabled. Routing in this case seems to make both networks share the bandwidth regardless of the polarization.format: test10: Trace of 802.11g long-distance measurements using directional antennas.configuration: In each of 13 tests, nodes 1 and 2 are on essid pair1, and nodes 3 and 4 are on essid pair2, this allows us to force the traffic to be routed through the multi-hop node instead of the overlap just reaching the far reciever in some cases. For each of 5 network configurations, we conducted 2 experiments; we tested througput in a 2-hop routing configuration (where we consider the middle node as a virutal single node), and we tested throughput in a non-routing configuration where 2 nodes, one from each essid, are sending at the same time. In the non-routing test the multi-hop node is sending on one interface and recieving on the other. Test 10: N4 -> N3 | N2 -> N1 This test was performed at 180 degree and both networks were set to the same vertical polarization. The Height of the antenna's was altered so that pair2 was at an elevation of 11 minutes and pair1 was at an elevation of 2 minutes. We wanted to see if this would have an effect on interference at the middle node. Nodes 2 and 4 transmitted simultaneously. The performance was a little bit worse than in test 3, the 180 degree case with no additional adjustments. This is most likely due to outside interference due to the fact that the field we were testing in became a parking lot for an event, and the influx of cars on this occasion cause unmeasureable effects on the results. We repeat this test again in test 12.format: test11: Trace of 802.11g long-distance measurements using directional antennas.configuration: In each of 13 tests, nodes 1 and 2 are on essid pair1, and nodes 3 and 4 are on essid pair2, this allows us to force the traffic to be routed through the multi-hop node instead of the overlap just reaching the far reciever in some cases. For each of 5 network configurations, we conducted 2 experiments; we tested througput in a 2-hop routing configuration (where we consider the middle node as a virutal single node), and we tested throughput in a non-routing configuration where 2 nodes, one from each essid, are sending at the same time. In the non-routing test the multi-hop node is sending on one interface and recieving on the other. Test 11: N4 -> N3 -> N2 -> N1 This test was performed at 180 degree and both networks were set to the same vertical polarization. The Height of the antenna's was altered so that pair2 was at an elevation of 11 minutes and pair1 was at an elevation of 2 minutes. We wanted to see if this would have an effect on interference at the middle node. Routing was enabled but performance was poor due to outside factors, the influx of cars on this occasion cause unmeasureable effects on the results. We repeat this test again in test 13.format: test12: Trace of 802.11g long-distance measurements using directional antennas.configuration: In each of 13 tests, nodes 1 and 2 are on essid pair1, and nodes 3 and 4 are on essid pair2, this allows us to force the traffic to be routed through the multi-hop node instead of the overlap just reaching the far reciever in some cases. For each of 5 network configurations, we conducted 2 experiments; we tested througput in a 2-hop routing configuration (where we consider the middle node as a virutal single node), and we tested throughput in a non-routing configuration where 2 nodes, one from each essid, are sending at the same time. In the non-routing test the multi-hop node is sending on one interface and recieving on the other. Test 12: N4 -> N3 | N2 -> N1 Simultaneous transmission height difference test - repeat of 10. Pair2 really dominated this time. The throughput on pair2 was much better than in test3, but pair1's thoughput was really poor. Again, channel contention algorithms have a big part in this phenomenon. Pair2 seems to have grabbed the bandwidth and stuck with it. Pair1's gains came during intervals of the 10 runs when pair2 stopped sending breifly to start another run.format: test13: Trace of 802.11g long-distance measurements using directional antennas.configuration: In each of 13 tests, nodes 1 and 2 are on essid pair1, and nodes 3 and 4 are on essid pair2, this allows us to force the traffic to be routed through the multi-hop node instead of the overlap just reaching the far reciever in some cases. For each of 5 network configurations, we conducted 2 experiments; we tested througput in a 2-hop routing configuration (where we consider the middle node as a virutal single node), and we tested throughput in a non-routing configuration where 2 nodes, one from each essid, are sending at the same time. In the non-routing test the multi-hop node is sending on one interface and recieving on the other. Test 13: N4 -> N3 -> N2 -> N1 Routing height separated test - repeat of 11. Here we actually do worse than in the 180 degree non-height separated routing scenario. We are not really sure why, we expected a benefit.format: