Detector Offsets and flags [gitlab]

[jmwample]

The detector program assumes that the zbalance_ipc channels will be 0-n for the n cores that it will run on. This is not always true (e.g. when we run tapdance and conjure on the same station).

Right now the -o optarg provides a uint8_t to specify the core affinity offset. However, the zbalance_ipc channels are assumed to start at 0. The tun mapping (tun that each PerCoreGlobal thread connects to) is assumed to be the same number as the zbalance_ipc channel because they have to be unique numerically. This is fine, but you have to be aware of this and know what offsets you will be using when setting up the tun environment.

• [x] Add option for zbalance_ipc channel offset
• [x] add an option for tun mapping offset

original submission: 12/17/2019

[jmwample]

Completed effectively by !18 (f4e7e8fc)

Left tun numbering associated with zbalance_ipc channel numbers.

The tun numbers can be automatically stood up using on-reboot.sh from !18

option is -z [NUM]

original comment: 12/19/2019

[jmwample]

• [ ] Document this in the Readme.md and the wiki.

This is also used in tapdance standup so it would be nice to have this for reference in our documentation.