User Tools

Site Tools


bestpractice:prototype-experiments

Prototype Experiments

WARNING: The experiments described here need CNS support for debian7-based sliver-system templates which is currently not supported by most deployed nodes. For reproducing use VCT with a recent revision from testing branch.

This page describes reference experiments that can be used as illustration for creating and executing experiments and to adapt for creating new experiments.

Experiment templates can be found here: http://redmine.confine-project.eu/projects/confine/repository/revisions/testing/show/utils/vct/experiments

Exploited Facilities

Sliver interfaces

CONFINE offers different kind of interfaces for executing experiments. These interfaces can be defined via the controller when creating a sliver. The following interface types are used in the experiments here:

  • Private interface can be used to communicate with the RD itself (eg interact with the restAPI) and to interact with the community network via a source network address translated (NAT) connection. In most CNs it is also possible to reach the global internet (although often via double NAT) using private interfaces. Private interfaces are used in experiment Http internet-download speedtest (using private interfaces) for measuring download performance from a given CONFINE url.
  • Management interface (and network) can be used to interact between slivers and other hosts connected to the management network (eg RDs, controller). The most common use case is to ssh into a sliver for controlling experiments or accessing experiment data. Management addresses are used in all experiments for downloading experiment data.
  • Public interface provide a sliver with a CN-public IP (usually in the private address range of 10.0.0.0/8). Thus, allowing communication with other CN-hosts and slivers without any NAT involved. In some CNs, the provided IP may even be a global one. Public Interfaces and addresses are used in Measuring connectivity and RTT between slivers (using public interfaces) for measuring RTT between slivers.
  • Isolated interfaces provide researchers an Layer-3-isolated access to specific interfaces (parent interfaces) and allow them to do any kind of Layer3 and above experiments. The main requirement for efficient usage of these interfaces is the physical connectivity of parent interfaces between neighboring slivers. Isolated interfaces are used in experiment BMX6 routing protocol experiment (using isolated interfaces) for executing a routing protocol experiment.

Sliver/Slice system templates

System templates define the operating system of a sliver by providing template images (a tgz of common linux distributions tailored for Confine slivers) and can be selected as a default for all Slivers when configuring the Slice or given explicitly for each Sliver. Confine currently offers debian6, debian7, and openWrt based template images. The experiments described here are tested using debian7-based template images. Recent node images are needed to fully support debian7-based templates.

When testing with VCT, such nodes (RDs) can be created using this node-base image: http://media.confine-project.eu/vct/vct-node-base-image-build.img.gz

Debian-7 based templates can be created using this template image: http://media.confine-project.eu/vct/vct-sliver-template-build-debian.tgz

Sliver/Slice system overlay

A system overlay allows a researcher to customize the base OS image provided via the system template. A system overlay comes as a tgz of the changes done to the original template image. One way for creating such overlay.tgz comes with VCT. Therefore, one first creates, deployes, and starts a slice and sliver using one of the provided template images. Then, ssh into the sliver and performing all desired changes (eg apt-get install package a b c). Finally, stopping the sliver via the controller (setting sliver state to 'DEPLOY'), ssh into the RD where the sliver is hosted and create the overlay.tgz with the command confine_sliver_dump_overlay, leave the sliver again and scp the created overlay from the RD to a local machine. The bash part of the whole procedure is illustrated in the following capture. A system overlay is used in experiment [] to predeploy the binaries of the tested routing protocol.

##################################################################################
# Assuming a STARTed sliver (named slice7) with management IP: fd65:fc41:c50f:3:1001::a
# and hosted in RD (called test1) 0003, with management IP: fd65:fc41:c50f:3:0:0:0:2

##################################################################################
# Ssh into the sliver from vct using the sliver management IP:
vct@vct:~$ ssh root@fd65:fc41:c50f:3:1001::a
Linux 00000000000a_0003 3.3.8 #43 Thu Nov 28 15:43:30 UTC 2013 i686
[...]
Last login: Fri Nov 29 05:20:22 2013 from fd65:fc41:c50f::2

##################################################################################
# Test internet connectivity from sliver:
root@00000000000a_0003:~# ping -n -c1 confine-project.eu
PING confine-project.eu (77.246.179.81) 56(84) bytes of data.
64 bytes from 77.246.179.81: icmp_req=1 ttl=53 time=78.5 ms
--- confine-project.eu ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 78.537/78.537/78.537/0.000 ms

