Raspberry Pi Zero Ethernet Problem

That is normal, because most likely your home network is something like 192.168.0.x or 192.168.1.x and you can't connect something with 10.0.0.x to it (assuming you're plugging into the switch-ports on the back of your router).

Something else is setting this (your /etc/network/interfaces file is set up to allow this), what do you observe if you use the desktop GUI to access the wireless network settings?

Also, by the way, this is quite an inefficient way to perform parallel processing (anything else would be cheaper, even a single Pi 3 with 4 x Pi 3 cores are cheaper than 4 x (Pi zero+USB-Eth+SDcard), and

better performing, but I'm guessing there is reasons for it.

He is trying to test distributed code out before moving to a bigger environment.

Clem

Out of interest, doesn't this set up cater for a manual interface setup?

If you are just issuing a "dhcpd" then I would assume it uses this conf file to check  what it needs to do which isn't a lot.

I would initially try forcing it using dhcpd<interface> ....."dhcpd eth0" in t his case

if not use ifconfig to set up eth0 manually and put it on the same network as the working RPI then see if you can at least ping that !

Yes you are right Shabaz... That said if you want to do something like  this you would be better off spinning up a few VM's on your Laptop or what ever than getting all the Zeros involved and thus saving you the Networking costs if y  ou are trying to save cash

Yes the reason that I'm doing things this way is because I already had the raspberry Pi's laying around, and have gotten into a little trouble "wasting resources" on the university cluster with trying to test my distributed code. All I had to purchase that I didn't already own for this were the Ethernet to Micro USB connectors. This project won't be doing any real "hefty" computation, I'm just hoping to test code on it so I no longer upset the people who run my university's cluster.

Using your suggestions I was able to ssh into the Pi zero's. However, now that I'm able to ssh into them, I decided to try using my ethernet switch that has been laying around in my box of toys to get them all on the network. For some reason they are all being assigned the same IP address. I tried editing the /etc/network/interfaces file to manually assign different static IP addresses, but they are still all being assigned the IP address defined in /etc/network/interfaces of whichever Pi I boot first. When I'm ssh'ed into a Pi, after a few seconds I get an error message saying "Broken Pipe." I have to remove the IP address from my list of known hosts, and then I can ssh into a Pi zero again, but when I go back in it is often a different Pi zero. It seems that they are fighting for the IP address, even though they are different machines being connected from separate ports of the ethernet switch at the same time.

For reference this is what I put in the /etc/network/interfaces file

iface eth0 inet static

     address 10.0.0.XX

     netmask 255.255.255.0

     network 10.0.0.0

     broadcast 10.0.0.255

     gateway 10.0.0.1

The Ethernet port is at the lower level(physical) and has not relation to IP address(at the TC/IP layer). See https://en.wikibooks.org/wiki/A-level_Computing/AQA/Computer_Components,_The_Stored_Program_Concept_and_the_Internet/Str…  &  https://en.wikipedia.org/wiki/OSI_model to understand.

Clem

This doesn't make sense unfortunately.

Get a single one working. No point experimenting with all 4 while you still have issues with a single one.

Once you're at the stage that you can successfully use a single Pi plugged into your switch, then work on the second one.

By "successfully use a single Pi" I mean you need to confirm that you can SSH into your Pi using your chosen IP address, see no unexpected behaviour like the broken pipe and see no issues with power supply fails/unintended reboots etc.

Once all that works, add a second Pi, and take typical prudent engineering steps like using a separate power supply, confirming both function before adding a third, etc. After it all works, you can optimise to reduce supplies, etc.

I should have been more specific in my last post. That is exactly what I'm doing. With any single pi plugged in I can successfully ssh into the Pi and stay logged in as long as I please. There are no reboots, and no "Broken Pipe" error messages. When I plug in a second Pi with a separate power source, it gets assigned the same IP address as the Pi that was already active and I had already been ssh'ed into. When the second Pi gets plugged in and assigned the same IP address as the first Pi, I get kicked out of ssh with the "Broken Pipe" error message, and when I attempt to ssh back in I get this message:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!

Someone could be eavesdropping on you right now (man-in-the-middle attack)!

It is also possible that a host key has just been changed.

The fingerprint for the ECDSA key sent by the remote host is

SHA256:Zl9WWVSRwUpIGG0k+y7I6nMUTL7/DUviVuYdiW3kGy0.

Please contact your system administrator.

Add correct host key in /home/william/.ssh/known_hosts to get rid of this message.

Offending ECDSA key in /home/william/.ssh/known_hosts:9

  remove with:

  ssh-keygen -f "/home/william/.ssh/known_hosts" -R 10.0.0.31

ECDSA host key for 10.0.0.31 has changed and you have requested strict checking.

Host key verification failed.

After seeing this error message I remove 10.0.0.31 from my known hosts and try to ssh to the same IP. After deleting this from the known hosts and using the same IP for ssh, I can successfully access a Pi again but it's the second Pi that was plugged in. With both of them connected, I can't stay logged into either Pi very long, before I get kicked out by the "Broken Pipe" error message. Every time I get the broken pipe message I see the same "REMOTE HOST IDENTIFICATION HAS CHANGED" error message, and it alternates which Pi I can access by using "ssh pi@10.0.0.31"

Are you assigning a different ip address for each of the Pi's? If you clone them, then you must change each one before a reboot.

Clem