Hi,
@Toulon7559
Ahaa
Copied by WinSCP from /etc/dhcpcd.conf in the 'problem-Raspberry'.
Just the bottom part of my file /etc/dhcpcd.conf, starting with examples etc. for static ip-addres-setting
The 2 blocks at the bottom are equivalent to a version in another well-working setup.
Originally the second block in this quote was inactive, marked on all lines with front-#:
later those lines activated trying to force a solution of the 'problem' (without any result).
I see that you published two blocks of configuration text, which are both part of the /etc/dhcpcd.conf file.
Just bewildering:
something related to latest release of Buster & Domoticz?
Because do not remember that difference for 'old' versions:
then it was easy to insert the static ip_settings through sudo nano.
For what reason what ever, if the upper part is the dhcpcd.conf file, you are missing configuration essentials.
If the bottom part is the dhcpcd.conf file, it is the same.
Short, if this is your configuration file, it is messed up
It is not related to Buster, as I will publish 2 configuration files, I have with buster.
1. RPi3+ (So with eth0 and wlan0, but without Domoticz)
2. Rpi2 (only with eth0, with Domoticz)
If we look to your lower part of the config file. we see:
# Example static IP configuration:
#interface eth0
#static ip_address=192.168.0.10/24
#static ip6_address=fd51:42f8:caae:d92e::ff/64
#static routers=192.168.0.1
#static domain_name_servers=192.168.0.1 8.8.8.8 fd51:42f8:caae:d92e::1
Everything is commented (#), I do not find this section with a valid static IP address and I cannot find a configuration that uses a DHCP issued IP address. So I assume, that you dont use your DHCP server for this Raspberry Pi, but you want a static address.
Then I see:
# It is possible to fall back to a static IP if DHCP fails:
# define static profile
profile static_eth0
static ip_address=192.168.1.6/24
static routers=192.168.1.2
static domain_name_servers=192.168.0.1 8.8.8.8
# fallback to static profile on eth0
#interface eth0
#fallback static_eth0
interface eth0
inform 192.168.1.6
static routers=192.168.1.2
interface wlan0
inform 192.168.0.185
static routers=192.168.0.1
This part is intended for emergency cases, if the DHCP server fails, and as you have not configured DHCP, it does fail.
You should not use this method as the standard to set a static IP address.
Find below a complete dhcpcd.conf file of a RPi3+
Code: Select all
# 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
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu
# A ServerID is required by RFC2131.
require dhcp_server_identifier
# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private
# Example static IP configuration:
#interface eth0
#static ip_address=192.168.0.10/24
#static ip6_address=fd51:42f8:caae:d92e::ff/64
#static routers=192.168.0.1
#static domain_name_servers=192.168.0.1 8.8.8.8 fd51:42f8:caae:d92e::1
interface eth0
static ip_address=192.168.10.53/24
static routers=192.168.10.30
static domain_name_servers=192.168.10.30
interface wlan0
static ip_address=192.168.10.54/24
static routers=192.168.10.30
static domain_name_servers=192.168.10.30
# It is possible to fall back to a static IP if DHCP fails:
# define static profile
#profile static_eth0
#static ip_address=192.168.1.23/24
#static routers=192.168.1.1
#static domain_name_servers=192.168.1.1
# fallback to static profile on eth0
#interface eth0
#fallback static_eth0
The next one is for RPi2 with Domoticz.
Code: Select all
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.
# Setup static interface
interface eth0
static ip_address=192.168.10.50/24
static routers=192.168.10.30
static domain_name_servers=192.168.10.30 195.121.1.34 195.121.1.66
# 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.
#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
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
# Some interface drivers reset when changing the MTU so disabled by default.
#option interface_mtu
# A ServerID is required by RFC2131.
require dhcp_server_identifier
# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private
# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
I hope this will help you to solve the issue.
Regards
Still headscratching ......
Need to remember next time when making an SD-image .......
Idea popping up: how to refresh/reset the interface driver for eth0?
Not positively surprised with further observations ....