Mystery Solved.
gewilli wrote:
Apparently this it related to apache (just a wild assed guess).
Yes, it is. I was able to catch this in fast loop after toggling the NTP switch about 200 times. :smileyvery-happy:
tcp 0 0 10.0.0.32:57054 8.8.8.8:53 TIME_WAIT -
tcp 0 0 10.0.0.32:57054 8.8.8.8:53 TIME_WAIT -
tcp 0 0 10.0.0.32:57054 8.8.8.8:53 TIME_WAIT -
tcp 0 0 10.0.0.32:57054 8.8.8.8:53 TIME_WAIT -
tcp 0 1 10.0.0.32:57067 8.8.8.8:53 SYN_SENT 15841/apache2
tcp 0 0 10.0.0.32:57054 8.8.8.8:53 TIME_WAIT -
tcp 0 0 10.0.0.32:57067 8.8.8.8:53 TIME_WAIT -
tcp 0 0 10.0.0.32:57054 8.8.8.8:53 TIME_WAIT -
tcp 0 0 10.0.0.32:57067 8.8.8.8:53 TIME_WAIT -
tcp 0 0 10.0.0.32:57054 8.8.8.8:53 TIME_WAIT -
From there, it was easy to find.
It’s simply the PHP script which determines whether Internet access is working OK.
The script uses two DNS servers that are well known: Google DNS (8.8.8.8) ad OpenDNS (208.67.222.222) and tries to open a TCP socket to them.
It first tries Google DNS, and if it fails, then tries OpenDNS. If both fail, the UI reports that there’s no working internet access.
I’m guessing it’s done this way so that even if the user specifies an invalid DNS, the connection check will still work.
The script is at
/var/www/rest-api/api/Remote/src/Remote/Controller//InternetAccess.php