Web lists-archives.com

Re: Strange Loss of Synaptic Functionality

On Sun, 11 Feb 2018, Stephen P. Molnar wrote:

On Sat, 2018-02-10 at 14:36 -0500, Stephen P. Molnar wrote:
On Sat, 2018-02-10 at 19:29 +0100, Ulf Volmer wrote:
On 10.02.2018 19:03, Stephen P. Molnar wrote:

Host -
root@AbNormal:/home/comp# ip -6 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP
    inet6 2600:1700:4280:3690::49/128 scope global dynamic
       valid_lft 1209477sec preferred_lft 1209477sec
    inet6 2600:1700:4280:3690:98c1:1a97:c2c5:b6f5/64 scope global
temporary dynamic
       valid_lft 604678sec preferred_lft 86021sec
    inet6 2600:1700:4280:3690:beee:7bff:fe5e:8336/64 scope global
mngtmpaddr noprefixroute dynamic
       valid_lft 1209509sec preferred_lft 1209509sec
    inet6 fe80::beee:7bff:fe5e:8336/64 scope link
       valid_lft forever preferred_lft forever
Incidentally, here's what I get when I attempt pinging
comp@AbNormal:~$ ping -6 security.debian.org
PING security.debian.org(mirror-umn2.debian.org
(2607:ea00:101:3c0b::1deb:215)) 56 data bytes
--- security.debian.org ping statistics ---
16 packets transmitted, 0 received, 100% packet loss, time

comp@AbNormal:~$ wget -6 security.debian.org
--2018-02-10 12:10:09--  http://security.debian.org/
Resolving security.debian.org (security.debian.org)...
2607:ea00:101:3c0b::1deb:215, 2610:148:1f10:3::73,
Connecting to security.debian.org
(security.debian.org)|2607:ea00:101:3c0b::1deb:215|:80... ^C

ok, that's looks likes expected, you have a (correct) ipv6
on your physical host and no ipv6 configuration on your VM (only
local ipv6 address).

So your should check either your local router or deal with your

Somebody announces your physical host an ipv6 address but this
connection will not works at the moment.

best regards

Just got off the phone with AT&T tech support.  Their testing
a problem which they will address tomorrow.

I would like to say that I really appreciate the support I've been

AT&T Tech Support has come and gone.   A nice chap and he did find a
low light level problem.  He checked the settings on the modem to be
sure they were optimum.

He'd played with Ubuntu some years ago, but was discouraged by monitor
driver issues and hasn't done anything lately.  He did find one URL:


but that complained about a gpg error about no public key.  So I would
assume that URL doesn't apply to my problem.

I have noticed that I can ping my router and my windows platform, but
not external ULR's, yahoo.com for instance.  I find the same behavior
on my MS Win platform, except external URL's time out rather than
require a ctrl-C to return control to the terminal.

As I see the same behavior on the part of two different computers and
two different OS' I can't believe that the modem is operating
correctly.  Can it be an OS problem.  The trouble started with the
installation of the new mode for the fiber optic network.  I should
also mention that when I install Linux I always depend on the automatic
configuration for the network and it worked worked perfectly before the
advent of the new modem.

I would appreciate comments and further suggestions.

Reading the man page for apt.conf, I notice there is a boolean
configuration option Acquire::ForceIPv4.

You might see what happens if you set that option to true when you
attempt update/upgrade:

 # apt-get -o Acquire::ForceIPv4=true update

and then

 # apt-get -o Acquire::ForceIPv4=true upgrade

It sounds to me like you experience a more general problem with ipv6
networking. But maybe this would enable you to update and upgrade your
OS in the meantime, while you sort out the more general problem.

Caveat: Regarding computer networks, I am a troglodyte, and this is a
blind stab in the dark.

Good luck!