dhcpcd-discuss

Re: dhcp6_listen: Address already in use

Moritz Warning

Wed May 16 16:13:27 2018

On 05/16/2018 10:28 AM, Roy Marples wrote:
> Hi Moritz
> 
> On 15/05/2018 23:37, Moritz Warning wrote:
>> from dhcpcd 7.0.4-1 on Arch Linux gives me "dhcp6_listen: Address already in use" and exits.
>> The problem appears when connecting to my WLAN using wicd 1.7.4-1:
>>
>> May 15 23:26:19 brick dhcpcd[18975]: DUID 00:01:00:01:22:23:49:d8:c8:ff:28:77:db:cb
>> May 15 23:26:19 brick dhcpcd[18975]: wlp58s0: IAID 28:77:db:cb
>> May 15 23:26:19 brick dhcpcd[18975]: wlp58s0: adding address fe80::5ff4:3245:b2a9:d6fc
>> May 15 23:26:19 brick dhcpcd[18975]: wlp58s0: soliciting a DHCP lease
>> May 15 23:26:19 brick dhcpcd[18975]: wlp58s0: offered 172.16.0.214 from 172.16.0.1
>> May 15 23:26:19 brick dhcpcd[18975]: wlp58s0: probing address 172.16.0.214/16
>> May 15 23:26:20 brick dhcpcd[18975]: wlp58s0: soliciting an IPv6 router
>> May 15 23:26:20 brick dhcpcd[18975]: wlp58s0: Router Advertisement from fe80::6666:b3ff:fe50:1230
>> May 15 23:26:20 brick dhcpcd[18975]: wlp58s0: adding address fdbc:652b:8f56:0:e70a:c5a7:f201:2127/64
>> May 15 23:26:20 brick dhcpcd[18975]: wlp58s0: adding route to fdbc:652b:8f56::/64
>> May 15 23:26:20 brick dhcpcd[18975]: wlp58s0: soliciting a DHCPv6 lease
>> May 15 23:26:20 brick dhcpcd[18975]: wlp58s0: ADV fdbc:652b:8f56::e3b/128 from fe80::6666:b3ff:fe50:1230
>> May 15 23:26:20 brick dhcpcd[18975]: wlp58s0: accepted reconfigure key
>> May 15 23:26:20 brick dhcpcd[18975]: wlp58s0: REPLY6 received from fe80::6666:b3ff:fe50:1230
>> May 15 23:26:20 brick dhcpcd[18975]: wlp58s0: adding address fdbc:652b:8f56::e3b/128
>> May 15 23:26:20 brick dhcpcd[18975]: wlp58s0: renew in 21600, rebind in 34560, expire in 4294967295 seconds
>> May 15 23:26:22 brick dhcpcd[18975]: forked to background, child pid 19022
>> May 15 23:26:22 brick dhcpcd[18975]: dhcp6_listen: Address already in use
>> May 15 23:26:22 brick dhcpcd[19025]: sending signal ALRM to pid 19022
>> May 15 23:26:22 brick dhcpcd[19025]: waiting for pid 19022 to exit
>> May 15 23:26:22 brick dhcpcd[19022]: received SIGALRM, releasing
>> May 15 23:26:22 brick dhcpcd[19022]: wlp58s0: removing interface
>> May 15 23:26:22 brick dhcpcd[19022]: wlp58s0: deleting address fdbc:652b:8f56::e3b/128
>> May 15 23:26:22 brick dhcpcd[19022]: wlp58s0: deleting address fdbc:652b:8f56:0:e70a:c5a7:f201:2127/64
>> May 15 23:26:22 brick dhcpcd[19022]: wlp58s0: deleting route to fdbc:652b:8f56::/64
>> May 15 23:26:22 brick dhcpcd[19022]: wlp58s0: deleting address fe80::5ff4:3245:b2a9:d6fc
>> May 15 23:26:22 brick dhcpcd[19022]: dhcpcd exited
>>
>> dhcpcd run as "/usr/bin/dhcpcd --noipv4ll wlp58s0"
>>
>> This ultimately prevents me from connection to my WLAN.
>>
>> I 'solved' the problem by sneaking in -4 as argument to the dhcpcd call.
>> Is this a known problem?
> 
> No, this isn't a known problem - at least not on NetBSD.
> Could you post the arguments wicd spawns dhcpcd as please? And attach your dhcpcd.conf to your reply.
> 
> Roy

dhcpcd is called this way:
/usr/bin/dhcpcd --noipv4ll  wlp58s0

/etc/dhcpcd.conf is attached
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
duid

# Persist interface configuration when dhcpcd exits.
persistent

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu

# Most distributions have NTP support.
#option ntp_servers

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate SLAAC address using the Hardware Address of the interface
#slaac hwaddr
# OR generate Stable Private IPv6 Addresses based from the DUID
slaac private
noipv4ll

Follow-Ups:
Re: dhcp6_listen: Address already in useRoy Marples
References:
dhcp6_listen: Address already in useMoritz Warning
Re: dhcp6_listen: Address already in useRoy Marples
Archive administrator: postmaster@marples.name