On Jan 14, 2021, at 5:59 PM, Kok-Yong Tan wrote:
> The wireshark-chmodbpf script stops at /dev/bpf1.
How do you know that it stops at /dev/bpf1?
The *messages* stop at /dev/bpf1, but those are *not* progress messages, those
are error messages from the shell.
The script does *not* print a
On Jan 14, 2021, at 5:43 PM, Gerald Combs wrote:
> I can replicate the "Resource busy" message here by running Wireshark,
> leaving the welcome screen up and attempting to read from /dev/bpf0:
>
>
> $ read -n 0 < /dev/bpf0 > /dev/null 2>&1
> bash: /dev/bpf0: Resource busy
>
>
>
The wireshark-chmodbpf script stops at /dev/bpf1.
However, there appears to be /dev/bpf0 through /dev/bpf10 in existence when I
do a “ls -lu /dev/bpf*” but nothing beyond bpf10.
crw-r- 1 root access_bpf 23, 0 Jan 14 16:57 /dev/bpf0
crw-r- 1 root access_bpf 23, 1 Jan 14 16:57
On 1/14/21 5:43 PM, Gerald Combs wrote:
Does MacPorts wireshark-chmodbpf the script create /dev/bpf up to
/dev/bpf255, or does it stop at /dev/bpf1?
That should be "Does the MacPorts wireshark-chmodbpf script" ...
___
Does MacPorts wireshark-chmodbpf the script create /dev/bpf up to
/dev/bpf255, or does it stop at /dev/bpf1?
The script appears to be
https://github.com/macports/macports-ports/blob/master/net/wireshark-chmodbpf/files/patch-wireshark-chmodbpf.diff
which in turn appears to be adapted from the
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
chgrp…” and “sudo chmod…” Unix commands used to work fine. Now it’s not.
> On 14 Jan, 2021, at 09:48 , Jaap Keuter wrote:
>
> Hi,
>
> It would
Hi,
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 wrote:
>
> sudo wireshark-chmodbpf
> /opt/local/sbin/wireshark-chmodbpf: line 35: /dev/bpf0: Resource busy
> /opt/local/sbin/wireshark-chmodbpf:
