After updating the new Raspberry Pi imager, as the message says, I have not been able to get the new node to work. I have deleted that version and gone back to 1.8.5 again, deleting and reinitializing the parameters, but I still have the same problem. It keeps breaking the network every time I start the new node.
Sounds like there are still parameters from the old install hanging around in the registry.
Perhaps try a uninstall, reboot, then reinstall the desired version.
You can also try the new (but not yet available from www.raspberrypi.com) version of the Raspberry Pi Imager that looks to have a fix.
You can download the latest from the GitHub assets at rpi-imager: Release v1.9.5.
I have tried the new version that eliminates the bug, deleting and restarting the profiles and with a new PC and using Wi-Fi instead of a cable, but the same result.
Maybe you need to expand on what's not working? Is the Raspberry Pi not joining your Wi-Fi network? Are you not able to get to the web landing page? Are you not able to ssh to the Pi?
2 Likes
Every time I connect my new node to another Raspberry, it blocks and disconnects the connection of another node that I have been running for a long time. When I disconnect it from the network, be it WiFi or the new node, the old node reconnects. I thought it could be that the new node takes the same Mac as the previous one that is running on the same LAN network.
This sounds like a config issue with network addresses or node#'s conflicting.
Start with the network IP and make sure they are 'ALL' unique addresses.
Then the node numbers.
If you copied a sd card for a starting point on the new system, you likely missed some setting that made it it's unique self.
Yes, sounds like either trying to reuse a node # or trying to use the same UDP port for both nodes - i.e. both are using UDP/4569.
I thought that at first, but the active node uses 4570, while the one I tried to install uses 4569 by default, so I ruled out that source of the problem.