162:
type is used to build up routing tables. A node 0 will broadcast that it wants to find a route to D. Then each node that receives the broadcast will add its id to the route and forward the packet. When node D receives a packet, it will reply back along the route that was found for that packet. Then node 0 can use this information to determine the best route using the ETX metrics and the route information returned from its query.
22:
185:
Each packet also includes a list that shows the progress of each packet through the list of radios. This list has one entry per packet. Each entry is the number of radio that is closest to the destination and has retransmitted that packet. The source initially sets this list all to the source radio's
161:
The routing protocol is called SrcRR. There are two broadcasts used with the protocol. The first is periodic broadcasts used to determine a metric called ETX. These public broadcasts measure the probability that a packet between two nodes in radio contact reaches its destination. The second broadcast
192:
Radios on the list save the packet. They update their list of radios transmitting each packet. But they wait a calibrated time before they retransmit any packet. The time is less if they are closer to the destination. The time is a probabilistic estimate of the time to retransmit the packets that
181:
The source radio uses routing data to establish a list of radios that could help reach the destination radio. The list is ordered so that radios closer to the destination are nearer to the head of the list. The destination is at the head of the list. The list is compactly stored in each packet.
196:
If a radio receives a packet transmitted from a radio that is closer to the destination, the farther radio throws away that packet, and never retransmits it. It also updates its list of packet progress.
203:
At the end, a few packets of each batch sent by the source may never reach the destination. It sends these on by the most reliable route, using conventional routing.
228:
200:
As they work backwards toward the source, the retransmissions propagate the batch of packets' progress information back to the source radio.
134:
105:
43:
36:
215:, a mesh networking startup founded by members of MIT's Parallel and Distributed Operating Systems group. Meraki was acquired by
171:
146:
270:
285:
86:
58:
32:
65:
72:
323:
54:
189:
Then, the source broadcasts a batch of packets. Radios not on a packet's list discard the packet.
142:
317:
216:
174:. ExOR simulates some advantages of multicasted data networks by using conventional
79:
233:
212:
141:
measurements of 802.11, finding high-throughput routes in the face of lossy links,
126:
145:, and developing new protocols which take advantage of radio’s unique properties (
150:
21:
297:
138:
259:
239:
308:
175:
122:
130:
170:
One media access and forwarding protocol tested with RoofNet was
149:). The software developed for this project is available free as
15:
303:
309:
MIT Computer
Science and Artificial Intelligence Laboratory
298:
Architecture and
Evaluation of the MIT Roofnet Mesh Network
193:
will be retransmitted by radios closer to the destination.
131:
Computer
Science and Artificial Intelligence Laboratory
242:– An open source operating system for wireless devices
300:– Draft research paper describing the Roofnet project
304:Parallel and Distributed Operating Systems Group
8:
178:digital radios operated in broadcast modes.
211:Roofnet's technology formed the basis for
271:Cisco to Acquire Meraki for $ 1.2 Billion
236:– An ad-hoc mesh network routing protocol
229:List of router and firewall distributions
106:Learn how and when to remove this message
252:
42:Please improve this article by adding
135:Massachusetts Institute of Technology
7:
260:Meraki Cooks Up Wireless Mesh Router
14:
20:
1:
44:secondary or tertiary sources
166:Media access and forwarding
340:
137:(MIT). Research included
286:MIT Roofnet project page
31:relies excessively on
121:was an experimental
129:developed by the
116:
115:
108:
90:
331:
273:
268:
262:
257:
157:Routing protocol
111:
104:
100:
97:
91:
89:
48:
24:
16:
339:
338:
334:
333:
332:
330:
329:
328:
314:
313:
294:
282:
277:
276:
269:
265:
258:
254:
249:
225:
209:
168:
159:
143:link adaptation
112:
101:
95:
92:
49:
47:
41:
37:primary sources
25:
12:
11:
5:
337:
335:
327:
326:
316:
315:
312:
311:
306:
301:
293:
292:External links
290:
289:
288:
281:
278:
275:
274:
263:
251:
250:
248:
245:
244:
243:
237:
231:
224:
221:
208:
205:
167:
164:
158:
155:
114:
113:
28:
26:
19:
13:
10:
9:
6:
4:
3:
2:
336:
325:
322:
321:
319:
310:
307:
305:
302:
299:
296:
295:
291:
287:
284:
283:
279:
272:
267:
264:
261:
256:
253:
246:
241:
238:
235:
232:
230:
227:
226:
222:
220:
218:
217:Cisco Systems
214:
206:
204:
201:
198:
194:
190:
187:
183:
179:
177:
173:
165:
163:
156:
154:
152:
148:
144:
140:
136:
132:
128:
124:
120:
110:
107:
99:
96:December 2008
88:
85:
81:
78:
74:
71:
67:
64:
60:
57: –
56:
52:
51:Find sources:
45:
39:
38:
34:
29:This article
27:
23:
18:
17:
266:
255:
234:B.A.T.M.A.N.
210:
202:
199:
195:
191:
188:
184:
180:
169:
160:
127:mesh network
118:
117:
102:
93:
83:
76:
69:
62:
50:
30:
324:IEEE 802.11
207:Development
151:open source
247:References
139:link-level
66:newspapers
33:references
219:in 2012.
55:"Roofnet"
318:Category
223:See also
186:number.
280:Sources
240:OpenWrt
133:at the
123:802.11b
119:Roofnet
80:scholar
213:Meraki
176:802.11
82:
75:
68:
61:
53:
87:JSTOR
73:books
172:ExOR
147:ExOR
59:news
125:/g
35:to
320::
153:.
46:.
109:)
103:(
98:)
94:(
84:·
77:·
70:·
63:·
40:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
