Raspberry Pi Zero Ethernet Problem

Just a quick check is the otg  plugged to a powered hub with enough current? Mine was not because I needed more than 100 mA which was not provided as my picture setup showed.

Clem

Actually I am having a lot of trouble with my USB hub, and I'll be purchasing another one. However when I plug the ethernet into one of the Pi zero's ports and the power into the other, it still doesn't show up on the network. To be clear I plugged the ethernet straight from my router to the Pi zero and used the other port to power on the zero. With this setup I probed the network from my laptop and found no IP for the Raspberry Pi.

That being said I wrote a little shell script to sleep 2m, then run the commands that you suggested I post the output of. Since I'm having trouble with the USB hub, I photographed the output of the three commands you suggested I try. They are as follows:

A little unorthodox, I know, but it's the best I can think to do without the functional USB hub. Hopefully I'll have that new hub tomorrow or Monday.

It looks like you've got a (most likely static) IP - 10.0.0.30.

What is your /etc/network/interfaces file contents?

I have the same chipset  as you do. Mine did not work until I had enough power(amps) > 100 mA. I used the inside micro for Ethernet and not the outside one(it is power only).

Clem

Okay I see what you mean about the ip address, however when I try to ssh into 10.0.0.30 from my laptop the connection times out, and when I probe the network to see all active IP addresses 10.0.0.30 doesn't appear. Here is my /etc/network/interfaces file:

I have tried running dhcpcd eth0 but that hasn't solved the problem.

The power source shouldn't matter if I have the ethernet plugged straight into the Pi's inner usb port, correct? Thanks for trying the alternate method.

Yes that is true, unless the power supply to the Raspberry Pi zero is nominal in current. Can you get the actual voltage/amperage in front of zero?

Thanks,

Clem

Yeah my power source is five volts and two amps.

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 !

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 !

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

Do you have a router connected? If so, unplug it, just to eliminate the possibility that DHCP is in (incorrect) operation.

Just use the switch for now.

Also, there is no way for a Linux box to look inside another Linux box to examine the IP addressing configuration and then self-configure with that configuration. No code or protocol exists to do that as far as I'm aware.

Can you paste or attach the entire content of your /etc/network/interfaces file, for the first Pi, and for the second Pi? I get that just the IP address will be different, but it will be good to see it in detail.

Also, a quick photo showing the router, Pi's etc would be great too. I can't see how it will help just yet, but I'm clutching at straws since your problem is bizarre.

By the way, out of curiosity, please can you paste the output of:

ifconfig -a 

For the Pi before and after you plug the second one in, and when then second pi takes over as you say.

Something like:

Step 1. Only Pi A connected

Step 2. Plug in Pi B

Step 3. wait until broken pipe and then delete from known_hosts and then reconnect

Step 4.  unplug pi A

After each step, record the following:

ssh pi@ip_address_A

