Trying to configure headless PI4B.
No files exist to set up static IP!
Its all change since the last setup only a month ago
When will these fuckers stop tinkering and decide for once and for ll
how things are to be done!
Help!
No files exist to set up static IP!
Trying to configure headless PI4B.
No files exist to set up static IP!
Its all change since the last setup only a month ago
When will these fuckers stop tinkering and decide for once and for ll
how things are to be done!
The Natural Philosopher <tnp@invalid.invalid> wrote:
Trying to configure headless PI4B.
No files exist to set up static IP!
Its all change since the last setup only a month ago
When will these fuckers stop tinkering and decide for once and for ll
how things are to be done!
You could set up your router to hand out the same IP address for your Pi's MAC address. With that, you can just leave DHCP enabled on the host and it'll always Just Work, regardless of what happens to the software on the host. As a bonus, if you configure a hostname, that should be picked up by the router and made available through internal DNS to other hosts, so you don't have to fool around with IP addresses at all.
In article (Dans l'article) <ugopuj$3mnhe$1@dont-email.me>, The Natural Philosopher <tnp@invalid.invalid> wrote (écrivait) :
No files exist to set up static IP!
Do you see /etc/dhcpcd.conf?
The Natural Philosopher <tnp@invalid.invalid> writes:
Trying to configure headless PI4B.
No files exist to set up static IP!
Its all change since the last setup only a month ago
When will these fuckers stop tinkering and decide for once and for ll
how things are to be done!
Help!
Uninstall network-manager package.
Populate /etc/network/interfaces the same way as always.
Reboot for good measure, to make sure all relics of networkmanager have
been purged.
I did this yesterday because networkmanager is written by idiots
(Redhat) and was constantly making my headless Pi drop off the
network. It's been fine since then.
john
The Natural Philosopher <tnp@invalid.invalid> writes:
Trying to configure headless PI4B.
No files exist to set up static IP!
Its all change since the last setup only a month ago
When will these fuckers stop tinkering and decide for once and
for ll how things are to be done!
Help!
Uninstall network-manager package.
Populate /etc/network/interfaces the same way as always.
Uninstall network-manager package.
In article <86jzrkrknw.fsf@building-m.net>,
John <john@building-m.simplistic-anti-spam-measure.net> wrote:
The Natural Philosopher <tnp@invalid.invalid> writes:
Trying to configure headless PI4B.
No files exist to set up static IP!
Its all change since the last setup only a month ago
When will these fuckers stop tinkering and decide for once and
for ll how things are to be done!
Help!
Uninstall network-manager package.
Populate /etc/network/interfaces the same way as always.
Could put some flesh on the bone please?
What do you mean by "populate"?
Is this an install process or just copying files and directories from
a bullseye build?
What do you do about the missing '/etc/dhcpcd.conf' which is where
I've always set statics in the past?
Thanks.
Bob.
On 18/10/2023 17:18, Jean-Pierre Kuypers wrote:
In article (Dans l'article) <ugopuj$3mnhe$1@dont-email.me>, The Natural Philosopher <tnp@invalid.invalid> wrote (écrivait) :
No files exist to set up static IP!
Do you see /etc/dhcpcd.conf?
No.
It no longer exists
In article <ugpdsv$3r2oj$2@dont-email.me>,
The Natural Philosopher <tnp@invalid.invalid> wrote:
On 18/10/2023 20:13, Bob Latham wrote:
In article <86jzrkrknw.fsf@building-m.net>,
John <john@building-m.simplistic-anti-spam-measure.net> wrote:
Bob. What eventually worked for me was to
Uninstall network-manager package.
Populate /etc/network/interfaces the same way as always.
Could put some flesh on the bone please?
What do you mean by "populate"? Is this an install process or
just copying files and directories from a bullseye build?
What do you do about the missing '/etc/dhcpcd.conf' which is
where I've always set statics in the past?
1. Ignore missing '/etc/dhcpcd.conf'
I understand that. :-)
2. CREATE /etc/network/interfaces
I don't understand that!
That *file* already exists in bookworm and it's exactly the same as
in bullseye ???
But on boot it seems to vanish, but I have a static address
Ah. something has created this
/etc/network/interfaces.d/eth0
allow-hotplug eth0
iface eth0 inet static
address 192.168.0.101
network 192.168.0.0
netmask 255.255.255.0
gateway 192.168.0.254
There must be more to it than that, there has to be. Where did your
pi learn what static address you wanted to put in the that file???
I suspect I'm not understanding (in this context) words like
'populate' and 'create'. I cannot create something that already
exists.
Sorry to be so thick.
Bob.
In article <5af5b94fa0bob@sick-of-spam.invalid>,
Bob Latham <bob@sick-of-spam.invalid> wrote:
In article <ugpdsv$3r2oj$2@dont-email.me>,
The Natural Philosopher <tnp@invalid.invalid> wrote:
[Snip]
Bob. What eventually worked for me was to
1. Ignore missing '/etc/dhcpcd.conf'
I understand that. :-)
2. CREATE /etc/network/interfaces
I don't understand that!
That *file* already exists in bookworm and it's exactly the same as
in bullseye ???
But on boot it seems to vanish, but I have a static address
Ah. something has created this
/etc/network/interfaces.d/eth0
allow-hotplug eth0
iface eth0 inet static
address 192.168.0.101
network 192.168.0.0
netmask 255.255.255.0
gateway 192.168.0.254
I've done some googling and been successful for once !!!
https://www.abelectronics.co.uk/kb/article/31/set-a-static-ip-address-on-raspberry-pi-os-bookworm
It says create a file /etc/network/interfaces.d/eth0 put all the data
above in there yourself. I did that and only that. It worked.
I don't know how yours created the file for you.
Bob.
On 19/10/2023 10:23, Bob Latham wrote:
Bob. What eventually worked for me was to
1. Ignore missing '/etc/dhcpcd.conf'
I understand that. :-)
2. CREATE /etc/network/interfaces
I don't understand that!
That *file* already exists in bookworm and it's exactly the same
as in bullseye ???
It didn't exist in my installation.
Did you use a GUI tool - i.e. Network manager - to set up
networking?
It is possible that that would have created it.
I am running with no monitor and keyboard at all.
Well the discussion was about the 'latest and greatest' - i.e. Bookworm.
I am sorry if I didnt make that clear.
In article (Dans l'article) <ugqvkv$9h41$2@dont-email.me>, The Natural Philosopher <tnp@invalid.invalid> wrote (écrivait) :
Well the discussion was about the 'latest and greatest' - i.e. Bookworm.
I am sorry if I didnt make that clear.
No problem.
It's interesting to see the differences with Bullseye.
This will definitely help me during my upgrade.
For my part I still use Bullseye:
$ cat /etc/debian_version
11.7
There is nothing in the "interfaces" file:
$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source /etc/network/interfaces.d/*
But this directory is empty:
$ ls -al /etc/network/interfaces.d/
total 8
drwxr-xr-x 2 root root 4096 4 nov 2020 .
drwxr-xr-x 7 root root 4096 3 mai 02:09 ..
On 18/10/2023 16:54, John wrote:
The Natural Philosopher <tnp@invalid.invalid> writes:I did that and it worked
Trying to configure headless PI4B.
No files exist to set up static IP!
Its all change since the last setup only a month ago
When will these fuckers stop tinkering and decide for once and for ll
how things are to be done!
Help!
Uninstall network-manager package.
Populate /etc/network/interfaces the same way as always.
Reboot for good measure, to make sure all relics of networkmanager have
been purged.
I did this yesterday because networkmanager is written by idiots
(Redhat) and was constantly making my headless Pi drop off the
network. It's been fine since then.
john
I would suggest that having an RS-232 console connection and USB to
Ethernet dongle does make solving a lot of the PiZeroW issues much
easier. My RS-232 cable is soldered to the A+ I can't be bothered moving
it to the PiZeroW hence the use of the A+. I use dhcp to get the IP
address but have the router always provide the same IP address based on
the MAC of the PiZeroW.
Bookworm is a lousy name for a version. Why couldn't they have called it 'Desdemona'
The Natural Philosopher wrote:
Bookworm is a lousy name for a version. Why couldn't they have called
it 'Desdemona'
Because Disney didn't exist in ℂ17 ?
The Natural Philosopher wrote:
Andy Burns wrote:
The Natural Philosopher wrote:
Bookworm is a lousy name for a version. Why couldn't they have
called it 'Desdemona'
Because Disney didn't exist in ℂ17 ?
?Huh?
Debian release names are characters from the Toy Story films, not from Shakespeare plays ...
Debian release names are characters from the Toy Story films, not from Shakespeare plays ...
On Sun, 22 Oct 2023 10:54:04 +0100
Andy Burns <usenet@andyburns.uk> wrote:
Debian release names are characters from the Toy Story films, not from
Shakespeare plays ...
Reminds me of a PPOE (I wonder if anyone will recognise it) where
the machine names were all gemstones. It must have been easy at first, diamond, ruby, emerald ... by the time I turned up for a contract they were down to Gabbro for my workstation and the network admin's bookshelf
contained a thick reference book listing precious and semi-precious stones.
That place convinced me that themed naming schemes were a bad idea, functional and serial number based naming schemes may be boring but they don't run out of steam and they're never confusing.
That admin might have (originally) been me. I remember 'mud' being used.
On Sun, 22 Oct 2023 12:44:49 +0100
The Natural Philosopher <tnp@invalid.invalid> wrote:
That admin might have (originally) been me. I remember 'mud' being used.
BT early 90s ?
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 190:49:40 |
Calls: | 184 |
Calls today: | 1 |
Files: | 5,413 |
Messages: | 222,750 |