the desired
> /dev/bpf devices. If it does, then that's definitely a bug.
>
> On 1/14/21 3:03 PM, Kok-Yong Tan wrote:
>> It’s a MacBook Pro running macOS 10.14.6. I just upgraded Wireshark3 by
>> rebuilding it using MacPorts. Previously, just manually entering the “sudo
&
> It would probably help if you listed what your system is and what you were
> doing before.
>
> Thanks,
> Jaap
>
>
>> On 14 Jan 2021, at 01:18, Kok-Yong Tan > <mailto:k...@realityartisans.com>> wrote:
>>
>> sudo wireshark-chmodbpf
>>
sudo wireshark-chmodbpf
/opt/local/sbin/wireshark-chmodbpf: line 35: /dev/bpf0: Resource busy
/opt/local/sbin/wireshark-chmodbpf: line 35: /dev/bpf1: Resource busy
Does anybody know how to fix the above?
signature.asc
Description: Message signed with OpenPGP
If you're filtering out everything except connections to the SMTP
port but no one's connecting to an SMTP port in the meantime, then
might it not be correct that nothing's showing up? If you want to
see if it's working while the packet capture is going on, why not try
to send a couple of
