close
Warning:
Can't synchronize with repository "(default)" ("(default)" is not readable or not a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
Nov 30, 2014, 4:39:52 AM (9 years ago)
- Author:
-
wontoniii
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v3
|
v4
|
|
3 | 3 | |
4 | 4 | == Topology Control == |
5 | | Since multiple routers may run in a single LAN, connectivity needs to be enforced and packets destined to non-neighbor nodes be dropped. This is enabled in the MobilityFirst router pipeline by way of topology enforcement element that takes a GUID-based connectivity graph passed as a topology file at start up time. Consider below a simple topology with three !MobilityFirst routers and two end hosts: |
| 5 | Since multiple routers may run in a single LAN, connectivity needs to be enforced and packets destined to non-neighbor nodes be dropped. This is enabled in the !MobilityFirst router pipeline by way of topology enforcement element that takes a GUID-based connectivity graph passed as a topology file at start up time. Consider below a simple topology with three !MobilityFirst routers and two end hosts: |
6 | 6 | {{{ |
7 | 7 | Sender ---- MFR1 ---- MFR2 ---- MFR3 ---- Receiver |
… |
… |
|
21 | 21 | == Logging Configuration == |
22 | 22 | The environment variable ''MF_CLICK_LOG_LEVEL'' can be set to an integer value between 0 and 7 corresponding to enable one of the following log levels for the Click-based MF router: |
23 | | || Value || Log Level || Description || |
| 23 | || '''Value''' || '''Log Level''' || '''Description''' || |
24 | 24 | || 0 || TRACE || || |
25 | 25 | || 1 || DEBUG || || |