Neither wireshark or nor tcpdump (AFAIK) can return the data in a form suitable
for use in a shell script (my need was (emphasis on “was”, I’ve already
re-worked my configuration to no longer need the lookup) get the current
address of example.local and then use it in the shell script).
In any
Wireshark works just fine on a Mac (I am using it right now) and yes, it is
a great tool. You also have the choice of using tcpdump in a terminal
window, if that's your preference. Personally I usually capture using
tcpdump and view later in Wireshark.
On Fri, 1 Jul 2022 at 12:01, Petr Menšík wro
Wireshark is a great tool with a nice GUI, which can record you traffic
on selected ports. Just use capture filter port 5353. But I am not
certain it works on Mac just as it does not Linux.
On 6/27/22 15:10, Larry Stone wrote:
Petr, you are going to have to tell me how to create an appropriate
Thanks. Submitted - #3428.
--
Larry Stone
lston...@stonejongleux.com
> On Jun 27, 2022, at 1:26 AM, Evan Hunt wrote:
>
> On Sun, Jun 26, 2022 at 10:00:08PM -0500, Larry Stone wrote:
>> I recently moved from 9.16 to 9.18 and just noticed that dig no longer
>> resolves mDNS queries.
>>
>> W
Greg, thanks. Exactly what I needed. Need to head out for a few hours but will
get on this later today.
--
Larry Stone
lston...@stonejongleux.com
> On Jun 27, 2022, at 8:18 AM, Greg Choules
> wrote:
>
> Hi Larry.
> sudo tcpdump -ni any -c 1000 -w .pcap port 5353
>
> For I usually inclu
Hi Larry.
sudo tcpdump -ni any -c 1000 -w .pcap port 5353
For I usually include the date, hostname and some other
meaningful stuff to help you remember what it was for in 6 months' time.
Whilst this is running, make some queries in another terminal window.
I hope this helps.
Cheers, Greg
On Mon
Petr, you are going to have to tell me how to create an appropriate PCAP file.
As most of this stuff works so well these days, it’s been years since I had to
do any sort of packet level analysis (moved on to other things professionally)
and what I knew of how to do that has long since been lost.
On 27. 06. 22 8:26, Evan Hunt wrote:
On Sun, Jun 26, 2022 at 10:00:08PM -0500, Larry Stone wrote:
I recently moved from 9.16 to 9.18 and just noticed that dig no longer
resolves mDNS queries.
With 9.16:
dig +short @224.0.0.251 -p 5353 hostname.local
192.168.0.82
With 9.18:
dig +short @224.0.0.
On Sun, Jun 26, 2022 at 10:00:08PM -0500, Larry Stone wrote:
> I recently moved from 9.16 to 9.18 and just noticed that dig no longer
> resolves mDNS queries.
>
> With 9.16:
> dig +short @224.0.0.251 -p 5353 hostname.local
> 192.168.0.82
>
> With 9.18:
> dig +short @224.0.0.251 -p 5353 hostname.l
I recently moved from 9.16 to 9.18 and just noticed that dig no longer resolves
mDNS queries.
With 9.16:
dig +short @224.0.0.251 -p 5353 hostname.local
192.168.0.82
With 9.18:
dig +short @224.0.0.251 -p 5353 hostname.local
;; connection timed out; no servers could be reached
I can’t find anythi
10 matches
Mail list logo
