• Re: Setting a manual IP address

    From Chris Townley@3:770/3 to bp@www.zefox.net on Tue May 14 20:16:08 2024
    On 14/05/2024 19:44, bp@www.zefox.net wrote:
    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


    the best way if you have an internet router is to enable DHCP (the
    default) and set the fixed IP on the router

    --
    Chris

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From bp@www.zefox.net@3:770/3 to All on Tue May 14 18:44:48 2024
    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

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Ahem A Rivet's Shot@3:770/3 to bp@www.zefox.net on Tue May 14 20:54:39 2024
    On Tue, 14 May 2024 18:44:48 -0000 (UTC)
    <bp@www.zefox.net> wrote:

    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.

    This may help:

    https://www.tomshardware.com/how-to/static-ip-raspberry-pi

    --
    Steve O'Hara-Smith
    Odds and Ends at http://www.sohara.org/
    For forms of government let fools contest
    Whate're is best administered is best - Alexander Pope

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Knute Johnson@3:770/3 to bp@www.zefox.net on Tue May 14 15:31:48 2024
    On 5/14/24 13:44, bp@www.zefox.net wrote:
    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


    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.

    --

    Knute Johnson

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Knute Johnson@3:770/3 to bp@www.zefox.net on Tue May 14 16:37:08 2024
    On 5/14/24 16:30, bp@www.zefox.net wrote:
    Knute Johnson <knute2024@585ranch.com> wrote:

    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.

    What is the path to NetworkManager? It's present if I run it
    from the command line, but that doesn't bring up any dialogs,
    it only reports that it's running and turns off WiFi 8-(

    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:

    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


    --

    Knute Johnson

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From bp@www.zefox.net@3:770/3 to Knute Johnson on Tue May 14 21:30:31 2024
    Knute Johnson <knute2024@585ranch.com> wrote:

    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.

    What is the path to NetworkManager? It's present if I run it
    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

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From bp@www.zefox.net@3:770/3 to Knute Johnson on Tue May 14 23:48:41 2024
    Knute Johnson <knute2024@585ranch.com> wrote:

    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:

    Ok, got it 8-) I was looking under the raspberry icon at top left...

    Thank you!

    bob prohaska

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From The Natural Philosopher@3:770/3 to bp@www.zefox.net on Wed May 15 11:15:00 2024
    On 14/05/2024 19:44, bp@www.zefox.net wrote:
    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.

    Depends on the release. Every new release reinvents the networking wheel.
    There is a CLI interface to network manager (nmcli) that works pretty well

    I stuck to that.


    --
    "If you don’t read the news paper, you are un-informed. If you read the
    news paper, you are mis-informed."

    Mark Twain

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Lawrence D'Oliveiro@3:770/3 to All on Sat May 18 23:45:13 2024
    On Tue, 14 May 2024 18:44:48 -0000 (UTC), bp wrote:

    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.

    The traditional Debian way is to hand-edit /etc/network/interfaces. If an interface entry begins “interface «name» inet static”, then you can follow
    them with explicit settings, and NetworkManager should not touch them.

    If you are using systemd-network (as Ubuntu does), then it is suffices to
    put config files named “«n»-«name».network»” in /etc/systemd/network, one
    for each interface, with manual settings in them. The format for these is documented in systemd.network(5).

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From bp@www.zefox.net@3:770/3 to All on Sun May 19 17:46:28 2024
    [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

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From 62hx.1708@3:770/3 to bp@www.zefox.net on Tue May 21 00:57:37 2024
    On 5/19/24 1:46 PM, bp@www.zefox.net wrote:
    [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


    BookWORM screwed it all up - and not JUST the
    networking stuff.

    Some months ago I posted some templates for the new,
    pointless, annoying, networking defs.

    I think Deb is now employing Canonical REJECTS who
    have totally screwed up the distro to ZERO advantage.

    On other units I've switched to Manjaro - but, to
    date, there's no Manjaro for the P5. Depending on
    what options you need, I'd suggest BeeLink and BMax
    mini-boxes instead of PIs.

    The trashing of Debian is BAD ... as it's used as
    the foundation for SO many other (formerly) useful
    distros.

    If you have a P4 or below you can still get older
    versions of Deb/PiOS ... but the P5 won't work
    with those.

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Anssi Saari@3:770/3 to bp@www.zefox.net on Tue May 21 11:52:12 2024
    <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.

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From The Natural Philosopher@3:770/3 to Anssi Saari on Tue May 21 11:37:16 2024
    On 21/05/2024 09:52, Anssi Saari wrote:
    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.

    Yes. The latest release of PIOS (Bookworm) has many slight 'issues' and
    seems less well understood and documented and its all changed yet again.
    The reliable way to get fixed IP is to use network manager if you have a
    GUI and nmcli if you dont.

    This is how its all set up, and although there may well be ways to fox
    it, you always run the risk that upgrades may overwrite the changes you
    made and fuck everything up.

    I can say that on my Pi4/Bookworm the nmcli route worked perfectly


    --
    I would rather have questions that cannot be answered...
    ...than to have answers that cannot be questioned

    Richard Feynman

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From druck@3:770/3 to All on Tue May 21 21:30:38 2024
    T24gMjEvMDUvMjAyNCAwNTo1NywgNjJoeC4xNzA4IHdyb3RlOg0KPiAgwqAgQm9va1dPUk0g c2NyZXdlZCBpdCBhbGwgdXAgLSBhbmQgbm90IEpVU1QgdGhlDQo+ICDCoCBuZXR3b3JraW5n IHN0dWZmLg0KDQpJIGRpZG4ndCByZWFsaXNlIGhvdyBtdWNoIHVudGlsIEkgdHJpZWQgYSBm cmVzaCBpbnN0YWxsIG9uIGEgUGkgNS4NCg0KPiAgwqAgSSB0aGluayBEZWIgaXMgbm93IGVt cGxveWluZyBDYW5vbmljYWwgUkVKRUNUUyB3aG8NCj4gIMKgIGhhdmUgdG90YWxseSBzY3Jl d2VkIHVwIHRoZSBkaXN0cm8gdG8gWkVSTyBhZHZhbnRhZ2UuDQoNCkkndmUgbm8gaWRlYSB3 aG8gdGhleSd2ZSBlbXBsb3llZCwgYnV0IGl0IGlzIGdvaW5nIGluIGEgZGlyZWN0aW9uIEkg DQpkb24ndCB3YW50IHRvIGZvbGxvdy4NCg0KPiAgwqAgSWYgeW91IGhhdmUgYSBQNCBvciBi ZWxvdyB5b3UgY2FuIHN0aWxsIGdldCBvbGRlcg0KPiAgwqAgdmVyc2lvbnMgb2YgRGViL1Bp T1MgLi4uIGJ1dCB0aGUgUDUgd29uJ3Qgd29yaw0KPiAgwqAgd2l0aCB0aG9zZS4NCg0KVGhl cmUgaXMgYSB3YXkgYXJvdW5kIHRoaXMuIElmIHlvdSBpbnN0YWxsIHRoZSA2NCBiaXQgdmVy c2lvbiBvZiANCkJ1bGxzZXllIG9uIGEgUGkgNCwgeW91IGNhbiBpbnN0YWxsIHRoZSBzYW1l IHNldCBvZiBwYWNrYWdlcyBjb3B5IHlvdXIgDQpjb25maWcgZmlsZXMgZnJvbSB0aGUgMzIg Yml0IHZlcnNpb24sIG1ha2luZyBpdCB3b3JrIGV4YWN0bHkgdGhlIHNhbWUuDQoNCllvdSB0 aGVuIGlnbm9yZSB0aGUgZGlyZSB3YXJuaW5ncyBhbmQgZG8gYW4gaW4gcGxhY2UgdXBncmFk ZSB0byANCkJvb2t3b3JtLiBUaGF0IHRoZW4gcmV0YWlucyByZXRhaW5zIHRoZSBwcmV2aW91 cyBzdHlsZSBkaGNwY2Q1IA0KbmV0d29ya2luZywgYW5kIGRvZXNuJ3QgaW5zdGFsbCBXYXls YW5kIGV0Yy4NCg0KVGhlIGNhcmQgY2FuIHRoZW4gYmUgdHJhbnNmZXJyZWQgdG8gYSBQaSA1 Lg0KDQotLS1kcnVjaw0K

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Chris Townley@3:770/3 to duck on Wed May 22 00:12:25 2024
    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 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

    I cannot believe all the carp I am seeing here.

    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!

    --
    Chris

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From bp@www.zefox.net@3:770/3 to Anssi Saari on Wed May 22 00:47:59 2024
    Anssi Saari <anssi.saari@usenet.mail.kapsi.fi> wrote:
    <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.

    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 don't remember what was installed/upgraded since the system was set up, apparently in 2022. The "about raspi-config" menu metions:
    Version: 20231012~bullseye but I'm not entirely sure that's
    the system name. If there's an "about this computer" command hidden
    somewhere please clue me in.


    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.

    The intent for now is just experimentation, but internal WiFi performance
    has degraded noticeably in the last couple of years, I think because of interference. If adding an ethernet-wifi bridge with a bigger, moveable
    antenna helps I might want to make it permanent.

    Thanks for the cautionary advice

    bob prohaska

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Richard Kettlewell@3:770/3 to druck on Wed May 22 09:05:27 2024
    druck <news@druck.org.uk> writes:
    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.

    Debian doesn’t employ anyone, it’s all volunteers.

    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.

    --
    https://www.greenend.org.uk/rjk/

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Anssi Saari@3:770/3 to bp@www.zefox.net on Wed May 22 12:07:30 2024
    <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.)

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From bp@www.zefox.net@3:770/3 to Anssi Saari on Wed May 22 16:28:58 2024
    Anssi Saari <anssi.saari@usenet.mail.kapsi.fi> wrote:
    <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.)

    /etc/issue is not more verbose than uname -a, but lsb_release says: Description: Debian GNU/Linux 11 (bullseye)

    So, I guess it's bullseye.

    Where does that leave me?

    Thanks for writing,

    bob prohaska

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From I R A Darth Aggie@3:770/3 to v2jfbv$r9d0$1@dont-email.me on Wed May 22 16:47:45 2024
    On Wed, 22 May 2024 00:47:59 -0000 (UTC),
    <bp@www.zefox.net> <bp@www.zefox.net>, in
    <v2jfbv$r9d0$1@dont-email.me> wrote:

    I can't find anything that reports a plain-language name, and unfortunately

    lsb_release -a

    Reports the following on my intel desktop:

    No LSB modules are available.
    Distributor ID: Debian
    Description: Debian GNU/Linux trixie/sid
    Release: n/a
    Codename: trixie

    --
    Consulting Minister for Consultants, DNRC
    I can please only one person per day. Today is not your day. Tomorrow
    isn't looking good, either.
    I am BOFH. Resistance is futile. Your network will be assimilated.

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Anssi Saari@3:770/3 to bp@www.zefox.net on Wed May 22 22:03:10 2024
    <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

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From druck@3:770/3 to Richard Kettlewell on Wed May 22 21:36:59 2024
    On 22/05/2024 09:05, Richard Kettlewell wrote:
    druck <news@druck.org.uk> writes:
    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
    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

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From druck@3:770/3 to All on Wed May 22 21:30:16 2024
    T24gMjIvMDUvMjAyNCAwMDoxMiwgQ2hyaXMgVG93bmxleSB3cm90ZToNCj4gT24gMjEvMDUv MjAyNCAyMTozMCwgZHVjayB3cm90ZToNCj4+IE9uIDIxLzA1LzIwMjQgMDU6NTcsIDYyaHgu MTcwOCB3cm90ZToNCj4+PiDCoMKgIEJvb2tXT1JNIHNjcmV3ZWQgaXQgYWxsIHVwIC0gYW5k IG5vdCBKVVNUIHRoZQ0KPj4+IMKgwqAgbmV0d29ya2luZyBzdHVmZi4NCj4+DQo+PiBJIGRp ZG4ndCByZWFsaXNlIGhvdyBtdWNoIHVudGlsIEkgdHJpZWQgYSBmcmVzaCBpbnN0YWxsIG9u IGEgUGkgNS4NCg0KPiBJIGNhbm5vdCBiZWxpZXZlIGFsbCB0aGUgY2FycCBJIGFtIHNlZWlu ZyBoZXJlLg0KDQpUaGFuayB5b3UgZm9yIHlvdXIgZWxvcXVlbnQgZGViYXRlLg0KDQo+IFdo ZW4gYm9va3dvcm0gY2FtZSBvdXQsIEkgZGlkIGEgZnJlc2ggaW5zdGFsbCBvbiBhIHBpNCAt IGFsbCBnb29kIGV4Y2VwdCANCj4gZm9yIGEgbWlub3IgZ2xpdGNoIHdpdGggV2F5bGFuZC4g U29vbiBmaXhlZCBhbmQgaXQgcnVucyB3ZWxsLg0KPiANCj4gV2hlbiBwaTUgYXJyaXZlZCwg SSBjb3BpZWQgdG8gYSBVU0IgU1NEIC0gYWxsIHdlbGwgZnJvbSBkYXkgMS4gV2hlbiBJIA0K PiBnb3QgYW4gQXJnb24gT05FIFYzLCB3aXRoIHRoZWlyIE5WTUUgYm9hcmQgaXQgdG9vayBh IGNvdXBsZSBvZiBnb2VzLCBidXQgDQo+IHdpdGggc29tZSBoZWxwIGZyb20gdGhlIFJhc3Bi ZXJyeSBmb3J1bSBpdCB3YXMgc29vbiB3ZWxsLiBTaWxsIGdvb2Qgbm93IQ0KPiANCg0KV2Vs bCBicmF2bywgaXQgd29ya2VkIGZvciB5b3UuDQoNClNvbWUgb2YgdXMgYXJlIHJ1bm5pbmcg ZmxlZXRzIG9mIGRvemVucyBvZiBSYXNwYmVycnkgUGkncyBvZiBtdWx0aXBsZSANCmdlbmVy YXRpb25zLCBhbmQgaGF2aW5nIGFuIE9TIHVwZ3JhZGUgcmVxdWlyZWQgYnkgdGhlIGxhdGVz dCBQaSBtb2RlbCANCndoaWNoIHdvcmtzIHZlcnkgZGlmZmVyZW50IGluIHJlc3BlY3QgdG8g bmV0d29ya2luZyBhbmQgdmlkZW8sIGlzIGEgDQptYXNzaXZlIHBhaW4gaW4gdGhlIGFyc2Uu DQoNClRoZSBvcHRpb25zIGFyZSB0byBwdXNoIHRoZSBPUyB1cGdyYWRlIHRvIGFsbCBtYWNo aW5lcyBhbmQgY2hhbmdlIHRoZSANCndheSBvZiB3b3JraW5nLCBvciBmaW5kIG91dCBob3cg dG8gbWFrZSB0aGUgbmV3IFBpIHdvcmsgY29uc2lzdGVudGx5IA0Kd2l0aCByZXN0IG9mIHRo ZSBmbGVldCAtIHdoaWNoIGlzIHdoYXQgSSBoYXZlIG9wdGVkIGZvci4NCg0KLS0tZHJ1Y2sN
    Cg==

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From bp@www.zefox.net@3:770/3 to Anssi Saari on Wed May 22 21:57:55 2024
    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

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Chris Townley@3:770/3 to druck on Thu May 23 00:03:22 2024
    On 22/05/2024 21:30, druck wrote:
    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.


    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.

    --
    Chris

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Anssi Saari@3:770/3 to bp@www.zefox.net on Thu May 23 11:29:48 2024
    <bp@www.zefox.net> writes:

    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...

    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."

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From The Natural Philosopher@3:770/3 to bp@www.zefox.net on Thu May 23 10:55:30 2024
    On 22/05/2024 22:57, bp@www.zefox.net wrote:
    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

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



    --
    "An intellectual is a person knowledgeable in one field who speaks out
    only in others...”

    Tom Wolfe

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Lawrence D'Oliveiro@3:770/3 to druck on Fri May 24 23:01:51 2024
    On Wed, 22 May 2024 21:36:59 +0100, druck wrote:

    ... I was unable to get it to recognise that I had
    installed an alternative Mate desktop ...

    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.

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Lawrence D'Oliveiro@3:770/3 to All on Fri May 24 22:59:32 2024
    On Tue, 21 May 2024 00:57:37 -0400, 62hx.1708 wrote:

    I think Deb is now employing Canonical REJECTS who have totally
    screwed up the distro to ZERO advantage.

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

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Lawrence D'Oliveiro@3:770/3 to Anssi Saari on Fri May 24 22:58:17 2024
    On Tue, 21 May 2024 11:52:12 +0300, Anssi Saari wrote:

    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.

    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.

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Lawrence D'Oliveiro@3:770/3 to druck on Fri May 24 23:00:19 2024
    On Tue, 21 May 2024 21:30:38 +0100, druck wrote:

    I've no idea who they've employed ...

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

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Lawrence D'Oliveiro@3:770/3 to All on Sat May 25 00:43:57 2024
    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.

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From bp@www.zefox.net@3:770/3 to Lawrence D'Oliveiro on Sat May 25 01:53:36 2024
    Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
    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.

    It appears that the instructions at

    https://www.jeffgeerling.com/blog/2024/set-static-ip-address-nmtui-on-raspberry-pi-os-12-bookworm

    might work, even though I'm using bullseye, not bookworm. That's to say
    the commands nmcli and nmtui are reconized by the system and seem to run.

    I'll tinker with them a bit further and return with more questions.

    Thanks for replying!

    bob prohaska

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)