On Sun, Apr 27, 2025 at 04:28:48PM -0400, Lee wrote:
> On Sun, Apr 27, 2025 at 3:33 PM wrote:
> >
> > Hi,
> >
> > Here are the output of the cmnds that tomas suggested.
>
> ... with all the good stuff elided
Sad, but True
> > 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.
>
The good test again, now in two parts.
With minor changes and additional information.
Part one:
sudo apt install tshark
Part two:
sudo tshark -f 'port 5353 or icmp or arp' -N dnt &
ping -c 4 whatever.local
kill %1
Part one installs a network sniffer, it diagnostic software for
computer networking challenges, it shows what happens on the wire.
(On wireless network, it shows what happens in the ether.)
Part two is the interest part. It is "the intended ping" that
stops after a count of 4 ping attempts. Before the ping is start,
is `tshark` started in the background. It watches all network traffic
but the filter makes it showing only mDNS, ping related packets
and Address Resolution Protocol packages. The `kill %1` will stop
the first background job, most likely the tshark process.
Please be warned that there will much output on the terminal, it will
be hard to type the `ping -c 4 whatever.local` and `kill %1`.
Shared the screen content with the mailinglist.
Groeten
Geert Stappers
<screen_content from="my test" test="ping -c 4 alpaca">
stappers@paddy:~
$ sudo tshark -f 'port 53 or icmp or arp' -N dnt &
[1] 2667205
stappers@paddy:~
$ Running as user "root" and group "root". This could be dangerous.
Capturing on 'wlan0'
1 0.000000000 48:d2:24:a5:cd:5e → 00:b0:d0:ed:73:57 ARP 42 Who has
172.24.0.10? Tell 172.24.0.36
2 0.002740520 00:b0:d0:ed:73:57 → 48:d2:24:a5:cd:5e ARP 60 172.24.0.10 is
at 00:b0:d0:ed:73:57
3 0.235064745 00:b0:d0:ed:73:57 → 48:d2:24:a5:cd:5e ARP 60 Who has
172.24.0.36? Tell 172.24.0.9
4 0.235082414 48:d2:24:a5:cd:5e → 00:b0:d0:ed:73:57 ARP 42 172.24.0.36 is
at 48:d2:24:a5:cd:5e
5 2.563991678 48:d2:24:a5:cd:5e → 00:b0:d0:ed:73:57 ARP 42 Who has
172.24.0.9? Tell 172.24.0.36
6 2.566194507 00:b0:d0:ed:73:57 → 48:d2:24:a5:cd:5e ARP 60 172.24.0.9 is at
00:b0:d0:ed:73:57
ping -c 7 12.142650250 24:65:11:a9:b5:43 → 48:d2:24:a5:cd:5e ARP 60 Who has
172.24.0.36? Tell 172.24.0.1
8 12.142666844 48:d2:24:a5:cd:5e → 24:65:11:a9:b5:43 ARP 42 172.24.0.36 is
at 48:d2:24:a5:cd:5e
4 alpaca
PING alpaca.gpm.stappers.nl (172.24.0.9) 56(84) bytes of data.
64 bytes from alpaca.gpm.stappers.nl (172.24.0.9): icmp_seq=1 ttl=64 time=1.30
ms
9 30.264172394 172.24.0.36 → 172.24.0.10 DNS 93 Standard query 0xef0f A
alpaca.gpm.stappers.nl OPT
10 30.265797294 172.24.0.10 → 172.24.0.36 DNS 109 Standard query response
0xef0f A alpaca.gpm.stappers.nl A 172.24.0.9 OPT
11 30.266161962 172.24.0.36 → alpaca.gpm.stappers.nl ICMP 98 Echo (ping)
request id=0x0002, seq=1/256, ttl=64
12 30.267437559 alpaca.gpm.stappers.nl → 172.24.0.36 ICMP 98 Echo (ping)
reply id=0x0002, seq=1/256, ttl=64 (request in 11)
13 30.268114471 172.24.0.36 → 172.24.0.10 DNS 94 Standard query 0x66be PTR
9.0.24.172.in-addr.arpa OPT
14 30.269635163 172.24.0.10 → 172.24.0.36 DNS 130 Standard query response
0x66be PTR 9.0.24.172.in-addr.arpa PTR alpaca.gpm.stappers.nl OPT
64 bytes from alpaca.local (172.24.0.9): icmp_seq=2 ttl=64 time=4.53 ms
15 31.268062754 172.24.0.36 → alpaca.gpm.stappers.nl ICMP 98 Echo (ping)
request id=0x0002, seq=2/512, ttl=64
16 31.272567646 alpaca.gpm.stappers.nl → 172.24.0.36 ICMP 98 Echo (ping)
reply id=0x0002, seq=2/512, ttl=64 (request in 15)
17 31.273216718 172.24.0.36 → 172.24.0.10 DNS 94 Standard query 0x66f7 PTR
9.0.24.172.in-addr.arpa OPT
18 31.275600004 172.24.0.10 → 172.24.0.36 DNS 130 Standard query response
0x66f7 PTR 9.0.24.172.in-addr.arpa PTR alpaca.gpm.stappers.nl OPT
64 bytes from alpaca.local (172.24.0.9): icmp_seq=3 ttl=64 time=4.10 ms
19 32.269495822 172.24.0.36 → alpaca.gpm.stappers.nl ICMP 98 Echo (ping)
request id=0x0002, seq=3/768, ttl=64
20 32.273577761 alpaca.gpm.stappers.nl → 172.24.0.36 ICMP 98 Echo (ping)
reply id=0x0002, seq=3/768, ttl=64 (request in 19)
21 32.274217422 172.24.0.36 → 172.24.0.10 DNS 94 Standard query 0x7301 PTR
9.0.24.172.in-addr.arpa OPT
22 32.324403220 172.24.0.10 → 172.24.0.36 DNS 130 Standard query response
0x7301 PTR 9.0.24.172.in-addr.arpa PTR alpaca.gpm.stappers.nl OPT
64 bytes from alpaca.local (172.24.0.9): icmp_seq=4 ttl=64 time=12.0 ms
--- alpaca.gpm.stappers.nl ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 1.296/5.469/11.952/3.943 ms
stappers@paddy:~
$ 23 33.270798738 172.24.0.36 → alpaca.gpm.stappers.nl ICMP 98 Echo (ping)
request id=0x0002, seq=4/1024, ttl=64
24 33.282729280 alpaca.gpm.stappers.nl → 172.24.0.36 ICMP 98 Echo (ping)
reply id=0x0002, seq=4/1024, ttl=64 (request in 23)
25 33.283371940 172.24.0.36 → 172.24.0.10 DNS 94 Standard query 0x912d PTR
9.0.24.172.in-addr.arpa OPT
26 33.286218342 172.24.0.10 → 172.24.0.36 DNS 130 Standard query response
0x912d PTR 9.0.24.172.in-addr.arpa PTR alpaca.gpm.stappers.nl OPT
27 35.327995754 48:d2:24:a5:cd:5e → 00:b0:d0:ed:73:57 ARP 42 Who has
172.24.0.10? Tell 172.24.0.36
28 35.332714625 00:b0:d0:ed:73:57 → 48:d2:24:a5:cd:5e ARP 60 172.24.0.10 is
at 00:b0:d0:ed:73:57
kil 29 37.375995228 48:d2:24:a5:cd:5e → 00:b0:d0:ed:73:57 ARP 42 Who has
172.24.0.9? Tell 172.24.0.36
30 37.381853603 00:b0:d0:ed:73:57 → 48:d2:24:a5:cd:5e ARP 60 172.24.0.9 is
at 00:b0:d0:ed:73:57
%1
bash: kil: opdracht niet gevonden
stappers@paddy:~
$ kill %1
stappers@paddy:~
$ 30 packets captured
[1]+ Klaar sudo tshark -f 'port 53 or icmp or arp' -N dnt
stappers@paddy:~
$
</screen_content>
Some dutch translated:
- opdracht niet gevonden: command not found
- Klaar: Ready
--
Silence is hard to parse
