Hi Tomás, many thanks for your response :-)
Am Samstag, 21. April 2018, 08:43:20 CEST schrieb to...@tuxteam.de: > On Fri, Apr 20, 2018 at 10:20:12PM +0200, Rainer Dorsch wrote: > > Am Freitag, 20. April 2018, 22:13:11 CEST schrieb to...@tuxteam.de: > > > curl -I http://security.debian.org/debian-security/ > > > > root@master:~/tmp# curl -I http://ftp.de.debian.org/debian/ > > HTTP/1.1 200 OK > > Date: Fri, 20 Apr 2018 20:19:14 GMT > > Server: Apache/2.4.10 (Debian) > > Content-Type: text/html;charset=UTF-8 > > > > root@master:~/tmp# curl -I http://security.debian.org/debian-security/ > > HTTP/1.1 200 OK > > [...] > > Yeah, that succeeded *once*, but you suggested that your problem > is intermittent. > > Either your network connection is sometimes down (you might see > traces of that in your system log) or security.debian.org is > sometimes down (somewhat less probable, since more folks would > complain), or "something" in the path between you two is sometimes > down. > > To catch this "sometimes" you'll have to invest a bit more of > work. > > I'd start by looking into syslog, around the times your upgrade > complains. Next, you might want to watch connectivity -- there sure > are nice programs out there, with graphing and things, but just > pinging your upstream router every minute might give you a rough > impression, like so: > > ping -i 60 <your upstream router here> > /tmp/connect.log 2>&1 & > > and have look at the result after a day or so. > > If you're on WiFi, check for bad signal quality or too many nearby > routers (or other sources of noise). If it's Ethernet, flakey cables > or connectors are known for doing nasty things. And so on. > > It's a bit like hunting :-) I am on ethernet and all other debian machines in the subnet are doing excellent. syslog was an excellent idea, indeed there are many suspicious entries: Apr 21 10:35:13 master kernel: [3019173.333566] IPv6: ipv6_create_tempaddr: retry temporary address regeneration Apr 21 10:36:01 master kernel: [3019221.240105] IPv6: ipv6_create_tempaddr: retry temporary address regeneration Apr 21 10:36:11 master kernel: [3019231.951162] IPv6: ipv6_create_tempaddr: retry temporary address regeneration Apr 21 10:36:35 master kernel: [3019256.044369] IPv6: ipv6_create_tempaddr: retry temporary address regeneration Apr 21 10:37:10 master kernel: [3019290.823572] IPv6: ipv6_create_tempaddr: retry temporary address regeneration Apr 21 10:37:10 master kernel: [3019290.823932] IPv6: ipv6_create_tempaddr: retry temporary address regeneration Apr 21 10:37:10 master kernel: [3019290.824625] IPv6: ipv6_create_tempaddr: retry temporary address regeneration Apr 21 10:37:13 master kernel: [3019293.735943] IPv6: ipv6_create_tempaddr: retry temporary address regeneration Apr 21 10:37:53 master kernel: [3019333.828612] IPv6: ipv6_create_tempaddr: retry temporary address regeneration Also the output of root@master:~# ip addr show|wc -l 63614 root@master:~# and root@master:~# ip addr show|head -40 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 18:66:da:20:6f:2d brd ff:ff:ff:ff:ff:ff inet 192.168.0.2/24 brd 192.168.0.255 scope global dynamic eno1 valid_lft 853609sec preferred_lft 853609sec inet6 fd38:81d3:9dac:0:f0ef:7ae3:c2bf:3bd8/64 scope global temporary dynamic valid_lft 604795sec preferred_lft 86240sec inet6 fd38:81d3:9dac:0:80cd:9129:26ce:bee5/64 scope global temporary dynamic valid_lft 604794sec preferred_lft 86239sec inet6 fd38:81d3:9dac:0:402a:7f5d:c391:9d23/64 scope global temporary dynamic valid_lft 604793sec preferred_lft 86238sec inet6 fd38:81d3:9dac:0:a457:e576:bdd9:84f5/64 scope global temporary dynamic valid_lft 604786sec preferred_lft 86231sec inet6 fd38:81d3:9dac:0:f928:5018:1834:fbc6/64 scope global temporary dynamic valid_lft 604783sec preferred_lft 86228sec inet6 fd38:81d3:9dac:0:8ce6:e31c:4745:e335/64 scope global temporary dynamic valid_lft 604783sec preferred_lft 86228sec inet6 fd38:81d3:9dac:0:818c:c093:8084:fcad/64 scope global temporary dynamic valid_lft 604774sec preferred_lft 86219sec inet6 fd38:81d3:9dac:0:1c74:e734:3319:2ae3/64 scope global temporary dynamic valid_lft 604749sec preferred_lft 86194sec inet6 fd38:81d3:9dac:0:15de:1534:8301:d55d/64 scope global temporary dynamic valid_lft 604728sec preferred_lft 86173sec inet6 fd38:81d3:9dac:0:b05b:c204:aa6e:4cf0/64 scope global temporary dynamic valid_lft 604720sec preferred_lft 86165sec inet6 fd38:81d3:9dac:0:9886:8ee9:627f:8bab/64 scope global temporary dynamic valid_lft 604706sec preferred_lft 86151sec inet6 fd38:81d3:9dac:0:2de1:2328:70a:deef/64 scope global temporary dynamic valid_lft 604698sec preferred_lft 86143sec inet6 fd38:81d3:9dac:0:191e:271d:2251:1bc9/64 scope global temporary dynamic valid_lft 604688sec preferred_lft 86133sec inet6 fd38:81d3:9dac:0:39e3:80e5:cb6e:381f/64 scope global temporary dynamic valid_lft 604643sec preferred_lft 86088sec inet6 fd38:81d3:9dac:0:c182:fa23:e7d:c3e2/64 scope global temporary dynamic valid_lft 604643sec preferred_lft 86088sec root@master:~# look really strange. That interface is managed by network-manager .... I am wondering if I should fall back to /etc/network/interfaces ... For network-manager I do not have experience on headless system, tried this here to get information (is the systemd-networkd not running expected?) root@master:~# networkctl --all WARNING: systemd-networkd is not running, output will be incomplete. IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback n/a unmanaged 2 eno1 ether n/a unmanaged 2 links listed. root@master:~# Any idea why IPv6 is not properly working is welcome. Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