##################################################################################
# Install desired package:
root@00000000000a_0003:~# apt-get update
[...]
root@00000000000a_0003:~# apt-get install mtr
The following NEW packages will be installed:
  mtr 
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 56.8 kB of archives. After unpacking 142 kB will be used.
Get: 1 http://ftp.debian.org/debian/ wheezy/main mtr i386 0.82-3 [56.8 kB]
Fetched 56.8 kB in 0s (265 kB/s)
[...]
Setting up mtr (0.82-3) ...

##################################################################################
# Test new functionality:               
root@00000000000a_0003:~# mtr --raw -n -c1 confine-project.eu
h 0 10.241.0.254
p 0 193
[...]
h 14 77.246.179.81
p 14 84414
h 15 77.246.179.81
p 15 71897

##################################################################################
# Leave the sliver:
root@00000000000a_0003:~# exit
logout
Connection to fd65:fc41:c50f:3:1001::a closed.
vct@vct:~$ 

##################################################################################
# Ssh into the RD hosting the sliver (using vct_node_ssh RDID or ssh and RD management IP):
vct@vct:~$ ssh root@fd65:fc41:c50f:3:0:0:0:2 # alternatively vct_node_ssh 0003
[...]
 -----------------------------------------------------
                confine-project.eu
Version: http://redmine.confine-project.eu/projects/confine/repository/show?branch=testing&rev=576cd0f
----------------------------------------------------

root@rd0003:~# confine_info 
CONFINE node-id=0x0003 node-state=started daemon-pid=3207
slice-id         lxc pid   state      name                           
----------------------------------------------------------
0x00000000000b   01  21618 started    'slice6'                       
0x00000000000a   02  14475 started    'slice7' 

##################################################################################
# Now stop the sliver by setting it to DEPLOY state via the controller:
# and wait till the sliver was stopped (state is deployed)

root@rd0003:~# confine_info 
CONFINE node-id=0x0003 node-state=started daemon-pid=3207
slice-id         lxc pid   state      name                           
----------------------------------------------------------
0x00000000000b   01  21618 started    'slice6'                       
0x00000000000a   02  -1    deployed   'slice7'                       

##################################################################################
# Now create the overlay.tgz:
root@rd0003:~# confine_sliver_dump_overlay 00000000000a
./
./usr/
./usr/bin/
./usr/bin/mtr
./usr/share/
./usr/share/man/
./usr/share/man/man8/
./usr/share/man/man8/mtr.8.gz
[...]
overlay of sliver=00000000000a dumped to /root/overlay-dump.tgz
overlay can be downloaded with: vct_node_scp 0003 remote://root/overlay-dump.tgz /var/lib/vct/downloads/

##################################################################################
# And leave the RD:
root@rd0003:~# exit
Connection to fd65:fc41:c50f:3:0:0:0:2 closed.

##################################################################################
# Download the just created overlay from the RD:
vct@vct:~$ vct_node_scp 0003 remote://root/overlay-dump.tgz /var/lib/vct/downloads/
vct_node_get_mac connecting to virtual node=0003 mac=52:54:00:00:00:03
overlay-dump.tgz                                    100%   19MB  18.5MB/s   00:01    
vct@vct:~$

##################################################################################
# The created overlay can now be uploaded to the controller for customizing 
# later slice and sliver deployments

Sliver data archive

Sliver data archives provide an alternative (more lightweight than overlays) way for customizing sliver deployments and defining experiments. They are typically used to deploy the init scripts of an experiments. The directory structure of an sliver data archieve matches the directory structure of the template rootfs. The easiest way to automatically start an experiment using debian-based template images is to customize the file: /etc/rc.local which got executed as soon as the sliver boot procedure has finished. A number of example directory structures for different experiments can be found here (one experiment per sub-directoy): http://redmine.confine-project.eu/projects/confine/repository/revisions/master/show/utils/vct/experiments/debian The experiments are explained in more detail in the following Section.

Once having added a new experiment sub-directory with needed init scripts and other experiment data, the needed archieve file (in .tgz format) can be created manually or using the vct command: vct_build_sliver_data as shown in the following example. Sliver data archives are used in all later experiments for deploying experiment init scripts and additional functionality as needed.

vct@vct:~/confine-dist/utils/vct$ vct_build_sliver_data experiments/debian/speedtest-confine-private-ifs/
./
./etc/
./etc/rc.local

The slice/sliver exp-data archive is available via the controller portal at:
slices->[select slice]->exp_data as:
vct-exp-data-build-speedtest-confine-private-ifs.tgz

