parseword

[root@host /tmp]# portmaster -Kvw glib-2.50.2_5,1

[...snip many lines of compile and install output...]

====> Compressing man pages (compress-man)

===>>> Creating a backup package for old version glib-2.50.2_5,1
Creating package for glib-2.50.2_5,1
Updating database digests format: 100%
Checking integrity... done (0 conflicting)

parseword

If you get errors like this when trying to compile pthreads for PHP 7.2, see the article Installing PHP 7.2 with pthreads on CentOS 6 for a solution.

[root@parox03 /home/files/php-7.2.1/ext/pthreads]# make
/bin/sh /home/files/php-7.2.1/ext/pthreads/libtool --mode=compile cc -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -I. -I/home/files/php-7.2.1/ext/pthreads -DPHP_ATOM_INC -I/home/files/php-7.2.1/ext/pthreads/include -I/home/files/php-7.2.1/ext/pthreads/main -I/home/files/php-7.2.1/ext/pthreads -I/usr/local/include/php -I/usr/local/include/php/main -I/usr/local/include/php/TSRM -I/usr/local/include/php/Zend -I/usr/local/include/php/ext -I/usr/local/include/php/ext/date/lib -I/home/files/php-7.2.1/ext/pthreads/.  -DHAVE_CONFIG_H  -g -O2   -c /home/files/php-7.2.1/ext/pthreads/php_pthreads.c -o php_pthreads.lo
mkdir .libs
 cc -DZEND_ENABLE_STATIC_TSRMLS_CACHE=1 -I. -I/home/files/php-7.2.1/ext/pthreads -DPHP_ATOM_INC -I/home

parseword

//bind9 logging stanza with dynamic severity that can be controlled via rndc
//
//To debug something, issue "rndc trace 99" and run your troublesome query.
//This will generate extremely verbose logs, so as soon as you capture the event, 
//run "rndc notrace" to return to standard non-verbose logging. Then copy and
//examine the log files at your leisure. 

logging {
    channel default_debug {
        file "/var/log/named/named.run";

parseword

Public DNS Service Comparisons

Network connectivity and latency only, from Comcast in Memphis, TN. 2018-04-02.

Cloudflare's 1.1.1.1

7 hops, ping average 13.1 ms

[parse@word ~]$ mtr -c 100 1.1.1.1

parseword

Public DNS Service Comparisons - www.amazon.com

This document is a companion to the article 1.1.1.1: Fast, but not so accurate (yet).

"A" response records for Amazon, and network connectivity and latency to the answers, from Comcast in Memphis, TN. Tests conducted 2018-04-04.

Note: Traceroutes into Amazon-operated networks, including CloudFront, have a tendency to be obfuscated due to network topology and ICMP policy.

parseword

Public DNS Service Comparisons - youtube.com

This document is a companion to the article 1.1.1.1: Fast, but not so accurate (yet).

"A" response records for YouTube, and network connectivity and latency to the answers, from Comcast in Memphis, TN. Tests conducted 2018-04-04.

Querying the A record for youtube.com, 1.1.1.1 gives the poorest answer: inexplicably, a server in Bogota, Colombia, South America. The most optimal results were returned by Comcast and Level3, which both gave the

parseword

Public DNS Service Comparisons - google.com

This document is a companion to the article 1.1.1.1: Fast, but not so accurate (yet).

"A" response records for Google, and network connectivity and latency to the answers, from Comcast in Memphis, TN. Tests conducted 2018-04-04.

Querying the A record for google.com, 1.1.1.1 gives the poorest answer, a server more than twice as distant as those returned by other resolvers. The most optimal results were returned by Comcast and Level3.

parseword

Public DNS Service Comparisons - slack.com

This document is a companion to the article 1.1.1.1: Fast, but not so accurate (yet).

"A" response records for Slack, and network connectivity and latency to the answers, from Comcast in Memphis, TN. Tests conducted 2018-04-04.

Note: Traceroutes into Amazon-operated networks, including CloudFront, have a tendency to be obfuscated due to network topology and ICMP policy.

parseword

tcpdump associated with the article Unusual HTTP POST traffic from 75.108.75.42

There were a total of 48 requests:

75.108.75.42 - - [15/Apr/2018:19:07:03 -0500] "POST / HTTP/1.1" 200 45 - "-" "Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko"
75.108.75.42 - - [15/Apr/2018:19:09:03 -0500] "POST / HTTP/1.1" 200 45 - "-" "Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko"
75.108.75.42 - - [15/Apr/2018:19:11:03 -0500] "POST / HTTP/1.1" 200 45 - "-" "Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko"
75.108.75.42 - - [15/Apr/2018:19:13:03 -0500] "POST / HTTP/1.1" 200 45 - "-" "Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko"
75.108.75.42 - - [15/Apr/2018:19:15:04 -0500] "POST / HTTP/1.1" 200 45 - "-" "Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko"

parseword

tcpdump associated with the article Unusual HTTP POST traffic

There were a total of 69 requests, starting with one that used "\xaf" as the HTTP verb:

108.75.16.72 - - [26/Apr/2018:09:44:10 -0500] "\xaf" 400 226 - "-" "-"
108.75.16.72 - - [26/Apr/2018:09:44:10 -0500] "POST / HTTP/1.1" 200 45 - "-" "Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko"
108.75.16.72 - - [26/Apr/2018:09:46:10 -0500] "POST / HTTP/1.1" 200 45 - "-" "Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko"
108.75.16.72 - - [26/Apr/2018:09:48:10 -0500] "POST / HTTP/1.1" 200 45 - "-" "Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko"
108.75.16.72 - - [26/Apr/2018:09:50:11 -0500] "POST / HTTP/1.1" 200 45 - "-" "Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko"