What's the easiest way to manually set a RasPiOS host's
IP address? Raspi-config offers DHCP or networkmanager,
but neither invites manual intervention.
What's the easiest way to manually set a RasPiOS host's
IP address? Raspi-config offers DHCP or networkmanager,
but neither invites manual intervention.
I've used DHCP up to now, but want to mess with a wireless
ethernt bridge to see if I can improve my WiFi connectivity.
To do that I need to manually set the Pi address on the wired
side so as to access the setup interface on the bridge.
If anybody's got pointers please post!
Thanks for reading,
bob prohaska
What's the easiest way to manually set a RasPiOS host's
IP address? Raspi-config offers DHCP or networkmanager,
but neither invites manual intervention.
I've used DHCP up to now, but want to mess with a wireless
ethernt bridge to see if I can improve my WiFi connectivity.
To do that I need to manually set the Pi address on the wired
side so as to access the setup interface on the bridge.
If anybody's got pointers please post!
Thanks for reading,
bob prohaska
Knute Johnson <knute2024@585ranch.com> wrote:
What is the path to NetworkManager? It's present if I run it
If you have a desktop use the NetworkManager to set your static IP.
Click on the Up/Down Arrows on the -> Advanced Options -> Edit
Connections, select the wired connection you want to change and then
click the IPv4 tab and set a static IP address.
from the command line, but that doesn't bring up any dialogs,
it only reports that it's running and turns off WiFi 8-(
If you don't have a desktop use nmtui from the command line. It has a
character interface similar to raspi-config. If you need further
instructions on nmtui, post again.
Nmtui seems closer to what I was looking for. Basically I need to
set a special IP, connect the bridge, log into the bridge and set
it up using a browser, then either set a static IP or use DHCP.
I think you've got me on the correct foot, thank you!
bob prohaska
If you have a desktop use the NetworkManager to set your static IP.
Click on the Up/Down Arrows on the -> Advanced Options -> Edit
Connections, select the wired connection you want to change and then
click the IPv4 tab and set a static IP address.
If you don't have a desktop use nmtui from the command line. It has a character interface similar to raspi-config. If you need further instructions on nmtui, post again.
Do you have a desktop? A graphical display? NetworkManager is in the
upper right corner. You open it by clicking on the up and down blue
arrows. If you don't have a desktop see below:
What's the easiest way to manually set a RasPiOS host's
IP address? Raspi-config offers DHCP or networkmanager,
but neither invites manual intervention.
What's the easiest way to manually set a RasPiOS host's IP address? Raspi-config offers DHCP or networkmanager,
but neither invites manual intervention.
[replying to lawrence]
The Pi in question is running a default RasPiOS version. Systemd
shows up in dmesg output, but nothing from system-network.
Here's the experiment I'd like to try:
Right now, wlan0 comes up using DHCP and connects to my WiFi router,
giving the usual net connectivity, which I'd like to keep active.
At the same time, I'd like to enable a second connection using an ethernet-to-WiFi bridge on eth0 using something like
auto eth0
iface eth0 inet static
address 192.168.1.8/24
gateway 192.168.1.254
Is that all it takes? Presently both /etc/network/interfaces
and /etc/network/interfaces.d are empty.
The plan is to bring up both interfaces, then turn off internal
WiFi to see if eth0 is working. Both use the same default route.
I'm simply trying to figure out if the bridge and its antenna can
be situated for better throughput than the Pi4 internal antenna.
Thanks very much for posting!
bob prohaska
At the same time, I'd like to enable a second connection using an ethernet-to-WiFi bridge on eth0 using something like
auto eth0
iface eth0 inet static
address 192.168.1.8/24
gateway 192.168.1.254
Is that all it takes? Presently both /etc/network/interfaces
and /etc/network/interfaces.d are empty.
just adding stuff to /etc/network/interfaces isn't going to do
anything and if you go and install ifupdown it might screw up your
network setup.
On 21/05/2024 05:57, 62hx.1708 wrote:
BookWORM screwed it all up - and not JUST the
networking stuff.
I didn't realise how much until I tried a fresh install on a Pi 5.
I think Deb is now employing Canonical REJECTS who
have totally screwed up the distro to ZERO advantage.
I've no idea who they've employed, but it is going in a direction I
don't want to follow.
If you have a P4 or below you can still get older
versions of Deb/PiOS ... but the P5 won't work
with those.
There is a way around this. If you install the 64 bit version of
Bullseye on a Pi 4, you can install the same set of packages copy your
config files from the 32 bit version, making it work exactly the same.
You then ignore the dire warnings and do an in place upgrade to
Bookworm. That then retains retains the previous style dhcpcd5
networking, and doesn't install Wayland etc.
The card can then be transferred to a Pi 5.
---druck
<bp@www.zefox.net> writes:
At the same time, I'd like to enable a second connection using an
ethernet-to-WiFi bridge on eth0 using something like
auto eth0
iface eth0 inet static
address 192.168.1.8/24
gateway 192.168.1.254
Is that all it takes? Presently both /etc/network/interfaces
and /etc/network/interfaces.d are empty.
Those files are used by ifupdown which is a package you can
install. It's the Debian default even today but I don't think Raspios
follows that. In fact, as I recall, earlier they had a strange
hodgepodge script launched by the DHCP client and then I think they
moved to NetworkManager.
So if you want specific help, always mention Raspios version.
Anyways, just adding stuff to /etc/network/interfaces isn't going to do anything and if you go and install ifupdown it might screw up your
network setup. So I'd work with whatever you have and add the ethernet connection there. Or if it's just for experimentation all you need to do
is to run ifconfig and route or the newer ip commands for same.
On 21/05/2024 05:57, 62hx.1708 wrote:
I think Deb is now employing Canonical REJECTS who
have totally screwed up the distro to ZERO advantage.
I've no idea who they've employed, but it is going in a direction I
don't want to follow.
There is a way around this. If you install the 64 bit version of
Bullseye on a Pi 4, you can install the same set of packages copy your
config files from the 32 bit version, making it work exactly the same.
You then ignore the dire warnings and do an in place upgrade to
Bookworm. That then retains retains the previous style dhcpcd5
networking, and doesn't install Wayland etc.
So if you want specific help, always mention Raspios version.
Well, uname -a reports:
Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
I can't find anything that reports a plain-language name, and unfortunately
<bp@www.zefox.net> writes:
So if you want specific help, always mention Raspios version.
Well, uname -a reports:
Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
cat /etc/issue or lsb_release -a (from lsb-release package.)
So, I guess it's bullseye.
Where does that leave me?
druck <news@druck.org.uk> writes:reason for the palather above, as I've explained before, is despite
There is a way around this. If you install the 64 bit version of
Bullseye on a Pi 4, you can install the same set of packages copy your
config files from the 32 bit version, making it work exactly the same.
You then ignore the dire warnings and do an in place upgrade to
Bookworm. That then retains retains the previous style dhcpcd5
networking, and doesn't install Wayland etc.
??? why not just install bookworm and then adjust it to taste. If you
want ifupdown-style network configuration (which I do) you can just
install it under bookworm, edit /etc/network/interfaces. No need to
take aroundabout routes like installing bullseye and upgrading.
The networking is annoyance but is fixable with too much pain, but the
<bp@www.zefox.net> writes:
So, I guess it's bullseye.
Where does that leave me?
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 https://www.tomshardware.com/how-to/static-ip-raspberry-pi
On 22/05/2024 00:12, Chris Townley wrote:
On 21/05/2024 21:30, duck wrote:
On 21/05/2024 05:57, 62hx.1708 wrote:
BookWORM screwed it all up - and not JUST the
networking stuff.
I didn't realise how much until I tried a fresh install on a Pi 5.
I cannot believe all the carp I am seeing here.
Thank you for your eloquent debate.
When bookworm came out, I did a fresh install on a pi4 - all good
except for a minor glitch with Wayland. Soon fixed and it runs well.
When pi5 arrived, I copied to a USB SSD - all well from day 1. When I
got an Argon ONE V3, with their NVME board it took a couple of goes,
but with some help from the Raspberry forum it was soon well. Sill
good now!
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.
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...
Anssi Saari <anssi.saari@usenet.mail.kapsi.fi> wrote:
<bp@www.zefox.net> writes:
So, I guess it's bullseye.
Where does that leave me?
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
https://www.tomshardware.com/how-to/static-ip-raspberry-pi
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
... I was unable to get it to recognise that I had
installed an alternative Mate desktop ...
Anyways, just adding stuff to /etc/network/interfaces isn't going to do anything and if you go and install ifupdown it might screw up your
network setup.
I think Deb is now employing Canonical REJECTS who have totally
screwed up the distro to ZERO advantage.
I've no idea who they've employed ...
Is it possible that the Pi OS won't support two simultaneous network connections?
On Wed, 22 May 2024 21:57:55 -0000 (UTC), bp wrote:
Is it possible that the Pi OS won't support two simultaneous network
connections
Of course it will. It’s Linux.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 307 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 116:06:26 |
| Calls: | 6,854 |
| Files: | 12,355 |
| Messages: | 5,416,745 |