local addresses works in Windows 10 but not LM 20.1

[ieee488]

I have a clean installation of Linux Mint 20.1 on my Dell desktop PC.

I have have two Raspberry Pi devices that have been configured and shows up as USB Ethernet/RNDIS Gadget in Windows 10.


I can ping both in Windows 10 using local addresses.

.
full size screen capture https://imgur.com/uZTlvvT

It looks like Windows 10 is using IPV6.

In Linux Mint 20.1, the devices show up, but ...

Code: Select all

user1@Dell-JLLK732:~$ ip address list
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: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether b0:83:fe:79:13:ca brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.118/24 brd 192.168.0.255 scope global dynamic noprefixroute enp2s0
       valid_lft 6782sec preferred_lft 6782sec
    inet6 2601:84:8900:51d:29dd:cc95:b1f8:6000/64 scope global temporary dynamic 
       valid_lft 340996sec preferred_lft 85917sec
    inet6 2601:84:8900:51d:68bb:8b1b:6b57:cf4f/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 340996sec preferred_lft 340996sec
    inet6 fe80::458f:43db:9d20:adec/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether ce:31:c8:5d:d3:f1 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::6cb3:c963:3db8:50ed/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
4: enx06000000000a: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 06:00:00:00:00:0a brd ff:ff:ff:ff:ff:ff
    inet6 fe80::4ccd:a037:cce7:41e6/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

I can only ping the device usb0 which has the name pi0a .

Code: Select all

user1@Dell-JLLK732:~$ ping -c 3 pi0a.local
PING pi0a.local (169.254.132.238) 56(84) bytes of data.
64 bytes from pi0a.local (169.254.132.238): icmp_seq=1 ttl=64 time=0.376 ms
64 bytes from pi0a.local (169.254.132.238): icmp_seq=2 ttl=64 time=0.441 ms
64 bytes from pi0a.local (169.254.132.238): icmp_seq=3 ttl=64 time=0.436 ms

--- pi0a.local ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2034ms
rtt min/avg/max/mdev = 0.376/0.417/0.441/0.029 ms

I get error when I try to ping enx06000000000a which has the name pi0b .

Code: Select all

user1@Dell-JLLK732:~$ ping -c 3 pi0b.local
ping: pi0b.local: Name or service not known

What do I need to change so I can use the local addresses pi0a.local and pi0b.local ?

It worked in Windows 10 as soon as I installed Apple's Bonjour software.

.

[SMG]

It worked in Windows 10 as soon as I installed Apple's Bonjour software.

Because it did not work in Windows until you added the Bonjour software, I did a search on Bonjour for Linux. I found this Bonjour (Zeroconf) Networking for Windows and Linux. Under "Linux (including Raspberry Pi):" iit mentions the avahi-daemon which I've seen in many Mint logs so I know it's there. (It must be there since you were able to see both pi.)

It indicates, "Once installed, the system can be contacted from other computers at hostname.local, where hostname is either the default (raspberrypi) or an alternate name assigned in the Advanced menu of raspi-config."

You indicated both devices show up in Mint, but you only got a response from one device.

I noticed in the output, where you indicated the devices were seen, one had a state of UNKNOWN while the other was UP. Yet the one for which you did not get a response was the one which was listed as UP. It made me wonder if somehow the states of the two devices might be changing and you happened to ping the one while it was in UNKNOWN state?

[ieee488]

I plug in one device at a time.

I ping pi0a.local, it is the only device and is usb0.
Then I plug in the second device and wait about 1 minute.
I ping pi0b.local. And I get

Code: Select all

PING pi0b.local (169.254.52.73) 56(84) bytes of data.
From Dell-JLLK732.local (169.254.248.38) icmp_seq=1 Destination Host Unreachable
From Dell-JLLK732.local (169.254.248.38) icmp_seq=2 Destination Host Unreachable
From Dell-JLLK732.local (169.254.248.38) icmp_seq=3 Destination Host Unreachable
From Dell-JLLK732.local (169.254.248.38) icmp_seq=4 Destination Host Unreachable
From Dell-JLLK732.local (169.254.248.38) icmp_seq=5 Destination Host Unreachable

Then, I did something I did not do before.
I remove the device #1 pi0a.
I ping pi0b.local and it works.

Code: Select all

PING pi0b.local (169.254.52.73) 56(84) bytes of data.
64 bytes from pi0b.local (169.254.52.73): icmp_seq=1 ttl=64 time=0.953 ms
64 bytes from pi0b.local (169.254.52.73): icmp_seq=2 ttl=64 time=0.433 ms
64 bytes from pi0b.local (169.254.52.73): icmp_seq=3 ttl=64 time=0.528 ms

I thought Bonjour can work with multiple devices.
It does in Windows 10.

[SMG]

I ping pi0a.local, it is the only device and is usb0.
Then I plug in the second device and wait about 1 minute.
I ping pi0b.local. And I get

Code: Select all

PING pi0b.local (169.254.52.73) 56(84) bytes of data.
From Dell-JLLK732.local (169.254.248.38) icmp_seq=1 Destination Host Unreachable
From Dell-JLLK732.local (169.254.248.38) icmp_seq=2 Destination Host Unreachable
From Dell-JLLK732.local (169.254.248.38) icmp_seq=3 Destination Host Unreachable
From Dell-JLLK732.local (169.254.248.38) icmp_seq=4 Destination Host Unreachable
From Dell-JLLK732.local (169.254.248.38) icmp_seq=5 Destination Host Unreachable

Which is different than what you got the first time:

I get error when I try to ping enx06000000000a which has the name pi0b .

Code: Select all

user1@Dell-JLLK732:~$ ping -c 3 pi0b.local
ping: pi0b.local: Name or service not known

In the first case the message said the name/service was not known, therefore it could not find something unknown. But in the second case it considered it unreachable which means it knew about it, but could not reach it? Maybe somehow this is just a timing issue?

I did some searching and didn't really find an answer, but here is Ubuntu man page for avahi-daemon (focal). That description references avahi and nss-mdns. I found more info about both of them, Welcome to Avahi and GitHub description of nss-mdns.