Comment # 5 on bug 1178221 from 
Nov 16 15:20:21.989577 bpim64tumhon wickedd-dhcp4[625]: eth0: Reinitiating
DHCPv4 discovery (ifindex 2)
Nov 16 15:20:21.989622 bpim64tumhon wickedd-dhcp4[625]: valid lease: 0; have
prefs: 0
Nov 16 15:20:21.989657 bpim64tumhon wickedd-dhcp4[625]: eth0: setting fsm
timeout to 64000 msec
Nov 16 15:20:21.989704 bpim64tumhon wickedd-dhcp4[625]: eth0: sending
DHCP4_DISCOVER with xid 0xa1b66a5 in state SELECTING
Nov 16 15:20:21.989838 bpim64tumhon wickedd-dhcp4[625]: timeout 4000 adjusted
by -571 to 3429 (jr 2000)
Nov 16 15:20:21.989871 bpim64tumhon wickedd-dhcp4[625]: arming retransmit timer
(3429 msec)
Nov 16 15:20:22.660834 bpim64tumhon wickedd-dhcp6[635]: timeout 360000 adjusted
by -22381 to 337619 (jr 72000)
Nov 16 15:20:22.660897 bpim64tumhon wickedd-dhcp6[635]: arming retransmit timer
(337619 msec)
Nov 16 15:20:22.660939 bpim64tumhon wickedd-dhcp6[635]: eth0: advanced xid
0xd68463 retransmission timeout from 360000 to 337619 [-36000 .. 36000]
Nov 16 15:20:22.660975 bpim64tumhon wickedd-dhcp6[635]: eth0: Retransmitting
DHCPv6 Info Request
Nov 16 15:20:22.661036 bpim64tumhon wickedd-dhcp6[635]: elapsed-time: 655.35
Nov 16 15:20:22.661091 bpim64tumhon wickedd-dhcp6[635]: client-id:
00:01:00:01:26:d9:b4:31:02:ba:f7:39:24:a4
Nov 16 15:20:22.661166 bpim64tumhon wickedd-dhcp6[635]: oro: info-refresh-time,
preference, inf-max-rt, dns-servers, dns-domains, sntp-servers,
posix-tz-string, posix-tz-dbname, bootfile-url, bootfile-param
Nov 16 15:20:22.661374 bpim64tumhon wickedd-dhcp6[635]: eth0: INFO-REQUEST
message #14, xid 0xd68463 sent with 52 of 52 byte to ff02::1:2
Nov 16 15:20:22.661414 bpim64tumhon wickedd-dhcp6[635]: eth0: xid 0xd68463
retransmitted, next deadline in 57m36.029s
I enabled debugging for wicked in /etc/sysconfig/network/config while using the
newest kernel-default-5.9.1-2. Did not see anything strange in the journalctl
log. Finally did "journalctl -b -o short-precise -f" and got a repeated patern
of messages (see below):

Nov 16 15:20:25.421522 bpim64tumhon wickedd-dhcp4[625]: eth0: retransmit
request
Nov 16 15:20:25.421687 bpim64tumhon wickedd-dhcp4[625]: timeout 8000 adjusted
by -253 to 7747 (jr 2000)
Nov 16 15:20:25.421721 bpim64tumhon wickedd-dhcp4[625]: arming retransmit timer
(7747 msec)
Nov 16 15:20:33.175722 bpim64tumhon wickedd-dhcp4[625]: eth0: retransmit
request
Nov 16 15:20:33.175897 bpim64tumhon wickedd-dhcp4[625]: timeout 16000 adjusted
by 918 to 16918 (jr 2000)
Nov 16 15:20:33.175933 bpim64tumhon wickedd-dhcp4[625]: arming retransmit timer
(16918 msec)
Nov 16 15:20:50.110064 bpim64tumhon wickedd-dhcp4[625]: eth0: retransmit
request
Nov 16 15:20:50.110237 bpim64tumhon wickedd-dhcp4[625]: timeout 32000 adjusted
by 976 to 32976 (jr 2000)
Nov 16 15:20:50.110273 bpim64tumhon wickedd-dhcp4[625]: arming retransmit timer
(32976 msec)
Nov 16 15:21:23.118478 bpim64tumhon wickedd-dhcp4[625]: eth0: retransmit
request
Nov 16 15:21:23.118652 bpim64tumhon wickedd-dhcp4[625]: timeout 64000 adjusted
by 707 to 64707 (jr 2000)
Nov 16 15:21:23.118692 bpim64tumhon wickedd-dhcp4[625]: arming retransmit timer
(64707 msec)
Nov 16 15:21:25.991793 bpim64tumhon wickedd-dhcp4[625]: eth0: timeout in state
SELECTING
Nov 16 15:21:25.991857 bpim64tumhon wickedd-dhcp4[625]: eth0: discovery got no
(valid) reply, retrying.
Nov 16 15:21:25.991897 bpim64tumhon wickedd-dhcp4[625]: eth0: Reinitiating
DHCPv4 discovery (ifindex 2)

I got two global IPv6 addresses, but they do not seem to be alive on the
network when I try to ping these addresses on the same network/switch. Also a
ping6 from the system gets nothing back. These two addresses are derived from
the MAC address and a random number. This would mean the system received data
from SLAAC.

Is there anything else I can do?

You are receiving this mail because: