Changes between Version 38 and Version 39 of Tutorials/oMF/tut1


Ignore:
Timestamp:
12/03/16 08:57:46 (13 months ago)
Author:
wontoniii
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Tutorials/oMF/tut1

    v38 v39  
    298298====== Configure MF components to use appropriate VLANs ====== 
    299299 
    300 The assumption is that the routers will be using VLAN 1XX1, and clients VLANs 1XX2 and 1XX3. 
    301 Edit file '''/usr/local/src/mobilityfirst/eval/orbit/tutorial/conf/hoststack2.conf''' on all four nodes to assign appropriate VLANs based on the instructions from the script.  
     300The assumption is that the routers will be using VLAN 1XX2, and clients VLANs 1XX1 and 1XX3. 
     301Edit file '''/usr/local/src/mobilityfirst/eval/orbit/tutorial/conf/hoststack1.conf''' on client 101 and '''/usr/local/src/mobilityfirst/eval/orbit/tutorial/conf/hoststack2.conf''' on client 102. For example, for the case of group 01 the two files should look like this: 
     302 
     303{{{ 
     304# node that it runs on. The stack would use this as a source GUID for  
     305# any messages sent by applications that do not specify their own, and  
     306# also when the communication originates from within the stack (e.g.,  
     307# from transport modules or for error messages). For now, it is a 
     308# 32-bit positive integer. 
     309# Example: 
     310# DEFAULT_GUID=234323 
     311# 
     312# Required. 
     313DEFAULT_GUID = 101 
     314 
     315# Define one or more interfaces to be used for network communication. 
     316# These are either a 3-tuple 'auto' or a 5-tuple 'manual' or a 5-tuple 'active' 
     317# configuration: 
     318# INTERFACE=<type>,<name>,auto,<headers_used> 
     319# INTERFACE=<type>,<name>,manual,<headers_used>,<access_router_ip_addr>,<access_router_mac_addr> 
     320# INTERFACE=<type>,<name>,active,<headers_used>,<access_router_ip_addr>,<getay_mac_addr> 
     321# where  
     322#  type is one of 'wifi', 'wimax', or 'ether' ('lte' will be supported in the future) 
     323#  name is the system name of interface, e.g., wlan0 or eth0 
     324#  headers_used is the level of overlay employed by the stack, e.g. ethernet only, 
     325#    ethernet+ip, ethernet+ip+udp or use of standard sockets. Valid values are: 
     326#    'ethernet', 'ip', 'upd', 'udp_socket' 
     327#  'auto', 'manual' and 'active' keywords distinguish whether network attachment 
     328#    (i.e., first hop router, another host in p2p mode, or first hop router traversing another network)  
     329#    is dynamically chosen by stack based on advertisements or is statically fixed for  
     330#    the interface. 
     331#  ip_addr is the IP4 address of first hop in fixed attachment 
     332#  mac_addr is the MAC address of first hop in fixed attachment 
     333# Examples:  
     334# INTERFACE=wifi,wlan0,auto 
     335# INTERFACE=wimax,wmx0,manual,192.168.1.1,11:22:33:44:55:66 
     336#  
     337# Must specify at least one 
     338INTERFACE = eth0.1011,ether,ip,auto 
     339}}} 
     340 
     341{{{ 
     342# node that it runs on. The stack would use this as a source GUID for  
     343# any messages sent by applications that do not specify their own, and  
     344# also when the communication originates from within the stack (e.g.,  
     345# from transport modules or for error messages). For now, it is a 
     346# 32-bit positive integer. 
     347# Example: 
     348# DEFAULT_GUID=234323 
     349# 
     350# Required. 
     351DEFAULT_GUID = 102 
     352 
     353# Define one or more interfaces to be used for network communication. 
     354# These are either a 3-tuple 'auto' or a 5-tuple 'manual' or a 5-tuple 'active' 
     355# configuration: 
     356# INTERFACE=<type>,<name>,auto,<headers_used> 
     357# INTERFACE=<type>,<name>,manual,<headers_used>,<access_router_ip_addr>,<access_router_mac_addr> 
     358# INTERFACE=<type>,<name>,active,<headers_used>,<access_router_ip_addr>,<getay_mac_addr> 
     359# where  
     360#  type is one of 'wifi', 'wimax', or 'ether' ('lte' will be supported in the future) 
     361#  name is the system name of interface, e.g., wlan0 or eth0 
     362#  headers_used is the level of overlay employed by the stack, e.g. ethernet only, 
     363#    ethernet+ip, ethernet+ip+udp or use of standard sockets. Valid values are: 
     364#    'ethernet', 'ip', 'upd', 'udp_socket' 
     365#  'auto', 'manual' and 'active' keywords distinguish whether network attachment 
     366#    (i.e., first hop router, another host in p2p mode, or first hop router traversing another network)  
     367#    is dynamically chosen by stack based on advertisements or is statically fixed for  
     368#    the interface. 
     369#  ip_addr is the IP4 address of first hop in fixed attachment 
     370#  mac_addr is the MAC address of first hop in fixed attachment 
     371# Examples:  
     372# INTERFACE=wifi,wlan0,auto 
     373# INTERFACE=wimax,wmx0,manual,192.168.1.1,11:22:33:44:55:66 
     374#  
     375# Must specify at least one 
     376INTERFACE = eth0.1013,ether,ip,auto 
     377}}} 
    302378 
    303379===== Executing the script =====