18 Apr
2010
18 Apr
'10
8:49 a.m.
Hi Andy,
Thanks for the advice on this.
Andy Smith wrote:
Thanks; I've gone for the "disable" option for now as that appears not
to have a disadvantage and I like to keep things simple. :-)
Joseph
On Thu, Apr 01, 2010 at 03:17:03PM +0900, Joseph
Heenan wrote:
Seems like it is fixed now.
Thanks for the thoughts. I do definitely have
this new key in the apt key
list now, but still get the problem.
Me too. I guess they haven't re-signed the files with the new key
yet. I've tried
to switch my sources.list to volatile.debian.org, but it seems
my VPS tries to contact this over ipv6 and fails to connect. (I've not
deliberately enabled ipv6 on my VPS, but it seems to be getting an ipv6
address from somewhere...)
Okay. Do you want to fix your IPv6, disable IPv6 or make your system
prefer IPv4 addresses?
If you want to fix IPv6, it might be a little involved. Please start
by showing the output of "ip -6 addr" and "ip -6 ro". Bear in mind
that once it's fixed you should then investigate ip6tables for IPv6
firewalling.
Disabling IPv6 can't be done without a reboot. Google for "blacklist
ipv6 debian" and you'll see how.