Setting a manual IP address

May 14, 2024 Last reply: 2 years ago 31 Replies

With the hairy script that's executed by dhcpcd and /etc/dhcpcd.conf, I believe. Setting a static address there isn't hard, one example is at

formatting link

Thank you for your eloquent debate.

Well bravo, it worked for you.

Some of us are running fleets of dozens of Raspberry Pi's of multiple generations, and having an OS upgrade required by the latest Pi model which works very different in respect to networking and video, is a massive pain in the arse.

The options are to push the OS upgrade to all machines and change the way of working, or find out how to make the new Pi work consistently with rest of the fleet - which is what I have opted for.

---druck

reason for the palather above, as I've explained before, is despite disabling Wayland I was unable to get it to recognise that I had installed an alternative Mate desktop, and I couldn't even get the Pixel desktop to change to the resolution of my 1440p monitor. When I went to look for answer in the logs, and found rsyslog wasn't even installed, and there was only the abhorrent journald, I nuked it from orbit, and upgraded from Bullseye instead.

---druck

The "network preferences" dialog box shown in that link is considerably different from, and simpler than, the dialog that comes up if I click on the network icon > advanced options > network connnections> editing eth0...

It reveals a window with seven tabs. The defaults in the Ethernet tab look reasonable and I can save them, but when I open the IPv4 Settings tab it doesn't seem possible to enable the Save button even after setting address, netmask, gateway (and routes, which seems redundant give there's already a gateway). It looks like I've forgotten to fill something in, but the dialog automatically check things like IP numbers and netmask as they're typed. If I've overlooked something there's no hint what it might be.

Is it possible that the Pi OS won't support two simultaneous network connections? I'm out of guesses.

Thanks for writing!

bob prohaska

Nice to see the usual usenet courtesy!

I have run everything from Pi1 to Pi5,and although I setup a GUI, I normally run them headless - ie XRDP if I want a GUI

I have always tried to use the latest distro - sometimes with a fresh install, sometimes with (against advice usually) done an in place upgrade - never with any unsolvable issues

For the Pi5, as Bookworm was a prerequisite, I did a fresh install on one of my Pi4s - everything was documented. No problem, then used that for the Pi5 when it arrived.

Seeing the level of the discussions here, I would recommend looking at the Raspberry Pi forum - there are plenty of use who know what they are doing, and advise the idiots

Here you seem to get the idiots advising. I rest my case, and will bow out.

I expected you'd ignore the difficult to document and always changing GUI stuff and just edit the dhcpcd.conf file, starting from the point where it says "4. Open /etc/dhcpcd.conf for editing in nano."

If you want to manually set up s*it, it is necessary to disable automatic options.

It should be possible to tell NetworkManager to keep its sticky fingers off particular network interfaces, which you can then manage manually. This would be done through nmcli.

I’ve been running Debian Unstable, on three different machines, for years.

Nobody. I don’t think anybody in the Debian project gets paid for their participation.

There should be a popup menu on the GUI login screen (aka display manager, whether lightdm, sddm or similar) showing all the GUI environments it knows about, to let you choose which one to login to.

Of course it will. It’s Linux.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required