Separate OONI management and test traffic onto different network interfaces
At 2014-01-28 17:19:21 Richard King wrote: As an administrator of OONI probes I want to perform management and configuration tasks over a network connection different to that under test for censorship so that I can manage a probe connected to a network I don't control even if its IP address is allocated dynamically.
This is similar to issue #269 (moved)
I'm involved with a project to monitor web censorship across domestic ISPs in the UK [1]. Our infrastructure plans include running multiple OONI probes in virtual machines on a single server. We are subscribing to a number of domestic ISPs and routing each connection to a VM using some network-level magic (I believe).
It would simplify our setup if we could manage and configure OONI probes via a different connection to that being tested. We would make sure this connection was unfiltered and had a static IP address (since ISP lines usually have dynamic addresses we would currently have to use dynamic DNS or similar to prevent being cut off).
The suggestion to raise this issue came out of an IRC discussion with our project team, which is logged on our wiki [2]. The discussion assumed network access to the OONI probe is needed in order to manage it and that this might be hampered by the nature of the domestic ISP lines to which we're subscribing.
I don't think we're sufficiently familiar with OONI's architecture yet to tell whether this feature request is sensible. I suspect management may occur over TOR anyway, in which case, this might not be needed. If we've misunderstood something and this request makes no sense please feel free to reject it and please accept my apologies.
[1] https://wiki.openrightsgroup.org/wiki/ORG_Censorship_Monitoring_Project [2] https://wiki.openrightsgroup.org/wiki/ORG-tech-vols_IRC_meeting_log_2014_01_22
This issue was automatically migrated from github issue https://github.com/TheTorProject/ooni-probe/issues/270