Page History

...

• Amity MA is unreliable so using it for a case study does not appear fruitful. Les is working with Amity to try and understand this unreliability (emails 10/6/2018), they say "There is an internet problem we are taking care of it and will get back soon".
• The Android version of the PingER MA,is described with  comments at  ePingER on Android Native - Amity project (this a proposal/description from Aayush Jain)

  • It describes a multipurpose, stand-alone device that can be widely distributed, something that we have brainstormed about for a long time. 

    • We agreed to request Amity to share the App and instructions with us; we will look at installing on a jailbroken Android phone at the San Francisco end and try it out.

    •  They are working on a paper. They sent a  1st draft they have sent to Bebo and Les that we responded to 10/6/2018, a 2nd draft was responded to 10/13/2018.

    • They will be attaching the android app for review after testing it again.

      • Topher  feels that the Android app (when completed and vetted by his team) could easily be installed as a default service on his rainforest monitors (certainly future ones, not devices already in place). Merging the service data that he already collects with that unique to PingER has the potential to lead to some interesting results.

    • Also August 16th and again September 3rd, then  October 6th and October 13th proposed a meeting between: Bebo, Umar and Les and the Amity folks.

    • The paper has an interesting suggestion for a way forward :- TOPIC to discuss
      • Firebase Application: The need for a proxy server can be completely eliminated by shifting to a cloud-based architecture for managing files. Instead of SLAC pulling in the generated txt files from MAs around the world, the MAs can themselves push these files to a centralized application server hosted on the cloud; which makes it easier for SLAC to access files as per their need.
        Considering the great degree of integration capabilities Google offers with its products, the flexibility arising from using the Google Cloud Platform would be pronounced. Google’s Firebase is a mobile and web application development platform that provides developers with a variety of tools and services to help develop high-quality apps, that can scale easily as per changing demands, and which delivers 99.99% uptime. The Firebase SDK allows mobile app developers to quickly add critical and reliable functionality to their applications in a short time. The recommended option here would be to leverage the Cloud Storage for Firebase that allows robust uploads and downloads onto the Google Cloud Storage buckets. Apart from the user authentication module that comes bundled with Firebase, developers can also declare file security parameters so as to allow only certain file types to be uploaded. Having all user uploaded files in one place will then enable SLAC to access and process files as and when needed. Server-side processing can be done on the Google Cloud Platform as well, thereby eliminating any need for SLAC to maintain its own physical infrastructure. This form of implementation can be highly beneficial in any kind of region of the world, also including remote places, like deep inside tropical rainforests, or places that have recently been hit by a natural calamity. As this implementation model is not dependent on any local measuring agent, the android mobile apps can directly deliver data to SLAC over any form on internet connection in minimal time with high reliability.

...

Many of the nodes have a single name and both an IPv4 and IPv6 address. Since the key of each record in NODEDETAILS is the name and a name can currently only have one IP address, where we already have the name in the database (with an IPv4 address) I have currently left the record as is. 

TOPIC to discuss:

We need to think about how to handle these hosts with both IPv4 and IPv6 addresses. I am leaning towards moving to the future and simply changing the IPv4 addresses to IPv6 addresses. In a few cases we few cases we may be able to find two hosts at a site, using an IPv4 address on one and an IPv6 on the other. This is the simplest solution. Doing this loses having a historical record of a target with both an IPv4 and IPv6 address. Umar and Les have some scripts that enable comparisons to be made between access to a host via its IPV4 and its IPv6 address without using the PingER data. An alternative would be to also have a pseudo name for such ambiguous hosts, another would be to modify the database schema. Both of the latter two would require changes to the code in several places.

Charnsak is looking at a host in Champasak University, Chan Parsa province in Laos as a potential site for a PingER MA. Charnsak just got approved to make contact with the Champasak University. He expects to set up the MA in the next 4-5 months (say towards end 2018). It also depends on the partner university, and there may be a lot of paperwork.

UNIMAS (No update 8/9/2018, no update 9/6/2018, no update 10/7/2018)

...

Next Meeting

...