# Duplicate IP address
**URL:** https://dietpi.com/forum/t/duplicate-ip-address/2058
**Category:** Troubleshooting
**Created:** [6 March 2018 20:23 UTC](https://dietpi.com/forum/t/duplicate-ip-address/2058 "2018-03-06T20:23:49Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@cu6apum](https://dietpi.com/forum/u/cu6apum)
#### Post date: [6 March 2018 20:23 UTC](https://dietpi.com/forum/t/duplicate-ip-address/2058/1 "2018-03-06T20:23:49Z")
Submitted the bug report already; perhaps letting people know is good too.
dietPi V159 , kernel 4.5.0-botic7-rc1 on beaglebone.
I almost got mad with unresponsive daemons like mpd/upmpdcli, and occasionally found out that the device is accessible on TWO ip addresses!! All the daemons bind to the second (that ifconfig shows), while local arp announces the first (of course) which makes dlna server / controller bite empty spaces.
Having investigated this weirdness I found out that the kernel sends DHCP request at boot, while hostname is not set yet, and THEN the dhclient comes, and takes another with new hostname. Craziness.
As I don’t want to disable dhclient in order to keep the interface hotpluggable, I’d love to find out how to disable kernel dhcp…
Setting ip=none or ip=192.168.1.1 don’t help.
Please advise! Thank you.
---
### Author:  [@cu6apum](https://dietpi.com/forum/u/cu6apum)
#### Post date: [15 March 2018 14:02 UTC](https://dietpi.com/forum/t/duplicate-ip-address/2058/2 "2018-03-15T14:02:23Z")
Ok silence.
I just deleted dhclient as I don’t have any idea how to tell it that dhcp is already taken.
Weirdness. Not linux behavior in any way.