I have a Raspberry PI 3 (with Stretch) that boots to a static IP. The problem is I can't find out where this IP is being configured.

Areas I have looked:

/etc/dhcpcd.conf
/etc/network/interfaces
/etc/network/interfaces.d
/boot/commandline.txt

I have even done a find/grep on the root directory for the static IP. No luck. Any ideas?

Edit:

ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet 10.10.90.201  netmask 255.255.240.0  broadcast 10.10.95.255
...

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
....
  • 1
    How do you know it's not obtained via DHCP? – Kamil Maciorowski Jul 14 at 1:09
  • I should've mention that. It is presently not connected to a network. – troxel Jul 14 at 1:29
  • What's the address then? Is it 169.254.aaa.bbb maybe? – Kamil Maciorowski Jul 14 at 1:32
  • The address is 10.10.90.201 – troxel Jul 14 at 1:38
  • 1
    The standard thing to do in situations like this is to describe the solution (maybe in a little more detail, like: how did you find it?) and post it as an answer (i.e., in the “Your Answer” box, below).  Yes, you are allowed (and even encouraged) to answer your own question.  It might help somebody someday, and you might get a little “reputation” on this site for doing it.  Beware that comments are sometimes deleted. – Scott Jul 16 at 5:50

Newer releases of Debian (e.g. stretch) are managed through systemd, as explained in the Debian Reference, Chapter 5: Network setup:

Under systemd, the network may be configured in /etc/systemd/network/ instead.

The same document says:

Debian squeeze and newer can manage the network connection via management daemon software such as NetworkManager (NM) (network-manager and associated packages) or Wicd (wicd and associated packages).

I suggest you actually read the whole chapter, since it is essential for a thorough understanding of how Debian works.

Do you have avahi-daemon or connman installed? I have had this (similar) problem happen before, and disabling/uninstalling these two removed the issue.

If it's another service doing it, dmesg | grep "10.10.90.201" should unveil the culprit...

Your Answer

 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.