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.

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

You saw it too

A couple of points:

First, you've got some typo in either your description, or in your config, because you first stated 10.0.0.31 but the file says 10.0.0.30 (see red highlights here)

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

Secondly, when you believe that you're connected to the second Pi by mistake, take a look at the ifconfig -a output, and examine the HW address (also known as the MAC address):

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

According to the output that you pasted, this MAC address is identical for Pi1 and Pi 2's network interface. This is not allowed. You may have cheap devices that (incorrectly) have the same MAC address. The manufacturer ought to supply them with totally unique numbers. If they are not unique, you cannot use them on the same network.

The driver or some utility for your network interface may have some way of programming a new MAC address, but I don't know anything about this area.

Wow you're right. I'll see what I can do about complaining to Amazon. They usually have excellent customer service.

Thanks everybody for your help!

Um, yeah some rely on the fact it's unlikely that some one will have a load of these modules

Any way before you rush off you can try setting the MAC manually which may be easier than sending the whole lot back

Check the manuals but the command will be something like

ifconfig eth0 hw ether <mac address>

obviously as root

set the MACs to different values and you should be OK

Also you will need this to run each time you boot or insert the NIC

Problemchildis correct. Try to force the mac address read How to set the mac address from /etc/network/interfaces in Debian | YourITronics .

When you load the network information the device should use the hwaddress. But be careful not to dupicate any address . I would change the last part from 01-ff range.

Like:

hwaddress ether 00:e0:4c:53:44:68 ### -> next one 00:e0:4c:53:44:78 etc.

Clem