Re: [Wireshark-dev] compilation hangs on Ubuntu
Submitted and validated by Guy Harris. All's fine now.
2018-05-14 20:29 GMT+02:00 Dario Lombardo :
> Can you submit a change on Gerrit for it?
>
> On Mon, May 14, 2018, 19:58 Eugène Adell wrote:
>
>>
>> Thanks all for the help and Darius for finding out this conflict with
>> ninja. Building with an ordinary user works.
>>
>>
>> By the way, I have another small request. Could you please change the
>> AUTHORS file to keep my personal address (my email at D2-SI didn't survive
>> after I left, and I contributed twice, the first time with D2-SI and later
>> under my personal address). Thanks.
>>
>> kind regards
>> Eugène
>>
>>
>>
>>
>> 2018-05-14 17:11 GMT+02:00 Darius Davis :
>>
>>> Hi Eugène,
>>>
>>>
>>>
>>> The strace log shows that your Ubuntu 16.04 system has the "ninja"
>>> package installed, which is "a privilege escalation detection and
>>> prevention system for GNU/Linux hosts" (https://packages.ubuntu.com/
>>> xenial/admin/ninja). It installs into /usr/sbin/ninja. Your build
>>> problem is caused by the presence of that "ninja" package on your system --
>>> and the fact that you appear to be building wireshark as "root".
>>>
>>>
>>>
>>> While running as "root", your PATH contains /usr/sbin, and that entry
>>> appears before /usr/bin, so instead of cmake launching the ninja build tool
>>> (/usr/bin/ninja), it launches the ninja privilege escalation detection tool
>>> (/usr/sbin/ninja), which busily monitors your /proc directory for evidence
>>> of system intrusion... but does not build Wireshark.
>>>
>>>
>>>
>>> 1900 access("/usr/sbin/ninja", R_OK) = 0
>>>
>>> 1900 stat("/usr/sbin/ninja", {st_mode=S_IFREG|0755, st_size=22872,
>>> ...}) = 0
>>>
>>> [...]
>>>
>>> 1901 execve("/usr/sbin/ninja", ["/usr/sbin/ninja", "--version"], [/* 22
>>> vars */]
>>>
>>>
>>>
>>> You should be able to resolve the issue by building Wireshark as a
>>> non-root user -- I don't think there is any need or reason to build as
>>> "root". As a regular user, your PATH should not contain /usr/sbin, and the
>>> ninja intrusion-detection program will be ignored. cmake should then find
>>> and launch the ninja build tool correctly.
>>>
>>>
>>>
>>> If you are not going to use the "ninja" privilege escalation detection
>>> program (for example, if it was installed by accident while you were
>>> looking for the "ninja-build" package), you can uninstall it by running
>>> "sudo apt-get remove ninja", and that would resolve the build problem too.
>>> (Regardless, I would really advise not building as "root" unless you have a
>>> very good reason to do so!)
>>>
>>>
>>>
>>> Cheers,
>>>
>>> --
>>>
>>> Darius
>>>
>>>
>>>
>>> *From: *Wireshark-dev on behalf
>>> of Eugène Adell
>>> *Reply-To: *Developer support list for Wireshark <
>>> wireshark-dev@wireshark.org>
>>> *Date: *Tuesday, 15 May 2018 at 12:25 am
>>> *To: *Developer support list for Wireshark
>>> *Subject: *Re: [Wireshark-dev] compilation hangs on Ubuntu
>>>
>>>
>>>
>>> It doesn't hang, it returns :
>>>
>>> 2;7;12
>>>
>>> As requested, the strace is attached.
>>>
>>>
>>>
>>>
>>>
>>> 2018-05-13 22:29 GMT+02:00 Jakub Zawadzki :
>>>
>>> Hello,
>>>
>>> W dniu 2018-05-13 17:15, Eugène Adell napisał(a):
>>>
>>> I'm facing a problem on my development server (Ubuntu 16.04 hosted on
>>> VMWARE) when trying to compile Wireshark. It was working with older
>>> versions (2.0 for example), but now it's like the compilation will never
>>> end.
>>> I installed/updated all the required packages, since version 2.6 seems
>>> quite different.
>>>
>>> I'm doing an strace -f -o to find out what could be wrong, but no clue.
>>> The
>>> strace log being too big, here is how it looks like :
>>>
>>> 1900 execve("/usr/bin/cmake", ["cmake", "-LH", "../wireshark"], [/*
>>> 22 vars */]) = 0
>>> [cut]
>>>
>>>
>>>
>>> thousands of lines such as :
>>>
>>> 1901 open("/proc/537/status", O_RDONLY) = -1 ENOENT (No such file or
>>> directory)
>>> 1901 open("/proc/538/status", O_RDONLY) = -1 ENOENT (No such file or
>>> directory)
>>> 1901 open("/proc/539/status", O_RDONLY) = -1 ENOENT (No such file or
>>> directory)
>>> 1901 open("/proc/540/status", O_RDONLY) = -1 ENOENT (No such file or
>>> directory)
>>> 1901 open("/proc/541/status", O_RDONLY) = -1 ENOENT (No such file or
>>> directory)
>>> 1901 open("/proc/542/status", O_RDONLY) = -1 ENOENT (No such file or
>>> directory)
>>> 1901 open("/proc/543/status", O_RDONLY) = -1 ENOENT (No such file or
>>> directory)
>>> 1901 open("/proc/544/status", O_RDONLY) = -1 ENOENT (No such file or
>>> directory)
>>>
>>>
>>> then thousands and thousands of lines such as the following, and it seems
>>> it will never end :
>>>
>>> 1901 open("/proc/882/status", O_RDONLY) = 3
>>> 1901 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
>>> 1901 read(3, "Name:\tvmhgfs-fuse\nUmask:\t\nSt"..., 1024) = 1024
>>> 1901 read(3, ",,,,"..., 1024) = 263
>>> 1901 read(3, "", 1024) = 0
>>> 1901 close(3)
Re: [Wireshark-dev] compilation hangs on Ubuntu
Can you submit a change on Gerrit for it?
On Mon, May 14, 2018, 19:58 Eugène Adell wrote:
>
> Thanks all for the help and Darius for finding out this conflict with
> ninja. Building with an ordinary user works.
>
>
> By the way, I have another small request. Could you please change the
> AUTHORS file to keep my personal address (my email at D2-SI didn't survive
> after I left, and I contributed twice, the first time with D2-SI and later
> under my personal address). Thanks.
>
> kind regards
> Eugène
>
>
>
>
> 2018-05-14 17:11 GMT+02:00 Darius Davis :
>
>> Hi Eugène,
>>
>>
>>
>> The strace log shows that your Ubuntu 16.04 system has the "ninja"
>> package installed, which is "a privilege escalation detection and
>> prevention system for GNU/Linux hosts" (
>> https://packages.ubuntu.com/xenial/admin/ninja). It installs into
>> /usr/sbin/ninja. Your build problem is caused by the presence of that
>> "ninja" package on your system -- and the fact that you appear to be
>> building wireshark as "root".
>>
>>
>>
>> While running as "root", your PATH contains /usr/sbin, and that entry
>> appears before /usr/bin, so instead of cmake launching the ninja build tool
>> (/usr/bin/ninja), it launches the ninja privilege escalation detection tool
>> (/usr/sbin/ninja), which busily monitors your /proc directory for evidence
>> of system intrusion... but does not build Wireshark.
>>
>>
>>
>> 1900 access("/usr/sbin/ninja", R_OK) = 0
>>
>> 1900 stat("/usr/sbin/ninja", {st_mode=S_IFREG|0755, st_size=22872, ...})
>> = 0
>>
>> [...]
>>
>> 1901 execve("/usr/sbin/ninja", ["/usr/sbin/ninja", "--version"], [/* 22
>> vars */]
>>
>>
>>
>> You should be able to resolve the issue by building Wireshark as a
>> non-root user -- I don't think there is any need or reason to build as
>> "root". As a regular user, your PATH should not contain /usr/sbin, and the
>> ninja intrusion-detection program will be ignored. cmake should then find
>> and launch the ninja build tool correctly.
>>
>>
>>
>> If you are not going to use the "ninja" privilege escalation detection
>> program (for example, if it was installed by accident while you were
>> looking for the "ninja-build" package), you can uninstall it by running
>> "sudo apt-get remove ninja", and that would resolve the build problem too.
>> (Regardless, I would really advise not building as "root" unless you have a
>> very good reason to do so!)
>>
>>
>>
>> Cheers,
>>
>> --
>>
>> Darius
>>
>>
>>
>> *From: *Wireshark-dev on behalf of
>> Eugène Adell
>> *Reply-To: *Developer support list for Wireshark <
>> wireshark-dev@wireshark.org>
>> *Date: *Tuesday, 15 May 2018 at 12:25 am
>> *To: *Developer support list for Wireshark
>> *Subject: *Re: [Wireshark-dev] compilation hangs on Ubuntu
>>
>>
>>
>> It doesn't hang, it returns :
>>
>> 2;7;12
>>
>> As requested, the strace is attached.
>>
>>
>>
>>
>>
>> 2018-05-13 22:29 GMT+02:00 Jakub Zawadzki :
>>
>> Hello,
>>
>> W dniu 2018-05-13 17:15, Eugène Adell napisał(a):
>>
>> I'm facing a problem on my development server (Ubuntu 16.04 hosted on
>> VMWARE) when trying to compile Wireshark. It was working with older
>> versions (2.0 for example), but now it's like the compilation will never
>> end.
>> I installed/updated all the required packages, since version 2.6 seems
>> quite different.
>>
>> I'm doing an strace -f -o to find out what could be wrong, but no clue.
>> The
>> strace log being too big, here is how it looks like :
>>
>> 1900 execve("/usr/bin/cmake", ["cmake", "-LH", "../wireshark"], [/*
>> 22 vars */]) = 0
>> [cut]
>>
>>
>>
>> thousands of lines such as :
>>
>> 1901 open("/proc/537/status", O_RDONLY) = -1 ENOENT (No such file or
>> directory)
>> 1901 open("/proc/538/status", O_RDONLY) = -1 ENOENT (No such file or
>> directory)
>> 1901 open("/proc/539/status", O_RDONLY) = -1 ENOENT (No such file or
>> directory)
>> 1901 open("/proc/540/status", O_RDONLY) = -1 ENOENT (No such file or
>> directory)
>> 1901 open("/proc/541/status", O_RDONLY) = -1 ENOENT (No such file or
>> directory)
>> 1901 open("/proc/542/status", O_RDONLY) = -1 ENOENT (No such file or
>> directory)
>> 1901 open("/proc/543/status", O_RDONLY) = -1 ENOENT (No such file or
>> directory)
>> 1901 open("/proc/544/status", O_RDONLY) = -1 ENOENT (No such file or
>> directory)
>>
>>
>> then thousands and thousands of lines such as the following, and it seems
>> it will never end :
>>
>> 1901 open("/proc/882/status", O_RDONLY) = 3
>> 1901 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
>> 1901 read(3, "Name:\tvmhgfs-fuse\nUmask:\t\nSt"..., 1024) = 1024
>> 1901 read(3, ",,,,"..., 1024) = 263
>> 1901 read(3, "", 1024) = 0
>> 1901 close(3) = 0
>> 1901 open("/proc/965/status", O_RDONLY) = 3
>> 1901 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
>> 1901 read(3, "Name:\tsystemd-logind\nUmask:\t0022"..., 1024) = 1024
>> 1901 read(3, "000,,,00"..., 1024) =
Re: [Wireshark-dev] compilation hangs on Ubuntu
Thanks all for the help and Darius for finding out this conflict with
ninja. Building with an ordinary user works.
By the way, I have another small request. Could you please change the
AUTHORS file to keep my personal address (my email at D2-SI didn't survive
after I left, and I contributed twice, the first time with D2-SI and later
under my personal address). Thanks.
kind regards
Eugène
2018-05-14 17:11 GMT+02:00 Darius Davis :
> Hi Eugène,
>
>
>
> The strace log shows that your Ubuntu 16.04 system has the "ninja" package
> installed, which is "a privilege escalation detection and prevention system
> for GNU/Linux hosts" (https://packages.ubuntu.com/xenial/admin/ninja).
> It installs into /usr/sbin/ninja. Your build problem is caused by the
> presence of that "ninja" package on your system -- and the fact that you
> appear to be building wireshark as "root".
>
>
>
> While running as "root", your PATH contains /usr/sbin, and that entry
> appears before /usr/bin, so instead of cmake launching the ninja build tool
> (/usr/bin/ninja), it launches the ninja privilege escalation detection tool
> (/usr/sbin/ninja), which busily monitors your /proc directory for evidence
> of system intrusion... but does not build Wireshark.
>
>
>
> 1900 access("/usr/sbin/ninja", R_OK) = 0
>
> 1900 stat("/usr/sbin/ninja", {st_mode=S_IFREG|0755, st_size=22872, ...})
> = 0
>
> [...]
>
> 1901 execve("/usr/sbin/ninja", ["/usr/sbin/ninja", "--version"], [/* 22
> vars */]
>
>
>
> You should be able to resolve the issue by building Wireshark as a
> non-root user -- I don't think there is any need or reason to build as
> "root". As a regular user, your PATH should not contain /usr/sbin, and the
> ninja intrusion-detection program will be ignored. cmake should then find
> and launch the ninja build tool correctly.
>
>
>
> If you are not going to use the "ninja" privilege escalation detection
> program (for example, if it was installed by accident while you were
> looking for the "ninja-build" package), you can uninstall it by running
> "sudo apt-get remove ninja", and that would resolve the build problem too.
> (Regardless, I would really advise not building as "root" unless you have a
> very good reason to do so!)
>
>
>
> Cheers,
>
> --
>
> Darius
>
>
>
> *From: *Wireshark-dev on behalf of
> Eugène Adell
> *Reply-To: *Developer support list for Wireshark <
> wireshark-dev@wireshark.org>
> *Date: *Tuesday, 15 May 2018 at 12:25 am
> *To: *Developer support list for Wireshark
> *Subject: *Re: [Wireshark-dev] compilation hangs on Ubuntu
>
>
>
> It doesn't hang, it returns :
>
> 2;7;12
>
> As requested, the strace is attached.
>
>
>
>
>
> 2018-05-13 22:29 GMT+02:00 Jakub Zawadzki :
>
> Hello,
>
> W dniu 2018-05-13 17:15, Eugène Adell napisał(a):
>
> I'm facing a problem on my development server (Ubuntu 16.04 hosted on
> VMWARE) when trying to compile Wireshark. It was working with older
> versions (2.0 for example), but now it's like the compilation will never
> end.
> I installed/updated all the required packages, since version 2.6 seems
> quite different.
>
> I'm doing an strace -f -o to find out what could be wrong, but no clue. The
> strace log being too big, here is how it looks like :
>
> 1900 execve("/usr/bin/cmake", ["cmake", "-LH", "../wireshark"], [/*
> 22 vars */]) = 0
> [cut]
>
>
>
> thousands of lines such as :
>
> 1901 open("/proc/537/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> 1901 open("/proc/538/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> 1901 open("/proc/539/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> 1901 open("/proc/540/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> 1901 open("/proc/541/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> 1901 open("/proc/542/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> 1901 open("/proc/543/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> 1901 open("/proc/544/status", O_RDONLY) = -1 ENOENT (No such file or
> directory)
>
>
> then thousands and thousands of lines such as the following, and it seems
> it will never end :
>
> 1901 open("/proc/882/status", O_RDONLY) = 3
> 1901 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
> 1901 read(3, "Name:\tvmhgfs-fuse\nUmask:\t\nSt"..., 1024) = 1024
> 1901 read(3, ",,,,"..., 1024) = 263
> 1901 read(3, "", 1024) = 0
> 1901 close(3) = 0
> 1901 open("/proc/965/status", O_RDONLY) = 3
> 1901 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
> 1901 read(3, "Name:\tsystemd-logind\nUmask:\t0022"..., 1024) = 1024
> 1901 read(3, "000,,,00"..., 1024) = 269
> 1901 read(3, "", 1024) = 0
> 1901 close(3) = 0
> 1901 open("/proc/968/status", O_RDONLY) = 3
> 1901 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
> 1901 read(3, "Name:\tdbus-daemon\nUmask:\t0022\nSt"...,
Re: [Wireshark-dev] compilation hangs on Ubuntu
Hi Eugène,
The strace log shows that your Ubuntu 16.04 system has the "ninja" package
installed, which is "a privilege escalation detection and prevention system for
GNU/Linux hosts" (https://packages.ubuntu.com/xenial/admin/ninja). It installs
into /usr/sbin/ninja. Your build problem is caused by the presence of that
"ninja" package on your system -- and the fact that you appear to be building
wireshark as "root".
While running as "root", your PATH contains /usr/sbin, and that entry appears
before /usr/bin, so instead of cmake launching the ninja build tool
(/usr/bin/ninja), it launches the ninja privilege escalation detection tool
(/usr/sbin/ninja), which busily monitors your /proc directory for evidence of
system intrusion... but does not build Wireshark.
1900 access("/usr/sbin/ninja", R_OK) = 0
1900 stat("/usr/sbin/ninja", {st_mode=S_IFREG|0755, st_size=22872, ...}) = 0
[...]
1901 execve("/usr/sbin/ninja", ["/usr/sbin/ninja", "--version"], [/* 22 vars
*/]
You should be able to resolve the issue by building Wireshark as a non-root
user -- I don't think there is any need or reason to build as "root". As a
regular user, your PATH should not contain /usr/sbin, and the ninja
intrusion-detection program will be ignored. cmake should then find and launch
the ninja build tool correctly.
If you are not going to use the "ninja" privilege escalation detection program
(for example, if it was installed by accident while you were looking for the
"ninja-build" package), you can uninstall it by running "sudo apt-get remove
ninja", and that would resolve the build problem too. (Regardless, I would
really advise not building as "root" unless you have a very good reason to do
so!)
Cheers,
--
Darius
From: Wireshark-dev on behalf of Eugène
Adell
Reply-To: Developer support list for Wireshark
Date: Tuesday, 15 May 2018 at 12:25 am
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] compilation hangs on Ubuntu
It doesn't hang, it returns :
2;7;12
As requested, the strace is attached.
2018-05-13 22:29 GMT+02:00 Jakub Zawadzki
mailto:darkjames...@darkjames.pl>>:
Hello,
W dniu 2018-05-13 17:15, Eugène Adell napisał(a):
I'm facing a problem on my development server (Ubuntu 16.04 hosted on
VMWARE) when trying to compile Wireshark. It was working with older
versions (2.0 for example), but now it's like the compilation will never
end.
I installed/updated all the required packages, since version 2.6 seems
quite different.
I'm doing an strace -f -o to find out what could be wrong, but no clue. The
strace log being too big, here is how it looks like :
1900 execve("/usr/bin/cmake", ["cmake", "-LH", "../wireshark"], [/*
22 vars */]) = 0
[cut]
thousands of lines such as :
1901 open("/proc/537/status", O_RDONLY) = -1 ENOENT (No such file or directory)
1901 open("/proc/538/status", O_RDONLY) = -1 ENOENT (No such file or directory)
1901 open("/proc/539/status", O_RDONLY) = -1 ENOENT (No such file or directory)
1901 open("/proc/540/status", O_RDONLY) = -1 ENOENT (No such file or directory)
1901 open("/proc/541/status", O_RDONLY) = -1 ENOENT (No such file or directory)
1901 open("/proc/542/status", O_RDONLY) = -1 ENOENT (No such file or directory)
1901 open("/proc/543/status", O_RDONLY) = -1 ENOENT (No such file or directory)
1901 open("/proc/544/status", O_RDONLY) = -1 ENOENT (No such file or directory)
then thousands and thousands of lines such as the following, and it seems
it will never end :
1901 open("/proc/882/status", O_RDONLY) = 3
1901 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
1901 read(3, "Name:\tvmhgfs-fuse\nUmask:\t\nSt"..., 1024) = 1024
1901 read(3, ",,,,"..., 1024) = 263
1901 read(3, "", 1024) = 0
1901 close(3) = 0
1901 open("/proc/965/status", O_RDONLY) = 3
1901 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
1901 read(3, "Name:\tsystemd-logind\nUmask:\t0022"..., 1024) = 1024
1901 read(3, "000,,,00"..., 1024) = 269
1901 read(3, "", 1024) = 0
1901 close(3) = 0
1901 open("/proc/968/status", O_RDONLY) = 3
1901 fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
1901 read(3, "Name:\tdbus-daemon\nUmask:\t0022\nSt"..., 1024) = 1024
1901 read(3, "00,,,,00"..., 1024) = 283
1901 read(3, "", 1024) = 0
1901 close(3) = 0
How can I resolve this ?
Not sure, but it seems that first subprocess (1901 == 1900 + 1) makes some
strange things.
Looking on my strace output of cmake -LH ../wireshark:
6410 execve("/usr/bin/cmake", ["cmake", "-LH", "../wireshark/"],
0x7ffe72092520 /* 32 vars */) = 0
(..)
6410 clone(child_stack=NULL,
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x7f7cde41ba50) = 6411
6411 execve("/usr/bin/python", ["/usr/bin/python", "-c", "import sys;
sys.stdout.write(';'.join([str(x)
Re: [Wireshark-dev] dumpcap broken on mac?
On Mon, May 14, 2018 at 03:09:39AM -0700, Guy Harris wrote: > On May 14, 2018, at 3:04 AM, Guy Harris wrote: > > > But what's XHC20? > > Oh, USB: > > https://lists.apple.com/archives/usb/2017/Jun/msg4.html I wanted to play with it after discovering it post-update but had too many other things going on and promptly forgot it again. > I guess I'll have to decide to trust High Sierra at some point and upgrade Yes, at least with only two non-Apple HW devices requiring drivers and almost no closed source software (except from Apple) it was an easy choice for me. Jörg -- Joerg Mayer We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] dumpcap broken on mac?
On Mon, May 14, 2018 at 03:04:06AM -0700, Guy Harris wrote: > On May 14, 2018, at 2:55 AM, Joerg Mayer wrote: > > jmayer@newegg:~/worktmp/wireshark/build/master/logs$ dumpcap -L > > dumpcap: Can't get list of interfaces: SIOCGIFMEDIA on XHC20 failed: > > Operation not supported by device > > Try the current libpcap master branch. To quote the most recent commit: Fixed. Many thanks! Jörg -- Joerg Mayer We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] dumpcap broken on mac?
On May 14, 2018, at 3:09 AM, Guy Harris wrote: > On May 14, 2018, at 3:04 AM, Guy Harris wrote: > >> But what's XHC20? > > Oh, USB: > > https://lists.apple.com/archives/usb/2017/Jun/msg4.html And pcap-bpf.c probably needs to ifconfig them up and down, just as we need to create and destroy the USB capture devices on FreeBSD: For example, if the device your interested in is connected to the XHCI controller XHC1@1400 then you would enable packet capture via "sudo ifconfig XHC20 up” and disable via “sudo ifconfig XHC20 down”. ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] dumpcap broken on mac?
On May 14, 2018, at 3:04 AM, Guy Harris wrote: > But what's XHC20? Oh, USB: https://lists.apple.com/archives/usb/2017/Jun/msg4.html I guess I'll have to decide to trust High Sierra at some point and upgrade ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] dumpcap broken on mac?
On May 14, 2018, at 2:55 AM, Joerg Mayer wrote: > since I recompiled libpcap and wireshark this weekend, capture doesn't work > any more on my Mac > (current macOS): > > jmayer@newegg:~/worktmp/wireshark/build/master/logs$ dumpcap -L > dumpcap: Can't get list of interfaces: SIOCGIFMEDIA on XHC20 failed: > Operation not supported by device Try the current libpcap master branch. To quote the most recent commit: UN*X - the OS family with at least 4 ways of saying "no can do" for an ioctl. Here's number 4 - ENODEV, in addition to EOPNOTSUPP and EINVAL and ENOTTY. But what's XHC20? ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] dumpcap broken on mac?
Hi, since I recompiled libpcap and wireshark this weekend, capture doesn't work any more on my Mac (current macOS): jmayer@newegg:~/worktmp/wireshark/build/master/logs$ dumpcap -L dumpcap: Can't get list of interfaces: SIOCGIFMEDIA on XHC20 failed: Operation not supported by device Anyone else hit by this? Ciao Jörg -- Joerg Mayer We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
