On 30/11/11 23:47, Doug Barton wrote:
This usually happens when the OS has signaled that it has IPv6
available, but it's not actually configured on any interfaces. The usual
way to fix this is to flip the knob that says IPv6 is *not* available.
Ah, okay. I figured this was not the case because
mike@Fuzzbutt:~$ gpg --keyserver grepular.com --recv-key
gpg: requesting key from hkp server grepular.com
gpgkeys: HTTP fetch error 7: Failed to connect to
2001:470:1f09:1186::beef: Network is unreachable
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
On Nov 30, 2011, at 7:18 AM, gn...@lists.grepular.com wrote:
mike@Fuzzbutt:~$ gpg --keyserver grepular.com --recv-key
gpg: requesting key from hkp server grepular.com
gpgkeys: HTTP fetch error 7: Failed to connect to
2001:470:1f09:1186::beef: Network is unreachable
gpg: no
On 30/11/11 16:25, David Shaw wrote:
mike@Fuzzbutt:~$ gpg --keyserver grepular.com --recv-key
gpg: requesting key from hkp server grepular.com
gpgkeys: HTTP fetch error 7: Failed to connect to
2001:470:1f09:1186::beef: Network is unreachable
gpg: no valid OpenPGP data
On Nov 30, 2011, at 11:43 AM, gn...@lists.grepular.com wrote:
On 30/11/11 16:25, David Shaw wrote:
mike@Fuzzbutt:~$ gpg --keyserver grepular.com --recv-key
gpg: requesting key from hkp server grepular.com
gpgkeys: HTTP fetch error 7: Failed to connect to
On 30/11/11 17:31, David Shaw wrote:
Seems curl tries IPv4 then IPv6.
mike@Fuzzbutt:~$ curl -v http://grepular.com:11371
* About to connect() to grepular.com port 11371 (#0)
* Trying 178.79.145.246... Connection refused
* Trying 2001:470:1f09:1186::beef... Failed to connect to
On 30/11/11 19:05, gn...@lists.grepular.com wrote:
You're correct. tcpdump has confirmed that the initial attempt is done
over IPv4. Still, the error message returned from gpg is misleading...
I also find the error message from curl somewhat misleading, although
technically correct. I would
On 11/30/2011 11:25, Peter Lebbing wrote:
On 30/11/11 19:05, gn...@lists.grepular.com wrote:
You're correct. tcpdump has confirmed that the initial attempt is done
over IPv4. Still, the error message returned from gpg is misleading...
I also find the error message from curl somewhat
