Arch Linux

Altriss

Member

Registered: 2022-06-05

Posts: 8

Trying to SSH into rbpi4 over USB Arch

Hi~

As the title says: I am trying to ssh over usb into my pi4
- I checked and according to rbpie forum 1pie4 can do it like pi0
- I did the setup of the pie, headless raspbian, ssh empty file, and edition of cmd and conf files
- I found this old solved case for pi0 on the arch forum https://bbs.archlinux.org/viewtopic.php?id=216968

Now, when I follow the described approach, at the last step, 6)  ssh -6 -o BindAddress=fe80::ccf3:3fff:3ff3:ccc1%enp0s20f0u12 pi@raspberrypi.local
I get as return ssh: Could not resolve hostname raspberrypi.local: No address associated with hostname

I checked that I did not have dhcp running at the time, actually I found out that it was not installed.
As specified in avahi wiki page I disabled systemd-resolved.service to avoid conflict with the mDNS

I am a bit running out of ideas.

The things that confuses me is that while my wifi is stable, the ethernet connection to the pi is dropped by the network manager after a while, so I am trying to find if the issue is not at this level. But as I searched around, I found discussion about potential conflicts of services, but when I check what's running systemctl status --no-pager I get the following tree which does not show other potentially conflicting services.

Any idea where I should search?

output of the systemctl status --no-pager command

Jobs: 0 queued
   Failed: 0 units
    Since: Sun 2022-06-05 08:15:45 CEST; 12min ago
   CGroup: /
           ├─init.scope
           │ └─1 /sbin/init
           ├─system.slice
           │ ├─NetworkManager.service
           │ │ └─392 /usr/bin/NetworkManager --no-daemon
           │ ├─acpid.service
           │ │ └─387 /usr/bin/acpid --foreground --netlink
           │ ├─bluetooth.service
           │ │ └─388 /usr/lib/bluetooth/bluetoothd
           │ ├─dbus.service
           │ │ └─389 /usr/bin/dbus-daemon --system --address=systemd: --nofork …
           │ ├─docker.service
           │ │ ├─573 /usr/bin/dockerd -H fd://
           │ │ └─581 containerd --config /var/run/docker/containerd/containerd.…
           │ ├─ntpd.service
           │ │ └─418 /usr/bin/ntpd -g -u ntp:ntp
           │ ├─polkit.service
           │ │ └─750 /usr/lib/polkit-1/polkitd --no-debug
           │ ├─rtkit-daemon.service
           │ │ └─746 /usr/lib/rtkit-daemon
           │ ├─slim.service
           │ │ └─427 /usr/lib/Xorg -nolisten tcp vt07 -auth /var/run/slim.auth
           │ ├─system-getty.slice
           │ │ └─getty@tty1.service
           │ │   └─415 /sbin/agetty -o "-p -- \\u" --noclear - linux
           │ ├─systemd-journald.service
           │ │ └─213 /usr/lib/systemd/systemd-journald
           │ ├─systemd-logind.service
           │ │ └─390 /usr/lib/systemd/systemd-logind
           │ ├─systemd-udevd.service
           │ │ └─271 /usr/lib/systemd/systemd-udevd
           │ ├─touchegg.service
           │ │ └─391 /usr/bin/touchegg --daemon
           │ ├─upower.service
           │ │ └─747 /usr/lib/upowerd
           │ └─wpa_supplicant.service
           │   └─435 /usr/bin/wpa_supplicant -u
           └─user.slice
             └─user-1000.slice
               ├─session-1.scope
               │ ├─ 417 /usr/bin/slim -nodaemon
               │ ├─ 736 fluxbox
               │ ├─ 741 wmbattery
               │ ├─ 742 nm-applet
               │ ├─ 938 /usr/bin/python /usr/bin/terminator
               │ ├─ 957 /bin/bash
               │ ├─ 961 /usr/lib/firefox/firefox
               │ ├─1052 /usr/lib/firefox/firefox -contentproc -childID 1 -isFor…
               │ ├─1115 /usr/lib/firefox/firefox -contentproc -childID 3 -isFor…
               │ ├─1181 /usr/lib/firefox/firefox -contentproc -childID 5 -isFor…
               │ ├─1296 /usr/lib/firefox/firefox -contentproc -parentBuildID 20…
               │ ├─1458 /usr/lib/firefox/firefox -contentproc -childID 10 -isFo…
               │ ├─1668 /usr/lib/firefox/firefox -contentproc -childID 12 -isFo…
               │ ├─2000 /usr/lib/firefox/firefox -contentproc -childID 17 -isFo…
               │ ├─2207 /usr/lib/firefox/firefox -contentproc -childID 18 -isFo…
               │ ├─2392 /usr/lib/firefox/firefox -contentproc -childID 19 -isFo…
               │ ├─2550 /usr/lib/firefox/firefox -contentproc -childID 20 -isFo…
               │ └─2630 systemctl status --no-pager
               └─user@1000.service
                 ├─app.slice
                 │ └─at-spi-dbus-bus.service
                 │   ├─793 /usr/lib/at-spi-bus-launcher
                 │   ├─799 /usr/bin/dbus-daemon --config-file=/usr/share/defaul…
                 │   └─809 /usr/lib/at-spi2-registryd --use-gnome-session
                 ├─init.scope
                 │ ├─728 /usr/lib/systemd/systemd --user
                 │ └─729 "(sd-pam)"
                 └─session.slice
                   ├─dbus.service
                   │ └─779 /usr/bin/dbus-daemon --session --address=systemd: --…
                   └─pulseaudio.service
                     ├─735 /usr/bin/pulseaudio --daemonize=no --log-target=jour…
                     └─815 /usr/lib/pulse/gsettings-helper