vct@vct:~/confine-dist/utils/vct$ ls -l /var/lib/vct/downloads/vct-exp-data-build-speedtest-confine-private-ifs.tgz 
-rw-r--r-- 1 vct vct 645 Nov 29 08:33 /var/lib/vct/downloads/vct-exp-data-build-speedtest-confine-private-ifs.tgz

vct@vct:~/confine-dist/utils/vct$

Debian7 (wheezy) Experiments

Http internet-download speedtest (using private interfaces)

This experiment executes in each started sliver a download of 3MB of data from an internet server using the natted internet access provided via private sliver interfaces.

Detailed steps for reproducing the experiment:

  1. Create the directory with your experiment-name inside the vct directory, eg: utils/vct/experiments/debian/speedtest-confine-private-ifs
  2. Create the subdirectory etc and the file etc/rc.local with the same content as shown here: http://redmine.confine-project.eu/projects/confine/repository/revisions/master/entry/utils/vct/experiments/debian/speedtest-confine-private-ifs/etc/rc.local . The instructions include:
    1. Sleeping for EXP_DELAY=20 seconds to slightly delay the experiment execution.
    2. Starting 'time' command to capture the complete execution time
    3. Setting disk usage limit for the following process to automatically stop the download after retrieval of DL_SIZE=3000000 bytes.
    4. Start recursive download using 'wget' command to DL_URL=“http://media.confine-project.eu/misc/” and saving downloaded data to DL_DST=/tmp/test
    5. List size of DL_DST=/tmp/test
    6. Log all command stdout and stderr messages to EXP_RESULTS=/root/experiment.data for later evaluation
  3. Make the file etc/rc.local executable (eg: chmod u+x etc/rc.local)
  4. Create the sliver data archive as descibed above Sliver data archive with vct_build_sliver_data. Alternatively, a precreated tgz can be downloaded here: http://media.confine-project.eu/vct/vct-exp-data-build-speedtest-confine-private-ifs.tgz
  5. Create and save a Slice:
    1. Template: debian7
    2. Set State: START
    3. Advanced (show):
      1. Sliver data: upload vct-exp-data-build-speedtest-confine-private-ifs.tgz
  6. Create and save at least one Sliver for the previous created Slice. Each sliver needs a private interface and a management interface (both default).
  7. The Sliver should now be visible via the controller with set state: START
  8. Obtain the sliver management IP via the controller (eg fd65:fc41:c50f:3:1001::a)
  9. Wait (reload) until the controller reports the Sliver state as: STARTED (this can take a few minutes)
  10. Wait some more seconds to let the experiment finish
  11. Download/access the EXP_RESULTS=/root/experiment.data file from the slivers (using the sliver management IP) for later post processing. This is shown in the following capture:
     
    vct@vct:~$ ssh root@fd65:fc41:c50f:3:1001::a tail -f /root/experiment.data
      2600K .......... .......... .......... .......... ..........  7%  417K 19s
      2650K .......... .......... .......... .......... ..........  7% 9.77M 19s
      2700K .......... .......... .......... .......... ..........  8% 9.77M 18s
      2750K .......... .......... .......... .......... ..........  8% 9.77M 18s
      2800K .......... .......... .......... .......... ..File size limit exceeded
    
    real    0m2.700s
    user    0m0.010s
    sys     0m0.140s
    -rw-r--r-- 1 root root 2999808 Nov 29 10:40 /tmp/test
    ^Cvct@vct:~$ 

Measuring connectivity and RTT between slivers (using public interfaces)

This experiment executes in each started sliver a ping process sending icmp requests to all other slivers of the slice with a public interface and logs the gathered RTT.

