Changes between Initial Version and Version 1 of Old/NodeHandler/TrackingBaseline


Ignore:
Timestamp:
Sep 29, 2005, 5:15:54 PM (19 years ago)
Author:
zhibinwu
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Old/NodeHandler/TrackingBaseline

    v1 v1  
     1
     2= Tracking information about baseline images for ORBIT nodes =
     3
     4== Tag: baseline-1.0.0 Image name: baseline-1.0.0.ndz ==
     5
     6||Package||Version||Comments||
     7||node-agent||1.0.1||Added RTS, Rate control support ||
     8||||||Added gateway functionality* (see comment below)||
     9||ipw2200||1.0.0||Installed from source - no debian||
     10||madwifi||0.9.6||Installed from source - no debian||
     11||oml-client||2.0.0||No changes||
     12||otg||1.1.1||No changes||
     13||iperf||2.0.2-1||No changes||
     14
     15== Other features ==
     16
     171) Uses gcc 3.3
     18
     192) Tagged (Check /root/.orbit_image)
     20
     213) fscked before imaging
     22
     234) tune2fs done - so no more fsck will be done
     24
     255) Uses Linux 2.6.10
     26
     27For all the packages that have comments listed, all these additions should be rolled out as the next debian package for that application
     28
     29
     30=== Explanation for gateway functionality ===
     31{{{
     32when 'gateway'
     33              return "route del default dev eth1; route add default gw #{value}; route add 224.10.10.6 dev eth1"
     34}}}
     35
     36This is used by the OTF application (forwarder)
     37
     38Command 1) When using a forwarder (or static routing), the user may need to specify a default route to the next hop, to do this one has to disable the existing default route
     39
     40Command 2) Add default route to the next hop
     41
     42Command 3) With this setup, OML sends its multicast trafic on wrong default route. Hence, we have to add an entry in the table to handle multicast OML traffic