Seems redoing the head pi's Ubuntu install and setting up NetworkManager and then doing DHCP server stuff worked! I see the second raspberry pi when doing `dhcp-lease-list` and can connect to it! Woo hoo!
The second pi seems quite slow when trying to sudo apt upgrade/update... I'm hoping that's just my internet rather than being extremely slow due to it going through the head pi...
I also can't use pi@pi1.local when already ssh'd into the head pi, "ssh: Could not resolve hostname pi1.local: Temporary failure in name resolution" so I'll figure out how to do that extra name server stuff tomorrow. Using the IP assigned by the dhcp server to connect works as expected.
I've also recorded all the commands and steps I've taken to set up the head node and the second node, so I can mess around and try other things and reset everything and easily get back to this point, so I'll check out that IP masquerade thing tomorrow.
Thank you very much! o7
The second pi seems quite slow when trying to sudo apt upgrade/update... I'm hoping that's just my internet rather than being extremely slow due to it going through the head pi...
I also can't use pi@pi1.local when already ssh'd into the head pi, "ssh: Could not resolve hostname pi1.local: Temporary failure in name resolution" so I'll figure out how to do that extra name server stuff tomorrow. Using the IP assigned by the dhcp server to connect works as expected.
I've also recorded all the commands and steps I've taken to set up the head node and the second node, so I can mess around and try other things and reset everything and easily get back to this point, so I'll check out that IP masquerade thing tomorrow.
Thank you very much! o7
Statistics: Posted by CMDR-JohnAlex — Wed Oct 30, 2024 2:14 am