Last edited by Altriss (2022-06-05 12:32:35)

Altriss

Member

Registered: 2022-06-05

Posts: 8

Re: Trying to SSH into rbpi4 over USB Arch

Edit, the ethernet issue is not longer occuring, in the end a reboot solved this issue.
however, when I attempt this command
ssh -6 -o BindAddress=fe80::8cc2:c933:eaa0:b69c%enp0s20f0u2il pi@raspberrypi.local
(address obtained from ip addr, and number is from dmesg)

i still get that answer
ssh: Could not resolve hostname raspberrypi.local: No address associated with hostname

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,275

Re: Trying to SSH into rbpi4 over USB Arch

enp0s20f0u2il

the last 2 symbols of that device address look weird, are you sure it needs to end with 2 letters ( small india and small lima) ?

please post the content of /etc/nsswitch.conf and the output of

$ systemctl status avahi-daemon.service
$ ip link show
$ ip address show

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Altriss

Member

Registered: 2022-06-05

Posts: 8

Re: Trying to SSH into rbpi4 over USB Arch

Hi, thanks for your answer!

here is my nsswitch

cat /etc/nsswitch.conf 
# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files systemd
group: files [SUCCESS=merge] systemd
shadow: files systemd
gshadow: files systemd

publickey: files

hosts: mymachines resolve [!UNAVAIL=return] files myhostname dns
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files

$ systemctl status avahi-daemon.service

avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; disabled; vendor preset: disabled)
     Active: active (running) since Sun 2022-06-05 13:09:26 CEST; 13min ago
TriggeredBy: ● avahi-daemon.socket
   Main PID: 10766 (avahi-daemon)
     Status: "avahi-daemon 0.8 starting up."
      Tasks: 2 (limit: 9363)
     Memory: 1.6M
        CPU: 2.037s
     CGroup: /system.slice/avahi-daemon.service
             ├─10766 "avahi-daemon: running [Archguillaume.local]"
             └─10767 "avahi-daemon: chroot helper"

Jun 05 13:21:45 Archguillaume avahi-daemon[10766]: Interface enp0s20f0u2i1.IPv6 no longer relevant for mDNS.
Jun 05 13:21:45 Archguillaume avahi-daemon[10766]: Joining mDNS multicast group on interface enp0s20f0u2i1.IPv6 with address fe80::8cc2:c933:eaa0:b69c.
Jun 05 13:21:45 Archguillaume avahi-daemon[10766]: New relevant interface enp0s20f0u2i1.IPv6 for mDNS.
Jun 05 13:21:45 Archguillaume avahi-daemon[10766]: Registering new address record for fe80::8cc2:c933:eaa0:b69c on enp0s20f0u2i1.*.
Jun 05 13:22:30 Archguillaume avahi-daemon[10766]: Withdrawing address record for fe80::8cc2:c933:eaa0:b69c on enp0s20f0u2i1.
Jun 05 13:22:30 Archguillaume avahi-daemon[10766]: Leaving mDNS multicast group on interface enp0s20f0u2i1.IPv6 with address fe80::8cc2:c933:eaa0:b69c.
Jun 05 13:22:30 Archguillaume avahi-daemon[10766]: Interface enp0s20f0u2i1.IPv6 no longer relevant for mDNS.
Jun 05 13:22:30 Archguillaume avahi-daemon[10766]: Joining mDNS multicast group on interface enp0s20f0u2i1.IPv6 with address fe80::8cc2:c933:eaa0:b69c.
Jun 05 13:22:30 Archguillaume avahi-daemon[10766]: New relevant interface enp0s20f0u2i1.IPv6 for mDNS.
Jun 05 13:22:30 Archguillaume avahi-daemon[10766]: Registering new address record for fe80::8cc2:c933:eaa0:b69c on enp0s20f0u2i1.*.

