Setting static IP address on a Pi 4

[Adri74100]

Hi,

I would like to set a static IP address on a Raspberry pi 4.
Actually, the Pi is connected with Wifi and ethernet, both with DHCP.
I connect using Putty (SSH).

I tried "nano /etc/dhcpcd.conf" :

Code: Select all

interface eth0
static ip_address=192.168.11.210/24
static routers=192.168.11.254
static domain_name_servers=192.168.11.254

After a reboot, "ip addr" shows :

Code: Select all

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether dc:a6:32:00:62:ac brd ff:ff:ff:ff:ff:ff
    inet 192.168.11.33/24 brd 192.168.11.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::e4ec:8456:daf1:b7be/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether dc:a6:32:00:62:ad brd ff:ff:ff:ff:ff:ff
    inet 192.168.11.48/24 brd 192.168.11.255 scope global noprefixroute wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::1f11:5fa:9945:f19b/64 scope link
       valid_lft forever preferred_lft forever

And of course, the Pi isn't reachable with the 192.168.11.210 address.
Do you have any suggestions ?

[epoch1970]

Check the DHCP range of addresses that are managed by the DHCP server.
The static IP .210 you want for yourself must be outside the range. Otherwise the server might well refuse to comply with the request and give the client another address, like .33 here.

In fact, do the other way around:
- configure the DHCP server to identify the MAC address of the Pi and always give it .210, from the pool
- revert to standard configuration in dhcpcd.conf.
You'll have your fixed .210 address on your LAN, and on other networks the Pi will work without need for reconfiguration.

[Adri74100]

Hi, and thanks for your help.

Our DHCP range is from 192.168.11.1 to 99, but we are voluntarily setting the fixed IP addresses outside of this range. And we already have a lot of servers in that case (Windows).

So, I can't set a MAC binding for the .210 IP on the router, because this IP is outside of the DHCP range.

Maybe I should follow the second solution here, which involves disabling the DHCP client on the Pi ?
https://raspberrypi.stackexchange.com/q ... 4428#74428

[epoch1970]

Then it should work as is.
Check there isn't another machine using .210 on the network...

(You can do whatever you want on that machine, it is yours. But assuming the dhcp client does not work as it should and uninstalling it looks more inspired by hubris than logic.)

[JohnSoCalUSA]

Maybe I should follow the second solution here, which involves disabling the DHCP client on the Pi ?
https://raspberrypi.stackexchange.com/q ... 4428#74428

Are you using Raspbian Buster?
I had a problem with dhcpcd crashing.
Try running dhcpcd from the command line and see what happens.

[Adri74100]

Then it should work as is.
Check there isn't another machine using .210 on the network...

(You can do whatever you want on that machine, it is yours. But assuming the dhcp client does not work as it should and uninstalling it looks more inspired by hubris than logic.)

I tried to ping this IP and checked the router, I'm pretty sure it's unused (but I forgot to check that, you were right !).

I thought of uninstalling the DHCP client because you said "the server might well refuse to comply with the request", and I thought the DHCP client could interfere with the fixed IP address I configured in dhcpcd.conf.
So I won't proceed that way for now, and wait for other answers !

[Adri74100]

Maybe I should follow the second solution here, which involves disabling the DHCP client on the Pi ?
https://raspberrypi.stackexchange.com/q ... 4428#74428

Are you using Raspbian Buster?
I had a problem with dhcpcd crashing.
Try running dhcpcd from the command line and see what happens.

Yes, Raspbian Buster Lite.
dhcpcd returns

sending commands to master dhcpcd process

[JohnSoCalUSA]

Yes, Raspbian Buster Lite.
dhcpcd returns

sending commands to master dhcpcd process

At least you did not get an error like I did.
You might want to try this command line to see if this works.

sudo dhcpcd -4 -S ip_address=192.168.11.210/24 \
-S routers=192.168.11.254 \
-S domain_name_servers=192.168.11.254 \
eth0

[drgeoff]

You did save dhcpcd.conf file before rebooting?

[DirkS]

You did save dhcpcd.conf file before rebooting?

