Diag not playing nice with Little Snitch #11
Description
Hey -- seems like running this script generates a different binary name (ie nextdns-diag-16136).
This means every time this runs I need to allow this in Little Snitch's firewall rules. However, the script does not wait and before I can click allow, it already fails in the script.
Do you want to continue? (press enter to accept)
Testing IPv6 connectivity
available: false
Fetching https://test.nextdns.io
Fetch error: Get "https://test.nextdns.io": unexpected EOF
For example, I do have IPv6 connectivity:
$ ping6 google.be -c 1
PING6(56=40+8+8 bytes) 2404:e801:200e:227f:8cab:3eee:8919:9502 --> 2404:6800:4003:c03::5e
16 bytes from 2404:6800:4003:c03::5e, icmp_seq=0 hlim=108 time=6.519 ms
--- google.be ping6 statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 6.519/6.519/6.519/0.000 ms
And opening tests in the browser works fine:
{
"status": "ok",
"protocol": "DOH",
"configuration": "xxx",
"client": "58.96.209.xxx",
"destIP": "103.62.48.147",
"server": "gsl-sin-1",
"clientName": "nextdns-cli",
"deviceName": "yeri-macbookpro1",
"deviceID": "xxx"
}