Oh..oh!! No...Something's wrong with my IP..Will start looking into that.Any suggestions with respect to how static IP is configured in the new Raspbian distro? I used the network settings in the top taskbar.
Here's what I did. removed the static configuration. restared and then reapplied static IP. now accessible. Previously even internet was inaccessible. What could be the reason?pcmanbob wrote: ↑Thu Jul 11, 2019 2:29 pmOK you could try unplugging the network cable for 60 seconds and then reconnect it to see if that restorers the connection ,
but it may be that you pi has crashed in which case that's not going to help , do you see any activity on the green LED on the pi ?
To set a static IP on the pi you need to edit /etc/dhcpcd.conf and add the static IP in there,
but the address must be outside the range of address that the router DHCP server can assign or you might get address conflicts.
The better option is to use address reservation on your router if it supports it.
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 # 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 # Example static IP configuration: interface eth0 static ip_address=192.168.1.95/24 #static ip6_address=fd51:42f8:caae:d92e::ff/64 static routers=192.168.1.1 #static domain_name_servers=192.168.0.1 22.214.171.124 fd51:42f8:caae:d92e::1 # 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
I had cofigured with restricted DHCP which was not conflicting with all the static IPs. Now I have changed over to DHCP reservation couple of days back.HawaiianPi wrote: ↑Thu Jul 11, 2019 4:49 pmIs your router configured with a restricted DHCP range that does not overlap your static IP?
Really, the best way to get a fixed IP is to reserve it in your router's DHCP settings (rather than mucking about with OS specific configuration files). You only have to do it once, and then that particular Pi will always get the same IP, even when booting from different cards or a new OS.