JensMuellerRestricted: Difference between revisions
No edit summary |
No edit summary |
||
Line 75: | Line 75: | ||
| | FromDevice |
| | FromDevice |
||
+-------------+ |
+-------------+ |
||
==Click== |
|||
Tried to implement an element by polymorphy (a diamon), which is possible in C++. But it did not worked in Click. Maybe someone has a working example. I tried virtual and so on, but it did not compile. I use the delegation pattern instead, which is also ugly, since I need to pass the set ports. |
Revision as of 20:00, 31 January 2006
ExOR
- entgegengesetzt zu Network Coding, denn ich weiß nicht, wer das Paket bekommen wird (aber aus der Menge meiner Nachbarn)
- verwende nur Broadcasts und der Knoten am nächsten zum Ziel leitet das Paket weiter (Problem, wenn das Netz voll ist; Broadcasts "zerstören" sich gegenseitig oder erweitertes RTS/CTS?)
- dichte Netze als Vorraussetzung
- Verwendung mehrerer Kanäle um "Self-Interference" zu vermeiden (oder erweitertes RTS/CTS?)
Using the LEDs of wgt634u
Routing in wireless Networks
Things to consider
- Negative effects
- self interference
- Postive effects
- Broadcast nature
Ideas:
- Minimizing transmissions (Network Coding / ExOR)
- Minimizing collisions (difficult)
Routingprotokolle aus Nachrichtensicht Layer 3 - Flooding - Multicast - Unicast
Layer 2 - Broadcast (lokal) - Multicast - Unicast
Die Idee ist, dass alle Routingprotokolle Nachrichten versenden müssen. In diese Nachrichten-Elemente steckt man dann nur noch den Payload.
Kann man das Routing auch adressunabhängig implementieren (mittels Polymorphie)
=> Besseres Engineering
config.xml CruiseControl ns2 click (i386, mips) testsuite
IvyCruise
Gateway - Wann neue Gatewaymetrik propagieren
Wann wechselt der GatewaySelector das Gateway (nicht nötig bei Google-Ansatz)?
Wie merke ich, dass das Gateway wegbricht (ICMP Nachricht)?
NAT Probleme
Nsclick
+-----------+ | | | MAC | | | +-----------+
| | wie FromHost () +------------------> +-----------+ | | | Click | ToDevice | | +------------ +-----------+ | ^ | | | | V | +-------------+ | | | | | PHY +--------------+ | | FromDevice +-------------+
Click
Tried to implement an element by polymorphy (a diamon), which is possible in C++. But it did not worked in Click. Maybe someone has a working example. I tried virtual and so on, but it did not compile. I use the delegation pattern instead, which is also ugly, since I need to pass the set ports.