Detailed steps for reproducing the experiment:

  1. Create the directory with your experiment-name inside the vct directory, eg: utils/vct/experiments/debian/ping-all-slivers-public4-ifs/
  2. Create the subdirectory root with the files:
    1. JSON.sh, a set of bash functions to browse json data, available from here: https://github.com/dominictarr/JSON.sh/blob/master/JSON.sh
    2. confine-exp.sh, the actual script controlling this experiment, with this content: http://redmine.confine-project.eu/projects/confine/repository/revisions/master/entry/utils/vct/experiments/debian/ping-all-slivers-public4-ifs/root/confine-exp.sh . The instructions include:
      1. The functions get_json_value, get_json_members, get_json_url_value, get_json_url_members to obtain desired information from a json object
      2. The function experiment which implements the experiment by iteratively parsing the controller, node, and sliver RestAPI in order to obtain the public IP addresses of other slivers.
      3. the final while-true loop calling the experiment function every 10 seconds
      4. The result of each ping probe is appended to the file EXP_RESULTS=/root/experiment.data for later retrieval and offline analysis
  3. Create the subdirectory etc and the file etc/rc.local with the same content as shown here: http://redmine.confine-project.eu/projects/confine/repository/revisions/master/entry/utils/vct/experiments/debian/ping-all-slivers-public4-ifs/etc/rc.local . The instructions only include:
    1. Calling /root/confine-exp.sh as a background process
  4. Make the file etc/rc.local, root/confine-exp.sh and root/JSON.sh executable (eg: chmod u+x etc/rc.local)
  5. Create the sliver data archive as descibed above Sliver data archive with vct_build_sliver_data. Alternatively, a precreated tgz can be downloaded here: http://media.confine-project.eu/vct/vct-exp-data-build-ping-all-slivers-public4-ifs.tgz
  6. Create and save a Slice:
    1. Template: debian7
    2. Set State: START
    3. Advanced (show):
      1. Sliver data: upload vct-exp-data-build-ping-all-slivers-public4-ifs.tgz
  7. Create and save at least two slivers for the previous created Slice. Each sliver needs a public interface and a management interface.
  8. The Slivers should now be visible via the controller with set state: START
  9. Obtain the sliver management IP via the controller (eg fd65:fc41:c50f:3:1002::a)
  10. Wait (reload) until the controller reports the Sliver states as: STARTED (this can take a few minutes)
  11. Wait some more seconds to let the experiment get started
  12. Download/access the EXP_RESULTS=/root/experiment.data file from the slivers (using the sliver management IP) for later post processing. This is shown in the following capture:
    vct@vct:~$ ssh root@fd65:fc41:c50f:3:1002::a cat /root/experiment.data
    The authenticity of host 'fd65:fc41:c50f:3:1002::a (fd65:fc41:c50f:3:1002::a)' can't be established.
    ECDSA key fingerprint is 33:de:c4:4f:e3:bb:15:e9:4f:3d:0f:94:ae:29:c5:a2.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added 'fd65:fc41:c50f:3:1002::a' (ECDSA) to the list of known hosts.
    new cycle Fri Nov 29 15:43:35 UTC 2013
    PING 10.241.0.93 (10.241.0.93) 56(84) bytes of data.
    64 bytes from 10.241.0.93: icmp_req=1 ttl=64 time=0.398 ms
    --- 10.241.0.93 ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 0.398/0.398/0.398/0.000 ms
    
    PING 10.241.0.17 (10.241.0.17) 56(84) bytes of data.
    64 bytes from 10.241.0.17: icmp_req=1 ttl=64 time=0.359 ms
    --- 10.241.0.17 ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 0.359/0.359/0.359/0.000 ms
    
    PING 10.241.0.31 (10.241.0.31) 56(84) bytes of data.
    64 bytes from 10.241.0.31: icmp_req=1 ttl=64 time=0.014 ms
    --- 10.241.0.31 ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 0.014/0.014/0.014/0.000 ms
    
    new cycle Fri Nov 29 15:44:51 UTC 2013
    
    PING 10.241.0.93 (10.241.0.93) 56(84) bytes of data.
    64 bytes from 10.241.0.93: icmp_req=1 ttl=64 time=0.472 ms
    --- 10.241.0.93 ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 0.472/0.472/0.472/0.000 ms
    [...]

BMX6 routing protocol experiment (using isolated interfaces)

This procedure is slightly obsolete: currently the sliver data feature provides overlay functionality, i.e. a sliver data archive actually acts as an overlay.

This experiment executes in each started sliver a bmx6 routing-protocol daemon instance using up-to 4 isolated interfaces for meshing with neighboring slivers (slivers of the same slice and having a physical link between parent interfaces of defined isolated sliver interfaces)

