On Mon, Apr 28, 2025 at 12:20 AM tomas wrote:
>
> On Sun, Apr 27, 2025 at 11:36:17PM +0200, Geert Stappers wrote:
> > On Sun, Apr 27, 2025 at 04:28:48PM -0400, Lee wrote:
> > > On Sun, Apr 27, 2025 at 3:33 PM wrote:
>
> [...]
>
> > > > Hope that helps.
> > >
> > > Not particularly.
> > >
> > > Try this:
> > >
> > > sudo apt install tshark
> > > sudo tshark -f 'port 5353' -c 4 -N dnt &
> > > ping -c 4 whatever.local
> > >
> > > At least for me, it shows the mdns requests being sent and the answers
> > > received.
> > >
<.. snip ..>
> While it is a good idea to have tshark, we already *know* that
> the OP's machine
>
> - is trying to resolve via mDNS
How do we know that? Has the OP sent you a private message showing
the mdns requests going out to the network?
If no then I would say we don't know if their machine is trying to do
mdns or not.
> - *that* part is failing.
I can believe that something is failing but at this point I don't
believe we can say exactly what is failing.
> ... because:
>
> - the interface link seems to be up and sees a connection
> - They said pinging by IP works
I'd still like to see a network trace showing mdns requests going out...
& if the OP doesn't want MAC addresses showing up in the mailing list
they can select 'Random' as the cloned mac address in network manager.
... or whatever you're using to set up the network most probably
allows you to set the mac address
For the OP:
your /etc/nsswitch.conf is probably OK if you haven't messed with it,
but it wouldn't hurt to check
$ grep 'hosts:' /etc/nsswitch.conf
hosts: files mdns4_minimal [NOTFOUND=return] dns
then make sure mdns requests are going out - you should get something like this
$ sudo tshark -f 'port 5353' -c 20 -N dnt &
[1] 6590
lee@an17 ~
$ Running as user "root" and group "root". This could be dangerous.
Capturing on 'wlp3s0'
** (tshark:6592) 10:06:51.056553 [Main MESSAGE] -- Capture started.
** (tshark:6592) 10:06:51.056647 [Main MESSAGE] -- File:
"/tmp/wireshark_wlp3s0JQKP52.pcapng"
ping pookie.local
PING pookie.local (192.168.8.148) 56(84) bytes of data.
64 bytes from 192.168.8.148 (192.168.8.148): icmp_seq=1 ttl=64 time=4.30 ms
1 0.000000000 fe80::b6e8:2f08:1ce8:621f → ff02::fb MDNS 92
Standard query 0x0000 A pookie.local, "QM" question
2 0.000079951 192.168.8.153 → 224.0.0.251 MDNS 72 Standard query
0x0000 A pookie.local, "QM" question
3 0.023286974 pookie.local → 224.0.0.251 MDNS 82 Standard query
response 0x0000 A, cache flush 192.168.8.148
64 bytes from 192.168.8.148 (192.168.8.148): icmp_seq=2 ttl=64 time=43.3 ms
64 bytes from 192.168.8.148 (192.168.8.148): icmp_seq=3 ttl=64 time=42.7 ms
64 bytes from 192.168.8.148 (192.168.8.148): icmp_seq=4 ttl=64 time=44.0 ms
64 bytes from 192.168.8.148 (192.168.8.148): icmp_seq=5 ttl=64 time=46.2 ms
64 bytes from 192.168.8.148 (192.168.8.148): icmp_seq=6 ttl=64 time=23.1 ms
^C
--- pookie.local ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5008ms
rtt min/avg/max/mdev = 4.296/33.927/46.243/15.348 ms
Regards,
Lee
