...
Amity (Updated 5/28/2018)
- Their PingER MA is up and running and we are successfully gathering some data.
- However, there is a problem with not being able to find data in the requested time window.
- There is also a problem with a missing beacons.txt. Les is working with Amity, emails We are unable to gather data from the Amity MA, or even ping it, emails sent May 28th and June 3rd, 2018, June 30th, no responses.
- Need to load the most recent version of gathering application (ping_data.pl) to assist in diagnosing problem.
- It has been loaded
- However, now I cannot gather data or diagnose problems since there is no access to pingeramity.in/cgi-bin/ping_data.pl.
- Check if Amity can upload beacons.txt table from SLAC. They say they can.
- The Android version of the PingER MA
- email sent June 5th and again June 30th:
- Now that you have support for regularly updating the Beacons, one of the next things is to think about is how to get the data to the repository/archive (SLAC).A possibility is outlined in https://confluence.slac.stanford.edu/display/IEPM/Proxy+support+for+PingER. Perhaps your team might be interested in pursuing step 1. If necessary we could also think about providing an account at SLAC to enable a student to work on step 2.
- email sent June 5th and again June 30th:
...
UNIMAS (No update 3/8/2018, 5/3/2018)
- The web page at http://pinger.unimas.my/pinger/contact.php was not accessibe also the web page on joining was not accessible, http://pinger.unimas.my/pinger/join.php.
- It was a faulty network card which was replaced. It was an old machine (10 years old) and finding compatible network card was a bit of a problem
UAF/GHZU (Updated 5/5/2018))
Saqib submitted the Camera ready paper on “A Blockchain-based Decentralized Data Storage and Access Framework for PingER” and it has been accepted in Trustcom2018.
Two previously accepted papers are now online on the following links.
UAF/GHZU (Updated 5/5/2018))
Saqib submitted the Camera ready paper on “A Blockchain-based Decentralized Data Storage and Access Framework for PingER” and it has been accepted in Trustcom2018.
Two previously accepted papers are now online on the following links.
- The paper titled “Detecting Anomalies from End-to-end Internet Performance Measurements ( PingER ) using Cluster-Based Local Outlier Factor” is online on IEEE portal. https://ieeexplore.ieee.org/document/8367380/ . This paper is not available in SLAC repository. Les will follow up.
- The paper titled “Internet Performance Analysis of South Asian Countries using End-to-End Internet Performance Measurements” The paper titled “Detecting Anomalies from End-to-end Internet Performance Measurements ( PingER ) using Cluster-Based Local Outlier Factor” is online on IEEE portal. https://ieeexplore.ieee.org/document/83673808367431/ . This paper is not available in SLAC repository . Les will follow up. The paper titled “Internet Performance Analysis of South Asian Countries using End-to-End Internet Performance Measurements” is online on IEEE portal. https://ieeexplore.ieee.org/document/8367431/ . This paper is available in SLAC repository (http://www.slac.(http://www.slac.stanford.edu/pubs/slacpubs/17000/slac-pub-17205.pdf). However, without doi no and other necessary details. Les will follow up.
...
- See Towards Analysis of ICMP vs TCP Ping Latencies - Umar
- Looked into Traffic Differentiation - Rate Limiting vs. Traffic Prioritization (QoS)
- Conclusions:
- Min RTT essentially reflects fixed delay, while average RTT subsumes variations and path load
- TCP Segment drops manifest as large increases in delay
- QoS can be implemented in at least two ways:
- When priorities are implemented, ICMP packets will only be dropped if ICMP quota is full and link is congested, otherwise ICMP traffic is allowed to go beyond quota
- When rate-limits are implemented, ICMP packets will be dropped when ICMP quota is met, even if links are not congested
- Path loads dictate latency estimates: With weighted QoS implementations, loaded links depress ICMP
- Found relevant papers and technical reports. The intent here is to understand the components of latency to help with the evaluation.
Y. Zhang, N. Duffield, V. Paxson, S. Shenker, On the Constancy of Internet Path Properties, in ACM SIGCOMM Internet Measurement Workshop 2001
A. Acharya, J. Saltz, A Study of Internet Round-Trip Delay, Univ of Maryland, Tech Rep. CS-TR-3736
M. Allman, V. Paxson, On Estimating End-to-End Network Path Properties, in ACM SIGCOMM 1999
V. Paxson, G. Almes, J. Mathis, Framework for IP Performance Metrics
- Setup NeuBot and experimented with tests but wasn't able to find useful examples of traffic differentiation (see https://www.measurementlab.net/tests/)
- Skimmed Glasnost to understand traffic shaping (see http://broadband.mpi-sws.org/transparency/glasnost.php and https://github.com/marcelscode/glasnost)
- [Not Relevant] Miscellaneous notes on ICMP Traceroutes, MPLS tunneling & ICMP (see http://cluepon.net/ras/traceroute.pdf), Measuring Performance
- Conclusions:
IPv6 results gathered using ping-vs-tcp.pl script. About 56 nodes with IPv6 addresses, 14 of which responded with Npings
- IPv4 results gathered from SLAC and Virginia Tech
- SLAC's batch may be downloaded here (approx. 24 MB)
- Skimmed results; findings are pretty much the same as before
- Looked into Traffic Differentiation - Rate Limiting vs. Traffic Prioritization (QoS)
- Pending
- Identified relevant events in the network stack that highlight timing (_RECVFROM, _RECVMSG, _IP_RECV, _NETIF_RX etc.). Looking for instrumentation that enables us to measure timestamps. We also need to figure out how to determine whether ICMP & TCP traffic are treated differently? and then how to measure the difference?
- perf-tools allows us to measure transport events
- If we could assume that the path for ICMP & TCP through the network is the same, then the only difference between two (controlled) tests would be the time spent in the transport layers. This can be measured using perftools.
- However, such measurements must be made in a controlled environment where ICMP and TCP are treated the same. (I say so because some results — e.g., in East Asia and South Asia — clearly show that ICMP performs much worse than TCP.)
- We would also need to cater for cross traffic and queuing delays. Given how small the differences are, one may argue that the variations in measurements are due to cross traffic. Perhaps we should start with controlled tests and then see if real world measurements reflect similar behavior.
- We need to setup a test environment. We can either setup a bare-metal box or use a VM.
- I will see if I can arrange for a bare-metal box.
- Identified relevant events in the network stack that highlight timing (_RECVFROM, _RECVMSG, _IP_RECV, _NETIF_RX etc.). Looking for instrumentation that enables us to measure timestamps. We also need to figure out how to determine whether ICMP & TCP traffic are treated differently? and then how to measure the difference?
PingER IPV6 support
- Les added an item to the pingtable.pl form to enable the ability to select IPv4 or IPv6 measurements or both.
Meeting with Amazon Web Services
- for cross traffic and queuing delays. Given how small the differences are, one may argue that the variations in measurements are due to cross traffic. Perhaps we should start with controlled tests and then see if real world measurements reflect similar behavior.
- We need to setup a test environment. We can either setup a bare-metal box or use a VM.
- I will see if I can arrange for a bare-metal box.
PingER IPV6 support
- PingER now seems to be fully IPv6 capable and stable, the logs have been improved to make it easier to debug problems.Dr Ali Khayam (ex NUST) is now at Amazon. He has a colleague at Amazon (Awais Nemet) who heads the External Network Services group for AWS. Awais is kicking off many projects in the Internet monitoring space and Ali recommended that Awais talks to Les to learn about the experiences of operating Pinger and leveraging the data that Pinger generated. Les updated the PingER front page at http://www-iepm.slac.stanford.edu/pinger/) so he could walk Awais through PingER.
Host | State | last seen | Status |
---|---|---|---|
pingersonar-um.myren.net.my | No response | 6/26/2018 | Pings |
pinger-ncp.ncp.edu.pk | pinger-ncp.ncp.edu.pk down | Nov 29, 2017 | |
121.56.146.180 (pinger.kohat.edu.pk) | Down | Nov 22nd, 2017 | |
cae.seecs.edu.pk | Down | Feb 27, 2018 | |
pinger.isra.edu.pk | Down | March 6, 2018 | |
pingeramity.in | It is partially working. Now working on missing beacons.txt file and missing data (i.e data disappears a few hours after it is measured and saved at MA). Also it is unable to access http://www-iepm.slac.stanford.edu/pinger/beacons.txt | April 27, 2018 |
...