$ ip link show

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s20f0u2i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether 22:79:55:86:fa:a5 brd ff:ff:ff:ff:ff:ff
3: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether a0:c5:89:7d:c9:72 brd ff:ff:ff:ff:ff:ff
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:31:fe:1f:16 brd ff:ff:ff:ff:ff:ff

$ ip address show

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp0s20f0u2i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 22:79:55:86:fa:a5 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::8cc2:c933:eaa0:b69c/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a0:c5:89:7d:c9:72 brd ff:ff:ff:ff:ff:ff
    inet 172.16.4.191/16 brd 172.16.255.255 scope global dynamic noprefixroute wlp1s0
       valid_lft 79944sec preferred_lft 79944sec
    inet6 fe80::6cc:9d81:1d3b:99a9/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:31:fe:1f:16 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

Last edited by Altriss (2022-06-05 11:30:16)

Altriss

Member

Registered: 2022-06-05

Posts: 8

Re: Trying to SSH into rbpi4 over USB Arch

enp0s20f0u2il

the last 2 symbols of that device address look weird, are you sure it needs to end with 2 letters ( small india and small lima) ?

Indeed it's a 1 not a l, I did a mistake there while posting. I am sorry for that.

Slithery

Administrator

From: Norfolk, UK

Registered: 2013-12-01

Posts: 5,776

Re: Trying to SSH into rbpi4 over USB Arch

Please edit your first post to use [⁣code] [/⁣code] tags around commands and their output...
https://wiki.archlinux.org/title/Genera … s_and_code

---

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,275

Re: Trying to SSH into rbpi4 over USB Arch

You need to change /etc/nsswitch.conf for avahi to resolve .local, see https://wiki.archlinux.org/title/Avahi# … resolution

Last edited by Lone_Wolf (2022-06-05 12:16:12)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

progandy

Member

Registered: 2012-05-17

Posts: 5,279

Re: Trying to SSH into rbpi4 over USB Arch

if you wish to use avahi instead of systemd-reolved, then change

hosts: mymachines resolve [!UNAVAIL=return] files myhostname dns

https://wiki.archlinux.org/title/Avahi# … resolution
Edit: ninja'd.

If you wanto to use systemd-resolved as well as avahi, you can do that. It is not required to disable it, only its MulticastDNS support has to be disabled.

Last edited by progandy (2022-06-05 12:19:53)

---

| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

Altriss

Member

Registered: 2022-06-05

Posts: 8

Re: Trying to SSH into rbpi4 over USB Arch

Please edit your first post to use [⁣code] [/⁣code] tags around commands and their output...
https://wiki.archlinux.org/title/Genera … s_and_code

done, sorry for the noob mistake

Altriss

Member

Registered: 2022-06-05

Posts: 8

Re: Trying to SSH into rbpi4 over USB Arch

You need to change /etc/nsswitch.conf for avahi to resolve .local, see https://wiki.archlinux.org/title/Avahi# … resolution

ok, thank you, I will search on this side.
I see a small paragraph about issue with local domain that looks like what I am encountering.
I will dig a bit and I will either come back to close or to ask another question.
Thanks a gain for your patience

Altriss

Member

Registered: 2022-06-05

Posts: 8

Re: Trying to SSH into rbpi4 over USB Arch

Hello everyone,

It took me some time to understand a bit all the resources, but it was all described in the wiki at the page shared by Progandy.
Also; it's just a side note, but imo the ssh over USB while being convenient, is less practical than using the wifi of the pi4 with a setup to ge directly the headless os to log in a local hotspot.
I leave that note here because I guess others might have similar troubles than me~

Thank you everyone, I I wish you all a great day!