+1
also make sure it was actually saved as you need admin rights to do that.

[Adri74100]

Yes, Raspbian Buster Lite.
dhcpcd returns

sending commands to master dhcpcd process

At least you did not get an error like I did.
You might want to try this command line to see if this works.

sudo dhcpcd -4 -S ip_address=192.168.11.210/24 \
-S routers=192.168.11.254 \
-S domain_name_servers=192.168.11.254 \
eth0

This command returns "sending commands to master dhcpcd process". And ip addr still shows another IP for eth0... even after a reboot.

For the others comments : yes I saved the file, and I connect as root. I'm used to configure some Debian web servers.

[pcmanbob]

So first question, are you connecting to a standard domestic broadband router or is it a work or university network ?

what happens if you remove one of the connections to the network , having both wired and wireless connection to the same network may not be a good idea.

[Adri74100]

So first question, are you connecting to a standard domestic broadband router or is it a work or university network ?

what happens if you remove one of the connections to the network , having both wired and wireless connection to the same network may not be a good idea.

Hi, and thanks for your help !

It is at work, the router is a Zyxel USG60.
I disabled the Wifi connection, but the Pi is still accesible at the .33 address

[pcmanbob]

It is at work, the router is a Zyxel USG60.

Then the first thing you should do it talk to the network admin to see if there is anything set on the router that prevents static IP addresses being set on a device.

if you had given us this information at the start you would have got this advice as the first response.

[Adri74100]

It is at work, the router is a Zyxel USG60.

Then the first thing you should do it talk to the network admin to see if there is anything set on the router that prevents static IP addresses being set on a device.

if you had given us this information at the start you would have got this advice as the first response.

As I already said : we already have a lot of servers in that case (with a fixed IP address, outside of the DHCP range).

However, I tried configuring my laptop to use this IP address, and I couldn't make it work.
So, the problem is probably not on the Raspberry side !

I contacted the network admin and will keep you informed.

[Adri74100]

Hi everyone,

For the record : I tried with another IP address (.211 instead of .210) and everything worked fine !
So, the procedure mentionned in my first post is okay.

Thanks for your help.

[Hcgrant]

I also thought Buster was not letting me set a static ip .. but thanks to this I looked at the router and found that the ip was already in use!
So thanks

[Heujenthro]

Here's the working one.
- Connected over hidden WiFi with wpa2-psk.

If wpa_supplicant utility is not installed
sudo apt-get install wpasupplicant

Generate a PSK version of your WLAN password with wpa_passphrase utility

Code: Select all

$ wpa_passphrase "<Your Wifi SSID>" "<Your Wifi PASSWORD>"

(Quotes are needed for whitespace)

Edit /etc/network/interfaces and add the following:

Code: Select all

auto lo

iface lo inet loopback
iface eth0 inet dhcp

# Enable this to use dhcp or dynamic ip
#auto wlan0

allow-hotplug wlan0
# Replace the 'manual' to dhcp for dynamic ip
iface wlan0 inet manual
   wpa-scan-ssid 1
   wpa-ap-scan 1
   wpa-key-mgmt WPA-PSK
   wpa-proto RSN WPA
   wpa-pairwise CCMP TKIP
   wpa-group CCMP TKIP
   wpa-ssid "<Your Wifi SSID>"
   wpa-psk <Your PSK Value>

iface default inet dhcp

# Setting a static IP
iface wlan0 inet static
address XXX.XXX.X.X
network XXX.XXX.X.X
gateway XXX.XXX.X.X

Save the all changes and reboot

[jphatter]

I am super new to the Pi, I only got one to use as an cheap means for an extra host on my networking lab. I want to set a static IP on the eth0 port but there is no router on my network. It is just a switch for right now. I have followed all the same instructions for dhcpcd.conf but when i reboot ifconfig still doesn't show an IP for my eth0 connection. What am I doing wrong? I even put a default gateway in even though I don't even have it connected to anything yet minus the wifi.

[DirkS]

What am I doing wrong?

Impossible to say without knowing what changes you made.
Start a new topic and add the relevant details