Clusterhat V2.3 on Pi 3b+ Zeros have no Connection

[Justiinfighter]

I have successfully installed the NAT image on the Pi 3b + and I can successfully control the Pi Zero W's with "Clusterhat on/off", but I can not establish Internet connection to them.

With ipconfig i have have these Output:

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.19.181.254  netmask 255.255.255.0  broadcast 172.19.181.255
        inet6 fe80::b2fd:17a6:fe3b:e4fd  prefixlen 64  scopeid 0x20<link>
        ether 00:22:82:ff:fe:01  txqueuelen 1000  (Ethernet)
        RX packets 492  bytes 25272 (24.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 480  bytes 29912 (29.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.2.133  netmask 255.255.255.0  broadcast 192.168.2.255
        inet6 2003:d2:5f03:ed12:bc03:daea:5092:6f43  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::c673:bb3b:592f:4309  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:30:d6:07  txqueuelen 1000  (Ethernet)
        RX packets 122716  bytes 111967403 (106.7 MiB)
        RX errors 0  dropped 2  overruns 0  frame 0
        TX packets 74286  bytes 40928657 (39.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


ethpi1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::222:82ff:feff:fe01  prefixlen 64  scopeid 0x20<link>
        ether 00:22:82:ff:fe:01  txqueuelen 1000  (Ethernet)
        RX packets 377  bytes 14292 (13.9 KiB)
        RX errors 2  dropped 0  overruns 0  frame 0
        TX packets 139  bytes 17426 (17.0 KiB)
        TX errors 300  dropped 0 overruns 0  carrier 0  collisions 0


ethpi2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::222:82ff:feff:fe02  prefixlen 64  scopeid 0x20<link>
        ether 00:22:82:ff:fe:02  txqueuelen 1000  (Ethernet)
        RX packets 57  bytes 5476 (5.3 KiB)
        RX errors 1  dropped 0  overruns 0  frame 0
        TX packets 404  bytes 21738 (21.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


ethpi3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::222:82ff:feff:fe03  prefixlen 64  scopeid 0x20<link>
        ether 00:22:82:ff:fe:03  txqueuelen 1000  (Ethernet)
        RX packets 58  bytes 5504 (5.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 369  bytes 16802 (16.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Lokale Schleife)
        RX packets 17  bytes 836 (836.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 17  bytes 836 (836.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:65:83:52  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

how i can control the Zeros over SSH?

[Justiinfighter]

lsusb -t gives me: 

/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M

    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M

        |__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/3p, 480M

            |__ Port 1: Dev 4, If 0, Class=Vendor Specific Class, Driver=lan78xx, 480M

            |__ Port 2: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M

                |__ Port 2: Dev 10, If 2, Class=Communications, Driver=cdc_acm, 480M

                |__ Port 2: Dev 10, If 0, Class=Communications, Driver=cdc_ether, 480M

                |__ Port 2: Dev 10, If 3, Class=CDC Data, Driver=cdc_acm, 480M

                |__ Port 2: Dev 10, If 1, Class=CDC Data, Driver=cdc_ether, 480M

                |__ Port 3: Dev 8, If 0, Class=Communications, Driver=cdc_ether, 480M

                |__ Port 3: Dev 8, If 1, Class=CDC Data, Driver=cdc_ether, 480M

                |__ Port 3: Dev 8, If 2, Class=Communications, Driver=cdc_acm, 480M

                |__ Port 3: Dev 8, If 3, Class=CDC Data, Driver=cdc_acm, 480M

                |__ Port 4: Dev 7, If 3, Class=CDC Data, Driver=cdc_acm, 480M

                |__ Port 4: Dev 7, If 1, Class=CDC Data, Driver=cdc_ether, 480M

                |__ Port 4: Dev 7, If 2, Class=Communications, Driver=cdc_acm, 480M

                |__ Port 4: Dev 7, If 0, Class=Communications, Driver=cdc_ether, 480M

[Chris Burton]

Hi, 

how i can control the Zeros over SSH?

From the controller you should be able to SSH to them with "ssh p...@p1.local" or the IP address "ssh p...@172.19.181.1".

You can also use the non-NAT image on the Pi 3b+ too now (I've just updated the website to remove the warning).

Chris.

[Justiinfighter]

Thanks! It worked from the Controller! 

[Justiinfighter]

Now with the not NAT-Image i cant access to the Zero's from the Controller.

ifconfig output is: 

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.2.133  netmask 255.255.255.0  broadcast 192.168.2.255

        inet6 fe80::ba27:ebff:fe30:d607  prefixlen 64  scopeid 0x20<link>

        inet6 2003:d2:5f03:ed12:41ed:1110:9c06:3491  prefixlen 64  scopeid 0x0<global>

        ether b8:27:eb:30:d6:07  txqueuelen 1000  (Ethernet)

        RX packets 9033  bytes 513172 (501.1 KiB)

        RX errors 0  dropped 103  overruns 0  frame 0

        TX packets 339  bytes 42452 (41.4 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        ether b8:27:eb:30:d6:07  txqueuelen 1000  (Ethernet)

        RX packets 9462  bytes 810671 (791.6 KiB)

        RX errors 0  dropped 97  overruns 0  frame 0

        TX packets 759  bytes 91319 (89.1 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ethpi1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet6 fe80::222:82ff:feff:fe01  prefixlen 64  scopeid 0x20<link>

        ether 00:22:82:ff:fe:01  txqueuelen 1000  (Ethernet)

        RX packets 91  bytes 9239 (9.0 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 6693  bytes 440128 (429.8 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ethpi2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet6 fe80::222:82ff:feff:fe02  prefixlen 64  scopeid 0x20<link>

        ether 00:22:82:ff:fe:02  txqueuelen 1000  (Ethernet)

        RX packets 90  bytes 8959 (8.7 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 6659  bytes 435600 (425.3 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ethpi3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet6 fe80::222:82ff:feff:fe03  prefixlen 64  scopeid 0x20<link>

        ether 00:22:82:ff:fe:03  txqueuelen 1000  (Ethernet)

        RX packets 89  bytes 8993 (8.7 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 6645  bytes 433487 (423.3 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::1  prefixlen 128  scopeid 0x10<host>

        loop  txqueuelen 1000  (Lokale Schleife)

        RX packets 25  bytes 1148 (1.1 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 25  bytes 1148 (1.1 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

        ether b8:27:eb:65:83:52  txqueuelen 1000  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lsusb -t output:

/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M

    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M

        |__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/3p, 480M

            |__ Port 1: Dev 5, If 0, Class=Vendor Specific Class, Driver=lan78xx, 480M

            |__ Port 2: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M

                |__ Port 2: Dev 12, If 2, Class=Communications, Driver=cdc_acm, 480M

                |__ Port 2: Dev 12, If 0, Class=Communications, Driver=cdc_ether, 480M

                |__ Port 2: Dev 12, If 3, Class=CDC Data, Driver=cdc_acm, 480M

                |__ Port 2: Dev 12, If 1, Class=CDC Data, Driver=cdc_ether, 480M

                |__ Port 3: Dev 11, If 0, Class=Communications, Driver=cdc_ether, 480M

                |__ Port 3: Dev 11, If 1, Class=CDC Data, Driver=cdc_ether, 480M

                |__ Port 3: Dev 11, If 2, Class=Communications, Driver=cdc_acm, 480M

                |__ Port 3: Dev 11, If 3, Class=CDC Data, Driver=cdc_acm, 480M

                |__ Port 4: Dev 10, If 3, Class=CDC Data, Driver=cdc_acm, 480M

                |__ Port 4: Dev 10, If 1, Class=CDC Data, Driver=cdc_ether, 480M

                |__ Port 4: Dev 10, If 2, Class=Communications, Driver=cdc_acm, 480M

                |__ Port 4: Dev 10, If 0, Class=Communications, Driver=cdc_ether, 480M

brctl output: 

bridge name     bridge id               STP enabled     interfaces

br0             8000.b827eb30d607       no              eth0

                                                        ethpi1

                                                        ethpi2

                                                        ethpi3

Where is the Fail?

[dave r]

Hi Justin,

The controller side ethpiN interfaces don't show the client side addresses.

I'm using the same hardware (B3+) and ZeroW, and I can ssh to the USB based IP addresses of the ZeroW's:

    172.19.181.1      and  .2      and  .3      and  .4

pi@controller:~ $ ip addr show dev br0

3: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000

    link/ether b8:27:eb:84:35:5e brd ff:ff:ff:ff:ff:ff

    inet 172.19.181.254/24 brd 172.19.181.255 scope global br0

       valid_lft forever preferred_lft forever

    inet6 fe80::c4f9:fc4b:8af8:d18/64 scope link 

       valid_lft forever preferred_lft forever

pi@controller:~ $ ssh p...@172.19.181.1

The authenticity of host '172.19.181.1 (172.19.181.1)' can't be established.

ECDSA key fingerprint is SHA256:n4tNNmjmaPATUczO5H0w/csAGidic8wQca5mq07RBOw.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added '172.19.181.1' (ECDSA) to the list of known hosts.

p...@172.19.181.1's password: 

Linux p1 4.14.52+ #1123 Wed Jun 27 17:05:32 BST 2018 armv6l

The programs included with the Debian GNU/Linux system are free software;

the exact distribution terms for each program are described in the

individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent

permitted by applicable law.

Last login: Fri Aug  3 07:19:32 2018 from 10.0.1.31

pi@p1:~ $ 

HTH

Dave.

[Chris Burton]

Hi, 

 

Now with the not NAT-Image i cant access to the Zero's from the Controller.

Where is the Fail?

This all looks OK, how are you trying to access them? 

When using the standard (non-NAT) controller image the Pi Zero and Controller get an IP address from the DHCP server on the local Ethernet network.

You should still be able to access them from the controller using "ssh p...@p1.local", etc. (or using the IP address your DHCP server assigns them - not the 172.19.181.x IP).

Chris.

[Justiinfighter]

I only get this:

pi@controller:~ $ ssh p...@p1.local

ssh: connect to host p1.local port 22: Connection timed out

pi@controller:~ $

With a simple Pingtest from the Controller i get:

PING p1.speedport.ip (192.168.2.134) 56(84) bytes of data.

From controller (192.168.2.133) icmp_seq=1 Destination Host Unreachable

From controller (192.168.2.133) icmp_seq=2 Destination Host Unreachable

From controller (192.168.2.133) icmp_seq=3 Destination Host Unreachable

with a local ip-research i find the Zero's with the 172.19.181.x Address but i cant get any access on them.

Hi,  

[dave r]

@Justin, try:

ssh p...@172.19.181.1

[Chris Burton]

Hi, 

with a local ip-research i find the Zero's with the 172.19.181.x Address but i cant get any access on them.

So just to check you're now using the non-NAT controller image, connecting the controller to a network with a DHCP server via Ethernet?

If so I'd advise shutting everything down, making sure the Ethernet cable is plugged into the Controller Pi OK, boot up the controller and check it gets an IP from the DHCP server on br0.

Then power on the Pi Zeros and wait a minute or so for them to boot. Check on the controller you can see the ethpiX interfaces (they shouldn't have IPs) and that "sudo brctl show" shows eth0 and the ethpiX interfaces are all in br0. 

If the above looks OK and you're unable to "ping p1.local" from the controller I'd normally advise trying to log into the Pi Zero through serial but currently this results in a kernel panic on my test setup here (you should normally be able to run "minicom p1" as the "pi" user, press enter and wait a few seconds for the login prompt but I'm seeing a kernel error and dts/rts error - if you try it please let me know if it works and the kernel version "uname -a").

If the above doesn't work or you want to login over the network you can temporarily add an IP to br0 with "ip addr add 172.19.181.254/24 dev br0" and you should then be able to ping/ssh into the Pi Zeros on 172.19.181.1/2/etc.

Once logged into the Pi Zero running "ifconfig" should show an IP addresses assigned to "usb0" (and none assigned to wlan0 if it exists) - if there's a 172.19.181.x address on usb0 then it hasn't got an IP from your DHCP server and has fallen back to that IP. If this is the case you may need to setup a static IP (from the range used on your local network with the routers IP as the gateway) on each Pi Zero "interface usb0" ( https://www.raspberrypi.org/learning/networking-lessons/rpi-static-ip-address/ ).

Chris.

[Justiinfighter]

If the above looks OK and you're unable to "ping p1.local" from the controller I'd normally advise trying to log into the Pi Zero through serial but currently this results in a kernel panic on my test setup here (you should normally be able to run "minicom p1" as the "pi" user, press enter and wait a few seconds for the login prompt but I'm seeing a kernel error and dts/rts error - if you try it please let me know if it works and the kernel version "uname -a").

minicom pX works!

Kernelversion Controller: Linux controller 4.14.52-v7+ #1123 SMP Wed Jun 27 17:35:49 BST 2018 armv7l GNU/Linux

Kernelversion Zero W: Linux p1 4.14.52+ #1123 Wed Jun 27 17:05:32 BST 2018 armv6l GNU/Linux

[Florent]

f the above looks OK and you're unable to "ping p1.local" from the controller I'd normally advise trying to log into the Pi Zero through serial but currently this results in a kernel panic on my test setup here (you should normally be able to run "minicom p1" as the "pi" user, press enter and wait a few seconds for the login prompt but I'm seeing a kernel error and dts/rts error - if you try it please let me know if it works and the kernel version "uname -a")....

Chris.

Hi Chris,

I'm testing the new images:

ClusterHAT-2018-06-27-lite-1-controller.img
ClusterHAT-2018-06-27-lite-1-p1.img

DHCP works on p1. minicom p1 also works for me:

pi@controller:~ $ uname -a

Linux controller 4.14.52-v7+ #1123 SMP Wed Jun 27 17:35:49 BST 2018 armv7l GNU/Linux

pi@controller:~ $ cat /sys/firmware/devicetree/base/model
Raspberry Pi 3 Model B Rev 1.2
pi@controller:~ $ minicom p1

...

pi@p1:~$ cat /sys/firmware/devicetree/base/model
Raspberry Pi Zero Rev 1.3
pi@p1:~$ uname -a

Linux p1 4.14.52+ #1123 Wed Jun 27 17:05:32 BST 2018 armv6l GNU/Linux

pi@p1:~$