cat /etc/hostname    (so we can see exactly which Pi you're connected to)

ifconfig -a

ssh pi@ip_address_B

cat /etc/hostname

ifconfig -a

Just so you know, for some reason the Pi that I'm trying to set to IP address 10.0.0.30 is for some reason getting assigned 10.0.0.31. Also I have an arris 2 in 1 modem/router, so there's no way to take my router out of the equation. But yes Clem I do have a router being used. That being said, here's all the output that you requested:

The contents of /etc/network/interfaces on Pi number 1 (ssh pi@10.0.0.31 with cat /etc/hostname showing pizero1):

# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd

# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:

source-directory /etc/network/interfaces.d

auto lo

iface lo inet loopback

iface eth0 inet static

  address 10.0.0.30

  netmask 255.255.255.0

  network 10.0.0.0

  broadcast 10.0.0.255

  gateway 10.0.0.1

allow-hotplug wlan0

iface wlan0 inet manual

    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

allow-hotplug wlan1

iface wlan1 inet manual

    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

The contents of /etc/network/interfaces on Pi number 2 (ssh pi@10.0.0.31 with cat /etc/hostname showing raspberrypi):

# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd

# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:

source-directory /etc/network/interfaces.d

auto lo

iface lo inet loopback

iface eth0 inet static

        address 10.0.0.31

        netmask 255.255.255.0

        network 10.0.0.0

        broadcast 10.0.0.255

        gateway 10.0.0.1

allow-hotplug wlan0

iface wlan0 inet manual

    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

allow-hotplug wlan1

iface wlan1 inet manual

    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

The results of ifconfig -a with only Pi number 1 plugged in (ssh pi@10.0.0.31 with cat /etc/hostname showing pizero1):

eth0      Link encap:Ethernet  HWaddr 00:e0:4c:53:44:58

          inet addr:10.0.0.31  Bcast:10.0.0.255  Mask:255.255.255.0

          inet6 addr: fe80::26a5:b629:f948:92c3/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:204 errors:1 dropped:1 overruns:1 frame:2

          TX packets:164 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:19673 (19.2 KiB)  TX bytes:23792 (23.2 KiB)

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:200 errors:0 dropped:0 overruns:0 frame:0

          TX packets:200 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:16656 (16.2 KiB)  TX bytes:16656 (16.2 KiB)

The output of ifconfig -a on Pi number 1 after plugging in Pi number 2 (ssh pi@10.0.0.31 with cat /etc/hostname showing pizero1):

eth0      Link encap:Ethernet  HWaddr 00:e0:4c:53:44:58

          inet addr:10.0.0.31  Bcast:10.0.0.255  Mask:255.255.255.0

          inet6 addr: fe80::26a5:b629:f948:92c3/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1134 errors:1 dropped:3 overruns:1 frame:2

          TX packets:329 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:96791 (94.5 KiB)  TX bytes:42976 (41.9 KiB)

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:200 errors:0 dropped:0 overruns:0 frame:0

          TX packets:200 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:16656 (16.2 KiB)  TX bytes:16656 (16.2 KiB)

The output of ifconfig -a on Pi number 2 after "taking over" with Pi number 1 still plugged in (ssh pi@10.0.0.31 with cat /etc/hostname showing raspberrypi):

eth0      Link encap:Ethernet  HWaddr 00:e0:4c:53:44:58

          inet addr:10.0.0.31  Bcast:10.0.0.255  Mask:255.255.255.0

          inet6 addr: fe80::26a5:b629:f948:92c3/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:3566 errors:0 dropped:0 overruns:0 frame:0

          TX packets:767 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:239048 (233.4 KiB)  TX bytes:101124 (98.7 KiB)

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:200 errors:0 dropped:0 overruns:0 frame:0

          TX packets:200 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:16656 (16.2 KiB)  TX bytes:16656 (16.2 KiB)

The output of ifconfig -a on Pi number 2 after unplugging Pi number 1 (ssh pi@10.0.0.31 with cat /etc/hostname showing rasperrypi):

eth0      Link encap:Ethernet  HWaddr 00:e0:4c:53:44:58

          inet addr:10.0.0.31  Bcast:10.0.0.255  Mask:255.255.255.0

          inet6 addr: fe80::26a5:b629:f948:92c3/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:3618 errors:0 dropped:0 overruns:0 frame:0

          TX packets:793 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:243745 (238.0 KiB)  TX bytes:105906 (103.4 KiB)

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:200 errors:0 dropped:0 overruns:0 frame:0

          TX packets:200 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:16656 (16.2 KiB)  TX bytes:16656 (16.2 KiB)

A picture of my setup:

Where the source of the blue ethernet cable to the ethernet switch is coming straight from the back of the modem/router unit.

Oh my gosh, I see the problem: they all have the same mac address 00:e0:4c:53:44:58 from Amazon.com: uxcell Micro USB to RJ45 Network Card

Which means the Chinese did not care to imprint unique ones for each adapter. I hope you can complain to where you got these.

Clem

shabaz  clem57

That's strange,  eth0 on both are showing the same hardware MAC address HWaddr 00:e0:4c:53:44:58