Detailed steps for reproducing the experiment:

  1. Create the directory with your experiment-name inside the vct directory, eg: utils/vct/experiments/debian/mesh-slivers-isolated-ifs
  2. Create the subdirectory etc and the file etc/rc.local with the same content as shown here: http://redmine.confine-project.eu/projects/confine/repository/revisions/master/entry/utils/vct/experiments/debian/mesh-slivers-isolated-ifs/etc/rc.local . The instructions include:
    1. Executing the predeployed (via overlay) bmx6 binary configured for meshing on isolated interfaces iso0, iso1, iso2, iso3, and iso4. If any of the interfaces does not exist it will be ignored by the daemon and address autoconfiguration of bmx6 makes the setup particularly easy.
    2. Execute a second bmx6 daemon in client and loop mode to periodically connect to the first one for accessing status information about the daemon itself, interfaces, links, other bmx6 nodes (originators), tunnels, and detailed descriptions of other nodes (as published by the bmx6 daemon running on other slivers)
    3. Log all accessed status information to file: EXP_RESULTS=/root/experiment.data
    4. Killall bmx6 processes after EXP_DURATION=3600 seconds
  3. Make the file etc/rc.local executable (eg: chmod u+x etc/rc.local)
  4. Create the sliver data archive as descibed above Sliver data archive with vct_build_sliver_data. Alternatively, a precreated tgz can be downloaded here: http://media.confine-project.eu/vct/vct-exp-data-build-mesh-slivers-isolated-ifs.tgz
  5. Build an overlay as described in Sliver/Slice system overlay that contains the bmx6 binary. Alternatively, a pre packaged overlay.tgz can be downloaded here: http://media.confine-project.eu/vct/vct-overlay-build-mesh-slivers-isolated-ifs.tgz . Specific steps to compile and install the bmx6 binary before dumping them into an overlay.tgz include:
    1. '$ apt-get install git-core build-essential'
    2. '$ cd bmx6; make; make install'
  6. Create and save a slice:
    1. Template: debian7
    2. Set State: START
    3. Advanced (show):
      1. Sliver data: upload vct-exp-data-build-mesh-slivers-isolated-ifs.tgz
      2. Overlay: upload vct-overlay-build-mesh-slivers-isolated-ifs.tgz
  7. Create and save at least two sliver for the previous created slice. Each sliver needs a management interface and at least one isolated interface called iso1 linked to an existing parent interface in the node hosting the sliver. Additional isolated interfaces may be called iso2, iso3, iso4.
  8. The slivers should now be visible via the controller with set state: START
  9. Obtain the sliver management IP via the controller (eg fd65:fc41:c50f:3:1002::a)
  10. Wait (reload) until the controller reports the sliver's state as: STARTED (this can take a few minutes)
  11. Wait some more seconds to let the experiment start…
  12. Download/access the EXP_RESULTS=/root/experiment.data file from the slivers (using the sliver management IP) for later post processing. This is shown in the following capture:
    vct@vct:~$ ssh root@fd65:fc41:c50f:3:1002::a cat /root/experiment.data
    status:
    version        compat revision globalId                               primaryIp                    tun6Address tun4Address myLocalId uptime     cpu nodes 
    BMX6-0.1-alpha 16     813b1c2  00000000000a_0003.EB9F2A047A99942EA43B fd66:66:66:2a:5254:ff:fe01:3 ---         ---         39010003  0:00:18:42 0.1 3    
    interfaces:
    devName state type     rateMin rateMax llocalIp                globalIp                        multicastIp primary 
    iso0    DOWN  INACTIVE INVALID INVALID /-1                     /-1                                         0       
    iso1    UP    ethernet 1000M   1000M   fe80::5054:ff:fe01:3/64 fd66:66:66:2a:5254:ff:fe01:3/64 ff02::2     1       
    iso2    UP    ethernet 1000M   1000M   fe80::5054:ff:fe02:3/64 fd66:66:66:29:5254:ff:fe02:3/64 ff02::2     0       
    iso3    DOWN  INACTIVE INVALID INVALID /-1                     /-1                                         0       
    iso4    DOWN  INACTIVE INVALID INVALID /-1                     /-1                                         0       
    links:
    globalId                               llocalIp             viaDev rxRate txRate bestTxLink routes wantsOgms nbLocalId 
    00000000000a_0007.03AAAF54C5A57942E799 fe80::5054:ff:fe01:7 iso1   100    100    1          1      1         28010007  
    00000000000a_0007.03AAAF54C5A57942E799 fe80::5054:ff:fe02:7 iso2   100    100    0          0      0         28010007  
    00000000000a_0008.0366D61BBCFD4F8C8180 fe80::5054:ff:fe01:8 iso1   100    100    1          1      1         2C010008  
    00000000000a_0008.0366D61BBCFD4F8C8180 fe80::5054:ff:fe02:8 iso2   100    100    0          0      0         2C010008  
    originators:
    globalId                               blocked primaryIp                    routes viaIp                viaDev metric myIid4x descSqn ogmSqn ogmSqnDiff lastDesc lastRef 
    00000000000a_0003.EB9F2A047A99942EA43B 0       fd66:66:66:2a:5254:ff:fe01:3 0      ::                   ---    128G   2       33257   11221  0          1121     0      
    00000000000a_0007.03AAAF54C5A57942E799 0       fd66:66:66:22:5254:ff:fe01:7 1      fe80::5054:ff:fe01:7 iso1   999M   3       21487   63872  0          1100     0      
    00000000000a_0008.0366D61BBCFD4F8C8180 0       fd66:66:66:22:5254:ff:fe01:8 1      fe80::5054:ff:fe01:8 iso1   999M   4       4024    7849   0          1093     0      
    
    descSha=D1C2865B9197A297625D9E3F7815FA20AE91304E blocked=0 size=126 :
     DESC_ADV:
        transmitterIid4x=2 globalId=00000000000a_0003.EB9F2A047A99942EA43B revision=813B capabilities=0 descSqn=33257 ogmSqnMin=10998 ogmSqnRange=4101 txInterval=500 reservedTtl=50 reserved=0 extensionLen=56 extensionData=C01200010000001000006500050101000001C2268000FD6600660066002A525400FFFE0100038000FD66006600660029525400FFFE020003
     METRIC_EXTENSION: 
        fmetric_u16_min=1 reserved=0 metricAlgo=16 flags=0 txExpDivisor=64 txExpNumerator=128 rxExpDivisor=64 rxExpNumerator=64 reserved2=0 pathWindow=5 pathLounge=1 pathRegression=1 pathHysteresis=0 hopPenalty=0 latenessPenalty=1
     HNA6_EXTENSION: 
        prefixlen=128 reserved=0 address=fd66:66:66:2a:5254:ff:fe01:3
        prefixlen=128 reserved=0 address=fd66:66:66:29:5254:ff:fe02:3
    descSha=9D8D00AB3A632CC76C6C178AE15D1877C6815277 blocked=0 size=126 :
     DESC_ADV:
        transmitterIid4x=3 globalId=00000000000a_0007.03AAAF54C5A57942E799 revision=813B capabilities=0 descSqn=21487 ogmSqnMin=63653 ogmSqnRange=6317 txInterval=500 reservedTtl=50 reserved=0 extensionLen=56 extensionData=C01200010000001000006500050101000001C2268000FD66006600660022525400FFFE0100078000FD66006600660023525400FFFE020007
     METRIC_EXTENSION: 
        fmetric_u16_min=1 reserved=0 metricAlgo=16 flags=0 txExpDivisor=64 txExpNumerator=128 rxExpDivisor=64 rxExpNumerator=64 reserved2=0 pathWindow=5 pathLounge=1 pathRegression=1 pathHysteresis=0 hopPenalty=0 latenessPenalty=1
     HNA6_EXTENSION: 
        prefixlen=128 reserved=0 address=fd66:66:66:22:5254:ff:fe01:7
        prefixlen=128 reserved=0 address=fd66:66:66:23:5254:ff:fe02:7
    descSha=D9E1003E500763196726E41335CB25CC65688724 blocked=0 size=126 :
     DESC_ADV:
        transmitterIid4x=4 globalId=00000000000a_0008.0366D61BBCFD4F8C8180 revision=813B capabilities=0 descSqn=4024 ogmSqnMin=7631 ogmSqnRange=6740 txInterval=500 reservedTtl=50 reserved=0 extensionLen=56 extensionData=C01200010000001000006500050101000001C2268000FD66006600660022525400FFFE0100088000FD66006600660023525400FFFE020008
     METRIC_EXTENSION: 
        fmetric_u16_min=1 reserved=0 metricAlgo=16 flags=0 txExpDivisor=64 txExpNumerator=128 rxExpDivisor=64 rxExpNumerator=64 reserved2=0 pathWindow=5 pathLounge=1 pathRegression=1 pathHysteresis=0 hopPenalty=0 latenessPenalty=1
     HNA6_EXTENSION: 
        prefixlen=128 reserved=0 address=fd66:66:66:22:5254:ff:fe01:8
        prefixlen=128 reserved=0 address=fd66:66:66:23:5254:ff:fe02:8

OpenWrt Experiments

Hello World

bestpractice/prototype-experiments.txt · Last modified: 2015/03/05 17:50 by ivilata