Patrick M. Hausen

> I was able to get the error to go away and have it work with `vagrant up` of existing and/or new boxes, by doing the following edit to my...

This code here **is a FreeBSD port**. All that is needed is submitting it in the FreeBSD Bugzilla to be included in the official collection. https://bugs.freebsd.org/bugzilla/

I think I could help with that. Time permitting. Why do you include some magic extracting libtensorflow from a docker image? There is a port of py-tensorflow already. Can't you...

OK, py-tensorflow is marked as "BROKEN". So one would have to make that work first. I fail to get the problem with the bazel dependency, there's this in the py-tensorflow...

BTW: policy selection does fundamentally work in FreeBSD. If I use FreeBSD's own `fetch` tool: ``` root@freebsd:~ # fetch -q -o - https://my.ip.fi 87.138.*.* ```

I do not quite understand - on Linux CURL does follow `/etc/gai.conf`. If I switch the priority from 100 to 10, it will return an IPv6 address. Back to 100...

Also on FreeBSD there's getaddrinfo(1): With policy set to prefer IPv4: ``` root@freebsd:~ # getaddrinfo my.ip.fi dgram inet udp 91.198.120.42 0 stream inet tcp 91.198.120.42 0 seqpacket inet sctp 91.198.120.42...

Interesting ... Debian, CURL 7.88.1: ``` root@debian:~# curl -vvv my.ip.fi * Trying 91.198.120.42:80... * Connected to my.ip.fi (91.198.120.42) port 80 (#0) ``` FreeBSD, CURL 8.11.1: ``` root@freebsd:~ # curl -vvv...

Section 6 of RFC 6555 reads: ``` 6. Example Algorithm What follows is the algorithm implemented in Google Chrome and Mozilla Firefox. 1. Call getaddinfo(), which returns a list of...

The particular case that called for this issue is a system that does have both IPv6 and IPv4 connectivity but the customer needs IPv4 to be preferred because "enterprise firewall...