You are not logged in.
Hi all,
I am unable to run pacman-key --refresh-keys as I guess I don't have IPv6 support. :
gpgkeys: HTTP fetch error 7: Failed to connect to 2001:1868:2003::12: Network is unreachable
My router is setup with shorewall, not shorewall6. Also, I am running pdnsd which appears to not have any ipv6 support compiled in.
Walter
Last edited by walterjwhite (2013-03-01 21:53:40)
Offline
You probably have a rogue IPv6 router in your network, typically a Windows box with ICS enabled?
Can you show output of "/sbin/ip -6 addr list" and "/sbin/ip -6 route show" ?
Offline
This is the error I'm getting from another network, basically the same thing:
gpg: Total number processed: 0
==> ERROR: A specified local key could not be updated from a keyserver.
Walter
Offline
I updated my DNS server to support IPv6, but am still getting the same error:
gpgkeys: HTTP fetch error 7: Failed to connect to 2a01:4f8:190:2ffe::99: Network is unreachable
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
==> ERROR: A specified local key could not be updated from a keyserver.
I will have to check what else needs to be done with supporting IPv6 as apparently it can't get to that network?
Walter
Offline
In response to your questions:
[walterjwhite@router ~]$ sudo ip -6 addr list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: iw: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 fe80::21e:68ff:fef3:ce6/64 scope link
valid_lft forever preferred_lft forever
3: uw-tplink: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 fe80::250:b6ff:fe0d:3004/64 scope link
valid_lft forever preferred_lft forever
5: uwl-tplink-2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 fe80::a2f3:c1ff:fe0a:b73d/64 scope link
valid_lft forever preferred_lft forever
6: uwl-tplink: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 fe80::fad1:11ff:fe16:c20/64 scope link
valid_lft forever preferred_lft forever
[walterjwhite@router ~]$ sudo ip -6 route show
fe80::/64 dev iw proto kernel metric 256
fe80::/64 dev uw-tplink proto kernel metric 256
fe80::/64 dev uwl-tplink-2 proto kernel metric 256
fe80::/64 dev uwl-tplink proto kernel metric 256
Walter
Offline
You don't have any globally routable IPv6 address, nor a route to any outside network, so apps should fallback to IPv4 automatically.
The first line is probably just a warning you can ignore – informing you it can't do IPv6 so it will fall back to IPv4 (it shouldn't really print this if IPv4 connection succeeds.)
The next line is an application level failure (not finding relevant PGP keys), but this is not related to IPv4/IPv6.
So it's an application issue not a network issue.
Offline